AI Crawler Access Matrix
Fetch any URL in parallel as ten AI crawlers and a default browser. See exactly which agents your site allows, blocks, redirects, challenges, or serves a different body to. Real HTTP fetches, real verdicts.
What each row means
- GPTBotblockedHTTP 403. The host is refusing this user-agent.
- ChatGPT-UserblockedHTTP 403. The host is refusing this user-agent.
- ClaudeBotblockedHTTP 403. The host is refusing this user-agent.
- Claude-UserblockedHTTP 403. The host is refusing this user-agent.
- PerplexityBotblockedHTTP 403. The host is refusing this user-agent.
- Google-ExtendedblockedHTTP 403. The host is refusing this user-agent.
- GooglebotallowedAllowed (2xx) and the body matches the browser baseline.
- BingbotallowedAllowed (2xx) and the body matches the browser baseline.
- CCBotblockedHTTP 403. The host is refusing this user-agent.
- BrowserallowedBaseline browser response, used as the comparison anchor.
Copyable summary for sharing with infra owners or filing an issue with your CDN.
AgentSpeed AI Crawler Access Matrix Target: https://openai.com Run: 2026-07-21T05:28:25.107Z Per-agent verdict: - GPTBot blocked status=403 sim=0.00 bytes=9978 - ChatGPT-User blocked status=403 sim=0.00 bytes=10085 - ClaudeBot blocked status=403 sim=0.00 bytes=9978 - Claude-User blocked status=403 sim=0.00 bytes=10000 - PerplexityBot blocked status=403 sim=0.00 bytes=10000 - Google-Extended blocked status=403 sim=0.00 bytes=9936 - Googlebot allowed status=200 sim=1.00 bytes=1951263 - Bingbot allowed status=200 sim=1.00 bytes=1950984 - CCBot blocked status=403 sim=0.00 bytes=9936 - Browser allowed status=200 sim=1.00 bytes=1951275 Run again at: https://agentspeed.com/tools/ai-crawler-access-matrix
Watch this URL — get alerted when this changes
Turn this one-off check into a scheduled watch. We re-run it, diff the result, and alert you on a regression through the same channels as your agent alerts. Watches are a paid feature.
Manage watches at /watches. You’ll be asked to sign in if you haven’t already.
Click an example to run the tool with pre-filled inputs.
Most agent-readiness problems show up here first. A site that blocks GPTBot at the WAF, redirects ChatGPT-User to /login, or serves a different body to PerplexityBot than to a browser will never show up in agent answers, and the only way to find out is to actually fetch as those agents.
This is the live equivalent of the journey.primary_probe check on a public scan, run on demand against any URL.
Is this the same as the Agent UA tester?
Why include Googlebot and Bingbot?
What does "allowed-different" mean?
Do you store the responses?
How do redirects show up?
Score the entire site against 30 agent-readiness checks across discoverability, readability, structured data, actionability, and performance.
Get the full report for openai.com →