Cloudflare is Agent-Ready to agents.
Discry independently scored how well an AI agent can discover and understand the Cloudflare API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.
SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.
Discovery
45% of score · 95/100Comprehension
55% of score · 96/100What we found
- Cloudflare has the best llms.txt architecture observed: a concise index (15KB) linking to per-product llms.txt files, each of which links to product-scoped llms-full.txt — perfect progressive disclosure for agents.
- The robots.txt explicitly allows all AI uses (ai-train=yes, search=yes, ai-input=yes) with detailed Content-Signal explanations citing EU copyright directive.
- AGENTS.md exists across 4+ repos (agents, workers-sdk, cloudflare-docs, mcp) — Cloudflare is clearly investing in agent-first developer tooling.
- Multiple official MCP servers cover different product areas (Workers, DNS, R2, D1, Browser Rendering, AI Gateway, Docs) — the most comprehensive official MCP coverage observed.
- The only discovery gap is .well-known/mcp.json, which would provide a single machine-discoverable entry point to all these MCP servers.
What to change
Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.
- 01Add .well-known/mcp.json that catalogs all official Cloudflare MCP servers with their capabilities — this would be the first multi-server mcp.json in the industry.
- 02Add explicit error recovery guidance to the API reference (most error codes currently lack actionable 'what to do next' steps).
- 03Consider publishing an idempotency key mechanism for write operations to help agents safely retry failed mutations.
Execution coverage · INFORMATIONAL, UNSCORED
Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.
Comprehensive execution documentation with OpenAPI-driven API reference, structured JSON error responses, rate limiting with headers, cursor-based pagination. Multiple official MCP servers demonstrate practical agent integration patterns.