Is chipotle.com agent ready?
chipotle.com is not yet agent ready: it scores 37/100 (grade D) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Discovery (0), Structured Data (23), Agent Protocols (27), Content Quality (44).
Changed since last check
+4 points since the previous check (2026-09-15)
Fixed: Token efficiency (HTML-to-text ratio)
Changed: Appropriate Schema.org type (fail → partial), Schema.org JSON-LD present (fail → partial)
Category scores
Technical
96
Agent Auth
0
Agent Discovery
0
Agent Protocols
27
Content Quality
44
Structured Data
23
Bot Accessibility
93
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ✓Response timepass
- ✓XML sitemap existspass
- ✓AI agent accesspass
- ✓Edge treatment of agent user-agentstracked, not scoredpass
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ~OpenGraph meta tagspartial
- ~Semantic HTML elementspartial
- ~Appropriate Schema.org typepartial
- ✓JSON-LD validpass
- ✗Heading hierarchyfail
- ~Schema.org JSON-LD presentpartial
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ~Answer-first contentpartial
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ~Citation readinesspartial
- ~Lists and tables for structured infopartial
Agent Discovery
- —llms.txt follows specskip
- ✗llms.txt existsfail
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- —llms.txt links resolveskip
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- ✗/.well-known/ucpfail
- —Structured formsskip
- —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 supportskip
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- —Agent/bot auth documentationskip
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- —Developer portalskip
- —Scoped API permissionsskip
- —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 headerspass
Other
- —ecommerce-gtin-validskip
- —ecommerce-product-schemaskip
- —ecommerce-checkout-accessibleskip
Score history
- 37/100 · rubric v3.0
- 33/100 · rubric v3.0
- 27/100 · rubric v3.0
- 20/100 · rubric v2.0
- 20/100 · rubric v2.0
- 21/100 · rubric v2.0
- 21/100 · rubric v2.0
- 21/100 · rubric v2.0
- 21/100 · rubric v2.0
- 30/100 · rubric v2.0
- 29/100 · rubric v2.0
- 31/100 · rubric v2.0