2s.io agentic web readiness

A+ Score 64 (coverage 50 + breadth 9 + conformance 5). 5 standards observed across 5 of 9 steps; 6 manifests present, 4 errors, 8 warnings. Checked 2026-10-19 00:42:52 UTC. This grades the agent-facing files published at 2s.io, not the organisation's products.

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

Coverage by step

01 DiscoverRFC 9727 02 Identifynothing observed 03 PermitAI Crawler User-Agent Tokens in robots.txt 04 Readllms.txt 05 Actagents.json 06 CoordinateA2A 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.json`	absent HTTP 404
AI Catalog well-known file `/.well-known/ai-catalog.json`	errors HTTP 200	body is not valid JSON
MCP Server Cards (SEP-2127) `/.well-known/mcp.json`	errors HTTP 200	$schema missing (required: https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json) name must be reverse-DNS with exactly one slash, e.g. com.example/weather version missing Content-Type is application/json; charset=utf-8; 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[] remotes missing: a card with no remotes gives clients nothing to connect to no ETag
Agent2Agent Protocol `/.well-known/agent-card.json`	valid HTTP 200	supportedInterfaces missing; A2A 1.0 cards declare interfaces there (url, protocolBinding, protocolVersion) and the top-level url is the 0.3 shape
llms.txt `/llms.txt`	valid HTTP 200	file is large; keep llms.txt an index and put the full text in llms-full.txt
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`	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) no Content-Signal: line (optional; states ai-train / search / ai-input preferences)
security.txt (RFC 9116) `/.well-known/security.txt`	absent HTTP 404
auth.md `/auth.md`	absent HTTP 404

What an agent can call

A2A agent 2s at https://2s.io/a2a, skills: Discover 2s endpoints
A2A agent 2s at https://2s.io
API description https://2s.io/openapi.json (application/vnd.oai.openapi+json;version=3.1)
API description https://2s.io/apis.json (application/json)
API description https://2s.io/llms.txt (text/markdown)
API description https://2s.io/discover (text/html)
API description https://2s.io/api/directory (application/json)
API description https://2s.io/.well-known/x402 (application/json)
API description https://2s.io/.well-known/ai-plugin.json (application/json)
API description https://2s.io/.well-known/mcp/server-card.json (application/json)
API description https://2s.io/.well-known/agent-card.json (application/json)
API description https://2s.io/api/openapi?group=agent (application/vnd.oai.openapi+json;version=3.1)
API description https://2s.io/agent (text/html)
API description https://2s.io/api/openapi?group=agriculture (application/vnd.oai.openapi+json;version=3.1)
API description https://2s.io/agriculture (text/html)
API description https://2s.io/api/openapi?group=ai (application/vnd.oai.openapi+json;version=3.1)
API description https://2s.io/ai (text/html)
API description https://2s.io/api/openapi?group=airport (application/vnd.oai.openapi+json;version=3.1)
API description https://2s.io/airport (text/html)
API description https://2s.io/api/openapi?group=aviation (application/vnd.oai.openapi+json;version=3.1)
API description https://2s.io/aviation (text/html)
API description https://2s.io/api/openapi?group=bank (application/vnd.oai.openapi+json;version=3.1)
llms.txt: 2s, 24 links
robots.txt AI policy: allows GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, anthropic-ai, Google-Extended, PerplexityBot, Perplexity-User, CCBot, Applebot-Extended, meta-externalagent, Bytespider, Amazonbot, cohere-ai, Diffbot, DuckAssistBot, MistralAI-User, YouBot; unlisted crawlers allowed

Standards observed

Agent2Agent Protocol https://2s.io/.well-known/agent-card.json
llms.txt https://2s.io/llms.txt
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://2s.io/.well-known/api-catalog
AI Crawler User-Agent Tokens in robots.txt https://2s.io/robots.txt
agents.json https://2s.io/.well-known/agents.json

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
AGENTS.md: instructions for coding agents working on or with the site
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