agenticweb.wiki

agent-ready.dev agentic web readiness

A+ Score 95 (coverage 70 + breadth 15 + conformance 10). 13 standards observed across 7 of 9 steps; 9 manifests present, 1 error, 9 warnings. Checked 2026-10-18 23:43:00 UTC. This grades the agent-facing files published at agent-ready.dev, not the organisation's products.

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

Coverage by step

01 DiscoverAI Catalog well-known file, RFC 972702 IdentifyWebBotAuth03 PermitContent Signals Policy, agent-permissions.json, auth.md, AI Crawler User-Agent Tokens in robots.txt, OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)04 Readllms.txt, AGENTS.md05 Actagents.json06 CoordinateA2A07 PayUCP08 Presentnothing observed

Manifests

ManifestResultFindings
Agentic Resource Discovery
/.well-known/ard.json
absent HTTP 404
AI Catalog well-known file
/.well-known/ai-catalog.json
valid HTTP 200
  • entries[2] has no description; registries index on it
  • entries[7] has no description; registries index on it
MCP Server Cards (SEP-2127)
/.well-known/mcp.json
errors HTTP 200
  • name must be reverse-DNS with exactly one slash, e.g. com.example/weather
  • Content-Type is application/json; SEP-2127 says serve application/mcp-server-card+json
  • pre-final card shape (url/transport/tools); the final SEP-2127 card uses name, version, description and remotes[]
  • $schema is not https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json
  • remotes missing: a card with no remotes gives clients nothing to connect to
  • tools/resources/prompts listed in the card; SEP-2127 excludes primitives (list them live, or under a namespaced _meta key)
  • no ETag
Agent2Agent Protocol
/.well-known/agent-card.json
valid HTTP 200
llms.txt
/llms.txt
valid HTTP 200
AGENTS.md
/AGENTS.md
valid HTTP 200
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 Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
security.txt (RFC 9116)
/.well-known/security.txt
valid HTTP 200
auth.md
/auth.md
valid HTTP 200

What an agent can call

Standards observed

Cheapest next steps

  1. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch

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