etherscan.io agentic web readiness

A Score 49 (coverage 30 + breadth 9 + conformance 10). 5 standards observed across 3 of 9 steps; 4 manifests present, 1 error, 2 warnings. Checked 2026-10-18 23:43:05 UTC. This grades the agent-facing files published at etherscan.io, not the organisation's products.

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

Coverage by step

01 Discoveragents.txt 02 Identifynothing observed 03 PermitContent Signals Policy 04 Readllms.txt, AGENTS.md 05 Actnothing observed 06 Coordinatenothing observed 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.json`	absent HTTP 200	answered with an HTML page (catch-all or soft 404), counted as absent
AI Catalog well-known file `/.well-known/ai-catalog.json`	absent HTTP 200	answered with an HTML page (catch-all or soft 404), counted as absent
MCP Server Cards (SEP-2127) `/mcp/server-card`	absent	not fetched: subrequest-limit
Agent2Agent Protocol `/.well-known/agent-card.json`	absent HTTP 200	answered with an HTML page (catch-all or soft 404), counted as absent
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`	absent HTTP 200	answered with an HTML page (catch-all or soft 404), counted as absent
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	not fetched: subrequest-limit
auth.md `/auth.md`	errors HTTP 200	none of the auth.md mechanism names found (identity_assertion, service_auth, anonymous)

What an agent can call

llms.txt: Etherscan, 48 links
robots.txt AI policy: unlisted crawlers partial

Standards observed

llms.txt https://etherscan.io/llms.txt
AGENTS.md https://etherscan.io/AGENTS.md
Content Signals Policy https://etherscan.io/robots.txt
agents.txt https://etherscan.io/agents.txt
AI Crawler User-Agent Tokens in robots.txt

Cheapest next steps

Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description
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