fly.io agentic web readiness

A+ Manifest validity: 89% (8/9 valid, 2 errors, 5 warnings) · Surface score 65 (coverage 40 + breadth 15 + conformance 10). 10 standards observed across 4 of 9 steps; 9 manifests present, 2 errors, 5 warnings. Checked 2026-10-23 14:55:37 UTC. This grades the agent-facing files published at fly.io, not the organisation's products.

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

Coverage by step

Manifests

What an agent can call

• MCP endpoint https://sprites.dev/mcp (streamable-http), tools: list_sprites, create_sprite, destroy_sprite, exec_list, exec, exec_kill, checkpoint_create, checkpoint_list, checkpoint_get, checkpoint_restore, policy_network_get, policy_network_update, service_list, service_get, service_create, service_start, service_stop, service_logs, file_read, file_write — from /.well-known/mcp/server-card.json
• API description https://docs.fly.io/api/machines/openapi.json (application/vnd.oai.openapi+json)
• API description https://docs.fly.io/api/machines/openapi.json (application/vnd.oai.openapi+json)
• API description https://docs.fly.io/api/machines/openapi.json (application/json)
• API description https://docs.fly.io/machines/api (text/html)
• API description https://api.sprites.dev/openapi.json (application/json)
• API description https://sprites.dev/api (text/html)
• API description https://fly.io/sprites/ecosystem (text/html)
• llms.txt: Fly.io, 41 links
• robots.txt AI policy: unlisted crawlers partial

Standards observed

• llms.txt https://fly.io/llms.txt
• AGENTS.md https://fly.io/AGENTS.md
• Content Signals Policy https://fly.io/robots.txt
• Agentic Resource Discovery https://fly.io/.well-known/ard.json
• AI Catalog well-known file https://fly.io/.well-known/ai-catalog.json
• api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://fly.io/.well-known/api-catalog
• auth.md https://fly.io/auth.md
• Agent Skills https://fly.io/.well-known/agent-skills/index.json
• Markdown for Agents https://fly.io/
• AI Crawler User-Agent Tokens in robots.txt

Cheapest next steps

1. security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback openapi). Call the MCP endpoint at https://sprites.dev/mcp first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://sprites.dev/mcp POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.

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 35/35, conformance 10/15, total 95/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