developers.cloudflare.com agentic web readiness

A+ Score 70 (coverage 40 + breadth 15 + conformance 15). 8 standards observed across 4 of 9 steps; 6 manifests present, 0 errors, 17 warnings. Checked 2026-10-18 22:06:06 UTC. This grades the agent-facing files published at developers.cloudflare.com, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/developers.cloudflare.com.svg) · JSON · Markdown · Re-check now

Coverage by step

01 DiscoverARD, AI Catalog well-known file, RFC 9727 02 Identifynothing observed 03 PermitContent Signals Policy 04 Readllms.txt 05 Act 06 Coordinatenothing observed 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.json`	valid HTTP 200	entries[0] has no description; registries index on it entries[1] has no description; registries index on it entries[2] has no description; registries index on it
AI Catalog well-known file `/.well-known/ai-catalog.json`	valid HTTP 200
MCP Server Cards (SEP-2127) `/.well-known/mcp/server-card.json`	valid HTTP 200	Content-Type is application/json; charset=utf-8; SEP-2127 says serve application/mcp-server-card+json description is over 100 characters remotes[0].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[1].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[2].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[3].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[4].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[5].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[6].supportedProtocolVersions missing; clients use it to pick a version before connecting no Access-Control-Allow-Origin: * (required for browser clients) no Cache-Control max-age; clients should be able to cache the card no ETag
Agent2Agent Protocol `/.well-known/agent-card.json`	absent HTTP 404
llms.txt `/llms.txt`	valid HTTP 200
AGENTS.md `/AGENTS.md`	absent HTTP 404
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs `/.well-known/api-catalog`	valid HTTP 200
AI Crawler User-Agent Tokens in robots.txt `/robots.txt`	valid HTTP 200	no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (partial) no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
security.txt (RFC 9116) `/.well-known/security.txt`	absent HTTP 404
auth.md `/auth.md`	absent HTTP 404

What an agent can call

MCP endpoint https://mcp.cloudflare.com/mcp (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://docs.mcp.cloudflare.com/mcp (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://containers.mcp.cloudflare.com/mcp (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://browser.mcp.cloudflare.com/mcp (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://dex.mcp.cloudflare.com/mcp (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://casb.mcp.cloudflare.com/mcp (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://blog.mcp.cloudflare.com/mcp (streamable-http) — from /.well-known/mcp/server-card.json
API description https://developers.cloudflare.com/openapi.json (application/vnd.oai.openapi+json)
API description https://developers.cloudflare.com/openapi.json (application/json)
API description https://developers.cloudflare.com/api/ (text/html)
llms.txt: Cloudflare Developer Documentation, 112 links
robots.txt AI policy: unlisted crawlers partial

Standards observed

llms.txt https://developers.cloudflare.com/llms.txt
Content Signals Policy https://developers.cloudflare.com/robots.txt
Agentic Resource Discovery https://developers.cloudflare.com/.well-known/ard.json
AI Catalog well-known file https://developers.cloudflare.com/.well-known/ai-catalog.json
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://developers.cloudflare.com/.well-known/api-catalog
MCP Server Cards (SEP-2127)
Model Context Protocol
AI Crawler User-Agent Tokens in robots.txt

Cheapest next steps

AGENTS.md: instructions for coding agents working on or with the site
security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules