AI agents are already reading your site. See what they see.
Paste a URL and get a graded report: which AI crawlers you block, whether your llms.txt works, and what an agent can actually read — with the exact fixes.
Building agents? Explore the live monitoring demo →
How agents actually fail on real sites
Every one of these looks fine in your browser. To an agent, the page is either invisible, unreadable, or unactionable — and no analytics event fires when they leave.
luigis-trattoria.examplesalon-luxe.exampleyourapp.exampletechstore.exampleairline-a.exampleshop.exampleAI agents can fully access, read, and act on your content.
A few barriers limit agent access. Fixable in an afternoon.
Critical issues prevent agents from reading or transacting.
Every score is a permanent public URL at agentspeed.com/score/<domain> — with a badge you can embed.
The 18 AI user agents we check
For each bot: is your robots.txt allowing it, blocking it, or silently challenging it? Most sites disallow at least one by accident.
ChatGPT-UserOAI-SearchBotClaude-UserClaude-SearchBotPerplexityBotPerplexity-UserYouBotAmazonbotGPTBotClaudeBotanthropic-aiCCBotGoogle-ExtendedApplebot-ExtendedBytespidercohere-aiDiffbotFacebookBotCoverage tracks each operator’s public documentation. Run the per-bot access matrix →
Four things only machines see
Which AI crawlers your site allows, blocks, redirects, or challenges. Real fetches as GPTBot, ClaudeBot, Perplexity, and friends.
run this check →Present, valid, and actually useful to an agent? Graded on six axes, with a suggested replacement that closes every gap.
run this check →Most agents never run your JavaScript. See what a bot reading raw HTML actually understands about your page.
run this check →The JSON-LD machines rely on: which types you ship, what fails validation, and what is missing for your page type.
run this check →The full scan grades your site against our public rubric. Powered by 11 free tools →
A check is a snapshot. A watch is monitoring.
A stray robots rule or a new bot wall can cut agents off silently — nothing errors, nothing shows in analytics. Turn any check into a watch and find out the moment it changes.
Hourly, daily, or weekly. The same check, the same URL, without you remembering to look.
A robots rule edited, a bot newly challenged, an llms.txt section dropped, a score that slid. Every snapshot is kept.
Slack, webhook, or email the moment a meaningful change lands. No alert storms; a 30-minute cooldown is built in.
Start one from any tool result — look for “Watch this URL”. Watches are included on paid plans (from $19/mo).
Building agents? Monitor those too.
Agents don’t crash. They quietly get slower, pricier, and wrong. Trace every run down to the token and the dollar, and get paged the moment something breaks.
Click a run and read it top to bottom: every LLM call, tool call, and retrieval with its own timing and tokens, plus live p50/p95 per agent.
Tokens and dollars by agent, by model, by run. One stuck retry loop can spend $40 before you finish your coffee. You will see it the same minute.
Send a quality score with each run, a number you already compute. Watch it per agent and per model, and catch the slide where success holds at 99% but answers quietly got worse.
Describe a critical flow in plain steps. On a schedule we probe the live site and verify each step is still supported by what it actually serves — and page you when one breaks. Bot walls get reported, never bypassed.
Threshold on failure rate, latency, cost, quality, or silence. Every failure keeps its error type, so a creeping RateLimitError cannot hide behind a healthy average.
Hand customers a status page with 30-day uptime bars. One link, always current.
| Status | Started | Latency | Model | Tokens | Cost | Error |
|---|---|---|---|---|---|---|
| running | just now | — | claude-opus-4-8 | — | — | |
| succeeded | 2m ago | 3.1s | claude-opus-4-8 | 1,540 | $0.021 | |
| succeeded | 4m ago | 2.7s | claude-sonnet-4-6 | 1,120 | $0.009 | |
| failed | 6m ago | 9.0s | gpt-4o | 2,310 | $0.038 | RateLimitError |
| succeeded | 8m ago | 3.4s | claude-opus-4-8 | 1,705 | $0.024 | |
| timeout | 11m ago | 30.0s | claude-opus-4-8 | 980 | $0.014 | TimeoutError |
| succeeded | 13m ago | 2.9s | claude-sonnet-4-6 | 1,260 | $0.010 |
Free for 10,000 events/month · No credit card · See how it all works →
One HTTP endpoint, from any language or framework that can send JSON. No SDK required.
The agent shipped. The hard part started.
The agent started failing overnight. You found out from a support ticket the next morning, with a screenshot you can’t reproduce.
This month cost more than last, and nobody touched the pricing. Something is retrying in a loop and there’s no quick way to see which agent.
Success rate slid from 98% to 91% after a small wording change. It shipped last Tuesday. You’re finding out now.
A 200 from the endpoint means the server is awake. It says nothing about whether the agent actually did the job.
If two of those landed, you’re who we built AgentSpeed for. Start watching →
One POST and you're live
Create a project and generate an API key. We hash it at rest, and the secret shows once.
Send one request from anything that speaks HTTP. Spans and events are optional. A new agent provisions itself the first time it reports.
Health appears right away. Set your thresholds, publish a status page, and get on with your day. No SDK to install.
curl -X POST https://agentspeed.com/api/v1/runs \
-H "Authorization: Bearer $AGENTSPEED_API_KEY" \
-d '{ "agent": "checkout-assistant", "status": "succeeded",
"model": "claude-opus-4-8", "inputTokens": 1200,
"outputTokens": 340, "costUsd": 0.0185, "score": 0.92 }'Basic, Deep, or Continuous — same rubric
A quick free look, a one-time deep audit, or ongoing monitoring — all three score against the same public rubric, so results are directly comparable.
17 checks nobody else runs
AgentSpeed grades your site against a versioned public rubric of 30 checks. Seventeen of them are agent-native — tested by no other tool we’ve found.
Explicit allow / disallow / challenge for 18 AI user agents, not a generic “reachable” probe.
H1, tagline, description, section coverage (Docs / Pricing / Contact / About), sitemap consistency, in-domain link ratio.
Whether /.well-known/mcp exposes a valid Model Context Protocol server manifest.
/.well-known/oauth-authorization-server — how agents obtain a token to act on the user’s behalf.
/.well-known/oauth-protected-resource — what an agent is allowed to touch once authenticated.
OpenAPI / Swagger / GraphQL / RSS surfaces linked from HTML and well-known paths.
Cryptographic bot identity per the draft IETF spec — no more spoofed user agents.
Accept: text/markdown — agents prefer clean markdown to reconstructed HTML text.
Anthropic’s emerging Skills protocol — declare what your site can do, not just what it is.
Client-side MCP endpoints for actionable agents (book, buy, file).
Not just present — validates against Schema.org and covers Product / Organization / FAQPage / Article as appropriate.
Detects OneTrust, Cookiebot, Osano, and 40+ vendors that hide content from unclickable agents.
JS-redirect and rendered-only login walls, not just HTTP redirects.
JS-on vs JS-off text-length diff. The number a crawler sees, not the number your browser sees.
Simulated agent completion of the top user flow. Bot walls get reported, never bypassed.
Total transferred KB — agents time out earlier than browsers on bloated pages.
Chrome CDP end-to-end, not Lighthouse’s synthetic first-paint.
Rubric r2026.07.1 — 65.9% deterministic checks, policy-enforced in CI. Read the full spec →
PageSpeed measures humans. AgentSpeed measures agents.
Keep PageSpeed. Keep Lighthouse. They measure real things. They just don’t measure the things an AI agent needs — which is now half your traffic.
Complementary, not competitive — run all three on any site you care about.
Flat tiers. No per-seat fees, no overage bills.
- ✓ 10,000 events/mo
- ✓ 1 project · 3 agents
- ✓ 7-day retention
- ✓ 1 journey canary · manual runs
- — watches on paid plans
- — alert channels on paid plans
- ✓ 100,000 events/mo
- ✓ 3 projects · 10 agents
- ✓ 30-day retention
- ✓ 10 journey canaries · scheduled + alerts
- ✓ Watches (scheduled site checks)
- ✓ Slack / webhook / email alerts
- ✓ 1,000,000 events/mo
- ✓ 10 projects · 50 agents
- ✓ 90-day retention
- ✓ 50 journey canaries · scheduled + alerts
- ✓ Watches (scheduled site checks)
- ✓ Slack / webhook / email alerts
- ✓ 10,000,000 events/mo
- ✓ 50 projects · 250 agents
- ✓ 180-day retention
- ✓ 200 journey canaries · scheduled + alerts
- ✓ Watches (scheduled site checks)
- ✓ Slack / webhook / email alerts
One event = one ingested row: a run report is 1 + its spans + its log events. Full pricing details & FAQ →