Orb vs RevenueCat
Orb wins · 18–12 (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 OrbA live probe confirms Orb serves a proper llms.txt at docs.withorb.com/llms.txt returning HTTP 200 with structured links to docs, directly satisfying the agent-oriented docs discovery story. Missing for 10: no independent third-party corroboration of agent usage/adoption beyond the probe itself.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.withorb.com/llms.txt # Orb - [Overview](https://docs.withorb.com/overview.md) - [What is Orb?](htt…”
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 RevenueCatOrb is API-first for core actions (e.g., subscription creation, event ingestion, webhooks) which implies operations can be automated without the UI, but there is no evidence of a CLI, SDK, or explicit CI/pipeline integration story — the evidence never discusses running Orb 'headlessly' in an automation/CI context. missing for 10: CLI or SDK for automation, explicit CI/pipeline integration examples, documentation framing API use as headless/agentic automation.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Orb provides per-event idempotency through the API to guarantee that duplicates are never processed within the account grace period.”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
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 RevenueCatOrbnone0/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 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 drawnOrbnone0/10Orb is a billing platform; the evidence pack shows no official CLI for AI-native or agentic workflows anywhere in its docs, only API/UI/webhooks and data export features. This is a fair axis (many SaaS platforms ship CLIs), so absence of evidence yields 'none' rather than 'na'.
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 OrbOrb's docs explicitly reference creating subscriptions via API, an api-reference error-responses page, per-event idempotency through the API, and a real-time webhooks system, indicating a documented public API spanning core billing operations. Missing for 10: a discoverable machine-readable OpenAPI/swagger spec (probe returned 404 on all candidates) and independent third-party corroboration of API usage.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “If you are processing an error programmatically, consider using the type URI along with the status code.”
- [claimed-docs] “Orb provides per-event idempotency through the API to guarantee that duplicates are never processed within the account grace period.”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
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 drawnOrbnone0/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/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 RevenueCatOrbnone0/10The evidence pack shows Orb has a REST API (endpoints, error responses, webhooks) but contains no mention of official language SDKs (e.g., Python, Node, Java client libraries), and the OpenAPI probe returned 404s, suggesting no public spec/SDK generation surface. Missing for 10: any documentation of official SDKs, client libraries, or language-specific packages for building AI-native integrations.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “If you are processing an error programmatically, consider using the type URI along with the status code.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
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 drawnOrb documents a real-time webhooks system that issues calls to an endpoint for account events, directly enabling event subscription. Missing for 10: details on event payload schema, list of supported event types, signature verification/security, and independent/hands-on confirmation beyond docs.
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
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 RevenueCatOrbnone0/10Orb is a billing/usage-metering platform; evidence covers forecasting, revenue recognition, invoicing, and pricing analytics, but none describes AI-generated insights or suggestions surfaced within the product itself. No mention of AI/ML features, copilots, or generative recommendations anywhere in the docs pack.
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 OrbOrb has several autonomous background processes (auto dunning retries, automatic invoice issuance after grace periods, usage-threshold alerts, and real-time webhooks) that run without manual intervention, which partially satisfies 'automations that run in the background.' However there is no evidence of an AI-native automation builder, agent-configurable workflows, or general-purpose autonomous task orchestration beyond these fixed billing behaviors. Missing for 10: user-configurable automation/workflow engine, AI-agent-triggered automation setup, evidence of arbitrary background task scheduling beyond billing-specific triggers.
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
- [claimed-docs] “Trigger alerts at usage thresholds to power product-led growth.”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
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 RevenueCatOrbnone0/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 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 RevenueCatOrbnone0/10No evidence anywhere in the pack of a natural-language interface, chat/AI assistant, or NL-driven command execution for Orb; all documented interactions are via UI or REST/SQL APIs.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Build complex billing metrics with full SQL control.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
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 drawnOrbnone0/10Evidence only shows standard API reference docs (e.g., error-responses.md) but no mention of an interactive explorer or runnable code examples; the openapi spec probe returned 404s, suggesting no discoverable machine-readable spec to power such interactivity.
- [claimed-docs] “If you are processing an error programmatically, consider using the type URI along with the status code.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
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 drawnOrbnone0/10The evidence pack shows explicit probes for a machine-readable OpenAPI spec (openapi.json, swagger.json, etc.) all returning 404, and no docs page offers a downloadable API spec — only an llms.txt index and general API reference mentions. Missing for 10: any working OpenAPI/Swagger endpoint, a documented spec download link, or third-party confirmation of spec availability.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.withorb.com/llms.txt # Orb - [Overview](https://docs.withorb.com/overview.md) - [What is Orb?](htt…”
- [claimed-docs] “If you are processing an error programmatically, consider using the type URI along with the status code.”
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 drawnOrbnone0/10The axis applies since billing/API platforms commonly offer sandbox/test environments, but the evidence pack never mentions a distinct sandbox or test-mode environment isolated from production data — only 'testing pricing changes against historical usage' (orb-docs-1), which is backtesting, not a sandbox. missing for 10: explicit sandbox/test-mode environment, API keys or docs distinguishing test vs live data, confirmation that test data never touches production.
- [claimed-docs] “Test pricing changes against historical usage before deploying.”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnOrbnone0/10No evidence pack item documents API versioning scheme or a deprecation policy; only error-response handling and general docs are covered. Missing for 10: versioning scheme (e.g., date-based API versions), deprecation/sunset policy, changelog or migration guides for breaking changes.
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 OrbOrb documents high-throughput event ingestion (1M+ events/sec) and backfilling historical usage events, which are forms of bulk data operations, but there is no explicit documentation of a bulk/batch API for operations like mass-editing subscriptions, invoices, or other resources. missing for 10: explicit bulk/batch API endpoints for subscriptions, invoices, or other catalog items; UI or API support for multi-item batch edits.
- [claimed-docs] “Handle 1M+ billing events per second in production deployments.”
- [claimed-docs] “If you want Orb to generate accurate invoices or analytics based on prior usage data, you can backfill events.”
- [claimed-docs] “Orb provides per-event idempotency through the API to guarantee that duplicates are never processed within the account grace period.”
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
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 OrbOrb offers usage-threshold alerts and a real-time webhooks system that fires on defined events, which functions as event-triggered automation, and dunning/invoice issuance include automatic rule-based actions (auto-retry, auto-issue). However, these are fixed, product-specific automations rather than a general user-defined rules/actions engine (no evidence of custom conditional logic, multi-step workflows, or arbitrary action definitions). Missing for 10: a general-purpose rule builder, evidence of custom conditional logic beyond thresholds, and support for arbitrary automated actions beyond alerts/webhooks/dunning.
- [claimed-docs] “Trigger alerts at usage thresholds to power product-led growth.”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
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 drawnOrb offers some built-in recurring automated processes—daily scheduled data exports, automatic dunning retries on fixed day intervals, and automatic invoice issuance after grace periods—which are recurring, schedule-driven jobs, but these are fixed billing-domain behaviors rather than a general-purpose scheduler or workflow engine that an AI-native user could configure for arbitrary recurring tasks. Missing for 10: a documented job/workflow scheduling API or UI, support for custom recurrence rules or triggers beyond billing events, and any evidence of user-defined automation workflows.
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
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 RevenueCatOrb documents a full programmatic surface for the core actions an agent would need: creating subscriptions via API (orb-docs-8), editing subscription pricing/config (orb-docs-10, orb-docs-11), and plan changes with automatic proration credit (orb-docs-16). However, there is no evidence of a scoped-permission or API-key-role model that would let an agent operate with restricted access rather than full account credentials — the error-handling doc (orb-docs-15) only covers error codes, not auth scopes, and the OpenAPI spec probe returned 404s (orb-probe-2), leaving the permission-scoping mechanism unverified. missing for 10: documented scoped API keys/OAuth roles for agent-level permissions, an official agent/MCP-style integration, independent confirmation that these endpoints support least-privilege access.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Preview the billing and invoice impact before you save, so you can confirm how charges and invoices will look.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
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 RevenueCatOrbnone0/10Evidence covers billing mechanics (dunning, revenue recognition, invoice issuance, exports) but nothing shows an agent-facing query interface for aggregate billing state like MRR, delinquent-account lists, or renewal schedules — no MCP server, natural-language API, or reporting endpoint is documented, and the openapi probe returned 404s, undermining even basic API discoverability for an autonomous agent.
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
- [claimed-docs] “Orb automatically calculates recognized revenue in a way that accords with ASC606 guidelines.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
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 OrbDocs confirm subscriptions can be aligned to the creation date (anniversary billing) and that billing cycle alignment is configurable, but there's no explicit evidence of calendar-vs-anniversary toggle, cross-subscription cycle alignment for a single customer, or custom invoice date overrides. Missing for 10: explicit calendar billing option, multi-subscription alignment mechanics, custom invoice date configuration.
- [claimed-docs] “Orb also allows you to align the billing cycles with the date that the subscription was created.”
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
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 OrbOrb documents day-based proration on plan changes, credits for unused time, a preview of billing/invoice impact before saving edits, and minimum/maximum charge handling — supporting the core proration and invoice line-item math. However, there is no explicit documentation of penny-level reconciliation guarantees, detailed audit trails, or worked examples showing exact credit/debit math across partial periods. missing for 10: worked/auditable proration examples, explicit 'reconciles to the penny' guarantee, audit-log/traceability documentation for finance review.
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Preview the billing and invoice impact before you save, so you can confirm how charges and invoices will look.”
- [claimed-docs] “Minimums: Ensures a minimum charge is applied. Maximums: Caps the charge at a certain amount.”
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 drawnOrbnone0/10Evidence covers dunning retry scheduling (orb-docs-19) but there is no mention of network account updater, backup payment methods, or hosted update-payment pages anywhere in the pack, so the specific card-self-update capability is unevidenced.
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
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 OrbOrb docs confirm basic dunning mechanics — automatic payment retries at 1/4/9 days (orb-docs-19) and automatic vs manual invoice issuance after grace periods (orb-docs-21) — but there is no evidence of branded/customizable dunning emails, in-app banners, or configurable final-state rules like cancel vs unpaid. missing for 10: branded email templates, in-app banner/notification configuration, customizable grace period settings beyond fixed retry schedule, and explicit cancel-vs-unpaid final state logic.
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
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 OrbOrb documents automatic dunning retries on a fixed schedule (1, 4, and 9 days after failed payment) via its 'essential-dunning' feature, which addresses the schedule-optimized retry cadence for involuntary churn recovery. However, there is no evidence of ML-based optimization of retry timing, nor any documented metrics or case studies showing measurable churn recovery impact. Missing for 10: ML-driven retry optimization, evidence of measured recovery rates/churn reduction, configurability of retry cadence per customer segment.
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
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 RevenueCatOrbnone0/10The evidence pack covers subscriptions, plans, usage metrics, invoicing, and revenue recognition, but nowhere mentions entitlements, feature-level access modeling, or an API/SDK for checking a customer's entitlements at runtime. Since billing platforms plausibly could offer such a feature, the axis applies, but there is no supporting evidence.
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 to OrbOrb documents subscription-level pricing edits with pre-save impact previews, proration on plan changes, and a Stripe migration path with usage backfill — enabling controlled repricing without breaking existing invoices. But there is no explicit documentation of plan versioning, formal grandfathering mechanisms, or a bulk cohort-migration tool for moving many subscribers to new prices at once. missing for 10: explicit plan-versioning/grandfathering feature, bulk cohort migration tooling beyond one-off Stripe import, evidence of moving existing subscriber cohorts to a new plan version at scale.
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Preview the billing and invoice impact before you save, so you can confirm how charges and invoices will look.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
- [claimed-docs] “Orb supports a seamless migration from Stripe Billing, whether you're using flat-rate subscriptions, usage-based pricing, pricing on seats, …”
- [claimed-docs] “If you want Orb to generate accurate invoices or analytics based on prior usage data, you can backfill events.”
- [claimed-docs] “Test pricing changes against historical usage before deploying.”
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 OrbOrb documents automatic invoice issuance, proration/minimums/maximums calculations, and revenue recognition, indicating invoices are generated and delivered automatically, but there is no explicit evidence of sequential invoice numbering, credit note generation, receipts, or custom fields/memos on invoices. missing for 10: sequential numbering guarantees, credit note issuance, receipt generation, custom fields/memo support on invoices, and independent confirmation of compliance formatting.
- [claimed-docs] “Minimums: Ensures a minimum charge is applied. Maximums: Caps the charge at a certain amount.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
- [claimed-docs] “Orb automatically calculates recognized revenue in a way that accords with ASC606 guidelines.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
Multi currency
finance leadBill customers in their local currency with per-currency price points and consolidated reporting in my home currency
weight 2 · round drawnOrbnone0/10No evidence in the pack mentions multi-currency support, per-currency price points, or currency-consolidated reporting; Orb's docs cover proration, revenue recognition, dunning, invoicing but nothing about local currency billing or FX consolidation.
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 drawnOrbnone0/10The evidence pack covers billing, metering, revenue recognition, dunning, and invoicing calculations but contains no mention of sales tax, VAT, GST calculation, tax registrations, or a first-class tax integration (e.g., Avalara, Stripe Tax). This is a fair axis for a billing/invoicing platform, so absent evidence yields 'none' rather than 'na'.
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 drawnOrb documents managed daily data exports of resource types to any destination (orb-docs-12) and revenue/financial exports (orb-docs-7), which could cover subscriptions/invoices/usage, but there is no evidence describing exporting stored payment methods or any outbound migration path — the only migration content covers importing customers *into* Orb from Stripe (orb-docs-13, orb-docs-14), not leaving Orb for another provider. Missing for 10: explicit payment-method export/portability, confirmation that exports cover all three record types comprehensively, and documentation of an outbound/offboarding migration process.
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
- [claimed-docs] “Track recognized and deferred revenue with exports for financial systems.”
- [claimed-docs] “Orb supports a seamless migration from Stripe Billing, whether you're using flat-rate subscriptions, usage-based pricing, pricing on seats, …”
- [claimed-docs] “If you want Orb to generate accurate invoices or analytics based on prior usage data, you can backfill events.”
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 drawnOrb documents migration from Stripe Billing (including flat-rate, usage-based, seat pricing) and backfilling historical usage events for accurate invoicing, which supports competing-platform migration. However there is no evidence of spreadsheet-based import tooling, PCI-compliant card/payment-method data transfer, or explicit assurances that migration is seamless enough that customers won't notice. Missing for 10: spreadsheet import support, PCI-compliant card data transfer mechanism, and documentation/testimony of zero customer disruption during migration.
- [claimed-docs] “Orb supports a seamless migration from Stripe Billing, whether you're using flat-rate subscriptions, usage-based pricing, pricing on seats, …”
- [claimed-docs] “If you want Orb to generate accurate invoices or analytics based on prior usage data, you can backfill events.”
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
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 many UI actions—creating subscriptions, editing subscriptions, configuring billing metrics, exports, webhooks—are explicitly available via API endpoints (orb-docs-8, orb-docs-10, orb-docs-12, orb-doces-18, orb-docs-23), suggesting strong UI/API parity for core billing workflows. However there is no explicit blanket claim that 'everything in the UI is possible via API,' and a probe for a public OpenAPI/swagger spec returned 404s, weakening confidence in full documented API surface coverage. missing for 10: an explicit parity statement, a discoverable full API reference/OpenAPI spec, and confirmation that dashboard-only features (e.g., invoice approval UI, analytics dashboards) have full API equivalents.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
- [claimed-docs] “A billable metric consists of event filters as well as an aggregation clause.”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
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 drawnOrb supports managed daily exports of resource types to a destination of choice and revenue/financial exports, which gives data portability, but this is billing-data export for downstream systems rather than a full account-level open-format export-and-leave capability aimed at an AI-native user. missing for 10: explicit full account/data export (all entities, configs, historical events) in open formats, documented data portability/deletion workflow for leaving the platform, and independent confirmation of export completeness.
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
- [claimed-docs] “Track recognized and deferred revenue with exports for financial systems.”
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 RevenueCatOrbnone0/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 drawnOrbnone0/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 drawnOrbnone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
ai-native userControl data retention and deletion
weight 2 · round drawnOrbnone0/10The evidence pack covers billing, invoicing, revenue recognition, and data exports, but contains no mention of customer data retention policies, deletion APIs, or privacy controls for AI-native users. This is an applicable axis for any SaaS handling customer data, but there is no evidence Orb provides retention/deletion controls.
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 RevenueCatOrb documents revenue-related metrics computed from billing data itself (accrued revenue, recognized/deferred revenue per ASC606, expansion forecasting) rather than a bolted-on BI export, and supports data exports/SQL for custom analytics. However, there is no explicit mention of MRR, churn, cohort retention, or LTV dashboards as native analytics features — these appear to require building via SQL/export rather than being out-of-the-box computed metrics. missing for 10: explicit MRR/churn/cohort retention/LTV dashboards or reports, evidence these are native computed analytics rather than DIY SQL queries, independent confirmation of accuracy/usability.
- [claimed-docs] “Track accrued revenue before invoices. Forecast and spot expansion.”
- [claimed-docs] “Build complex billing metrics with full SQL control.”
- [claimed-docs] “Track recognized and deferred revenue with exports for financial systems.”
- [claimed-docs] “Orb automatically calculates recognized revenue in a way that accords with ASC606 guidelines.”
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
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 to OrbOrb documents ASC606-compliant revenue recognition tracking and generic data exports 'for financial systems' to 'a data destination of your choice,' which could feed a GL, but no evidence names a native QuickBooks, Xero, or NetSuite connector or a no-CSV sync path — buyers would need to build the export pipeline themselves. Missing for 10: named ERP/accounting-system integrations, automated invoice/payment sync (not just data exports), and confirmation that no manual CSV mapping is required.
- [claimed-docs] “Track recognized and deferred revenue with exports for financial systems.”
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
- [claimed-docs] “Orb automatically calculates recognized revenue in a way that accords with ASC606 guidelines.”
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 OrbOrb explicitly automates ASC606-compliant recognized/deferred revenue calculation (orb-docs-22), tracks accrued revenue before invoicing (orb-docs-4), and supports exporting recognized/deferred revenue data for financial systems (orb-docs-7), plus general data exports to downstream destinations (orb-docs-12). This covers the core finance-lead need of ASC606 deferred revenue schedules and exportable recognition data. missing for 10: no explicit mention of IFRS 15 compliance, no detail on audit-ready report formatting/controls, and no independent/hands-on corroboration beyond vendor docs.
- [claimed-docs] “Orb automatically calculates recognized revenue in a way that accords with ASC606 guidelines.”
- [claimed-docs] “Track accrued revenue before invoices. Forecast and spot expansion.”
- [claimed-docs] “Track recognized and deferred revenue with exports for financial systems.”
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
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 OrbDocs confirm subscription creation via API (orb-docs-8), billing cycle alignment (orb-docs-9), and editing subscription pricing with preview of impact (orb-docs-10, orb-docs-11), plus plan-change proration logic (orb-docs-16) — covering create/update well. However, no explicit documentation of 'pause' or 'cancel' subscription API endpoints appears in the evidence pack, and no OpenAPI/spec confirmation was found (orb-probe-2 shows 404s for spec files), so full lifecycle coverage is unverified via API alone. Missing for 10: explicit pause/cancel endpoint documentation, confirmed OpenAPI spec listing all lifecycle operations, independent/hands-on verification of API-only workflow.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Orb also allows you to align the billing cycles with the date that the subscription was created.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Preview the billing and invoice impact before you save, so you can confirm how charges and invoices will look.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
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 OrbOrb documents a real-time webhooks system for triggering calls on event occurrence, and related lifecycle mechanics (dunning retries, proration on plan change, invoice issuance) exist, implying underlying state changes are trackable. However, the evidence never enumerates which specific lifecycle events (renewal, upgrade, cancellation, payment failure) fire webhooks, nor details delivery guarantees like retries/signing for reliability. Missing for 10: explicit list of webhook event types covering renewal/upgrade/cancellation/payment failure, documentation of delivery reliability guarantees (retries, at-least-once delivery, signature verification), and independent/hands-on confirmation of webhook reliability.
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
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 drawnOrbnone0/10The evidence pack details subscription creation, edits, plan changes, and proration via the Orb UI or API, but nowhere mentions a hosted customer-facing portal or embeddable self-serve components that end customers could use to upgrade/downgrade/cancel without a support ticket. Missing for 10: any mention of a hosted billing portal, embeddable UI components, or self-serve customer-facing flows.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Orb also allows you to align the billing cycles with the date that the subscription was created.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Preview the billing and invoice impact before you save, so you can confirm how charges and invoices will look.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
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 RevenueCatOrbnone0/10The evidence pack covers subscriptions, proration, dunning, invoicing, and revenue recognition, but contains no mention of free trials, coupon/promotion codes, automatic trial-to-paid conversion, or trial-end notifications required by card-network rules. Since Orb is a subscription billing platform, this axis is a fair question, but there is no supporting evidence for these specific capabilities.
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 OrbOrb's docs directly support high-volume streaming ingestion (1M+ events/sec), per-event idempotency guarantees, and backdating/backfill support for historical usage recalculation and invoice adjustment. missing for 10: independent/hands-on benchmarks corroborating the 1M+ events/sec claim, and more detail on the exact idempotency key mechanism/grace period edge cases.
- [claimed-docs] “Handle 1M+ billing events per second in production deployments.”
- [claimed-docs] “Orb provides per-event idempotency through the API to guarantee that duplicates are never processed within the account grace period.”
- [claimed-docs] “Late data handled safely. Orb recalculates affected invoices automatically.”
- [claimed-docs] “If you want Orb to generate accurate invoices or analytics based on prior usage data, you can backfill events.”
- [claimed-docs] “Test pricing changes against historical usage before deploying.”
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 OrbOrb's docs cover billable metrics with flexible aggregation/SQL (orb-docs-5, orb-docs-18), subscription edits and plan changes with proration (orb-docs-10, orb-docs-16), minimums/maximums for commitments and overage (orb-docs-20), and subscription/plan configuration via UI or API — collectively supporting tiered, volume, graduated, per-unit, and hybrid subscription+usage pricing without custom code. missing for 10: explicit named documentation pages for each pricing model (tiered/volume/graduated) and credits/prepaid commitment mechanics, plus independent (non-vendor) confirmation of these pricing structures in production use.
- [claimed-docs] “Build complex billing metrics with full SQL control.”
- [claimed-docs] “A billable metric consists of event filters as well as an aggregation clause.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Preview the billing and invoice impact before you save, so you can confirm how charges and invoices will look.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
- [claimed-docs] “Minimums: Ensures a minimum charge is applied. Maximums: Caps the charge at a certain amount.”
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Orb also allows you to align the billing cycles with the date that the subscription was created.”
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 OrbOrb docs confirm accrued cost/revenue tracking before invoicing (orb-docs-4), configurable usage-threshold alerts for product-led growth (orb-docs-6), and real-time webhooks for event notifications (orb-docs-23), covering the core alerting/real-time-visibility ask. missing for 10: explicit evidence of a customer-facing self-serve usage dashboard and independent/hands-on confirmation that alerts reliably fire before invoice generation.
- [claimed-docs] “Track accrued revenue before invoices. Forecast and spot expansion.”
- [claimed-docs] “Trigger alerts at usage thresholds to power product-led growth.”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableOrbn/aOrb is a billing/revenue platform, not an AI agent or MCP-serving product; the evidence covers billing, invoicing, revenue recognition and webhooks with no mention of MCP servers or agent tool integration, so this axis is a category error for this product.
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 comparableOrbn/aOrb is a usage-based billing and revenue platform, not an automation-building tool; it has no concept of 'automations' to version, review, or roll back. The evidence pack covers billing metrics, subscriptions, invoicing, and revenue recognition, none of which relate to versioning/rollback of automations, so this axis is a category mismatch for Orb's product type.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableOrbn/aOrb is a billing/revenue infrastructure platform; AI-model-training data usage opt-out is not a relevant axis for this product category, and none of the evidence touches AI training data policy.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableOrbn/aOrb is a billing/revenue platform, not an AI agent or tool with telemetry collected from AI-native usage; the evidence pack contains no telemetry/analytics-opt-out feature relevant to an 'AI-native user's own tool usage tracking. This axis is a category mismatch for a billing infrastructure product.