Chargebee vs RevenueCat
Chargebee
Chargebee Inc.
Chargebee wins · 23–9 (18 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 to ChargebeeA 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…”
RevenueCat serves a live llms.txt (HTTP 200) describing itself in agent-friendly terms, and docs pages throughout the evidence pack use the .md suffix convention (agent-oriented docs format) confirming machine-readable documentation exists. missing for 10: no root docs.md index (404) and no OpenAPI spec discoverable, which would round out full agentic documentation coverage.
- [probe] “PROBE llms.txt: HTTP 200 at https://www.revenuecat.com/llms.txt # RevenueCat > RevenueCat is the App Monetization OS for mobile and web app…”
- [probe] “PROBE docs-md: HTTP 404 at https://www.revenuecat.com/docs.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.revenuecat.com/openapi.json, https://www.revenuecat.com/swagger.json, https://www.revenu…”
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
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.”
RevenueCat exposes a REST API authenticated via API keys and supports server-side data import/export (revenuecat-docs-5, revenuecat-docs-4, revenuecat-docs-7), which enables non-interactive, programmatic use suitable for automation pipelines. However, there is no explicit documentation of CI/CD integration, headless test runners, or scripted deployment workflows. Missing for 10: explicit CI/CD examples, headless SDK testing guidance, and confirmation of non-interactive automation use cases.
- [claimed-docs] “RevenueCat authenticates requests from the RevenueCat SDK and the REST API using API keys.”
- [claimed-docs] “Importing existing purchase data to RevenueCat can be done server-side, or client-side.”
- [claimed-docs] “RevenueCat delivers your apps' data to a cloud storage provider or to email on a schedule you control.”
ai-native userConnect an agent via an official MCP server
weight 3 · round drawnChargebee 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”
RevenueCat documents an official MCP server that lets AI assistants manage subscription apps, Products, Entitlements, etc. directly, without the dashboard, which directly satisfies the story. Missing for 10: independent/hands-on third-party corroboration of the MCP server working, and technical setup/auth details beyond the docs summary.
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
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.
RevenueCatnone0/10No evidence pack item describes a dedicated official CLI tool; the closest items are an MCP server (revenuecat-docs-9), an AI toolkit doc (revenuecat-docs-8), and a natural-language analytics assistant 'Rico' (revenuecat-docs-10), none of which are described as a command-line interface. Missing for 10: explicit CLI product/documentation, installation instructions, command reference, or community confirmation of CLI usage.
- [claimed-docs] “Set up subscriptions, including projects, apps, Products, Entitlements, Offerings, and Packages”
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
- [claimed-docs] “Instead of digging through charts and tables yourself, you can ask Rico plain-language questions like "Why did MRR drop in Germany last week…”
ai-native userDrive the product through a documented public API
weight 3 · round to ChargebeeChargebee 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…”
RevenueCat confirms a REST API secured by API keys (revenuecat-docs-5) and even offers an MCP server letting AI assistants manage subscriptions programmatically (revenuecat-docs-9) and an AI toolkit (revenuecat-docs-8), showing real support for AI-driven API access. However, probes for a public OpenAPI/swagger spec or docs.md all 404 (revenuecat-probe-2, revenuecat-probe-3), so a fully documented, discoverable public API reference isn't evidenced. Missing for 10: a published OpenAPI/API reference spec, broader REST endpoint documentation beyond auth, and independent confirmation of programmatic API usage outside RevenueCat's own docs.
- [claimed-docs] “RevenueCat authenticates requests from the RevenueCat SDK and the REST API using API keys.”
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
- [claimed-docs] “Set up subscriptions, including projects, apps, Products, Entitlements, Offerings, and Packages”
- [probe] “PROBE docs-md: HTTP 404 at https://www.revenuecat.com/docs.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.revenuecat.com/openapi.json, https://www.revenuecat.com/swagger.json, https://www.revenu…”
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”
RevenueCatnone0/10Evidence shows RevenueCat uses API keys for authentication (revenuecat-docs-5) and has an MCP server/AI toolkit for agents (revenuecat-docs-8, revenuecat-docs-9), but nothing describes scoped, granular, or least-privilege API key permissions for agents — no mention of read-only keys, role-based scopes, or key restriction settings.
- [claimed-docs] “RevenueCat authenticates requests from the RevenueCat SDK and the REST API using API keys.”
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
ai-native userBuild against official SDKs
weight 2 · round to RevenueCatChargebee 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…”
RevenueCat ships official native SDKs (iOS, and implied Android/cross-platform per GitHub repo) with well-documented capabilities—purchases, entitlements, customer info, authentication—that developers, including AI-native ones, can build against directly, and this is corroborated by both first-party GitHub repos and extensive docs. Missing for 10: independent hands-on developer corroboration specifically praising SDK integration ergonomics, and explicit multi-platform SDK breadth beyond iOS in the evidence pack.
- [github] “Fetch products, make purchases, and check subscription status with our native SDKs.”
- [claimed-docs] “Entitlements are used to ensure a user has appropriate access to content based on their purchases, without having to manage all of the produ…”
- [claimed-docs] “The CustomerInfo object contains all of the purchase and subscription data available about a customer.”
- [claimed-docs] “RevenueCat authenticates requests from the RevenueCat SDK and the REST API using API keys.”
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnChargebee 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…”
RevenueCat explicitly documents webhooks for real-time event notifications, letting external systems (including AI agents) subscribe to subscription/purchase events. Missing for 10: no first-party docs on webhook payload schema/customization or independent hands-on confirmation of reliability, and no mention of AI-specific webhook consumption patterns.
- [github] “Get notified of real-time events through webhooks.”
- [claimed-docs] “RevenueCat authenticates requests from the RevenueCat SDK and the REST API using API keys.”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to RevenueCatChargebee 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…”
RevenueCat's Rico feature explicitly lets users ask plain-language questions about their data (e.g. "Why did MRR drop in Germany last week?") and get AI-driven insights, directly matching the story; charts/metrics dashboard provides the underlying data surface. Missing for 10: independent/hands-on validation of Rico's insight quality and broader coverage beyond the single documented example.
- [claimed-docs] “Instead of digging through charts and tables yourself, you can ask Rico plain-language questions like "Why did MRR drop in Germany last week…”
- [claimed-docs] “RevenueCat charts allow you to understand your user base with key subscription specific metrics, filters, and segments.”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to ChargebeeChargebee 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”
RevenueCat offers webhooks for real-time event notifications and scheduled data exports that run on a set cadence, which are background automations, but these are infrastructure features rather than AI-driven autonomous agentic workflows. The MCP server and AI toolkit let AI assistants configure or query RevenueCat interactively, not run persistent background automations. Missing for 10: evidence of AI agents autonomously triggering actions or workflows in the background without human initiation, scheduling/orchestration of agentic tasks, or any first-party 'automation builder' feature.
- [github] “Get notified of real-time events through webhooks.”
- [claimed-docs] “RevenueCat delivers your apps' data to a cloud storage provider or to email on a schedule you control.”
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
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…”
RevenueCat documents "Rico", a built-in AI assistant in the dashboard that lets users ask plain-language questions about their data instead of digging through charts (revenuecat-docs-10). This shows a built-in assistant capability, but evidence only covers Q&A/insight generation, not broader task delegation or action-taking within the product, and there's no independent/community corroboration of its real-world reliability. Missing for 10: evidence of Rico performing actions/tasks beyond answering questions, and independent user reports validating its usefulness.
- [claimed-docs] “Instead of digging through charts and tables yourself, you can ask Rico plain-language questions like "Why did MRR drop in Germany last week…”
ai-native userOperate the product with natural-language commands
weight 2 · round drawnChargebee 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”
RevenueCat offers an MCP server letting AI assistants manage products/entitlements via natural language, and Rico allows plain-language analytics queries — both first-party docs confirm agentic/NL control of the dashboard. However, this covers admin/analytics operations, not the core end-user subscription flows, and there's no independent/hands-on corroboration of these NL features working reliably. Missing for 10: third-party validation of MCP/Rico usage, broader coverage of NL control across all product surfaces (not just admin tasks).
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
- [claimed-docs] “Instead of digging through charts and tables yourself, you can ask Rico plain-language questions like "Why did MRR drop in Germany last week…”
- [claimed-docs] “Set up subscriptions, including projects, apps, Products, Entitlements, Offerings, and Packages”
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…”
RevenueCatnone0/10No evidence of an interactive API reference or runnable examples; probes for openapi/swagger specs and docs.md return 404, and no documentation item describes a try-it-out console or embedded runnable code samples.
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”
RevenueCatnone0/10RevenueCat exposes a REST API (per revenuecat-docs-5) but no evidence of a downloadable OpenAPI/Swagger spec; the probe explicitly found all standard OpenAPI spec paths return 404, and no docs reference a machine-readable API spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://www.revenuecat.com/openapi.json, https://www.revenuecat.com/swagger.json, https://www.revenu…”
- [claimed-docs] “RevenueCat authenticates requests from the RevenueCat SDK and the REST API using API keys.”
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…”
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.”
RevenueCatnone0/10No evidence of API versioning scheme or a documented deprecation policy; OpenAPI spec probes returned 404s and no docs mention version lifecycle or deprecation commitments.
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”
RevenueCatnone0/10The evidence shows RevenueCat's MCP server and AI toolkit let an AI assistant manage individual Products, Entitlements, and Offerings, and server-side import of existing purchase data exists, but nothing describes batch/bulk operations across many items at once (e.g., bulk-editing many products, mass customer updates, or batch API calls) for an AI-native workflow. Missing for full credit: explicit bulk/batch API endpoints, documentation of bulk operations via MCP/AI toolkit, and any example of operating on many items simultaneously.
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
- [claimed-docs] “Set up subscriptions, including projects, apps, Products, Entitlements, Offerings, and Packages”
- [claimed-docs] “Importing existing purchase data to RevenueCat can be done server-side, or client-side.”
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…”
RevenueCat offers webhooks for real-time event notifications (revenuecat-gh-3) that can be wired to trigger external actions, but there's no built-in rule engine to define conditional logic or automated actions natively within RevenueCat itself. A community feature request explicitly asks for 'timed hooks' like trial-expiry reminders, indicating this kind of automation isn't natively supported (revenuecat-comm-6). Missing for 10: native rule/trigger builder, conditional logic definitions, in-product automated actions beyond raw webhook delivery.
- [github] “Get notified of real-time events through webhooks.”
- [community] “Feature request: handling timed hooks to send notifications, e.g. reminding users before a trial expires and subscription cancels.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to RevenueCatChargebeenone0/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…”
RevenueCat supports scheduled recurring data exports to cloud storage/email, which is a narrow instance of a recurring job, but there is no evidence of a general-purpose scheduler for recurring workflows or automations (e.g., via MCP/AI toolkit) that an AI-native user could configure. missing for 10: evidence of configurable recurring workflow/job scheduling beyond data exports, integration of scheduling with the MCP/AI toolkit or Rico assistant, and any cron-like automation API.
- [claimed-docs] “RevenueCat delivers your apps' data to a cloud storage provider or to email on a schedule you control.”
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
- [claimed-docs] “Instead of digging through charts and tables yourself, you can ask Rico plain-language questions like "Why did MRR drop in Germany last week…”
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 drawnChargebee 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”
RevenueCat ships an MCP server explicitly for AI assistants to manage subscription apps, Products, Entitlements, and Offerings (revenuecat-docs-9), backed by a REST API authenticated via scoped API keys (revenuecat-docs-5), and SDK/dashboard features let you grant promotional subscriptions and view customer transaction histories (revenuecat-gh-4). However, the evidence centers on catalog/config management (products, entitlements, offerings) rather than explicit end-user billing actions like 'create a subscription', 'apply a credit', or 'change a plan' for a specific customer, and there's no documentation of granular per-action permission scoping beyond generic API keys. Missing for 10: explicit agent-driven customer-level actions (create subscription, apply credit, change plan) and detailed scoped-permission/role model for agent access.
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
- [claimed-docs] “RevenueCat authenticates requests from the RevenueCat SDK and the REST API using API keys.”
- [github] “See customer transaction histories, chart lifetime value, and grant promotional subscriptions.”
- [claimed-docs] “Set up subscriptions, including projects, apps, Products, Entitlements, Offerings, and Packages”
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”
RevenueCat's Rico assistant explicitly lets users ask plain-language billing questions like 'why did MRR drop,' and the MCP server/CustomerInfo API expose subscription and customer purchase data programmatically, showing agent-queryable billing state. However, there's no explicit evidence for querying delinquent accounts, upcoming renewals, or per-customer invoice histories via an agent interface. Missing for 10: documented support for delinquency/renewal queries, invoice-level querying, and independent confirmation of Rico's accuracy/scope beyond MRR examples.
- [claimed-docs] “Instead of digging through charts and tables yourself, you can ask Rico plain-language questions like "Why did MRR drop in Germany last week…”
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
- [claimed-docs] “The CustomerInfo object contains all of the purchase and subscription data available about a customer.”
- [claimed-docs] “RevenueCat charts allow you to understand your user base with key subscription specific metrics, filters, and segments.”
- [github] “See customer transaction histories, chart lifetime value, and grant promotional subscriptions.”
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 drawnChargebeenone0/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…”
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 drawnChargebeenone0/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.
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 to ChargebeeChargebee 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…”
RevenueCatnone0/10RevenueCat's evidence covers subscription management, entitlements, paywalls, MCP/AI tools, and analytics, but nothing addresses card-level dunning recovery mechanics like network account updater, backup payment methods, or hosted update-payment pages — these are Stripe/payment-processor-level features that RevenueCat, as an app-store/subscription management layer, does not document handling itself.
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 to ChargebeeDocs 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…”
RevenueCatnone0/10The evidence pack shows RevenueCat's core subscription infrastructure (entitlements, offerings, paywalls, webhooks, exports) but contains no mention of dunning-specific features like branded recovery emails, in-app banners, configurable grace periods, or cancel-vs-unpaid final-state rules. A community comment even requests exactly this kind of timed-notification/dunning hook as a missing feature, reinforcing the absence of evidence for it.
- [community] “Feature request: handling timed hooks to send notifications, e.g. reminding users before a trial expires and subscription cancels.”
- [claimed-docs] “Paywalls — Remotely configure your product offering with powerful paywalls.”
- [claimed-docs] “Set up subscriptions, including projects, apps, Products, Entitlements, Offerings, and Packages”
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…”
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 RevenueCatChargebee 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”
Docs confirm entitlements model access based on purchases without hardcoding product identifiers, and CustomerInfo (via SDK/API, authenticated by API keys) exposes purchase/entitlement data at runtime. This directly matches the story of entitlements attached to plans checked at runtime via SDK/API. Missing for 10: explicit code snippet showing an entitlement check call and independent/hands-on developer confirmation of the runtime check pattern.
- [claimed-docs] “Entitlements are used to ensure a user has appropriate access to content based on their purchases, without having to manage all of the produ…”
- [claimed-docs] “The CustomerInfo object contains all of the purchase and subscription data available about a customer.”
- [claimed-docs] “RevenueCat authenticates requests from the RevenueCat SDK and the REST API using API keys.”
- [github] “Fetch products, make purchases, and check subscription status with our native SDKs.”
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.
RevenueCatnone0/10While RevenueCat's Offerings/Packages system (revenuecat-docs-8) implies some product versioning, there is no evidence of price-specific grandfathering, versioned pricing plans, or bulk cohort migration tools; the only 'migration' documentation (revenuecat-docs-4) concerns importing existing purchase data when onboarding to RevenueCat, not moving cohorts between price tiers post-launch. This is a fair capability to expect from a subscription billing platform, so the axis applies, but no concrete evidence supports it.
- [claimed-docs] “Set up subscriptions, including projects, apps, Products, Entitlements, Offerings, and Packages”
- [claimed-docs] “Importing existing purchase data to RevenueCat can be done server-side, or client-side.”
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 drawnChargebeenone0/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.
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.”
RevenueCatnone0/10No evidence describes local-currency price points, per-currency pricing configuration, or consolidated home-currency reporting; the evidence pack covers entitlements, paywalls, SDKs, MCP tools, and dashboards but nothing about multi-currency billing or currency-consolidated financial reports.
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…”
RevenueCatnone0/10No evidence RevenueCat calculates or manages sales tax, VAT, or GST, nor any mention of tax registrations, rates, or a tax integration; RevenueCat's role for App Store/Play purchases means Apple/Google handle tax, and no tax-handling capability is documented for its own billing (e.g., Stripe-side) invoicing.
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 RevenueCatChargebee'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.”
RevenueCat offers scheduled data exports to cloud storage/email and REST API access to customer/subscription data (docs-7, docs-5, docs-3), which covers some of the 'export subscriptions/customer records' need. However, there is no evidence of invoice-level or usage-record export, and no mention anywhere of porting stored payment methods to another provider — RevenueCat itself doesn't store card details (they live with Stripe/Apple/Google), so this key part of the story is unaddressed. Community discussion even flags that migrating subscriptions between providers is 'hard to make smooth' (revenuecat-comm-8), reinforcing the gap. Missing for 10: documented invoice/usage export, explicit payment-method portability/export mechanism, and confirmation of smooth cross-provider migration.
- [claimed-docs] “RevenueCat delivers your apps' data to a cloud storage provider or to email on a schedule you control.”
- [claimed-docs] “RevenueCat authenticates requests from the RevenueCat SDK and the REST API using API keys.”
- [claimed-docs] “The CustomerInfo object contains all of the purchase and subscription data available about a customer.”
- [community] “User considering migrating to RevenueCat asks whether it can handle users moving subscriptions between iOS/Android in-app purchases and Stri…”
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 RevenueCatChargebeenone0/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.
RevenueCat explicitly documents importing existing purchase/subscription data 'server-side or client-side' when migrating to the platform, which supports the core migration story, but there is no evidence describing spreadsheet-based import, PCI-compliant card data transfer, or explicit guarantees that migration is invisible to end customers. Community comments (revenuecat-comm-8, revenuecat-comm-3) show users actively wondering whether smooth cross-platform migration (App Store/Stripe) is even possible, indicating this remains an open question rather than a proven capability. missing for 10: PCI-compliant card data transfer mechanics, spreadsheet import tooling, documented zero-customer-disruption guarantee, and independent confirmation of smooth migration.
- [claimed-docs] “Importing existing purchase data to RevenueCat can be done server-side, or client-side.”
- [community] “User considering migrating to RevenueCat asks whether it can handle users moving subscriptions between iOS/Android in-app purchases and Stri…”
- [community] “"Man I wish this existed 8 months ago when I built our own version internally! We have a mix of Stripe and App Store customers so we'll defi…”
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…”
RevenueCat documents a REST API/authentication (revenuecat-docs-5), an MCP server that lets AI assistants manage apps, Products, Entitlements 'without using the RevenueCat dashboard' (revenuecat-docs-9), and an AI toolkit for setting up subscriptions, offerings, and packages (revenuecat-docs-8), showing strong API parity for core configuration tasks. However, no OpenAPI spec was discoverable (revenuecat-probe-3) and UI-centric features like paywall design, charts, and dashboard-and-metrics exploration appear tied to the dashboard or scheduled exports rather than full API control (revenuecat-docs-6, revenuecat-docs-7, revenuecat-docs-11). Missing for 10: publicly documented OpenAPI/full REST API reference, evidence that paywall building/analytics dashboards are fully API-accessible, and independent confirmation of complete UI-API parity.
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
- [claimed-docs] “Set up subscriptions, including projects, apps, Products, Entitlements, Offerings, and Packages”
- [claimed-docs] “RevenueCat authenticates requests from the RevenueCat SDK and the REST API using API keys.”
- [claimed-docs] “RevenueCat charts allow you to understand your user base with key subscription specific metrics, filters, and segments.”
- [claimed-docs] “Paywalls — Remotely configure your product offering with powerful paywalls.”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.revenuecat.com/openapi.json, https://www.revenuecat.com/swagger.json, https://www.revenu…”
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.”
RevenueCat does support scheduled data exports to cloud storage/email and a REST API for programmatic access to customer/subscription data, giving some data portability. However, there's no documented comprehensive 'export all your data and leave' feature, no explicit open-format full account export, and no OpenAPI spec found (probe returned 404s). Missing for 10: a documented full-account data export/deletion workflow, explicit open-format guarantees, and confirmation of a public OpenAPI/schema for complete data extraction.
- [claimed-docs] “RevenueCat delivers your apps' data to a cloud storage provider or to email on a schedule you control.”
- [claimed-docs] “RevenueCat authenticates requests from the RevenueCat SDK and the REST API using API keys.”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.revenuecat.com/openapi.json, https://www.revenuecat.com/swagger.json, https://www.revenu…”
ai-native userRead the product's source under an open license
weight 2 · round to RevenueCatChargebeenone0/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.)
RevenueCat publishes open-source client SDKs on GitHub (e.g., purchases-ios) showing feature code, but the evidence never states a specific open-source license nor shows the core backend/platform source, which remains a closed SaaS product. missing for 10: explicit license statement, evidence of core platform/service source being open, independent confirmation of license terms.
- [github] “Fetch products, make purchases, and check subscription status with our native SDKs.”
- [github] “Host and configure products remotely from our dashboard.”
- [github] “Get notified of real-time events through webhooks.”
- [github] “See customer transaction histories, chart lifetime value, and grant promotional subscriptions.”
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.)
RevenueCatnone0/10RevenueCat is delivered purely as a hosted SaaS platform (dashboard, cloud APIs, webhooks, MCP server) with no mention of an on-premises or self-hosted deployment option anywhere in the evidence pack; community discussion even treats it as an external service to 'switch to' rather than something to run locally. Missing for 10: any documentation of self-hosted/on-prem deployment, open-source core, or Docker/Kubernetes packaging.
- [probe] “PROBE llms.txt: HTTP 200 at https://www.revenuecat.com/llms.txt # RevenueCat > RevenueCat is the App Monetization OS for mobile and web app…”
- [claimed-docs] “RevenueCat authenticates requests from the RevenueCat SDK and the REST API using API keys.”
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
- [community] “User asks why use RevenueCat over Stripe, which is developer-friendly, robust, and unlikely to disappear.”
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.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnChargebeenone0/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.
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 to RevenueCatChargebeenone0/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…”
RevenueCat's dashboard/charts and Rico assistant explicitly surface MRR and LTV computed directly from subscription/billing events (revenuecat-docs-6, revenuecat-docs-10, revenuecat-gh-4), and scheduled exports let founders pull this data (revenuecat-docs-7), all sourced from the billing data rather than a bolted-on BI tool. However, the evidence pack never explicitly mentions churn metrics or cohort retention analysis by name, so the story's full metric set isn't documented. Missing for 10: explicit churn-rate analytics, explicit cohort retention analytics/reporting.
- [claimed-docs] “RevenueCat charts allow you to understand your user base with key subscription specific metrics, filters, and segments.”
- [claimed-docs] “Instead of digging through charts and tables yourself, you can ask Rico plain-language questions like "Why did MRR drop in Germany last week…”
- [github] “See customer transaction histories, chart lifetime value, and grant promotional subscriptions.”
- [claimed-docs] “RevenueCat delivers your apps' data to a cloud storage provider or to email on a schedule you control.”
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.”
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…”
RevenueCatnone0/10Evidence covers subscription SDKs, entitlements, charts, and data exports, but nothing addresses ASC 606/IFRS 15 deferred revenue schedules or audit-ready recognition reporting. Missing for 10: any mention of deferred revenue calculation, revenue recognition compliance, or audit-ready financial reports.
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 to ChargebeeChargebee'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.”
RevenueCat exposes API-based mechanisms for parts of subscription management (granting promotional subscriptions via API/dashboard, managing Products/Entitlements/Offerings via the AI toolkit and MCP server 'without using the dashboard'), and confirms REST API authentication exists. However, there's no direct evidence of documented endpoints to create, update, pause, or cancel a live subscription's lifecycle end-to-end, and a probe for OpenAPI/swagger docs returned 404s, suggesting the full API surface isn't publicly documented in this pack. missing for 10: explicit API endpoints for pause/cancel/update, a discoverable OpenAPI spec, and confirmation that full lifecycle actions (not just entitlement grants/catalog config) can be done purely via API.
- [claimed-docs] “RevenueCat authenticates requests from the RevenueCat SDK and the REST API using API keys.”
- [claimed-docs] “Set up subscriptions, including projects, apps, Products, Entitlements, Offerings, and Packages”
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
- [github] “See customer transaction histories, chart lifetime value, and grant promotional subscriptions.”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.revenuecat.com/openapi.json, https://www.revenuecat.com/swagger.json, https://www.revenu…”
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…”
RevenueCat explicitly advertises real-time webhook events (revenuecat-gh-3) and dashboard/customer-info data on subscription state (revenuecat-docs-3), supporting the general claim that lifecycle changes are exposed as events. However, the evidence pack lacks detail on which specific lifecycle events (renewal, upgrade, payment failure, cancellation) are covered, delivery guarantees/retries, or reliability at scale, and a community request for additional timed hooks (revenuecat-comm-6) suggests some lifecycle notifications are still missing today. Missing for 10: documented list of webhook event types, delivery/retry guarantees, and evidence of reliability under real-world load.
- [github] “Get notified of real-time events through webhooks.”
- [claimed-docs] “The CustomerInfo object contains all of the purchase and subscription data available about a customer.”
- [community] “Feature request: handling timed hooks to send notifications, e.g. reminding users before a trial expires and subscription cancels.”
Self serve
founderMy customers can upgrade, downgrade, or cancel themselves through a hosted portal or embeddable components, without a support ticket
weight 2 · round drawnChargebeenone0/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.
RevenueCatnone0/10The evidence covers RevenueCat's SDKs, entitlements, paywalls, and dashboard analytics, but nothing describes a hosted customer portal or embeddable UI components letting end customers upgrade/downgrade/cancel without a support ticket. Community threads even discuss the difficulty of managing cross-platform (iOS/Android/Stripe) subscription moves, but no resolution or feature is cited that gives self-service cancellation/upgrade capability.
- [claimed-docs] “Paywalls — Remotely configure your product offering with powerful paywalls.”
- [community] “User considering migrating to RevenueCat asks whether it can handle users moving subscriptions between iOS/Android in-app purchases and Stri…”
- [community] “Feature request: handling timed hooks to send notifications, e.g. reminding users before a trial expires and subscription cancels.”
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 to RevenueCatChargebeenone0/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.
RevenueCat supports free-trial eligibility checks, entitlements, and granting promotional subscriptions, and webhooks could be used to build custom trial-reminder logic, but there is no documented native coupon/promo-code management or built-in trial-end notification feature — in fact a community post explicitly requests this as a missing feature ('handling timed hooks to send notifications... reminding users before a trial expires'). missing for 10: native coupon/promo-code support, built-in trial-end notification delivery, card-network compliance documentation.
- [claimed-docs] “The Purchases SDK allows for easy checking of eligibility for introductory offers on iOS, so that you as the developer can display the prope…”
- [github] “See customer transaction histories, chart lifetime value, and grant promotional subscriptions.”
- [github] “Get notified of real-time events through webhooks.”
- [community] “Feature request: handling timed hooks to send notifications, e.g. reminding users before a trial expires and subscription cancels.”
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 to ChargebeeChargebee'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.”
RevenueCatnone0/10RevenueCat is a subscription/purchase management platform focused on entitlements, offerings, and billing data — nothing in the evidence describes streaming high-volume usage events (API calls, tokens, compute-seconds) with idempotent ingestion or backdating support, which is a usage-based metering capability outside RevenueCat's documented scope.
- [claimed-docs] “The CustomerInfo object contains all of the purchase and subscription data available about a customer.”
- [claimed-docs] “Importing existing purchase data to RevenueCat can be done server-side, or client-side.”
- [claimed-docs] “RevenueCat charts allow you to understand your user base with key subscription specific metrics, filters, and segments.”
- [probe] “PROBE llms.txt: HTTP 200 at https://www.revenuecat.com/llms.txt # RevenueCat > RevenueCat is the App Monetization OS for mobile and web app…”
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 ChargebeeEvidence 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.”
RevenueCatnone0/10RevenueCat's evidence covers mobile subscription entitlements, offerings, paywalls, and analytics, but there is no mention of tiered/volume/graduated/per-unit pricing, usage-based billing, credits, commitments, or overage handling — the core usage-metering pricing models in the story are entirely absent.
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.”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableChargebeenone0/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”
RevenueCatn/aRevenueCat is a subscription/monetization backend platform, not an AI agent or assistant that a user interacts with and extends via plugged-in MCP servers. The evidence shows RevenueCat ships its OWN MCP server (revenuecat-docs-9) so that external AI assistants can call RevenueCat's tools — this is the server role, the opposite of the client-side 'plug servers into this product' story, so the axis is a category mismatch here.
- [claimed-docs] “The RevenueCat MCP (Model Context Protocol) server enables AI assistants to manage subscription apps, Products, Entitlements, and everything…”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableChargebeenone0/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.
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.