Agent Ready vs isitagentready.com

At a glance

Competitor column verified against the live isitagentready.com on 2026-06-20. Cloudflare iterates this tool quickly — check the live scanner for its current category list.

What is isitagentready.com?

isitagentready.com is Cloudflare’s free, web-based AI agent-readiness scanner. Paste a URL and it grades the site across five categories — discoverability (robots.txt, sitemap, DNS-AID, Link headers), content accessibility (markdown content negotiation), bot access control (AI bot rules, Content Signals, Web Bot Auth), protocol discovery (MCP server cards, Agent Skills, WebMCP, API Catalog, OAuth), and commerce (x402, MPP, UCP, ACP) — then returns a score and AI-generated recommendations. It’s a genuinely broad, well-distributed tool, and for a quick free pass it’s a fine place to start.

What is Agent Ready?

Agent Ready is an independent agent-readability scanner. It checks the same discovery and protocol surfaces, but adds a 10-point structural llms.txt validation, A2A agent cards, Wildcard agents.json, NLWeb /ask endpoints, and AGENTS.md — and every check ships a deterministic, plain-English fix mapped to a published methodology and spec registry. You can run it from the web, a REST API, a CLI, an MCP server, an SDK, or a browser extension. It also ships three companion tools the single-form competitor doesn’t — a structured-data validator, a dedicated MCP server scanner, and an llms.txt generator — covered below.

How do they differ?

Protocol coverage has converged — both tools now validate MCP cards, Agent Skills, API Catalog, Web Bot Auth, and the commerce protocols. The differences that actually decide which one to reach for are these:

• Surfaces. isitagentready.com is a web form. Agent Ready also ships a REST API, a CLI, an MCP server, a client SDK (npm + PyPI), and a browser extension — so you can gate CI, script bulk scans, or let an agent call it as a tool.
• Deterministic vs AI-generated output. Agent Ready returns the same pass/fail and the same fix text for the same input every time, each mapped to a numbered check in a public registry. Cloudflare’s tool returns AI-generated recommendations, which are flexible but not reproducible or independently auditable.
• Independence. Agent Ready isn’t tied to one infrastructure vendor. Cloudflare’s scanner naturally centres Cloudflare-led signals (Content Signals, Web Bot Auth) — useful if you run Cloudflare, less neutral if you don’t.
• A few extra protocols. Agent Ready additionally validates A2A agent cards, agents.json, NLWeb, and AGENTS.md; Cloudflare currently checks WebMCP, which Agent Ready defers. Neither is a strict superset of the other.

What does Agent Ready’s structured-data validator add?

Agent Ready includes a separate structured-data validator that parses a page’s JSON-LD and grades it against eight checks drawn from the schema.org vocabulary and common rich-result requirements — valid syntax, recognised @typevalues, required and recommended properties, and the entity graph that AI agents and search engines read to understand what a page is about. isitagentready.com doesn’t evaluate structured data at all; its five categories stop at discovery, content negotiation, bot control, protocol discovery, and commerce. If you lean on JSON-LD to describe products, articles, or your organisation — the markup that powers rich results and grounds the facts an LLM repeats about you — that’s an entire surface Cloudflare’s scanner leaves unchecked.

How does MCP server scanning differ from MCP card detection?

Both tools touch MCP, but at different depths. isitagentready.com checks whether a site advertisesan MCP server card — a discovery signal that says “a server exists here.” Agent Ready’s MCP server scanner connects to the live server itself and grades its actual tools against a battery of weighted checks (M1–M13): whether it exposes a usable tool list, whether tools are named and described clearly enough for an agent to pick the right one, how it handles errors and annotations, and whether it’s reachable and safe to call. That’s the difference between confirming a server is announced and confirming it actually worksfor an agent — and it produces its own tool-level score, separate from the site-readability scan, that the competitor doesn’t offer.

Can either tool generate an llms.txt for you?

Only Agent Ready. Its llms.txt generator builds a spec-valid llms.txt for any site from its sitemap and each page’s own title and description — generation, not just validation — so you can publish a first draft in one step. isitagentready.com offers neither: it doesn’t generate an llms.txt, and llms.txt isn’t among its check categories.

Is Agent Ready the same as the Cloudflare tool?

No — and the similar names cause real confusion. agent-ready.dev is an independent project; isitagentready.com is Cloudflare’s. They are not affiliated, don’t share a score, and don’t share a check registry. If you were sent an “Agent Ready” score, check the domain on the report to know which tool produced it.

Which should you use?

They’re complementary. Use Cloudflare’s tool for a fast, free first look — especially if you’re on Cloudflare and care about its Content Signals and Web Bot Auth checks. Reach for Agent Ready when you need to automate scans in CI, want a deterministic remediation list tied to a published methodology, or need the protocols Cloudflare doesn’t cover (A2A, agents.json, NLWeb, AGENTS.md). Running both and fixing the union of what they flag is a perfectly good strategy.

Frequently asked questions

Is agent-ready.dev the same tool as isitagentready.com?

No. They are two separate AI agent-readiness scanners from different makers. isitagentready.com is operated by Cloudflare; agent-ready.dev is an independent project not affiliated with Cloudflare. The names are similar and both score how ready a site is for AI agents, which causes regular confusion — but they are distinct tools with different surfaces and coverage.

Who makes isitagentready.com?

Cloudflare. It is a free, web-based scanner that grades a URL across discoverability, content accessibility, bot access control, protocol discovery, and commerce signals, and returns AI-generated recommendations for improving the score.

What's the difference between agent “readability” and agent “readiness”?

They describe the same goal from two angles. “Readability” (Agent Ready's framing, anchored to the Vercel Agent Readability Spec) emphasises how easily an agent can discover, parse, and act on your content. “Readiness” (Cloudflare's framing) emphasises whether the site is prepared for agent traffic. In practice the check sets overlap heavily; the label is mostly positioning.

Can I use both isitagentready.com and Agent Ready?

Yes, and it's a reasonable workflow. Run Cloudflare's tool for a fast, free first pass — especially if you're already in the Cloudflare ecosystem and care about its Content Signals and Web Bot Auth checks. Use Agent Ready when you need to automate scans (REST API, CLI, MCP server, SDK, browser extension), want a deterministic per-check fix list mapped to a published methodology, or need coverage of A2A agent cards, agents.json, NLWeb, and AGENTS.md.

Which scanner is more thorough?

As of the last verification the two are close on protocol breadth — both cover MCP server cards, Agent Skills, API Catalog, Web Bot Auth, and the commerce protocols (x402, MPP, UCP, ACP). Agent Ready additionally validates A2A agent cards, agents.json, NLWeb /ask, AGENTS.md, and runs a 10-point structural llms.txt check, and it publishes its full check registry and weighting. Cloudflare's tool actively checks WebMCP (which Agent Ready currently defers) and Cloudflare-native signals like Content Signals. The bigger practical gap is surfaces and transparency, not raw count.