Agent readiness · Payments and billing
chargebee.com
10 of 16 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- PASSllms.txt publishedllms.txt present at https://www.chargebee.com/llms.txt and https://www.chargebee.com/docs/llms.txt, and the 12 links we sampled across the file all answer
- PASSDocs readable without JavaScript10,123 characters of text without JS, on https://www.chargebee.com/docs/billing/2.0/multi-business-entity/mbe-api-key-related-best-practices rather than on https://www.chargebee.com/docs/
- PASSOn-demand agents not blockedExplicitly allowed: ChatGPT-User, Claude-User
- N/APaths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- FAILAgent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
- FAILOAuth dynamic client registrationOAuth metadata published, but no registration_endpoint in it
- PASSMCP surfaceLive MCP endpoint at https://mcp.chargebee.com/mcp, answered 401 with an auth challenge
C · Registration
- FAILNo CAPTCHA in the signup HTMLrecaptcha appears in the signup page's server HTML
- PASSSignup reachable without a browserForm renders in server HTML at https://www.chargebee.com/trial-signup/
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 6 documents we read
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://chargebee.com/pricing: "Free Trial", "$0"
E · Integration
- PASSTyped SDK on the registrychargebee@3.30.1 ships types, matched from the registry by who publishes it rather than by a link on your site
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://www.chargebee.com/docs/billing/2.0/site-configuration/api_keys.md
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for chargebee.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.