aaif.io agentic web readiness
A Manifest validity: 100% (2/2 valid, 0 errors, 2 warnings) · Surface score 54 (coverage 30 + breadth 9 + conformance 15). 5 standards observed across 3 of 9 steps; 2 manifests present, 0 errors, 2 warnings. Checked 2026-10-23 12:28:57 UTC. This grades the agent-facing files published at aaif.io, 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 | valid |
|
AGENTS.md/AGENTS.md | absent HTTP 404 | |
Agent Skills/.well-known/agent-skills/index.json | 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 | valid |
|
security.txt (RFC 9116)/.well-known/security.txt | absent HTTP 404 | |
auth.md/auth.md | absent HTTP 404 | |
Open Knowledge Format/okf/index.md | absent HTTP 404 |
What an agent can call
- llms.txt: Agentic AI Foundation (AAIF), 212 links, llms-full.txt present
- robots.txt AI policy: unlisted crawlers partial
Standards observed
- llms.txt https://aaif.io/llms.txt
- Content Signals Policy https://aaif.io/robots.txt
- AI Crawler User-Agent Tokens in robots.txt https://aaif.io/robots.txt
- agents.txt https://aaif.io/agents.txt
- Markdown for Agents https://aaif.io/
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
- api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description
Agent pre-flight & practical readiness
Preferred mode: llms_txt (fallback markdown_negotiation). GET /llms.txt and follow the links it names. That index is the page list an agent should read.
Fetch: GET https://aaif.io/llms.txt GET /llms.txt and follow its links.
Practical readability: exa_parsable yes, markdown negotiation yes, render markdown_native, HTML quality high, first content at byte 0.
AI crawler posture: open_to_all · Assistant access: OpenAI partial, Anthropic partial, Google partial, Perplexity partial, Exa partial.
Readiness subscores: reach 20/20, readability 30/30, capabilities 6/35, conformance 15/15, total 71/100, grade A.
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). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. 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