Chargebee vs Recurly
Chargebee
Chargebee Inc.
Recurly
Recurly, Inc.
Chargebee wins · 20–10 (21 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round drawnA live probe confirms llms.txt returns HTTP 200 with a proper agent-oriented summary of the API reference, and docs are also served in .md format for direct agent consumption, alongside first-party MCP server docs for agent tool access. Missing for 10: no independent/community confirmation of agents actually using llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://apidocs.chargebee.com/llms.txt # Chargebee API Reference > REST API reference for Chargebee Billing. Th…”
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
- [claimed-docs] “Connect AI clients such as Cursor, Claude, ChatGPT, Codex, and other MCP-compatible tools to Chargebee MCP Servers to securely access select…”
A live llms.txt is confirmed via direct probe (HTTP 200) at docs.recurly.com/llms.txt, and Recurly also documents a public MCP server (Compass) that connects AI dev tools directly to its documentation and API knowledge, giving agents a first-party structured path to Recurly's docs. missing for 10: independent/community confirmation of agents actually using these endpoints successfully.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.recurly.com/llms.txt # Recurly Documentation Documentation > Welcome to the Recurly Documentation …”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to ChargebeeChargebee exposes a full REST API (Basic Auth, JSON) plus SDKs like Node.js, which can be scripted and called from CI pipelines without a UI, and an API Explorer confirms programmatic testing is possible outside the UI. However, there is no explicit CI/CD documentation, no official CLI, and no example pipelines or automation recipes demonstrating headless CI usage. missing for 10: CI/CD-specific docs or examples, an official CLI tool, and evidence of automated pipeline integration beyond generic API/SDK access.
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
- [claimed-docs] “Node.js — /docs/sdks/nodejs - Install: npm install chargebee”
- [claimed-docs] “The API Explorer lets you make live API calls in a browser using a guided interface. Use it to test endpoints without writing code.”
Recurly offers a full REST API and official client libraries (Ruby, Node, Python, .NET, Java, PHP, Go) which could be scripted headlessly in CI, but there is no explicit documentation of a CLI, CI/CD examples, or automation-focused tooling for headless/agentic workflows. missing for 10: explicit CI/headless usage examples, a documented CLI tool, evidence of non-interactive/automation-first design beyond generic API/SDK availability.
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [claimed-docs] “The Recurly Native Mobile SDKs allow you to integrate recurrent payments in your existing Android or iOS apps in a matter of minutes.”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round drawnChargebeenone0/10Evidence only shows Chargebee exposes MCP servers for external AI clients (Cursor, Claude, ChatGPT) to consume Chargebee's own tools, i.e. Chargebee acts as the MCP server, not as a client plugging in third-party MCP servers to gain their tools. There is no documentation or example of Chargebee's AI features consuming external MCP servers. Missing for 10: any evidence of Chargebee acting as an MCP client, configuration for adding external MCP server endpoints, or first-party support for extending its AI assistant with third-party MCP tool servers.
- [claimed-docs] “Connect AI clients such as Cursor, Claude, ChatGPT, Codex, and other MCP-compatible tools to Chargebee MCP Servers to securely access select…”
- [claimed-docs] “Custom MCP servers let you combine tools from Chargebee's full tool catalog into a server tailored to your use case—for example, an invoice …”
- [claimed-docs] “Use AI inside the Chargebee Billing UI to answer questions and complete tasks.”
- [probe] “official MCP server documented at https://www.chargebee.com/docs/billing/2.0/ai-in-chargebee/chargebee-mcp”
Recurlynone0/10Evidence only shows Recurly publishing its own MCP server (Compass) so external AI tools can query Recurly's docs/API — this is Recurly acting as an MCP server provider, not as a client that can plug in and use other MCP servers' tools. No evidence Recurly itself can consume/plug in external MCP servers.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
ai-native userConnect an agent via an official MCP server
weight 3 · round to ChargebeeChargebee documents official MCP Servers that let AI clients (Cursor, Claude, ChatGPT, Codex, etc.) connect and access selected Chargebee capabilities, plus a custom MCP server builder for tailored tool sets, confirmed via docs and a probe hit. Missing for 10: independent/hands-on third-party corroboration of the MCP server working in practice.
- [claimed-docs] “Connect AI clients such as Cursor, Claude, ChatGPT, Codex, and other MCP-compatible tools to Chargebee MCP Servers to securely access select…”
- [claimed-docs] “Custom MCP servers let you combine tools from Chargebee's full tool catalog into a server tailored to your use case—for example, an invoice …”
- [probe] “official MCP server documented at https://www.chargebee.com/docs/billing/2.0/ai-in-chargebee/chargebee-mcp”
Recurly ships an official 'Compass' MCP server that connects AI dev tools directly to Recurly's documentation and API knowledge, confirmed both in docs and via a live probe of the docs page. However, evidence only describes it as a documentation/knowledge connector, not a full agentic interface for performing billing actions (e.g., managing subscriptions, invoices) via MCP. Missing for 10: evidence of MCP tool-calling for actual account/subscription operations, independent hands-on validation of the MCP server in use.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
ai-native userUse an official CLI
weight 2 · round drawnChargebeenone0/10Evidence shows SDKs (Node.js), REST API, and MCP servers, but there is no mention of an official CLI tool for Chargebee. Missing for 10: any documentation or evidence of an official CLI, install instructions, or command-line usage.
Recurlynone0/10No evidence of an official Recurly CLI; documentation instead references client libraries (Ruby, Node.js, Python, etc.), mobile SDKs, and an MCP server for AI tools, but nothing about a command-line interface.
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [claimed-docs] “The Recurly Native Mobile SDKs allow you to integrate recurrent payments in your existing Android or iOS apps in a matter of minutes.”
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
ai-native userDrive the product through a documented public API
weight 3 · round drawnChargebee documents a full REST API with auth, JSON responses, SDKs, an API Explorer for live testing, and an llms.txt reference confirming API v2 coverage — this is a clearly documented, drivable public API. Missing for 10: publicly hosted OpenAPI/swagger spec (probe found 404s) and independent third-party corroboration of API robustness.
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
- [claimed-docs] “Node.js — /docs/sdks/nodejs - Install: npm install chargebee”
- [claimed-docs] “The API Explorer lets you make live API calls in a browser using a guided interface. Use it to test endpoints without writing code.”
- [probe] “PROBE llms.txt: HTTP 200 at https://apidocs.chargebee.com/llms.txt # Chargebee API Reference > REST API reference for Chargebee Billing. Th…”
- [probe] “PROBE openapi: all candidate paths 404 (https://apidocs.chargebee.com/openapi.json, https://apidocs.chargebee.com/swagger.json, https://apid…”
Recurly documents a full public API with official client libraries in seven languages, entitlements checkable via API, and even an MCP server (Compass) exposing API/doc knowledge to AI tools, indicating strong API-first, AI-accessible design. missing for 10: independent developer corroboration of API robustness/rate limits and no evidence of API versioning or webhooks documentation depth.
- [claimed-docs] “Entitlements can be applied across platforms (web, mobile, and app stores) and checked in real time via the Recurly API.”
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.recurly.com/llms.txt # Recurly Documentation Documentation > Welcome to the Recurly Documentation …”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to ChargebeeChargebee's API uses HTTP Basic Auth with API keys and offers custom MCP servers that can be scoped to a subset of the tool catalog (e.g., invoice-only), suggesting some ability to limit an agent's surface area, but there is no documented support for scoped/least-privilege API key roles, granular permission scopes, or agent-specific credential issuance in the core REST API. missing for 10: explicit API key roles/permission scopes documentation, least-privilege credential issuance workflow for agents, independent verification that custom MCP server scoping enforces true least-privilege access control.
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
- [claimed-docs] “Custom MCP servers let you combine tools from Chargebee's full tool catalog into a server tailored to your use case—for example, an invoice …”
- [probe] “official MCP server documented at https://www.chargebee.com/docs/billing/2.0/ai-in-chargebee/chargebee-mcp”
Recurlynone0/10No evidence of scoped or least-privilege API key/credential issuance for agents; the MCP server (recurly-docs-12, recurly-probe-2) only connects AI tools to documentation, not scoped API credentials, and no API key management or permission-scoping docs are present.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
ai-native userBuild against official SDKs
weight 2 · round to RecurlyChargebee documents official SDKs (e.g., Node.js via npm) and a REST API with docs, satisfying the core 'build against official SDKs' ask, but evidence only lists one SDK explicitly and lacks broader SDK language coverage, versioning, or independent developer corroboration; OpenAPI spec discovery also failed in probes. Missing for 10: multi-language SDK list/documentation depth, independent hands-on validation, discoverable OpenAPI/schema artifacts.
- [claimed-docs] “Node.js — /docs/sdks/nodejs - Install: npm install chargebee”
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
- [probe] “PROBE openapi: all candidate paths 404 (https://apidocs.chargebee.com/openapi.json, https://apidocs.chargebee.com/swagger.json, https://apid…”
Recurly documents official client libraries across seven languages (Ruby, Node.js, Python, .NET, Java, PHP, Go) plus native mobile SDKs for iOS/Android, giving AI-native developers a solid multi-language SDK surface, and an official Compass MCP server ties AI tools into its API docs. Missing for 10: independent hands-on developer confirmation of SDK quality/reliability and no explicit mention of AI-specific SDK tooling beyond the MCP docs connector.
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [claimed-docs] “The Recurly Native Mobile SDKs allow you to integrate recurrent payments in your existing Android or iOS apps in a matter of minutes.”
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
ai-native userSubscribe to events via webhooks
weight 2 · round to ChargebeeChargebee documents event-driven webhooks (events trigger configured webhooks) and community evidence confirms multiple webhook URLs can be configured for different environments, showing real-world subscription-to-events usage. missing for 10: no detailed webhook payload/signature-verification docs, no explicit AI-agent-oriented subscription workflow beyond generic webhook config, and no independent hands-on verification beyond the one HN mention.
- [claimed-docs] “If webhooks are configured in Chargebee, events trigger those webhooks.”
- [community] “With Chargebee I can add multiple webhook URLs, so all events get sent to both dev and staging and each environment only cares about its own…”
The only mention of webhooks in the evidence pack is an indirect community comparison noting Recurly automates retention 'without needing to implement webhooks' for dunning, implying webhook functionality exists, but no first-party documentation, API reference, or event-list evidence describes how to subscribe to or configure webhooks. Missing for 10: official webhook API/docs, list of subscribable events, setup instructions, and any AI-agent-specific webhook integration guidance.
- [community] “Comparing Stripe and Recurly: It's faster to get going with Stripe (no merchant account required) but Recurly appears to offer more automate…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to ChargebeeChargebee docs describe an in-product AI assistant ('Use AI inside the Chargebee Billing UI to answer questions and complete tasks') and AI that can draft plans/pricing from documents, which are in-product AI-driven capabilities, but there's no evidence of proactive AI-generated insights or suggestions derived from the customer's own billing/subscription data (e.g., churn risk, revenue anomalies) — the described features skew toward Q&A and configuration drafting rather than data-driven insight generation. Missing for 10: evidence of analytics-style insights/suggestions surfaced from account data, and independent/hands-on validation of the AI assistant's usefulness.
- [claimed-docs] “Use AI inside the Chargebee Billing UI to answer questions and complete tasks.”
- [claimed-docs] “Let Chargebee AI draft product families, plans, addons, charges, prices, features, and entitlements from a pricing page, document, or descri…”
- [claimed-docs] “Connect AI clients such as Cursor, Claude, ChatGPT, Codex, and other MCP-compatible tools to Chargebee MCP Servers to securely access select…”
Recurlynone0/10No evidence Recurly generates AI-driven insights or suggestions from a merchant's own subscription/billing data; the only AI-related feature (Compass MCP) merely connects AI dev tools to documentation/API knowledge, not to account data analytics.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnChargebee offers webhooks, dunning/smart retry, and MCP servers that let AI clients access billing capabilities, which could underpin background automations, but there's no direct evidence of a scheduler or agent-orchestration feature that runs autonomous, unattended workflows over time. missing for 10: explicit autonomous/background automation or workflow engine documentation, evidence of scheduled/triggered agentic tasks, independent confirmation of unattended operation.
- [claimed-docs] “If webhooks are configured in Chargebee, events trigger those webhooks.”
- [claimed-docs] “Connect AI clients such as Cursor, Claude, ChatGPT, Codex, and other MCP-compatible tools to Chargebee MCP Servers to securely access select…”
- [claimed-docs] “Custom MCP servers let you combine tools from Chargebee's full tool catalog into a server tailored to your use case—for example, an invoice …”
- [claimed-docs] “With Chargebee's Dunning feature, you can send email reminders to your customers asking them to update payment details and schedule payment …”
- [claimed-docs] “Chargebee's Smart retry logic retries payments at dynamic intervals based on the type of gateway transaction errors, and it acts on the hard…”
- [probe] “official MCP server documented at https://www.chargebee.com/docs/billing/2.0/ai-in-chargebee/chargebee-mcp”
Recurly ships built-in autonomous background processes—dunning campaigns (up to 50 targeted campaigns), automatic backup payment method fallback, and involuntary churn recovery tools—that run without manual intervention once configured. However, there is no evidence of a general-purpose automation/workflow builder, triggers, or agent-configurable rules engine that an AI-native user could set up beyond these fixed billing-retention features. Missing for 10: a configurable automation/rules engine, evidence of user-defined triggers/actions beyond dunning, and any AI-agent-specific automation tooling.
- [claimed-docs] “merchants on Professional and Elite plans can create up to 50 targeted campaigns for different customer segments or plans”
- [claimed-docs] “Involuntary churn happens when customers are lost due to factors outside their intent — expired cards, bank changes, or failed payments. Rec…”
- [claimed-docs] “Let customers designate a backup payment method so service continues automatically if their primary payment fails.”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to ChargebeeChargebee documents a built-in AI assistant inside the Billing UI that can 'answer questions and complete tasks' and draft pricing/product configurations from a description, showing real in-product task delegation (chargebee-docs-16, chargebee-docs-14). However, the primary AI-native evidence emphasizes MCP servers for external AI clients (Cursor, Claude, ChatGPT) rather than a deeply documented native assistant experience, and there is no independent/hands-on corroboration of the in-app assistant's task scope or reliability. missing for 10: independent verification of the built-in assistant's capabilities, detail on task types beyond drafting/answering, and community evidence confirming real-world use.
- [claimed-docs] “Use AI inside the Chargebee Billing UI to answer questions and complete tasks.”
- [claimed-docs] “Let Chargebee AI draft product families, plans, addons, charges, prices, features, and entitlements from a pricing page, document, or descri…”
- [claimed-docs] “Connect AI clients such as Cursor, Claude, ChatGPT, Codex, and other MCP-compatible tools to Chargebee MCP Servers to securely access select…”
Recurlynone0/10Recurly is a subscription billing platform; evidence shows an MCP server for connecting AI dev tools to documentation/API knowledge, but nothing indicates a built-in AI assistant within the product that users can delegate tasks to.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
ai-native userOperate the product with natural-language commands
weight 2 · round to ChargebeeChargebee documents an in-product AI assistant that lets users 'answer questions and complete tasks' via natural language inside the Billing UI, plus AI-driven drafting of pricing/plans from a description, and MCP servers that let external AI clients (Cursor, Claude, ChatGPT) operate Chargebee capabilities conversationally. This is first-party doc evidence only, with no independent/hands-on corroboration of how robust or complete the natural-language command coverage actually is. Missing for 10: independent/hands-on validation of the AI assistant's command coverage, and detail on which actions can be fully executed vs. only queried via natural language.
- [claimed-docs] “Use AI inside the Chargebee Billing UI to answer questions and complete tasks.”
- [claimed-docs] “Let Chargebee AI draft product families, plans, addons, charges, prices, features, and entitlements from a pricing page, document, or descri…”
- [claimed-docs] “Connect AI clients such as Cursor, Claude, ChatGPT, Codex, and other MCP-compatible tools to Chargebee MCP Servers to securely access select…”
- [claimed-docs] “Custom MCP servers let you combine tools from Chargebee's full tool catalog into a server tailored to your use case—for example, an invoice …”
- [probe] “official MCP server documented at https://www.chargebee.com/docs/billing/2.0/ai-in-chargebee/chargebee-mcp”
Recurly's Compass MCP server lets AI dev tools query Recurly's documentation and API knowledge, which is a step toward AI-native/agentic interaction, but the evidence describes it as a knowledge/docs connector rather than a natural-language interface for actually executing billing operations (e.g., changing subscriptions, issuing credits) end-to-end. Missing for 10: evidence of natural-language command execution for actual account/subscription actions, hands-on proof of the MCP server performing operations (not just doc lookup), and any client-facing chat/NL interface.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to ChargebeeChargebee documents an API Explorer that lets users make live API calls in a browser with a guided interface to test endpoints without writing code, which matches the interactive/runnable-example story. However, no OpenAPI spec was discoverable via probe (all candidate paths 404), and there's no independent/hands-on corroboration of the explorer's depth or coverage. Missing for 10: discoverable OpenAPI/Swagger spec, independent/hands-on validation of the API Explorer's runnable examples across endpoints.
- [claimed-docs] “The API Explorer lets you make live API calls in a browser using a guided interface. Use it to test endpoints without writing code.”
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
- [probe] “PROBE openapi: all candidate paths 404 (https://apidocs.chargebee.com/openapi.json, https://apidocs.chargebee.com/swagger.json, https://apid…”
Recurlynone0/10Evidence shows client libraries, SDKs, an MCP server for docs/API knowledge, and an llms.txt file, but there is no mention of an interactive API reference with runnable/live-executable examples (e.g., a try-it-now console). Missing for 10: interactive API console, runnable code examples, in-browser execution/testing of API calls.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.recurly.com/llms.txt # Recurly Documentation Documentation > Welcome to the Recurly Documentation …”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnChargebeenone0/10Direct probes for standard OpenAPI/Swagger spec locations all returned 404, and no documentation page claims a downloadable OpenAPI/machine-readable spec exists; only an llms.txt index and human-readable markdown docs were found.
- [probe] “PROBE openapi: all candidate paths 404 (https://apidocs.chargebee.com/openapi.json, https://apidocs.chargebee.com/swagger.json, https://apid…”
- [probe] “PROBE llms.txt: HTTP 200 at https://apidocs.chargebee.com/llms.txt # Chargebee API Reference > REST API reference for Chargebee Billing. Th…”
- [probe] “PROBE docs-md: HTTP 404 at https://apidocs.chargebee.com/docs/api/getting-started.md.md”
Recurlynone0/10The evidence pack shows official client libraries, mobile SDKs, an llms.txt file, and an MCP server, but no mention of a downloadable OpenAPI/Swagger spec or any machine-readable API schema file. Since Recurly is an API-based product, this axis clearly applies, but there is no evidence of the specific capability requested.
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.recurly.com/llms.txt # Recurly Documentation Documentation > Welcome to the Recurly Documentation …”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to ChargebeeEvidence shows Chargebee supports separate dev/staging environments (webhooks routed independently per environment) and an API Explorer for testing endpoints without code, implying some sandbox-like testing capability, but there is no explicit documentation of a dedicated sandbox/test site that guarantees production data isolation for AI-driven testing. Missing for 10: explicit sandbox/test-mode documentation, confirmation that API keys or MCP tools can target a non-production environment, and first-party guidance on avoiding production data during AI testing.
- [claimed-docs] “The API Explorer lets you make live API calls in a browser using a guided interface. Use it to test endpoints without writing code.”
- [community] “With Chargebee I can add multiple webhook URLs, so all events get sent to both dev and staging and each environment only cares about its own…”
Recurlynone0/10No evidence pack item mentions a sandbox, test/dev environment, or test API keys for Recurly; documentation covers subscription changes, billing, and MCP tooling but not isolated test environments. Missing for 10: any mention of sandbox/test mode, test credentials, or separation from production data.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to ChargebeeEvidence shows Chargebee's API is versioned (API v2, Product Catalog) per the llms.txt probe, but there is no documentation of a deprecation policy, sunset timeline, or migration guidance for older API versions anywhere in the pack. Missing for 10: explicit deprecation/sunset policy docs, versioning changelog, migration guide for deprecated endpoints, independent confirmation of long-term API stability.
- [probe] “PROBE llms.txt: HTTP 200 at https://apidocs.chargebee.com/llms.txt # Chargebee API Reference > REST API reference for Chargebee Billing. Th…”
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to ChargebeeChargebee's REST API, SDKs, and Export resource allow programmatic access to many records at once (e.g. bulk export jobs), and its MCP servers let AI clients invoke these API operations, but the evidence never documents a dedicated bulk/batch-update endpoint for mutating many items in a single call — automation would rely on looping single-item API calls. missing for 10: explicit bulk-create/bulk-update API endpoints, documented batch size limits, and independent confirmation of bulk operations working via MCP/AI clients.
- [claimed-docs] “Export resource represents an export job and contains the status of the job and the download URL, if the job is successfully completed.”
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
- [claimed-docs] “Node.js — /docs/sdks/nodejs - Install: npm install chargebee”
- [claimed-docs] “Connect AI clients such as Cursor, Claude, ChatGPT, Codex, and other MCP-compatible tools to Chargebee MCP Servers to securely access select…”
- [claimed-docs] “Custom MCP servers let you combine tools from Chargebee's full tool catalog into a server tailored to your use case—for example, an invoice …”
- [probe] “official MCP server documented at https://www.chargebee.com/docs/billing/2.0/ai-in-chargebee/chargebee-mcp”
Recurly's docs mention bulk data import/export to populate accounts and analyze records, which implies some bulk operation support, and API client libraries could theoretically be used to script batch changes. However, there is no explicit documentation of a bulk-update/bulk-cancel/bulk-modify API for subscriptions, invoices, or entitlements, nor any AI-native tooling for orchestrating such bulk actions. missing for 10: explicit bulk subscription/invoice update API, bulk operation endpoints or SDK examples, evidence of AI-driven or agentic bulk workflows, independent confirmation of bulk import scale/performance.
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Import customer data to populate accounts and records across your Recurly account.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to ChargebeeChargebee supports event-driven automation via webhooks (events trigger webhooks, multiple URLs supported) and has built-in automated actions like Dunning email reminders and Smart Retry logic that act on transaction event types, but there's no evidence of a general-purpose, user-configurable rules/workflow engine where an AI-native user can define arbitrary 'if event X then action Y' rules beyond these pre-built billing automations. Missing for 10: a documented rules/workflow builder or automation engine, evidence of custom trigger-action definitions beyond webhooks/dunning/retries, and independent confirmation of flexibility.
- [claimed-docs] “If webhooks are configured in Chargebee, events trigger those webhooks.”
- [community] “With Chargebee I can add multiple webhook URLs, so all events get sent to both dev and staging and each environment only cares about its own…”
- [claimed-docs] “With Chargebee's Dunning feature, you can send email reminders to your customers asking them to update payment details and schedule payment …”
- [claimed-docs] “Chargebee's Smart retry logic retries payments at dynamic intervals based on the type of gateway transaction errors, and it acts on the hard…”
Recurly ships built-in automated responses to specific billing events—dunning campaigns triggered by failed payments (up to 50 targeted campaigns) and automatic fallback to backup payment methods—but these are pre-defined behaviors within fixed billing workflows, not a general-purpose rule engine where users define arbitrary event→action logic. Missing for 10: a configurable trigger/condition/action framework (e.g., custom webhooks-driven rules, if-this-then-that automation builder) and evidence of user-defined (not just Recurly-provided) automation logic.
- [claimed-docs] “merchants on Professional and Elite plans can create up to 50 targeted campaigns for different customer segments or plans”
- [claimed-docs] “Involuntary churn happens when customers are lost due to factors outside their intent — expired cards, bank changes, or failed payments. Rec…”
- [claimed-docs] “Let customers designate a backup payment method so service continues automatically if their primary payment fails.”
- [community] “Comparing Stripe and Recurly: It's faster to get going with Stripe (no merchant account required) but Recurly appears to offer more automate…”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to RecurlyChargebeenone0/10Chargebee's evidence covers recurring billing cycles, dunning retry schedules, and async export jobs, but these are internal billing mechanics, not a user- or AI-schedulable job/workflow automation feature (e.g., no API endpoint or MCP tool to create/schedule arbitrary recurring workflows). The MCP server evidence describes connecting AI clients to Chargebee's data/tools, not job scheduling.
- [claimed-docs] “With Chargebee's Dunning feature, you can send email reminders to your customers asking them to update payment details and schedule payment …”
- [claimed-docs] “Chargebee's Smart retry logic retries payments at dynamic intervals based on the type of gateway transaction errors, and it acts on the hard…”
- [claimed-docs] “Multi-frequency billing: Subscriptions are billed according to the billing period of each recurring item price within the subscription, whet…”
- [claimed-docs] “Export resource represents an export job and contains the status of the job and the download URL, if the job is successfully completed.”
- [claimed-docs] “Connect AI clients such as Cursor, Claude, ChatGPT, Codex, and other MCP-compatible tools to Chargebee MCP Servers to securely access select…”
Recurly's core product is built around recurring billing cycles that run automatically (subscription renewals, usage-based billing at cycle end, dunning email campaigns), which functions as a domain-specific recurring workflow engine, but it offers no general-purpose job/task scheduler an AI-native user could configure for arbitrary recurring workflows. Missing for 10: a generic scheduling/automation API or cron-like mechanism for arbitrary AI-driven tasks, and any evidence of AI-agent-triggered scheduling beyond built-in billing cycles.
- [claimed-docs] “Recurly's usage-based billing model lets you charge customers at the end of each billing cycle based on their actual consumption”
- [claimed-docs] “merchants on Professional and Elite plans can create up to 50 targeted campaigns for different customer segments or plans”
- [claimed-docs] “Involuntary churn happens when customers are lost due to factors outside their intent — expired cards, bank changes, or failed payments. Rec…”
- [claimed-docs] “Recurly bills only the difference during an immediate change when the underlying plan is unchanged.”
ai-native userVersion, review, and roll back my automations
weight 1 · round drawnChargebeenone0/10No evidence of any versioning, review, or rollback capability for automations (e.g., workflow/automation revision history or undo) in Chargebee's docs — only export jobs, webhooks, and MCP AI access are mentioned, none of which describe automation change tracking or rollback.
Recurlynone0/10No evidence of version control, review workflows, or rollback for automations/workflows in Recurly; the docs cover subscription/billing config changes, dunning campaigns, and an MCP server for documentation access, but none describe versioning, audit/review, or rollback of automations themselves.
Billing agent access — stories about billing agent access in this arenaBilling agent access
Stories about billing agent access in this arena
Agent operations
ai-native userAn agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissions
weight 3 · round to ChargebeeChargebee has a full REST API (with Basic Auth, SDKs) that supports subscription creation, plan changes, and credits, plus an official MCP server that exposes 'selected capabilities' to AI clients like Cursor/Claude/ChatGPT, and custom MCP servers that scope which tools are exposed. This directly supports agent-driven billing operations with some permission scoping, but evidence doesn't confirm granular scoped-permission models (e.g., per-action API keys) for agents beyond curated tool subsets, nor independent/hands-on validation of agent-driven write operations. missing for 10: documented fine-grained scoped API-key/OAuth permission model for agent use, independent/hands-on evidence of an agent successfully executing subscription/credit/plan-change operations via MCP or API.
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
- [claimed-docs] “An item price is compatible with a plan-item price if their currencies are the same.”
- [claimed-docs] “Connect AI clients such as Cursor, Claude, ChatGPT, Codex, and other MCP-compatible tools to Chargebee MCP Servers to securely access select…”
- [claimed-docs] “Custom MCP servers let you combine tools from Chargebee's full tool catalog into a server tailored to your use case—for example, an invoice …”
- [claimed-docs] “Use AI inside the Chargebee Billing UI to answer questions and complete tasks.”
- [probe] “official MCP server documented at https://www.chargebee.com/docs/billing/2.0/ai-in-chargebee/chargebee-mcp”
Recurly exposes a full REST API and client libraries covering subscription changes, credits, and invoices (recurly-docs-1, -2, -9, -13), which could technically be driven by an agent. However, the only AI-specific surface documented, Recurly Compass MCP, is explicitly a documentation/knowledge connector for AI dev tools, not an operational interface for executing billing actions (recurly-docs-12, recurly-probe-2), and there is no evidence of scoped/restricted API keys or permission models designed for autonomous agent use. Missing for 10: an agent-oriented action interface (e.g., MCP server or agent SDK) that can actually invoke billing operations, and documentation of scoped/least-privilege API credentials for agent access.
- [claimed-docs] “Recurly gives you full control over how and when subscription changes take effect. Upgrade or downgrade a plan, adjust quantity or price, ad…”
- [claimed-docs] “Recurly bills only the difference during an immediate change when the underlying plan is unchanged.”
- [claimed-docs] “Credit invoices give every credit its own distinct invoice — separate from charge invoices.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
Agent queries
ai-native userAn agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directly
weight 2 · round to ChargebeeChargebee offers a REST API for querying subscriptions, invoices, and account data (chargebee-docs-1) plus official MCP servers letting AI clients like Cursor, Claude, ChatGPT and Codex 'securely access selected capabilities' including subscription/invoice lookups (chargebee-docs-7, chargebee-docs-8, chargebee-probe-4), directly enabling agent-driven billing queries. Missing for 10: explicit documented support for MRR/delinquent-account aggregate queries via MCP or API, and independent/hands-on confirmation that the MCP server reliably answers such billing-state questions.
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
- [claimed-docs] “Connect AI clients such as Cursor, Claude, ChatGPT, Codex, and other MCP-compatible tools to Chargebee MCP Servers to securely access select…”
- [claimed-docs] “Custom MCP servers let you combine tools from Chargebee's full tool catalog into a server tailored to your use case—for example, an invoice …”
- [claimed-docs] “Use AI inside the Chargebee Billing UI to answer questions and complete tasks.”
- [probe] “official MCP server documented at https://www.chargebee.com/docs/billing/2.0/ai-in-chargebee/chargebee-mcp”
Recurly exposes a REST API and official client libraries that could let an agent fetch account/invoice/subscription data, and entitlements are described as checkable in real time via the API. However, the only AI-agent integration evidenced (Compass MCP) is explicitly scoped to documentation and API knowledge, not live billing-state queries, and there is no evidence of dedicated endpoints/reports for MRR, delinquent-account lists, or renewal forecasts that an agent could query directly. missing for 10: evidence of an MCP or agent-facing endpoint returning MRR/delinquency/renewal data, documentation of a reporting/analytics API for these metrics, independent confirmation of agent-driven billing queries working in practice.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [claimed-docs] “Entitlements can be applied across platforms (web, mobile, and app stores) and checked in real time via the Recurly API.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [claimed-docs] “Modify invoice details post-issuance — including account notes, due dates, PO numbers, customer notes, and terms — to keep records accurate.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
Billing math — stories about billing math in this arenaBilling math
Stories about billing math in this arena
Billing cycles
ops userControl billing anchors and cycles — calendar vs anniversary billing, alignment across a customer's subscriptions, custom invoice dates
weight 2 · round to RecurlyChargebeenone0/10The evidence pack contains no documentation on billing anchor dates, calendar-vs-anniversary billing choice, cross-subscription date alignment, or custom invoice date control — only generic multi-frequency billing (chargebee-docs-15) which doesn't address anchor/alignment mechanics. Missing for 10: docs on billing anchor/alignment settings, calendar vs anniversary billing options, custom invoice date configuration.
- [claimed-docs] “Multi-frequency billing: Subscriptions are billed according to the billing period of each recurring item price within the subscription, whet…”
Evidence only shows post-issuance invoice detail edits (due dates, PO numbers, terms) via recurly-docs-10, which loosely touches 'custom invoice dates' but doesn't address billing anchor/cycle configuration. No documentation covers calendar-vs-anniversary billing modes or aligning billing cycles across a customer's multiple subscriptions. Missing for 10: explicit billing anchor/cycle-start configuration, calendar vs anniversary billing toggle, cross-subscription date alignment tooling, and any independent/hands-on confirmation of these mechanics.
- [claimed-docs] “Modify invoice details post-issuance — including account notes, due dates, PO numbers, customer notes, and terms — to keep records accurate.”
Proration
finance leadMid-cycle upgrades and downgrades are prorated with documented, auditable math — credits, partial periods, and invoice line items that reconcile to the penny
weight 3 · round to RecurlyChargebeenone0/10The evidence pack contains only generic API/billing feature docs (usage events, item price compatibility, dunning, RevRec) but nothing about proration mechanics, credit calculations, partial-period invoice line items, or auditable math for upgrades/downgrades. Missing for 10: proration policy docs, credit note reconciliation examples, partial-period invoice line item breakdowns, and any audit-trail evidence.
Recurly's docs confirm mid-cycle changes are billed as prorated differences and that credits get their own separate, dedicated invoices, plus invoices can be amended post-issuance for record accuracy — supporting the core proration/credit reconciliation need. However, there's no documented breakdown of the proration math formula, no explicit audit trail feature, and no evidence (first-party or independent) that invoice reconciliation is verified to the penny in practice. Missing for 10: detailed proration calculation documentation, explicit audit-log/traceability feature, and independent verification of penny-accurate reconciliation.
- [claimed-docs] “Recurly bills only the difference during an immediate change when the underlying plan is unchanged.”
- [claimed-docs] “Credit invoices give every credit its own distinct invoice — separate from charge invoices.”
- [claimed-docs] “Modify invoice details post-issuance — including account notes, due dates, PO numbers, customer notes, and terms — to keep records accurate.”
Dunning recovery — stories about dunning recovery in this arenaDunning recovery
Stories about dunning recovery in this arena
Card recovery
ops userExpiring or replaced cards update themselves — network account updater, backup payment methods, and hosted update-payment pages
weight 2 · round drawnChargebee documents dunning email reminders and smart retry logic for recovering failed payments, which supports part of the dunning-recovery workflow, but the evidence pack contains no explicit mention of network account updater, backup payment methods, or hosted update-payment pages. missing for 10: explicit documentation of network account updater (card auto-refresh via card networks), backup/secondary payment method fallback, and hosted payment page update flows for customers.
- [claimed-docs] “With Chargebee's Dunning feature, you can send email reminders to your customers asking them to update payment details and schedule payment …”
- [claimed-docs] “Chargebee's Smart retry logic retries payments at dynamic intervals based on the type of gateway transaction errors, and it acts on the hard…”
Docs confirm backup payment methods and general 'tools to proactively catch and resolve' involuntary churn from expired cards/failed payments, but the evidence pack never explicitly names or documents a network account updater feature or hosted update-payment pages. missing for 10: explicit documentation of account updater integration, explicit hosted update-payment page feature, and any hands-on confirmation these self-heal expiring cards.
- [claimed-docs] “Involuntary churn happens when customers are lost due to factors outside their intent — expired cards, bank changes, or failed payments. Rec…”
- [claimed-docs] “Let customers designate a backup payment method so service continues automatically if their primary payment fails.”
Dunning comms
ops userConfigure automated dunning sequences — branded emails, in-app banners, grace periods, and final-state rules like cancel vs unpaid
weight 2 · round drawnDocs confirm Chargebee's Dunning feature sends email reminders and schedules smart payment retries, covering core automated dunning emails and retry logic, but there is no evidence of in-app banners, configurable grace periods, or explicit cancel-vs-unpaid final-state rule configuration. missing for 10: in-app banner support, grace period configuration, final-state (cancel vs unpaid) rule documentation, branding/customization details for dunning emails.
- [claimed-docs] “With Chargebee's Dunning feature, you can send email reminders to your customers asking them to update payment details and schedule payment …”
- [claimed-docs] “Chargebee's Smart retry logic retries payments at dynamic intervals based on the type of gateway transaction errors, and it acts on the hard…”
Docs confirm dunning campaigns (up to 50 targeted campaigns) and proactive involuntary-churn tools like backup payment methods, and community evidence corroborates automated dunning emails as a differentiator vs competitors. However, there's no documentation of branded email customization, in-app banners, configurable grace periods, or final-state rules distinguishing cancel vs unpaid outcomes. missing for 10: branded email templates/customization, in-app banner support, grace period configuration, and cancel-vs-unpaid final-state rule settings.
- [claimed-docs] “merchants on Professional and Elite plans can create up to 50 targeted campaigns for different customer segments or plans”
- [claimed-docs] “Involuntary churn happens when customers are lost due to factors outside their intent — expired cards, bank changes, or failed payments. Rec…”
- [claimed-docs] “Let customers designate a backup payment method so service continues automatically if their primary payment fails.”
- [community] “Comparing Stripe and Recurly: It's faster to get going with Stripe (no merchant account required) but Recurly appears to offer more automate…”
- [community] “Chargify finally has statements. Recurly has a large emphasis on making sure your customers are retained -- so much so that they added their…”
Smart retries
finance leadFailed renewal payments are retried automatically on an ML- or schedule-optimized cadence that measurably recovers involuntary churn
weight 3 · round to ChargebeeChargebee's docs confirm scheduled dunning retries and "Smart Retry" logic that varies intervals dynamically based on gateway decline type, directly supporting automated, optimized retry cadences aimed at recovering failed renewal payments. However, missing for 10: no quantified recovery-rate data, no explicit claim of ML-based optimization (only 'dynamic intervals based on error type'), and no independent/customer evidence measuring actual involuntary-churn recovery impact.
- [claimed-docs] “With Chargebee's Dunning feature, you can send email reminders to your customers asking them to update payment details and schedule payment …”
- [claimed-docs] “Chargebee's Smart retry logic retries payments at dynamic intervals based on the type of gateway transaction errors, and it acts on the hard…”
Recurly documents dunning management and involuntary-churn tools like targeted campaigns and backup payment methods, and community commentary notes Recurly's automated retention/dunning emails as a differentiator, but there is no evidence of ML-optimized or schedule-optimized retry cadence logic, nor any quantified recovery-rate/churn-reduction metrics. missing for 10: documentation of the actual retry scheduling/ML logic behind payment retries, evidence of adaptive or optimized cadence (vs simple campaign rules), and third-party or first-party data on measurable involuntary churn recovery.
- [claimed-docs] “merchants on Professional and Elite plans can create up to 50 targeted campaigns for different customer segments or plans”
- [claimed-docs] “Involuntary churn happens when customers are lost due to factors outside their intent — expired cards, bank changes, or failed payments. Rec…”
- [claimed-docs] “Let customers designate a backup payment method so service continues automatically if their primary payment fails.”
- [community] “Comparing Stripe and Recurly: It's faster to get going with Stripe (no merchant account required) but Recurly appears to offer more automate…”
- [community] “Chargify finally has statements. Recurly has a large emphasis on making sure your customers are retained -- so much so that they added their…”
Entitlements — stories about entitlements in this arenaEntitlements
Stories about entitlements in this arena
Entitlement checks
developerFeatures and limits are modeled as entitlements attached to plans, and my application can check a customer's entitlements at runtime via API or SDK
weight 3 · round to RecurlyChargebee documents an entitlements/Features model attached to plans, including a UI to manage customer privileges and AI-assisted entitlement creation, and separately documents a general REST API and Node.js SDK. However, no evidence explicitly shows an API/SDK endpoint or method for checking a customer's entitlements at runtime. missing for 10: explicit entitlements-check API endpoint or SDK method, code sample showing runtime lookup, independent/hands-on confirmation of this specific capability.
- [claimed-docs] “Chargebee provides you an efficient UI to allocate and manage the customer privileges using Features.”
- [claimed-docs] “Let Chargebee AI draft product families, plans, addons, charges, prices, features, and entitlements from a pricing page, document, or descri…”
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
- [claimed-docs] “Node.js — /docs/sdks/nodejs - Install: npm install chargebee”
Recurly's docs explicitly describe an entitlements feature that can be checked in real time via the Recurly API across platforms, matching the core of the story. Missing for 10: detailed documentation of how entitlements are attached to specific plans, explicit SDK-level (not just API) entitlement-check examples, and independent/hands-on confirmation of this specific feature.
- [claimed-docs] “Entitlements can be applied across platforms (web, mobile, and app stores) and checked in real time via the Recurly API.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
Plan versioning
ops userChange pricing without breaking existing subscribers — versioned plans, grandfathering, and bulk migration tools for moving cohorts to new prices
weight 2 · round drawnChargebeenone0/10Chargebee's docs describe item prices, subscriptions, and entitlements, but none of the evidence mentions versioned plans, grandfathering existing subscribers, or bulk cohort migration tools for pricing changes. Missing for 10: explicit versioned-plan mechanism, grandfathering documentation, and a bulk subscription migration tool.
Recurlynone0/10Docs only describe changing an individual subscription's plan/price/add-ons (recurly-docs-1, recurly-docs-2); there is no mention of versioned plan definitions, grandfathering existing subscribers on old pricing, or bulk/cohort migration tooling for moving groups of subscribers to new pricing.
- [claimed-docs] “Recurly gives you full control over how and when subscription changes take effect. Upgrade or downgrade a plan, adjust quantity or price, ad…”
- [claimed-docs] “Recurly bills only the difference during an immediate change when the underlying plan is unchanged.”
Invoicing tax — stories about invoicing tax in this arenaInvoicing tax
Stories about invoicing tax in this arena
Invoices
ops userThe platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automatically
weight 2 · round to RecurlyChargebeenone0/10The evidence pack contains no documentation of invoice/credit note/receipt generation, sequential numbering, custom fields, or memos — only tangential billing topics like dunning, revenue recognition, and API basics. missing for 10: invoice generation docs, credit note/receipt automation, sequential numbering compliance, custom fields/memos support.
Docs confirm invoice modification (notes, due dates, PO numbers, terms), separate credit invoices, and account/record-keeping features, implying automated invoice generation and delivery, but there is no explicit evidence of sequential/compliant numbering rules, custom field configuration on invoices, memo fields, or receipt generation/delivery workflows. missing for 10: explicit documentation of sequential invoice numbering compliance, custom fields on invoices, memo support, automatic receipt generation/delivery, and independent confirmation of these features working as described.
- [claimed-docs] “Credit invoices give every credit its own distinct invoice — separate from charge invoices.”
- [claimed-docs] “Modify invoice details post-issuance — including account notes, due dates, PO numbers, customer notes, and terms — to keep records accurate.”
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
Multi currency
finance leadBill customers in their local currency with per-currency price points and consolidated reporting in my home currency
weight 2 · round to ChargebeeChargebee docs mention item prices tied to specific currencies (implying per-currency price points exist), but there is no evidence describing consolidated reporting back into a home currency for finance leads. Missing for 10: explicit multi-currency pricing catalog documentation, currency conversion/consolidation reporting features, and any finance-lead-facing reporting tool showing home-currency rollups.
- [claimed-docs] “An item price is compatible with a plan-item price if their currencies are the same.”
Recurlynone0/10None of the evidence items mention multi-currency pricing, per-currency price points, or consolidated home-currency reporting — the pack covers subscription changes, usage billing, dunning, entitlements, invoices, and general community commentary, none of which address currency handling. This is a fair capability to expect from a billing platform, so absence of evidence yields 'none' rather than 'na'.
Tax
finance leadSales tax, VAT, and GST are calculated on every invoice — natively or through a first-class tax integration — with the right registrations and rates
weight 2 · round drawnChargebeenone0/10No evidence in the pack shows Chargebee performing native or integrated sales tax/VAT/GST calculation, registrations, or rate management on invoices. The only related community comment explicitly states dissatisfaction with having to 'handle VAT' themselves, implying no seamless native solution, and no docs reference tax engines like Avalara/TaxJar or VAT/GST features.
- [community] “So to be clear I absolutely love Chargebee! It's rich of features, very flexible and support is always friendly and ready to help. It's prob…”
Recurlynone0/10The evidence pack contains no mention of tax calculation, VAT/GST handling, tax registrations, or any first-party or third-party tax integration (e.g., Avalara, TaxJar) — invoicing/credit/dunning features are covered but tax compliance is entirely absent. missing for 10: any documentation of sales tax/VAT/GST calculation, tax registration management, or tax engine integration.
Migration portability — stories about migration portability in this arenaMigration portability
Stories about migration portability in this arena
Export
finance leadExport every subscription, invoice, and usage record — and port stored payment methods out to another provider — if I choose to leave
weight 2 · round to RecurlyChargebee's docs confirm a generic Export API resource that creates export jobs and provides a download URL (chargebee-docs-6), implying some data-export capability, but there is no evidence specifying export of subscriptions, invoices, and usage records specifically, nor any mention of porting stored payment methods to another provider. missing for 10: explicit documentation of exporting subscriptions/invoices/usage data, any payment-method portability/export mechanism, and independent confirmation of successful migration workflows.
- [claimed-docs] “Export resource represents an export job and contains the status of the job and the download URL, if the job is successfully completed.”
Recurly docs mention a general 'Data Imports and Exports' feature for populating accounts and keeping compliance records, and a community comment specifically praises Recurly's gateway for supporting 'credit card portability' to another provider. However, there is no vendor documentation detailing bulk export of subscriptions, invoices, or usage records, nor an official description of the payment-method portability mechanism (it's only referenced anecdotally by a user, not documented by Recurly). Missing for 10: explicit docs on invoice/usage-record export formats and scope, official documentation of stored payment-method portability/migration tooling, and any independent verification that a full data export actually contains all subscription/invoice/usage history.
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Import customer data to populate accounts and records across your Recurly account.”
- [community] “I am in the process of integrating Recurly into my existing business... I want all the subscription management features Recurly provides. Fu…”
Import
ops userMigrate live subscriptions in from a spreadsheet or a competing platform — including PCI-compliant card data transfer — without customers noticing
weight 3 · round to RecurlyChargebeenone0/10No evidence of any migration tooling, bulk import for live subscriptions, PCI-compliant card data transfer/tokenization import, or zero-downtime cutover capability is present in the evidence pack. Only general API/export/dunning/revrec docs are shown, none addressing subscription migration from spreadsheets or competitor platforms.
Recurly's docs mention generic data import/export tools (recurly-docs-11, recurly-docs-15) and a community comment notes Recurly's gateway offers 'credit card portability' (recurly-comm-7), suggesting some support for migrating billing data and card credentials. However, there is no documentation of a structured migration workflow, PCI-compliant card tokenization/transfer process, or assurance that live subscriptions migrate without customer disruption. missing for 10: explicit migration/onboarding documentation, PCI-compliant card data transfer mechanics, evidence of seamless customer experience during migration.
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Import customer data to populate accounts and records across your Recurly account.”
- [community] “I am in the process of integrating Recurly into my existing business... I want all the subscription management features Recurly provides. Fu…”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round drawnChargebee's REST API documentation covers a broad range of core UI-configurable features (subscriptions, usage events, exports, webhooks, entitlements) suggesting strong API/UI parity, and an API Explorer lets users test all documented endpoints. However, there's no explicit vendor claim of full UI-API parity, and features like AI drafting (chargebee-docs-14) or dunning setup are only described as UI features without confirmation they're also fully API-driven. Missing for 10: explicit parity statement, evidence that every UI action (e.g., AI drafting, dunning configuration) has an API equivalent, independent/hands-on confirmation of parity.
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
- [claimed-docs] “This resource allows you to record usage events, which are essential for usage-based billing.”
- [claimed-docs] “An item price is compatible with a plan-item price if their currencies are the same.”
- [claimed-docs] “If webhooks are configured in Chargebee, events trigger those webhooks.”
- [claimed-docs] “Export resource represents an export job and contains the status of the job and the download URL, if the job is successfully completed.”
- [claimed-docs] “The API Explorer lets you make live API calls in a browser using a guided interface. Use it to test endpoints without writing code.”
- [claimed-docs] “Chargebee provides you an efficient UI to allocate and manage the customer privileges using Features.”
- [claimed-docs] “With Chargebee's Dunning feature, you can send email reminders to your customers asking them to update payment details and schedule payment …”
- [claimed-docs] “Let Chargebee AI draft product families, plans, addons, charges, prices, features, and entitlements from a pricing page, document, or descri…”
Docs show broad API coverage of core subscription, invoicing, entitlements, and data import/export features (recurly-docs-1,8,10,11) alongside official client libraries (recurly-docs-13), suggesting most UI actions are API-accessible. However, there is no explicit statement of full UI/API parity, and some UI-only features like dunning campaign configuration (recurly-docs-5) aren't confirmed as API-manageable. Missing for 10: an explicit parity guarantee or comprehensive API reference mapping every UI action, and independent confirmation that all UI-configurable settings (e.g., dunning campaigns) are exposed via API.
- [claimed-docs] “Recurly gives you full control over how and when subscription changes take effect. Upgrade or downgrade a plan, adjust quantity or price, ad…”
- [claimed-docs] “Entitlements can be applied across platforms (web, mobile, and app stores) and checked in real time via the Recurly API.”
- [claimed-docs] “Modify invoice details post-issuance — including account notes, due dates, PO numbers, customer notes, and terms — to keep records accurate.”
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [claimed-docs] “merchants on Professional and Elite plans can create up to 50 targeted campaigns for different customer segments or plans”
ai-native userExport all of my data in open formats and leave
weight 3 · round to ChargebeeChargebee documents an Export resource that produces job status and a download URL (chargebee-docs-6), and its REST API returns JSON that could be used to pull data programmatically (chargebee-docs-1), giving a route to extract data in a machine-readable format. However there is no explicit documentation of bulk/full-account data export, no mention of standard open formats like CSV/JSON dumps of all account data, and no evidence of a clear 'leave with your data' workflow. missing for 10: explicit full-account bulk export documentation, confirmation of open/standard export formats (CSV/JSON) for all entities, and independent confirmation that this satisfies a complete data portability use case.
- [claimed-docs] “Export resource represents an export job and contains the status of the job and the download URL, if the job is successfully completed.”
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
Recurly documents a data-imports-and-exports feature for populating accounts and keeping records, and community mentions note credit-card portability, suggesting some data can be extracted, but there is no evidence of a comprehensive, open-format (CSV/JSON) full-account export or an official data-portability/exit process. missing for 10: explicit open-format export documentation, full account data export scope, and confirmation of easy migration/exit workflow.
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Import customer data to populate accounts and records across your Recurly account.”
- [community] “I am in the process of integrating Recurly into my existing business... I want all the subscription management features Recurly provides. Fu…”
ai-native userRead the product's source under an open license
weight 2 · round drawnChargebeenone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
ai-native userSelf-host the core product
weight 3 · round drawnChargebeenone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnChargebeenone0/10No evidence in the pack discusses data residency, regional data storage options, or hosting location controls for Chargebee; the docs cover API usage, billing features, and MCP integration but nothing about choosing storage regions. Missing for 10: any mention of data residency/region selection, compliance certifications tied to geographic storage, or customer-facing controls for data location.
ai-native userControl data retention and deletion
weight 2 · round drawnChargebeenone0/10No evidence in the pack discusses data retention policies, deletion controls, or privacy/data lifecycle management for AI-native users; the pack covers billing APIs, MCP integrations, and dunning/revenue features but nothing about controlling or deleting stored data.
Recurlynone0/10Evidence covers subscription management, billing, invoicing, imports/exports and an MCP docs connector, but nothing addresses data retention policies, deletion requests, or privacy/GDPR-style controls for AI-native users. missing for 10: data retention policy documentation, data deletion/right-to-erasure mechanisms, privacy compliance controls (GDPR/CCPA), evidence of user-initiated data deletion API or workflow.
Revenue recognition — stories about revenue recognition in this arenaRevenue recognition
Stories about revenue recognition in this arena
Analytics
founderI get MRR, churn, cohort retention, and LTV analytics computed from the billing source of truth, not a bolted-on BI export
weight 2 · round drawnChargebeenone0/10The evidence shows RevRec for ASC 606 compliance and generic data Export jobs, but nothing documents native MRR, churn, cohort retention, or LTV analytics computed within Chargebee itself — the only analytics-adjacent capability shown (Exports) is exactly the 'bolted-on export' pattern the story asks to avoid.
- [claimed-docs] “Export resource represents an export job and contains the status of the job and the download URL, if the job is successfully completed.”
- [claimed-docs] “RevRec is fully compliant with ASC 606 revenue recognition capabilities that cover your sales activities right from contract changes (renewa…”
Recurlynone0/10The evidence pack covers subscription changes, dunning, entitlements, invoicing, and data import/export, but contains no mention of MRR, churn, cohort retention, or LTV analytics/reporting dashboards computed from billing data. Missing for 10: any documentation of built-in revenue/retention analytics, cohort or LTV reporting, or dashboards distinct from raw data export.
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Import customer data to populate accounts and records across your Recurly account.”
Gl sync
finance leadInvoices, payments, and recognition entries sync to my general ledger or ERP — QuickBooks, Xero, NetSuite — so the close doesn't need CSV surgery
weight 2 · round drawnChargebeenone0/10The pack shows Chargebee has RevRec (ASC 606) and generic Export/API/webhook capabilities, but no evidence of any named QuickBooks, Xero, or NetSuite connector or GL/ERP sync workflow — missing for 10: named ERP/accounting integrations, sync mechanism details, and evidence that invoices/payments/recognition entries flow automatically without manual export/import.
- [claimed-docs] “RevRec is fully compliant with ASC 606 revenue recognition capabilities that cover your sales activities right from contract changes (renewa…”
- [claimed-docs] “Export resource represents an export job and contains the status of the job and the download URL, if the job is successfully completed.”
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
Recurlynone0/10The evidence pack shows generic data import/export capability but no mention of specific GL/ERP integrations (QuickBooks, Xero, NetSuite) or revenue recognition sync. Missing for 10: any documentation of accounting/ERP connectors, revenue recognition automation, or close-process integration.
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Import customer data to populate accounts and records across your Recurly account.”
Revrec reports
finance leadRevenue is recognized on an ASC 606 / IFRS 15 basis — deferred revenue schedules and audit-ready recognition reports straight from billing data
weight 3 · round to ChargebeeChargebee's RevRec product is explicitly documented as ASC 606 compliant, covering contract changes like renewal/modification/cancellation, directly matching the finance-lead's revenue recognition need. However, evidence lacks detail on IFRS 15 specifically, deferred revenue schedule specifics, audit-ready report generation/export workflows, or independent/community corroboration of accuracy in practice. Missing for 10: IFRS 15 explicit coverage, deferred revenue schedule detail, audit trail/report examples, and third-party validation of RevRec accuracy.
- [claimed-docs] “RevRec is fully compliant with ASC 606 revenue recognition capabilities that cover your sales activities right from contract changes (renewa…”
Recurlynone0/10Evidence covers subscriptions, invoicing, dunning, entitlements, and data import/export for general compliance, but nothing addresses ASC 606/IFRS 15 deferred revenue schedules or audit-ready recognition reporting specifically. Absence of evidence for this applicable billing-platform capability means it can't be credited as delivered.
Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycle
Stories about subscription lifecycle in this arena
Lifecycle api
developerCreate, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboard
weight 3 · round drawnChargebee's REST API and Subscriptions resource are documented (chargebee-docs-1, chargebee-docs-4), and it supports form-encoded requests, JSON responses, and even a live API Explorer for testing endpoints (chargebee-docs-9), consistent with full CRUD-style subscription management. However, the evidence pack never explicitly cites 'create', 'update', 'pause', or 'cancel' subscription endpoints or their request/response schemas, so the full lifecycle claim is inferred rather than directly documented. missing for 10: explicit endpoint-level documentation for pause and cancel operations, and independent developer confirmation of using these endpoints end-to-end.
- [claimed-docs] “It's a REST API that uses HTTP Basic Auth, accepts form-encoded requests, and returns JSON.”
- [claimed-docs] “An item price is compatible with a plan-item price if their currencies are the same.”
- [claimed-docs] “The API Explorer lets you make live API calls in a browser using a guided interface. Use it to test endpoints without writing code.”
Docs confirm a documented API for changing subscriptions (upgrade/downgrade, quantity/price, add-ons) with official client libraries in 7 languages, supporting programmatic subscription management. However, the evidence never explicitly documents 'create' or 'pause'/'cancel' endpoints—only mid-cycle change operations are detailed, so full lifecycle coverage is inferred rather than shown directly. Missing for 10: explicit documentation of subscription creation and cancellation/pause API calls, and any hands-on developer confirmation of the full lifecycle working end-to-end via API alone.
- [claimed-docs] “Recurly gives you full control over how and when subscription changes take effect. Upgrade or downgrade a plan, adjust quantity or price, ad…”
- [claimed-docs] “Recurly bills only the difference during an immediate change when the underlying plan is unchanged.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
Lifecycle events
developerEvery subscription state change — renewal, upgrade, payment failure, cancellation — emits a webhook or event my systems can act on reliably
weight 2 · round to ChargebeeChargebee's Events API triggers configured webhooks (chargebee-docs-5), and community evidence confirms multiple webhook URLs can be configured for different environments, corroborating reliable event delivery (chargebee-comm-2). Missing for 10: explicit documentation of the full set of lifecycle event types (renewal, upgrade, payment failure, cancellation) and delivery-retry/reliability guarantees for webhook events.
- [claimed-docs] “If webhooks are configured in Chargebee, events trigger those webhooks.”
- [community] “With Chargebee I can add multiple webhook URLs, so all events get sent to both dev and staging and each environment only cares about its own…”
Recurlynone0/10The evidence pack contains no documentation of Recurly's webhook or event system for subscription lifecycle changes (renewal, upgrade, payment failure, cancellation). The only indirect mention is a community comment noting dunning emails work 'without needing to implement webhooks,' which implies webhooks exist as an option but provides no detail on reliability, event types, or delivery guarantees.
- [community] “Comparing Stripe and Recurly: It's faster to get going with Stripe (no merchant account required) but Recurly appears to offer more automate…”
Self serve
founderMy customers can upgrade, downgrade, or cancel themselves through a hosted portal or embeddable components, without a support ticket
weight 2 · round to RecurlyChargebeenone0/10The evidence pack covers Chargebee's API, dunning, entitlements admin UI, and MCP/AI tooling, but nothing describes a hosted customer portal or embeddable self-service components letting end customers upgrade/downgrade/cancel on their own. missing for 10: hosted customer portal documentation, embeddable self-service widget docs, evidence of ticket-free self-service flow.
Docs confirm customers can change plans (upgrade/downgrade, add-ons, proration) via Recurly's subscription APIs, implying self-service capability, but no direct evidence of a hosted customer portal or embeddable UI components for self-cancel/upgrade, nor explicit mention of eliminating support tickets. missing for 10: explicit hosted portal documentation, embeddable component/widget evidence, self-service cancellation flow.
- [claimed-docs] “Recurly gives you full control over how and when subscription changes take effect. Upgrade or downgrade a plan, adjust quantity or price, ad…”
- [claimed-docs] “Recurly bills only the difference during an immediate change when the underlying plan is unchanged.”
Trials promos
ops userRun free trials, coupons, and promotion codes with automatic conversion to paid — including trial-end notifications required by card-network rules
weight 2 · round drawnChargebeenone0/10The evidence pack covers dunning/smart retry, entitlements, RevRec, and multi-frequency billing, but contains no mention of free trials, coupon/promotion code functionality, automatic trial-to-paid conversion, or trial-end notification requirements — the specific subscription-lifecycle capabilities named in the story are entirely undocumented here.
Recurlynone0/10The evidence pack contains no documentation of free trials, coupons/promotion codes, automatic trial-to-paid conversion, or card-network-mandated trial-end notifications. Related dunning/involuntary-churn features are covered, but none address trial or coupon lifecycle specifically. missing for 10: docs on free trial setup, coupon/promo code creation, automatic trial conversion, and trial-end notification compliance.
Usage metering — stories about usage metering in this arenaUsage metering
Stories about usage metering in this arena
Event ingestion
developerStream high-volume usage events — API calls, tokens, compute-seconds — into a metering pipeline with idempotent ingestion and backdating support
weight 3 · round drawnChargebee's API docs confirm a usage_events resource for recording usage-based billing events, but the evidence pack contains no detail on idempotent ingestion, backdating, or high-volume streaming capability. Missing for 10: idempotency key support, backdating/late event handling, batch/streaming ingestion guarantees, and any performance/scale documentation.
- [claimed-docs] “This resource allows you to record usage events, which are essential for usage-based billing.”
Recurly documents usage-based billing where usage-based add-ons are reported and billed at the end of a cycle (recurly-docs-3, recurly-docs-4), showing basic support for metering usage into billing, but there is no evidence of a high-volume streaming ingestion API, idempotency keys/idempotent ingestion, or explicit backdating support for usage events. Missing for 10: evidence of a streaming/bulk usage ingestion endpoint, documented idempotency guarantees for usage events, and backdating/timestamp-adjustment support for late-arriving usage records.
- [claimed-docs] “Recurly's usage-based billing model lets you charge customers at the end of each billing cycle based on their actual consumption”
- [claimed-docs] “Measured units describe the usage tracked by a usage-based add-on and enable consistent reporting across multiple add-ons and plans.”
Pricing models
finance leadPrice with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom code
weight 3 · round to RecurlyEvidence confirms usage-event recording for usage-based billing and multi-frequency subscription billing, which supports basic usage-plus-subscription models, but there is no documentation of tiered, volume, graduated, per-unit, or hybrid pricing structures, nor of credits, commitments, or overage handling. missing for 10: explicit tiered/volume/graduated/per-unit pricing model docs, credit/commitment/overage handling documentation, no-code configuration evidence for these pricing types.
- [claimed-docs] “This resource allows you to record usage events, which are essential for usage-based billing.”
- [claimed-docs] “Multi-frequency billing: Subscriptions are billed according to the billing period of each recurring item price within the subscription, whet…”
- [claimed-docs] “An item price is compatible with a plan-item price if their currencies are the same.”
Recurly's docs confirm usage-based billing with measured units and flexible subscription/add-on changes (recurly-docs-1, recurly-docs-3, recurly-docs-4), which supports basic per-unit and subscription-plus-usage hybrid billing without code. However, the evidence never explicitly documents tiered, volume, or graduated pricing structures, nor named 'commitment' or 'overage' billing mechanics as configurable models. missing for 10: explicit tiered/volume/graduated pricing tier configuration docs, explicit commitment and overage billing mechanics, independent confirmation these complex pricing combos work without custom code.
- [claimed-docs] “Recurly gives you full control over how and when subscription changes take effect. Upgrade or downgrade a plan, adjust quantity or price, ad…”
- [claimed-docs] “Recurly's usage-based billing model lets you charge customers at the end of each billing cycle based on their actual consumption”
- [claimed-docs] “Measured units describe the usage tracked by a usage-based add-on and enable consistent reporting across multiple add-ons and plans.”
- [claimed-docs] “Credit invoices give every credit its own distinct invoice — separate from charge invoices.”
Usage visibility
ops userCustomers and my team can see current-cycle usage and accrued cost in real time, with thresholds and alerts before an invoice surprises anyone
weight 2 · round to ChargebeeChargebee's usage_events API supports recording usage for usage-based billing and webhooks can propagate events, but there is no documented dashboard for real-time cycle usage/cost visibility to customers and teams, nor any explicit threshold/alert feature for pre-invoice warnings. Missing for 10: real-time usage/cost dashboard for customers, configurable usage thresholds, proactive alerting before invoicing.
- [claimed-docs] “This resource allows you to record usage events, which are essential for usage-based billing.”
- [claimed-docs] “If webhooks are configured in Chargebee, events trigger those webhooks.”
Recurlynone0/10Recurly's docs mention usage-based billing that charges at the end of the billing cycle and 'measured units' for reporting, but there is no evidence of real-time current-cycle usage/cost dashboards, customer-facing usage views, or threshold/alert mechanisms to warn before an invoice is generated.
- [claimed-docs] “Recurly's usage-based billing model lets you charge customers at the end of each billing cycle based on their actual consumption”
- [claimed-docs] “Measured units describe the usage tracked by a usage-based add-on and enable consistent reporting across multiple add-ons and plans.”
Not comparable on these axes
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableChargebeenone0/10No evidence in the pack addresses AI training data opt-out, data usage policies for model training, or any privacy controls specific to preventing data from being used to train AI models; evidence only covers billing API/MCP features unrelated to this privacy axis.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableChargebeenone0/10No evidence in the pack addresses telemetry/usage-tracking opt-out settings for Chargebee's product, MCP servers, or SDKs; this is an applicable privacy-posture axis for any SaaS/API product but no documentation or community evidence confirms such a control exists.