Readiness

Agent Standards

Track adoption of agent-readiness checks such as machine-readable docs, API discovery, and content negotiation.

Range
7d 30d 90d
Current Signal 90d
robotsTxt 91,571
sitemap 76,055
linkHeaders 10,491
markdownNegotiation 7,497

Agent readiness checks

Updated: 2026-06-08

Use this to: prioritize machine-readable signals that make the site easier for agents.

robotsTxt 91,571
robotsTxtAiRules 87,809
sitemap 76,055
linkHeaders 10,491
markdownNegotiation 7,497
oauthDiscovery 7,210
ucp 6,407
contentSignals 6,003
apiCatalog 241
agentSkills 203
oauthProtectedResource 184
mcpServerCard 183
webBotAuth 33
a2aAgentCard 23
mpp 6

Country activity

Use geography as a planning signal before changing crawl policy or regional infrastructure.

Why This Matters

Agent standards make sites easier for AI systems to navigate without scraping brittle UI assumptions.

What To Do

  • Start with robots.txt, sitemap, and API docs.
  • Add markdown negotiation where it preserves meaning.
  • Expose machine-readable service descriptions for repeatable agent use.
Data source: Cloudflare Radar. Processed by LLMBase for publisher and agent-readiness workflows.