fastify.dev agentic web readiness

C Manifest validity: 100% (1/1 valid, 0 errors, 2 warnings) · Surface score 20 (coverage 10 + breadth 0 + conformance 10). 1 standard observed across 1 of 9 steps; 1 manifest present, 0 errors, 2 warnings. Checked 2026-10-25 23:38:05 UTC. This grades the agent-facing files published at fastify.dev, not the organisation's products.

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

Coverage by step

Manifests

What an agent can call

• llms.txt: fastify.dev, 849 links, llms-full.txt present

Standards observed

• llms.txt https://fastify.dev/llms.txt

Cheapest next steps

1. AI Crawler User-Agent Tokens in robots.txt: state what AI crawlers may do in robots.txt you already serve
   Generate starter /robots.txt for fastify.dev

   # search and answer-engine crawlers
   User-agent: Googlebot
   User-agent: bingbot
   User-agent: OAI-SearchBot
   User-agent: Claude-SearchBot
   User-agent: PerplexityBot
   User-agent: ExaSearchBot
   User-agent: TavilyBot
   Allow: /
   
   # model-training crawlers: choose Allow or Disallow and keep it explicit
   User-agent: GPTBot
   User-agent: ClaudeBot
   User-agent: Google-Extended
   User-agent: Applebot-Extended
   User-agent: CCBot
   User-agent: meta-externalagent
   User-agent: Bytespider
   Disallow: /
   
   # user-triggered fetchers (a person asked for this page)
   User-agent: ChatGPT-User
   User-agent: Claude-User
   User-agent: Perplexity-User
   Allow: /
   
   # default fallback for unlisted crawlers (RFC 9309 §2.2.1: specific groups above take precedence over *)
   User-agent: *
   Allow: /
   Disallow: /account/
   Content-Signal: ai-train=no, search=yes, ai-input=yes
   
   Sitemap: https://fastify.dev/sitemap.xml
   Agentmap: https://fastify.dev/.well-known/ard.json
   

2. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "fastify.dev"}))
3. AGENTS.md: instructions for coding agents working on or with the site
   Generate starter /AGENTS.md for fastify.dev

   # Fastify for agents
   
   Fastify and what it offers to agents
   
   ## Read the data, not the HTML
   - Index: https://fastify.dev/llms.txt
   - API description: https://fastify.dev/openapi.json
   - Discovery catalog: https://fastify.dev/.well-known/ard.json
   
   ## Calling
   - MCP server (Streamable HTTP): https://fastify.dev/mcp
   - Rate limits and authentication: describe them here
   
   ## Conventions
   - How to cite or attribute content
   - What not to do (no scraping of /account/, no automated sign-ups, etc.)
   
   Contact: security@fastify.dev
   

Agent pre-flight & practical readiness

Preferred mode: llms_txt. GET /llms.txt and follow the links it names. That index is the page list an agent should read.

Fetch: GET https://fastify.dev/llms.txt GET /llms.txt and follow its links.

Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high, first content at byte 13234, HTML-to-llms.txt token ratio 1.705×, JSON-LD WebSite.

AI crawler posture: unspecified · Assistant access: OpenAI unspecified, Anthropic unspecified, Google unspecified, Perplexity unspecified, Exa unspecified.

Readiness subscores: reach 0/20, readability 22/30, capabilities 4/35, conformance 10/15, total 36/100, grade C.

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