Is your site Ready for aI Agents to use It?

Wed, 23 Sep 2026 16:53:34 +0000

What's agent readiness? Agent readiness is how legible and usable a website, API, or MCP server is to autonomous AI agents. A human customer studying a hero on a touchdown page is okay without structured knowledge. An agent that hits the identical URL wants specific machine-readable signals: a sitemap it might probably crawl, an llms.txt at the foundation, OpenGraph plus JSON-LD on every page, predictable rate-restrict headers, an OpenAPI spec for any public endpoint, and (more and more) a discoverable MCP server card or AP2 manifest. Without those indicators the agent guesses, fails halfway, or provides up. The Open Agent Readiness scanner right here measures all agreement of subject and verb examples that against a public spec so you can repair the gaps before agents begin showing up at your site. Each scan groups checks into seven categories. A failing class drops the overall rating; a green class contributes weighted points. The category breakdown lives in the general public leaderboard and in the JSON returned by the v1 API. Sitemap.xml, robots.txt, llms.txt, llms-full.txt, MCP server card, AP2 manifest, OpenAPI spec at a predictable path.

If an agent cannot find your endpoints by crawling, the remainder of the categories do not matter. OpenGraph tags on every web page, JSON-LD structured data (Organization, Product, FAQPage, BreadcrumbList), canonical URLs, and meta-description coverage. Determines whether your content material surfaces in AI search (Perplexity, ChatGPT search, Claude search) and will get cited accurately. Rate-limit headers (RateLimit-Limit, RateLimit-Remaining, Retry-After), correct 401/403 semantics, idempotency-key assist on Post/PUT, CORS configured for cross-origin agent calls. What the endpoint really exposes. For MCP servers: number of instruments, assets, prompts. For Rest APIs: documented endpoints, schemas, instance responses. For websites: structured product or pricing data. Whether the endpoint can take an agent's money: x402 micropayments, MPP (the Tempo / Stripe Machine Payments Protocol), AP2, and ACK-ID for pay-per-name access, and whether prices are advertised in machine-readable type. We probe each separately, so an MPP-only endpoint (which solutions with WWW-Authenticate: Payment, not x402) is detected too. The bar Coinbase and Stripe both endorsed. Response-time consistency, schema stability throughout requests, deterministic error shapes, content material-type honesty (returning JSON when the docs say JSON).

Identity verification (DNS data, signed manifests), phrases-of-service URL discoverability, ai.txt or similar bot-policy information, and uptime monitor document from prior scans. Agentic traffic is not hypothetical. ChatGPT search, Perplexity, Claude, Gemini Deep Research, Cursor, Devin, and a protracted tail of vertical brokers all crawl the public web and name APIs as a part of regular request dealing with. By Q1 2026 agentic traffic on B2B SaaS websites already accounts for 5-15% of all non-bot requests, and the curve is steeper than the human cell transition was. Sites that ship readiness alerts get cited in AI answers, picked up by agent activity plans, and routed to in agent-pushed discovery flows. Sites with out them get politely skipped. The leaderboard above tracks who's already ahead. Paste a URL, hit scan. The scanner makes a sequence of HEAD and GET requests, parses HTML, fetches sitemaps, probes properly-recognized paths (/llms.txt, /.nicely-known/mcp.json, /.effectively-identified/ap2.json, /openapi.json), and runs spec-outlined checks against every response. Non-2xx responses are categorised (skip vs fail) so a lacking-but-non-compulsory file doesn't penalise you a similar as a misconfigured-required one.

Results render as the rating ring above plus a paste-ready fix immediate for each failure which you can drop into Claude or Cursor and have it carried out in minutes. The same spec runs over MCP for AI agents that want to self-audit, and over Rest at /api/v1/agent-readiness. Missing llms.txt. The only most typical gap. Add a plaintext file at the basis itemizing your key URLs and a one-paragraph site description. JSON-LD on the homepage only. Engines like google already settle for this; brokers want it on product, pricing, docs, and particular person content pages too. Generate from a shared helper, not hand-rolled. Rate-restrict headers lacking on API responses. Even if your limits are generous, the lack of headers makes brokers back off conservatively. Add RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset to every authenticated route. MCP server with no card. In the event you publish an MCP server, drop the JSON card at /.nicely-identified/mcp.json with identify, description, model, transport, tools array.

Without it the server is invisible to discovery. 402 endpoint without printed pricing. Return the value within the 402 response body within the format the x402 spec defines. Otherwise paying brokers cannot finances the decision. Cloudflare's product is about blocking agent traffic; this scanner is about welcoming it. The 2 solve opposite issues. Should you actively want to be discoverable to agents (most sites should, by 2026), you want the readiness audit; if you want to maintain brokers out of premium content material, Cloudflare is the reply. They compose properly: gate paid endpoints behind Cloudflare, make the rest of your surface readiness-compliant. Full breakdown on the devoted comparison web page. Is the scanner free? Yes. Public scans are free with no signup required. The /api/v1/agent-readiness endpoint prices 1 credit score per name (Free plan contains 1,500 credit per 30 days, loads for occasional checks). Paid agent entry through x402 can also be supported for autonomous agents with no API key. Do you store the URLs I scan?

Freeweb-apps.info QtoA - Recent questions tagged britain

Is your site Ready for aI Agents to use It?