AgentSpeed: See what AI agents see on your site — then monitor it agentspeed . Free check Live demo Pricing Tools Docs Sign in Start free → Free check · no signup · ~30 seconds 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. Scan my site → Building agents? Explore the live monitoring demo → The invisible problem 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.example cookie wall blocks menu HTML → agent can’t read the menu salon-luxe.example booking requires login → agent bounces before it starts yourapp.example JS-rendered pricing, empty HTML → agent quotes competitor.example instead techstore.example CAPTCHA on the support page → warranty flow dead on arrival airline-a.example robots.txt disallows GPTBot + ClaudeBot → no citations, ever shop.example Product JSON-LD missing price → agent won’t compare or recommend What your report looks like 94 / 100 Agent Ready AI agents can fully access, read, and act on your content. 67 / 100 Needs Work A few barriers limit agent access. Fixable in an afternoon. 23 / 100 Agent Blocked 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. Coverage 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-User OAI-SearchBot Claude-User Claude-SearchBot PerplexityBot Perplexity-User YouBot Amazonbot GPTBot ClaudeBot anthropic-ai CCBot Google-Extended Applebot-Extended Bytespider cohere-ai Diffbot FacebookBot Coverage tracks each operator’s public documentation. Run the per-bot access matrix → The check Four things only machines see Crawler access Which AI crawlers your site allows, blocks, redirects, or challenges. Real fetches as GPTBot, ClaudeBot, Perplexity, and friends. run this check → llms.txt Present, valid, and actually useful to an agent? Graded on six axes, with a suggested replacement that closes every gap. run this check → Readability without JS Most agents never run your JavaScript. See what a bot reading raw HTML actually understands about your page. run this check → Structured data 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 → Watches 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. Re-runs on your schedule Hourly, daily, or weekly. The same check, the same URL, without you remembering to look. Diffs what changed A robots rule edited, a bot newly challenged, an llms.txt section dropped, a score that slid. Every snapshot is kept. Alerts on regression 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). Agent monitoring 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. Metadata-first · we never store your prompts or outputs Runs & spans 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. Cost & tokens 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. Quality drift 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. Journey canaries 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. Alert rules 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. Public status pages Hand customers a status page with 30-day uptime bars. One link, always current. Live render · this is the real product UI, not a screenshot Checkout assistant · sample data agentspeed . Projects Alerts Status pages Billing Settings Projects · production Checkout assistant sample data 24h 7d 30d Success rate 98.7% 1,301 succeeded Failure rate 1.3% 17 failed / timeout p95 latency 4.7s p50 2.9s Total runs 1,318 3 running Cost $211.84 1.9M tokens Runs per day last 14 days Recent runs 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 Start monitoring free → Explore the live demo → Free for 10,000 events/month · No credit card · See how it all works → WORKS WITH THE STACK YOU ALREADY SHIP Python TypeScript cURL Anthropic OpenAI LangChain LlamaIndex CrewAI One HTTP endpoint, from any language or framework that can send JSON. No SDK required. Is this you? The agent shipped. The hard part started. You hear about outages from customers The agent started failing overnight. You found out from a support ticket the next morning, with a screenshot you can’t reproduce. The token bill keeps creeping up 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. A prompt tweak quietly tanked quality Success rate slid from 98% to 91% after a small wording change. It shipped last Tuesday. You’re finding out now. Your “monitoring” is a ping check 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 → Setup One POST and you're live 01 Make a key Create a project and generate an API key. We hash it at rest, and the secret shows once. 02 POST a run Send one request from anything that speaks HTTP. Spans and events are optional. A new agent provisions itself the first time it reports. 03 Watch it Health appears right away. Set your thresholds, publish a status page, and get on with your day. No SDK to install. POST /api/v1/runs 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 }' Metadata only. Your prompts and outputs stay on your side. Full API docs → How to buy 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. Basic Free Deep one-time Continuous Recommended Price Free $29 one-time From $19/mo Checks 30 checks, top fixes shown All 30, complete fix list Same rubric, re-run + diffed Remediation detail Top 6 fixes Every finding, step-by-step