Is docs.expo.dev agent ready?

docs.expo.dev is partly agent ready: it scores 58/100 (grade C) on the w2agent rubric. Weakest areas: Agent Auth (22), Agent Protocols (25), Agent Discovery (49).

58/ 100
Grade: C

Last checked · Platform: nextjs

Scored Oct 14, 2026 · Rubric v3.0

Changed since last check

−5 points since the previous check (2026-09-16)

Regressed: FAQ content, Discoverable API endpoints, Response time

Changed: Structured forms (partial → fail)

Category scores

Technical
89
Agent Auth
22
Agent Discovery
49
Agent Protocols
25
Content Quality
68
Structured Data
76
Bot Accessibility
91

Agent protocol panel

  • A2A agent cardNot found
  • OAuth discoveryNot measured
  • MCP discoveryNot found
  • llms.txt validityPresent

Check results

Bot Accessibility

  • ✓No error status codespass
  • ~Response timepartial
  • ✓XML sitemap existspass
  • ✓AI agent accesspass
  • ✓Edge treatment of agent user-agentstracked, not scoredpass
  • ✓robots.txt existspass
  • ✓Content negotiation (Markdown)pass
  • ✓Declared AI usage preferencestracked, not scoredpass

Structured Data

  • ✓OpenGraph meta tagspass
  • ~Semantic HTML elementspartial
  • ✓Appropriate Schema.org typepass
  • ✓JSON-LD validpass
  • ✓Heading hierarchypass
  • ✓Schema.org JSON-LD presentpass
  • ~Schema.org completenesspartial

Content Quality

  • ✗FAQ contentfail
  • ✓Answer-first contentpass
  • ✓Content lengthpass
  • ✗Token efficiency (HTML-to-text ratio)fail
  • ✓Freshness signalspass
  • ✗Author attributionfail
  • ✓Citation readinesspass
  • ✓Lists and tables for structured infopass

Agent Discovery

  • ✓llms.txt follows specpass
  • ✓llms.txt existspass
  • —MCP server cardtracked, not scoredskip
  • ✓Markdown alternate linkspass
  • ✗/.well-known/agent-card.jsonfail
  • ~llms.txt links resolvepartial

Agent Protocols

  • ✗Discoverable API endpointsfail
  • ✗MCP endpointfail
  • ✗Action schemasfail
  • —/.well-known/ucpskip
  • ✗Structured formsfail
  • —WebMCP imperative APItracked, not scoredskip
  • —WebMCP declarative APItracked, not scoredskip
  • ✓Reachable as Google-Agentpass
  • ✓Reachable as ChatGPT-Userpass
  • ✓Reachable as Perplexity-Userpass

Agent Auth

  • —MCP authorization (401 challenge → protected resource metadata)skip
  • ✗PKCE S256 supportfail
  • ✗Public API surfacefail
  • —Client ID Metadata Documents (bonus)skip
  • —OpenAPI specificationskip
  • ✗Agent/bot auth documentationfail
  • —OAuth discovery chain (RFC 9728 → RFC 8414)skip
  • ✓Developer portalpass
  • ✗Scoped API permissionsfail
  • —API catalog (RFC 9727)skip
  • —Agent operator signing directorytracked, not scoredskip

Technical

  • ✓HTTPSpass
  • ✓UTF-8 charsetpass
  • ✓Canonical URLspass
  • ✓Mobile viewportpass
  • ✓Content accessible without JSpass
  • ~Security headerspartial

Other

  • ✗nextjs-metadata-apifail
  • ✓nextjs-static-generationpass
  • ✗nextjs-well-known-servedfail

Score history

  • 58/100 · rubric v3.0
  • 63/100 · rubric v3.0
  • 63/100 · rubric v3.0
  • 52/100 · rubric v2.0
  • 52/100 · rubric v2.0
  • 52/100 · rubric v2.0
  • 52/100 · rubric v2.0
  • 52/100 · rubric v2.0
  • 52/100 · rubric v2.0

Related websites