agents.coinbase.com agentic web readiness
D Score 10 (coverage 10 + breadth 0 + conformance 0). 1 standard observed across 1 of 9 steps; 0 manifests present, 0 errors, 0 warnings. Checked 2026-10-20 05:32:02 UTC. This grades the agent-facing files published at agents.coinbase.com, not the organisation's products.
Coverage by step
Manifests
| Manifest | Result | Findings |
|---|---|---|
Agentic Resource Discovery/.well-known/ard.json | absent HTTP 404 | |
AI Catalog well-known file/.well-known/ai-catalog.json | absent HTTP 404 | |
MCP Server Cards (SEP-2127)/mcp/server-card | absent HTTP 404 | |
Agent2Agent Protocol/.well-known/agent-card.json | absent HTTP 404 | |
llms.txt/llms.txt | absent HTTP 404 | |
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 | absent HTTP 404 | |
AI Crawler User-Agent Tokens in robots.txt/robots.txt | absent HTTP 404 | |
security.txt (RFC 9116)/.well-known/security.txt | absent HTTP 404 | |
auth.md/auth.md | absent HTTP 404 |
What an agent can call
- OAuth protected resource
https://agents.coinbase.com/mcp, authorization servers: https://login.coinbase.com/
Standards observed
- OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://agents.coinbase.com/.well-known/oauth-protected-resource
Cheapest next steps
- llms.txt: one Markdown index file; the most widely read agent-facing file
- AI Crawler User-Agent Tokens in robots.txt: state what AI crawlers may do in robots.txt you already serve
- 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