AgentReadyWebsite vs Cloudflare’s scanner

Both offerings speak to agent-readiness and overlap on many of the same emerging AI industry standard protocol files. Cloudflare’s tool is a free diagnostic scanner. AgentReadyWebsite is a managed subscription that generates, installs, and refreshes a standards-aligned protocol file package monthly. This page states what each provides as of July 20, 2026.

At a glance

isitagentready.com AgentReadyWebsite
Who Cloudflare free tool Managed subscription
Job Scan a URL; emit pass/fail checks and remediation prompts for a coding agent Analyze the site; generate a standards-aligned package; deliver a zip with install guidance; refresh while subscribed
Cost Free Basic $99/month ($999/year), Medium $199/month ($1,999/year), Complex $399/month ($3,999/year), see pricing
Score Cloudflare “agent readiness score” (UI also describes readiness levels 0–5 across ~20 checks) Agent Readiness Score across four package-anchored dimensions (Discoverability, Content Understanding, Agentic Capabilities, Permissions and Governance), 0–100 with grades A–F
Output Check results plus prompts to paste into Cursor, Claude Code, Windsurf, Copilot, etc. Custom-generated Zip file + INSTRUCTIONS.txt; WordPress sites can use the free installer plugin
Ongoing One-shot scan (re-run yourself) Monthly re-analysis and standards-aware package refresh while the subscription is active

What each product is

isitagentready.com is Cloudflare’s free Agent Readiness scanner, launched April 17, 2026 during Agents Week (launch blog). It requests the site, scores emerging standards across Discoverability, Content Accessibility, Bot Access Control, and Protocol Discovery / API-Auth-MCP, shows Commerce checks informatively, and offers coding-agent prompts for failing checks. The tool also exposes an MCP discovery document at /.well-known/mcp.json and an Agent Skills index. The same checks appear in Cloudflare URL Scanner’s Agent Readiness tab.

AgentReadyWebsite is a managed subscription: free Pre-Check calculates a website’s Agent Readiness Score, then after checkout a site analysis generates a custom 13-file agent-readiness package for customer installation. Each month thereafter we re-analyze the site, the custom agent-readiness package is regenerated to reflect any website changes and validated against changes to industry standards, and the Agent Readiness Score is updated on the customer’s Agent Readiness Dashboard showing how the score moves over time (see how it works and the files).

Agent readiness score models are not the same

Do not treat the two scoring models as interchangeable.

isitagentready.com (labels shown in their tool) AgentReadyWebsite Agent Readiness Score
Discoverability, robots.txt, Sitemap, Link headers, DNS-AID Discoverability (35%), llms.txt, robots.txt AI crawl rules, .well-known/agent-card.json, sitemap.xml
Content Accessibility, Markdown content negotiation only Content Understanding (30%), llm-info.html, agenticweb.md, schema.jsonld
Bot Access Control, AI bot rules, Content Signals, Web Bot Auth Permissions and Governance (15%), .well-known/agent-permissions.json, robots.txt Content-Signals, .well-known/ucp
Protocol Discovery / API-Auth-MCP, API Catalog, OAuth, Auth.md, MCP Server Card, A2A Agent Card, Agent Skills, WebMCP Agentic Capabilities (20%), MCP server card, Agent Skills index, webmcp-registration.js, API Catalog
Commerce (informational; does not count toward score), x402, MPP, UCP, ACP UCP ships in the package under Permissions and Governance (commerce terms / placeholder when non-commerce)

Where the check surfaces overlap

Cloudflare’s scanner mixes checks for files and signals on the site with checks that need server-side or runtime capabilities. Our package aims to cover the file-and-signal set. The second set is outside what a static-file delivery can provide.

Often satisfiable by a static package (when files are correctly shaped and served)

  • robots.txt AI bot rules and Content Signals
  • sitemap.xml
  • .well-known/api-catalog
  • .well-known/mcp/server-card.json
  • .well-known/agent-skills/index.json
  • A2A .well-known/agent-card.json (our package includes this path)
  • .well-known/ucp (placeholder or populated profile)
  • Static webmcp-registration.js presence (their live WebMCP runtime check is a separate bar)

Outside a static-file package (their score can still fail after install)

  • Markdown content negotiation (Accept: text/markdown)
  • Link response headers (RFC 8288)
  • DNS for AI Discovery (DNS-AID)
  • Web Bot Auth
  • OAuth discovery / OAuth Protected Resource / Auth.md as live endpoints
  • Live MCP tools / WebMCP runtime registration
  • Agentic commerce protocols that require payment or checkout infrastructure (x402, MPP, ACP)

On July 7, 2026 we scanned our own domain on their tool: checks for files our package covers passed; failures were in the server-side / runtime group above. That result is dated evidence for that scan, not a guarantee for any site.

llms.txt: a real standards disagreement

Cloudflare’s default Content Accessibility check is Markdown content negotiation. As of July 20, 2026, their Customize checklist still has no llms.txt toggle (the April 2026 launch blog still says you can customize the scan to include it, that claim is outdated compared with what their tool shows today). Their homepage meta tag description still mentions llms.txt.

AgentReadyWebsite ships llms.txt as a foundational package file. Google Chrome Lighthouse Agentic Browsing audits for llms.txt. That is a genuine difference of opinion between Cloudflare’s preferred content answer and Lighthouse’s audit, not a trick question, and not something either vendor resolves for the other.

What we ship that their primary content check does not score

Their Content Accessibility dimension scores Markdown negotiation. Several files in our package are scored in our model and documented on the files hub, but are not their default content check:

  • llms.txt, foundational discovery index (Howard / llmstxt.org format)
  • llm-info.html, agent-facing business briefing
  • agenticweb.md, agent-capability narrative
  • schema.jsonld, Schema.org structured data (augment-if-present)
  • .well-known/agent-permissions.json, action and resource policy

Sources and last verified

isitagentready.com facts on this page were verified July 20, 2026 against their homepage (including the Customize panel), the Cloudflare launch blog, and /.well-known/mcp.json. AgentReadyWebsite facts come from our published product details (tiers, score dimensions, package composition).

If you want a custom agent-readiness managed service, start with the free Pre-Check.