Is chargebee.com agent ready?
chargebee.com is partly agent ready: it scores 55/100 (grade C) on the w2agent rubric. Weakest areas: Agent Auth (30), Agent Discovery (38), Structured Data (40).
Changed since last check
−4 points since the previous check (2026-09-16)
Regressed: Structured forms, Token efficiency (HTML-to-text ratio)
Changed: Appropriate Schema.org type (partial → fail), JSON-LD valid (partial → fail), Freshness signals (partial → fail), Schema.org completeness (partial → fail)
Category scores
Technical
96
Agent Auth
30
Agent Discovery
38
Agent Protocols
72
Content Quality
61
Structured Data
40
Bot Accessibility
69
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryPresent
- MCP discoveryPresent
- llms.txt validityPresent
Check results
Bot Accessibility
- ✓No error status codespass
- ✗Response timefail
- ✓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 tagspass
- ✓Semantic HTML elementspass
- ✗Appropriate Schema.org typefail
- ✗JSON-LD validfail
- ~Heading hierarchypartial
- ~Schema.org JSON-LD presentpartial
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓Content lengthpass
- ✗Token efficiency (HTML-to-text ratio)fail
- ✗Freshness signalsfail
- ✗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 linksfail
- ✗/.well-known/agent-card.jsonfail
- ✓llms.txt links resolvepass
Agent Protocols
- ✓Discoverable API endpointspass
- ✓MCP endpointpass
- ✗Action schemasfail
- —/.well-known/ucpskip
- ~Structured formspartial
- —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 surfacepartial
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- ✗Agent/bot auth documentationfail
- ~OAuth discovery chain (RFC 9728 → RFC 8414)partial
- ✓Developer portalpass
- ✗Scoped API permissionsfail
- ✗API catalog (RFC 9727)fail
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✓Security headerspass
Other
- ✓nuxt-ssr-hintspass
- ~nuxt-schema-orgpartial
- ✗nuxt-seo-modulefail
- ✗nuxt-llms-modulefail
Score history
- 55/100 · rubric v3.0
- 59/100 · rubric v3.0
- 60/100 · rubric v3.0
- 54/100 · rubric v2.0
- 54/100 · rubric v2.0
- 52/100 · rubric v2.0
- 52/100 · rubric v2.0
- 48/100 · rubric v2.0
- 49/100 · rubric v2.0
- 49/100 · rubric v2.0
- 47/100 · rubric v2.0