Recurly vs RevenueCat
Recurly
Recurly, Inc.
Recurly wins · 16–14 (19 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 RecurlyA 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.”
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 RevenueCatRecurly 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.”
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 to RevenueCatRecurly 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”
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 drawnRecurlynone0/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.”
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 RecurlyRecurly 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”
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 drawnRecurlynone0/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”
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 drawnRecurly 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”
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 to RevenueCatThe 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…”
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 RevenueCatRecurlynone0/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”
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 RecurlyRecurly 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.”
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 RevenueCatRecurlynone0/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”
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 to RevenueCatRecurly'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”
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 drawnRecurlynone0/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”
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 drawnRecurlynone0/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”
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 drawnRecurlynone0/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 drawnRecurlynone0/10The evidence pack covers subscription features, client libraries, and an MCP server, but contains no documentation of API versioning schemes or a deprecation policy. Missing for 10: any mention of API version headers/URLs, changelog, or a documented deprecation/sunset policy.
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 RecurlyRecurly'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”
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 drawnRecurly 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…”
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 RecurlyRecurly'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.”
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 to RevenueCatRecurly 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”
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 RevenueCatRecurly 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”
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 to RecurlyEvidence 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 RecurlyRecurly'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 to RecurlyDocs 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.”
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 RecurlyDocs 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…”
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 RecurlyRecurly 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 RevenueCatRecurly'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”
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 drawnRecurlynone0/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.”
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 to RecurlyDocs 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 drawnRecurlynone0/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'.
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 drawnRecurlynone0/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.
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 RecurlyRecurly 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…”
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 RevenueCatRecurly'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…”
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 drawnDocs 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”
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 drawnRecurly 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…”
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 RevenueCatRecurlynone0/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 drawnRecurlynone0/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 drawnRecurlynone0/10No evidence in the pack mentions data residency, regional storage options, or geographic data control for Recurly; this is a fair axis for a SaaS billing platform handling customer/payment data, but absence of evidence means 'none'.
ai-native userControl data retention and deletion
weight 2 · round drawnRecurlynone0/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 to RevenueCatRecurlynone0/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.”
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 drawnRecurlynone0/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 drawnRecurlynone0/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.
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 RecurlyDocs 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”
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 RevenueCatRecurlynone0/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…”
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 to RecurlyDocs 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.”
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 RevenueCatRecurlynone0/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.
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 RecurlyRecurly 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.”
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 RecurlyRecurly'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.”
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 drawnRecurlynone0/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 userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableRecurlynone0/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”
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 comparableRecurlynone0/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.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableRecurlyn/aRecurly is a subscription billing/payments platform, not an AI model or AI product that trains on user data; the axis of preventing data use for AI training does not apply to its category.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableRecurlyn/aRecurly is a subscription billing platform, not an AI agent/tool whose telemetry or usage-tracking opt-out would be a meaningful axis for AI-native users; this consumer-privacy-style story doesn't map to its product category.