Agent DoorAgents are not one audience - open the right door to each.
Answer a short interview about which AI agents reach your product, then paste your robots.txt and anything you probed. Your browser sets a policy per agent class and surface, reads robots.txt token by token (ClaudeBot is not Claude-User), runs the reachability gate against your CDN preset and signup CAPTCHA, checks the agent-safe API basics, and ranks the rungs - measurement, docs, credentials, a CLI, MCP, the claim flow. Then the plan, and the rollout.
Try a sample:
1 The product, and which agents reach it free
2 Surfaces, the edge, risk and constraints free
3 robots.txt, probes and the API basics free
4 The matrix, the gate and the rungs free
What the page flags
The gates
Agent class by surface
robots.txt, token by token
The rungs
Probe results
Area by area
5 A robots.txt that states the matrix free
One group per policy, per vendor token. It states a preference only - put the same rules in your CDN, and keep the app behind login.
The run did not finish. Nothing was saved and what you entered is still here - press the button to try again.
The reply could not be read. Here it is as it came back:
NOT RUN YET
Caveats
Keep it handy:
Caveats
The page's check of this reply
7 Saved plans
How it works - and what is sourced
The matrix starts from the skill's defaults: docs open to every class, signup and the app closed to crawlers, browser agents verified rather than CAPTCHA-gated, coding agents and fleets through credentials of their own. robots.txt states a preference per token - ClaudeBot is Anthropic's training crawler, Claude-User fetches a page a person asked about - and some user-triggered fetchers may ignore it, so a deny needs the CDN. A user-agent is a claim; a vendor IP list or a verified signature is an identity.
The rungs follow the skill: measurement first as the baseline, then docs and credentials by default; a CLI moves up when shell agents fail at login; MCP survives only on shell-less clients; provision-then-claim is promoted when agents already create accounts; a hard date keeps only what ships inside it; money-moving operations put credentials above everything. Vendor tokens change - re-read each vendor's crawler page before you ship rules.