--- title: "Waymark report for chargebee.com" canonical: "https://waymark.genedai.me/score/chargebee.com" last-updated: "2026-08-26T16:17:28.811Z" --- # Waymark report for chargebee.com Waymark scored chargebee.com 63.2/100 (C) on 26 Aug 2026. Score: 63.2/100 — Blockers remain Scanned: 2026-08-26T16:17:28.811Z Canonical report: https://waymark.genedai.me/score/chargebee.com ## Layer breakdown - Discovery: 15.4/20 (12 of 18 eligible checks passed) - Access: 18.9/30 (15 of 29 eligible checks passed) - Usability: 22.7/40 (7 of 13 eligible checks passed) - Payments: N/A (excluded from the denominator) ## Findings ### 1. AGENTS.md - Layer: discovery - Result: failed - Evidence: agents.md status 404. - Recommended fix: Publish /agents.md with agent-oriented usage notes. ### 2. Well-known AI catalog - Layer: discovery - Result: failed - Evidence: No ai-plugin.json or ai-catalog.json. - Recommended fix: Add /.well-known/ai-plugin.json or /.well-known/ai-catalog.json. ### 3. OpenAPI / Swagger link - Layer: access - Result: failed - Evidence: No OpenAPI/Swagger link in HTML. - Recommended fix: Link to an OpenAPI or Swagger document from the homepage. ### 4. RSS or Atom feed - Layer: access - Result: failed - Evidence: No RSS/Atom link. - Recommended fix: Expose an RSS or Atom feed for machine subscribers. ### 5. CORS / API hint - Layer: access - Result: partial - Evidence: No CORS header or obvious API path. - Recommended fix: If you expose an API, send Access-Control-Allow-Origin for intended clients. ### 6. OAuth / OIDC well-known - Layer: access - Result: partial - Evidence: No oauth-authorization-server or openid-configuration. - Recommended fix: Publish /.well-known/openid-configuration or oauth-authorization-server if you authenticate agents. ### 7. Login or docs link - Layer: access - Result: failed - Evidence: No login/docs/developers link. - Recommended fix: Link to login and developer documentation from the homepage. ### 8. llms-full.txt - Layer: discovery - Result: failed - Evidence: llms-full.txt status 404. - Recommended fix: Optionally publish /llms-full.txt for one-shot ingest. ### 9. HTTP Link header - Layer: discovery - Result: failed - Evidence: No rel=sitemap|describedby|api-catalog|alternate on homepage. - Recommended fix: Send RFC 8288 Link headers for related machine resources. ### 10. MCP initialize - Layer: usability - Result: failed - Evidence: No MCP card to initialize - Recommended fix: Expose Streamable HTTP MCP and answer initialize. ### 11. ai-plugin.json - Layer: discovery - Result: failed - Evidence: No /.well-known/ai-plugin.json. - Recommended fix: Optionally publish a plugin-style capability manifest. ### 12. security.txt - Layer: access - Result: failed - Evidence: No /.well-known/security.txt Contact. - Recommended fix: Publish /.well-known/security.txt with a Contact field. ### 13. change-password well-known - Layer: access - Result: failed - Evidence: Login surface without /.well-known/change-password. - Recommended fix: If users have passwords, serve /.well-known/change-password. ### 14. Rate limit signal - Layer: usability - Result: partial - Evidence: API surface without a rate-limit signal. - Recommended fix: Document or send rate-limit headers on APIs. ### 15. Idempotency signal - Layer: usability - Result: partial - Evidence: API surface without idempotency notes. - Recommended fix: Document idempotency keys for mutating calls. ### 16. Machine-readable errors - Layer: usability - Result: partial - Evidence: API surface without a JSON error shape. - Recommended fix: Return a JSON or problem+json error body. ### 17. OpenAPI document - Layer: access - Result: failed - Evidence: OpenAPI probe. - Recommended fix: Publish an OpenAPI document at a stable URL. ### 18. MCP server - Layer: usability - Result: partial - Evidence: MCP mentioned without a documented initialize. - Recommended fix: Publish an MCP card or document the MCP URL in llms.txt, then answer initialize. ### 19. Trust pages - Layer: access - Result: failed - Evidence: No about/privacy/contact link. - Recommended fix: Link about or privacy from the homepage. ### 20. Package homepage match - Layer: discovery - Result: failed - Evidence: No npm package homepage matching chargebee.com. - Recommended fix: Publish an official package whose homepage is this domain. ### 21. Content without JavaScript - Layer: access - Result: partial - Evidence: Raw HTML has 35140 characters but no H1. - Recommended fix: Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML. ### 22. Agent instruction / when-to-use - Layer: access - Result: failed - Evidence: Agent file exists without when-to-use guidance. - Recommended fix: Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases. ### 23. llms.txt links resolve - Layer: access - Result: partial - Evidence: 6 real, 2 homepage-shell, 0 dead of 8 sampled links. - Recommended fix: Make every link your llms.txt declares resolve to real content, not a homepage shell 200. ### 24. Markdown frontmatter metadata - Layer: access - Result: failed - Evidence: Served markdown has no YAML frontmatter block. - Recommended fix: Open served markdown with a --- frontmatter block carrying title plus description, canonical, or last-updated. ### 25. Accessible document structure - Layer: usability - Result: failed - Evidence: Homepage HTML lacks main/nav/H1 document structure. - Recommended fix: Give the homepage a main region, nav, H1, and a heading order that does not skip levels. ### 26. Agent-UA markdown docs - Layer: access - Result: failed - Evidence: Docs host did not serve markdown to GPTBot (HTTP 200, text/html). - Recommended fix: Serve text/markdown to GPTBot (and similar agent UAs) on your docs host. ## Interpretation Public technical snapshot; not a guarantee of task completion. Private and authenticated workflows are outside this scan. Cite scanned_at and the canonical report URL; the URL serves the latest completed snapshot and can change after a rescan. The official Waymark score is Discovery 20 / Access 30 / Usability 40 / Payments 10. N/A and scanner-error checks drop out of the denominator; they are not scored as failures. An observed agent journey is supporting evidence and does not change the numeric score.