Metronome vs RevenueCat

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Metronome✓fullprobed8/10

   A direct probe confirms Metronome serves a valid llms.txt at docs.metronome.com/llms.txt (HTTP 200) listing structured doc links, and an OpenAPI spec is also available, both of which an agent could be pointed at for agent-oriented consumption. Missing for 10: no explicit vendor documentation/blog announcing or explaining the llms.txt file's purpose or independent commentary confirming agents use it successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.metronome.com/llms.txt # Metronome ## Docs - [Metronome Docs](https://docs.metronome.com/guides/g…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   RevenueCat✓fullprobed8/10

   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…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to RevenueCat
   Metronome~partialprobed4/10

   Metronome exposes a REST/API surface (bearer-token auth, OpenAPI spec, ingest endpoint, webhooks) that could be scripted headlessly in CI for usage ingestion or billing automation, but there's no documented CLI, SDK for CI pipelines, or explicit guidance/examples for running Metronome workflows in automated/headless CI contexts. missing for 10: explicit CI/headless automation documentation, official CLI or SDK examples for scripted/automated pipelines, and independent evidence of real-world CI usage.

   • [claimed-docs] “Metronome’s API uses bearer tokens to authenticate requests. This page walks through how to create and manage tokens.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Send usage events to Metronome through the /ingest endpoint or by connecting Metronome to Segment.”
   • [claimed-docs] “Metronome sends an HTTP POST request to that URL when certain events occur, such as a contract being created, a threshold being reached or a…”

   proof ↗⚑ flag

   RevenueCat~partialclaimed5/10

   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.”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to RevenueCat
   Metronome—none0/10

   No evidence of an official MCP server for Metronome; docs cover REST API, webhooks, integrations, and llms.txt/openapi probes but nothing about MCP support.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.metronome.com/llms.txt # Metronome ## Docs - [Metronome Docs](https://docs.metronome.com/guides/g…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   RevenueCat✓fullclaimed8/10

   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…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Metronome—none0/10

   No evidence of an official Metronome CLI; evidence shows API, webhooks, and integrations but nothing about a command-line tool for AI-native workflows.

   ⚑ flag

   RevenueCat—none0/10

   No 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…”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Metronome
   Metronome✓fullprobed8/10

   Metronome exposes a documented public API (bearer-token auth, ingest endpoints, subscription/webhook management) plus a verified OpenAPI spec and llms.txt for machine discoverability, confirming programmatic drivability. Missing for 10: no explicit AI-agent/SDK-for-agents examples or independent third-party confirmation of agentic usage.

   • [claimed-docs] “Send usage events to Metronome through the /ingest endpoint or by connecting Metronome to Segment.”
   • [claimed-docs] “Metronome’s API uses bearer tokens to authenticate requests. This page walks through how to create and manage tokens.”
   • [claimed-docs] “Metronome sends an HTTP POST request to that URL when certain events occur, such as a contract being created, a threshold being reached or a…”
   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.metronome.com/llms.txt # Metronome ## Docs - [Metronome Docs](https://docs.metronome.com/guides/g…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   RevenueCat~partialprobed6/10

   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…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Metronome—none0/10

   Metronome's docs confirm bearer-token API authentication but give no evidence of scoped, least-privilege, or agent-specific credential issuance — no mention of API key scopes, permission granularity, or agent-oriented tokens.

   • [claimed-docs] “Metronome’s API uses bearer tokens to authenticate requests. This page walks through how to create and manage tokens.”

   proof ↗⚑ flag

   RevenueCat—none0/10

   Evidence 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…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to RevenueCat
   Metronome—none0/10

   The evidence pack shows Metronome has a REST API, bearer-token auth, and an OpenAPI spec, but nowhere mentions official client SDKs (e.g., Node, Python, Go libraries) for developers to build against. missing for 10: explicit official SDK documentation, language-specific client libraries, SDK versioning/support info.

   • [claimed-docs] “Metronome’s API uses bearer tokens to authenticate requests. This page walks through how to create and manage tokens.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   RevenueCat✓fullclaimed8/10

   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…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Metronome✓fullclaimed7/10

   Metronome documents outbound webhooks that POST events (contract creation, threshold reached, invoice finalized) to a configured URL, directly matching the subscribe-to-events story. Missing for 10: no evidence of granular event-type filtering/selection, retry/signature verification details, or independent/hands-on confirmation of webhook reliability.

   • [claimed-docs] “Metronome sends an HTTP POST request to that URL when certain events occur, such as a contract being created, a threshold being reached or a…”

   proof ↗⚑ flag

   RevenueCat✓fullclaimed7/10

   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.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to RevenueCat
   Metronome—none0/10

   Evidence covers usage-based billing, invoicing, revenue recognition, data export and dashboards, but nothing describes AI-generated insights or suggestions surfaced within the product. Missing for 10: any mention of AI/ML-driven analytics, anomaly detection, or automated recommendations derived from billing/usage data.

   ⚑ flag

   RevenueCat✓fullclaimed8/10

   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.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to RevenueCat
   Metronome—none0/10

   Metronome is a usage-based billing platform; evidence covers ingestion, invoicing, webhooks, and subscription management, but there is no mention of autonomous background automations or agentic workflows that run independently for an AI-native user.

   ⚑ flag

   RevenueCat~partialclaimed3/10

   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…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to RevenueCat
   Metronome—none0/10

   No evidence of a built-in AI assistant within Metronome; the pack only covers billing, usage ingestion, invoicing, and reporting features.

   ⚑ flag

   RevenueCat~partialclaimed5/10

   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…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to RevenueCat
   Metronome—none0/10

   No evidence Metronome supports natural-language command interfaces, chat-based operation, or an AI assistant layer for managing billing; evidence only shows a REST API, webhooks, and dashboards. Missing for 10: any NL command interface, chat/AI assistant, or agentic control surface.

   ⚑ flag

   RevenueCat~partialclaimed6/10

   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”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Metronome—none0/10

   Evidence shows Metronome has an OpenAPI spec and auth docs, but nothing indicates an interactive API reference with runnable/try-it examples; the only 'explorer' mentioned is for event pipeline data, not API docs.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Metronome’s API uses bearer tokens to authenticate requests. This page walks through how to create and manage tokens.”
   • [claimed-docs] “The Metronome UI offers direct access to inspect your event pipeline through our dedicated event explorer.”

   proof ↗⚑ flag

   RevenueCat—none0/10

   No 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.

   • [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…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Metronome
   Metronome✓fullprobed9/10

   A direct probe confirms https://docs.metronome.com/openapi.json returns HTTP 200 with a valid 'openapi' key, i.e. a downloadable machine-readable OpenAPI spec, supplemented by an llms.txt for AI-native discovery. Missing for 10: no independent/community corroboration of using this spec in practice.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.metronome.com/llms.txt # Metronome ## Docs - [Metronome Docs](https://docs.metronome.com/guides/g…”

   proof ↗⚑ flag

   RevenueCat—none0/10

   RevenueCat 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.”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Metronome
   Metronome~partialclaimed4/10

   Docs confirm a distinct sandbox environment exists (data can be sent 'from sandbox and production' separately), implying isolated testing is possible, but there is no dedicated guide on switching to/using sandbox mode, sandbox API keys, or seeding test data without affecting production. missing for 10: explicit sandbox setup/switching docs, sandbox API key management, independent confirmation that sandbox testing never touches production billing/customer data.

   • [claimed-docs] “Metronome can send your sandbox and production data directly to your data warehouse, giving you the flexibility to build reports and dashboa…”

   proof ↗⚑ flag

   RevenueCat—none0/10

   The evidence pack contains no mention of a sandbox/test mode, test API keys, or any mechanism to validate purchases/subscriptions without affecting production data—only production-oriented SDK, dashboard, and AI-toolkit/MCP features are described.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Metronome—none0/10

   Evidence shows an OpenAPI spec and bearer-token auth docs, but nothing about API versioning scheme or a documented deprecation policy. Missing for 10: explicit API version headers/paths, changelog, deprecation/sunset policy documentation.

   • [claimed-docs] “Metronome’s API uses bearer tokens to authenticate requests. This page walks through how to create and manage tokens.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   RevenueCat—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; OpenAPI spec probes returned 404s and no docs mention version lifecycle or deprecation commitments.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.revenuecat.com/openapi.json, https://www.revenuecat.com/swagger.json, https://www.revenu…”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.revenuecat.com/docs.md”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Metronome
   Metronome~partialprobed5/10

   Metronome supports high-throughput event ingestion (up to 110k events/sec) and bulk import of existing invoices/contracts, and exposes a full REST API (openapi.json) that could be scripted for bulk operations. However there is no explicit documentation of a batch/bulk endpoint for operations like updating many customers, contracts, or seats at once beyond single-entity API calls. Missing for 10: dedicated bulk/batch API endpoints, documented bulk update/delete operations across many resources, and any AI-native tooling (SDK helpers, scripts) demonstrating bulk operations in practice.

   • [claimed-docs] “Metronome's infrastructure supports up to 110,000 events per second (6.6 million events per minute) without requiring pre-aggregation or rol…”
   • [claimed-docs] “Metronome offers a unified source of truth for your customers' billing history, even if you initially provisioned them outside of Metronome.…”
   • [claimed-docs] “Understand how to change the number of seats on a subscription, monitor active balance, and poll history of edits.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   RevenueCat—none0/10

   The 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.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Metronome
   Metronome~partialclaimed5/10

   Metronome supports webhooks that fire automatically on system events (contract created, threshold reached, invoice finalized), which is a form of event-triggered automation, but there's no evidence of a general user-defined rules engine (custom conditions/actions) beyond these fixed trigger types. Missing for 10: user-configurable rule/condition builder, evidence of custom action chaining beyond webhook notification, and any UI for defining arbitrary automation logic.

   • [claimed-docs] “Metronome sends an HTTP POST request to that URL when certain events occur, such as a contract being created, a threshold being reached or a…”

   proof ↗⚑ flag

   RevenueCat~partialcommunity4/10

   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.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to RevenueCat
   Metronome—none0/10

   The 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.)

   ⚑ flag

   RevenueCat~partialclaimed3/10

   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…”

   proof ↗⚑ flag

Agent operations

1. 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 RevenueCat
   Metronome~partialprobed5/10

   Metronome exposes a programmatic API (OpenAPI spec, bearer-token auth) that can manage subscription lifecycle changes, seat/plan changes, and credits, which an agent could call. However there is no evidence of scoped/fine-grained permissions (e.g., per-action or per-resource API keys) or of an agent-oriented interface (like an MCP server or agent SDK) — only generic bearer tokens are documented. missing for 10: scoped/least-privilege permission model for API keys, explicit agent/automation integration (MCP or similar), and hands-on evidence of an agent successfully executing these billing operations end-to-end.

   • [claimed-docs] “Metronome’s API uses bearer tokens to authenticate requests. This page walks through how to create and manage tokens.”
   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”
   • [claimed-docs] “Understand how to change the number of seats on a subscription, monitor active balance, and poll history of edits.”
   • [claimed-docs] “Set up Metronome to allow customers to purchase a batch of credits upfront, with auto-recharge or gated access when credits run out.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   RevenueCat~partialclaimed6/10

   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”

   proof ↗⚑ flag

Agent queries

1. 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 RevenueCat
   Metronome~partialprobed5/10

   Metronome exposes a documented REST API (bearer-token auth, full OpenAPI spec) covering subscriptions, invoices, revenue data, and data warehouse export, which a custom agent could technically query for billing state. However, there is no evidence of a purpose-built agent/AI interface, natural-language query layer, or MCP server exposing MRR, delinquent accounts, or renewal status directly. Missing for 10: agent-facing query tools/MCP server, explicit MRR/delinquency/renewal endpoints, and any hands-on demonstration of an agent querying billing state.

   • [claimed-docs] “Metronome’s API uses bearer tokens to authenticate requests. This page walks through how to create and manage tokens.”
   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”
   • [claimed-docs] “Understand how to change the number of seats on a subscription, monitor active balance, and poll history of edits.”
   • [claimed-docs] “Metronome stores all of the raw data necessary to manage complex revenue recognition for usage-based business models.”
   • [claimed-docs] “Metronome can send your sandbox and production data directly to your data warehouse, giving you the flexibility to build reports and dashboa…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   RevenueCat~partialclaimed6/10

   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.”

   proof ↗⚑ flag

Billing cycles

1. ops userControl billing anchors and cycles — calendar vs anniversary billing, alignment across a customer's subscriptions, custom invoice dates

   weight 2 · round drawn
   Metronome—none0/10

   The evidence covers subscription lifecycle, seats, invoicing integrations, and revenue recognition, but nothing addresses billing anchor control, calendar vs anniversary billing alignment, or custom invoice date setting. This is a plausible axis for a billing platform, but no evidence demonstrates the specific capability.

   ⚑ flag

   RevenueCat—none0/10

   No evidence pack items mention billing anchor/cycle controls, calendar vs anniversary billing alignment, or custom invoice dates — RevenueCat's documented features focus on entitlements, purchases, offerings, and analytics, not invoice/billing-cycle configuration.

   ⚑ flag

Proration

1. 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 Metronome
   Metronome~partialclaimed5/10

   Docs confirm subscription lifecycle management (upgrades/downgrades), seat-change balance tracking with edit history, and revenue-recognition data storage, which together imply proration handling, but none of the evidence documents the actual proration formulas, credit line-item breakdowns, or penny-level reconciliation examples a finance lead would need for audit. Missing for 10: explicit proration/credit calculation documentation, sample invoice line-item reconciliation, and independent/finance-user validation that math ties out to the penny.

   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”
   • [claimed-docs] “Understand how to change the number of seats on a subscription, monitor active balance, and poll history of edits.”
   • [claimed-docs] “Metronome stores all of the raw data necessary to manage complex revenue recognition for usage-based business models.”
   • [claimed-docs] “Use Metronome’s native Stripe integration to invoice your customers with Stripe. ... Metronome automatically creates a corresponding invoice…”

   proof ↗⚑ flag

   RevenueCat—none0/10

   No evidence addresses proration math, credits, partial-period calculations, or invoice line-item reconciliation; documentation covers entitlements, SDKs, paywalls, and dashboards but nothing about auditable billing math for upgrades/downgrades.

   ⚑ flag

Card recovery

1. ops userExpiring or replaced cards update themselves — network account updater, backup payment methods, and hosted update-payment pages

   weight 2 · round drawn
   Metronome—none0/10

   Metronome delegates payment collection to Stripe (metronome-docs-5) but no evidence describes card updater networks, backup payment methods, or hosted update-payment pages being managed by Metronome itself; this is a Stripe-level dunning feature not documented here.

   • [claimed-docs] “Use Metronome’s native Stripe integration to invoice your customers with Stripe. ... Metronome automatically creates a corresponding invoice…”

   proof ↗⚑ flag

   RevenueCat—none0/10

   RevenueCat'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.

   ⚑ flag

Dunning comms

1. ops userConfigure automated dunning sequences — branded emails, in-app banners, grace periods, and final-state rules like cancel vs unpaid

   weight 2 · round drawn
   Metronome—none0/10

   Evidence covers billing/invoicing, Stripe integration, revenue recognition, and webhooks, but nothing addresses dunning sequences, branded emails, in-app banners, grace periods, or cancel-vs-unpaid final states. Missing for 10: any mention of dunning workflows, email/banner templates, grace period configuration, or automated account state transitions.

   • [claimed-docs] “Use Metronome’s native Stripe integration to invoice your customers with Stripe. ... Metronome automatically creates a corresponding invoice…”
   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”

   proof ↗⚑ flag

   RevenueCat—none0/10

   The 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”

   proof ↗⚑ flag

Smart retries

1. finance leadFailed renewal payments are retried automatically on an ML- or schedule-optimized cadence that measurably recovers involuntary churn

   weight 3 · round drawn
   Metronome—none0/10

   Evidence shows Metronome handles invoicing (including Stripe integration for payment collection), subscription lifecycle, and revenue reporting, but there is no mention of automated dunning/retry logic, ML- or schedule-optimized payment retry cadences, or churn recovery metrics. This is a distinct dunning-recovery capability that would need explicit documentation to credit.

   • [claimed-docs] “Use Metronome’s native Stripe integration to invoice your customers with Stripe. ... Metronome automatically creates a corresponding invoice…”
   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”

   proof ↗⚑ flag

   RevenueCat—none0/10

   No evidence in the pack mentions failed payment retry logic, dunning, billing recovery, or ML/schedule-optimized retry cadences; RevenueCat evidence covers entitlements, paywalls, SDKs, analytics, and AI tools but nothing about involuntary churn recovery.

   ⚑ flag

Entitlement checks

1. 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 RevenueCat
   Metronome—none0/10

   Evidence covers usage ingestion, invoicing, subscription lifecycle, and revenue recognition, but nothing describes entitlements modeling attached to plans or a runtime entitlement-check API/SDK. This is a fair question for a usage-based billing/pricing platform, but no evidence supports it.

   ⚑ flag

   RevenueCat✓fullclaimed8/10

   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.”

   proof ↗⚑ flag

Plan versioning

1. ops userChange pricing without breaking existing subscribers — versioned plans, grandfathering, and bulk migration tools for moving cohorts to new prices

   weight 2 · round to Metronome
   Metronome~partialclaimed4/10

   Docs show subscription lifecycle management including pricing changes, upgrades/downgrades, and seat changes, which implies some ability to alter pricing for individual subscribers without full evidence of plan versioning or grandfathering mechanics. There's no explicit mention of bulk migration tooling for moving entire cohorts to new pricing. Missing for 10: versioned plan definitions, grandfathering logic for existing subscribers, and bulk/cohort migration tooling.

   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”
   • [claimed-docs] “Understand how to change the number of seats on a subscription, monitor active balance, and poll history of edits.”

   proof ↗⚑ flag

   RevenueCat—none0/10

   While 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.”

   proof ↗⚑ flag

Invoices

1. ops userThe platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automatically

   weight 2 · round to Metronome
   Metronome~partialclaimed3/10

   Metronome documents invoice generation (via Stripe integration) and importing/managing invoices, showing it can produce and deliver invoices automatically, but there is no evidence of sequential invoice numbering, credit notes, receipts, custom fields, or memos as compliance features. missing for 10: sequential numbering, credit notes, receipts, custom fields, memos.

   • [claimed-docs] “Use Metronome’s native Stripe integration to invoice your customers with Stripe. ... Metronome automatically creates a corresponding invoice…”
   • [claimed-docs] “Metronome offers a unified source of truth for your customers' billing history, even if you initially provisioned them outside of Metronome.…”

   proof ↗⚑ flag

   RevenueCat—none0/10

   No evidence RevenueCat generates compliant invoices, credit notes, or receipts with sequential numbering, custom fields, or memos; evidence covers subscription management, entitlements, paywalls, and analytics only.

   ⚑ flag

Multi currency

1. finance leadBill customers in their local currency with per-currency price points and consolidated reporting in my home currency

   weight 2 · round drawn
   Metronome—none0/10

   The evidence pack contains no mention of multi-currency support, per-currency price points, FX conversion, or consolidated home-currency reporting anywhere in Metronome's docs, integrations, or reporting features. Billing platforms commonly support multi-currency, so this axis applies, but no evidence confirms the capability. Missing for 10: any documentation of currency configuration, FX rate handling, or currency-consolidated financial reporting.

   ⚑ flag

   RevenueCat—none0/10

   No 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.

   ⚑ flag

Tax

1. 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 drawn
   Metronome—none0/10

   No evidence of native tax calculation or a first-class tax integration (e.g., Avalara, Stripe Tax, TaxJar) anywhere in the evidence pack; only Stripe invoicing integration for payment collection is mentioned, not tax logic.

   ⚑ flag

   RevenueCat—none0/10

   No 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.

   ⚑ flag

Export

1. 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 Metronome
   Metronome~partialclaimed5/10

   Metronome docs show data warehouse export of usage/invoice/contract data and an import path for existing contracts/invoices, suggesting some data portability, but there is no evidence of a dedicated 'export everything' migration tool or of exporting/porting stored payment methods (which live in Stripe, not Metronome) to another provider. Missing for 10: explicit payment-method export/portability feature, and a documented full-account export/migration workflow for finance leads leaving the platform.

   • [claimed-docs] “Metronome offers a unified source of truth for your customers' billing history, even if you initially provisioned them outside of Metronome.…”
   • [claimed-docs] “Metronome can send your sandbox and production data directly to your data warehouse, giving you the flexibility to build reports and dashboa…”
   • [claimed-docs] “Use Metronome’s native Stripe integration to invoice your customers with Stripe. ... Metronome automatically creates a corresponding invoice…”

   proof ↗⚑ flag

   RevenueCat~partialcommunity4/10

   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…”

   proof ↗⚑ flag

Import

1. 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 RevenueCat
   Metronome~partialclaimed3/10

   Metronome docs show it can import existing contracts/invoices from outside systems and manage subscription lifecycle/seats, giving a foundation for migrating billing data, and its Stripe integration handles payment processing which is PCI-compliant by nature of using Stripe. However, there is no explicit documentation of a spreadsheet-import workflow, no dedicated migration tooling, and no mention of transferring stored card data (vaulted PANs) between platforms or ensuring seamless/no-notice cutover for live subscriptions. Missing for 10: dedicated spreadsheet/CSV migration tooling, explicit PCI card-data transfer/vaulting process, documented zero-downtime cutover guarantees, and independent case studies of live migrations.

   • [claimed-docs] “Metronome offers a unified source of truth for your customers' billing history, even if you initially provisioned them outside of Metronome.…”
   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”
   • [claimed-docs] “Understand how to change the number of seats on a subscription, monitor active balance, and poll history of edits.”
   • [claimed-docs] “Use Metronome’s native Stripe integration to invoice your customers with Stripe. ... Metronome automatically creates a corresponding invoice…”

   proof ↗⚑ flag

   RevenueCat~partialcommunity4/10

   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…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Metronome~partialprobed6/10

   Metronome documents extensive API coverage for core billing operations (usage ingestion, subscriptions, seats, invoices, webhooks, revenue recognition, data export) and has a public OpenAPI spec, suggesting broad API-UI parity. However, docs explicitly call out UI-only features like the 'event explorer' for pipeline inspection, and no evidence confirms parity for UI-specific customization like the in-product billing dashboard. Missing for 10: explicit statement or evidence of full API parity for the event explorer and dashboard customization features, and independent/hands-on confirmation of parity claims.

   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”
   • [claimed-docs] “Understand how to change the number of seats on a subscription, monitor active balance, and poll history of edits.”
   • [claimed-docs] “Metronome stores all of the raw data necessary to manage complex revenue recognition for usage-based business models.”
   • [claimed-docs] “Metronome can send your sandbox and production data directly to your data warehouse, giving you the flexibility to build reports and dashboa…”
   • [claimed-docs] “The Metronome UI offers direct access to inspect your event pipeline through our dedicated event explorer.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   RevenueCat~partialprobed6/10

   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…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Metronome
   Metronome~partialprobed5/10

   Metronome documents exporting usage/billing data to a customer's own data warehouse and provides an OpenAPI-described API for programmatic access to raw event and invoice data, giving a path to open-format export. However there is no documented one-click 'export everything and leave' capability, no explicit open-format (CSV/JSON) account-wide export guarantee, and no mention of full account/data portability upon offboarding. missing for 10: explicit full-account export/offboarding docs, named open export formats, independent confirmation of complete data portability.

   • [claimed-docs] “Metronome can send your sandbox and production data directly to your data warehouse, giving you the flexibility to build reports and dashboa…”
   • [claimed-docs] “Metronome stores all of the raw data necessary to manage complex revenue recognition for usage-based business models.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   RevenueCat~partialprobed4/10

   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…”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to RevenueCat
   Metronome—none0/10

   The 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.)

   ⚑ flag

   RevenueCat~partialclaimed3/10

   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.”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Metronome—none0/10

   Metronome is a hosted SaaS billing platform with no evidence of a self-hostable core product, on-prem deployment package, or open-source release; all evidence pack items describe cloud API/docs usage only.

   ⚑ flag

   RevenueCat—none0/10

   RevenueCat 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.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Metronome—none0/10

   No evidence pack items mention data residency, region selection, or data storage location controls for Metronome; all citations concern billing, ingestion, webhooks, and integrations. missing for 10: any mention of data residency options, regional storage, or compliance certifications tied to geography.

   ⚑ flag

   RevenueCat—none0/10

   No evidence of data residency/region selection controls in RevenueCat's docs, GitHub, or community sources; nothing addresses where customer/subscription data is stored or region choice.

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Metronome—none0/10

   Metronome is a usage-based billing platform; evidence covers ingestion, invoicing, webhooks, revenue recognition, etc., but nothing addresses data retention policies, deletion controls, or privacy/data lifecycle management for AI-native users. Missing for 10: any documentation on data retention periods, deletion/erasure APIs, or privacy controls.

   ⚑ flag

   RevenueCat—none0/10

   No evidence describes data retention policies, deletion controls, or GDPR/CCPA-style data management features for RevenueCat customers or end-users; evidence covers subscription management, entitlements, dashboards, and AI tooling only.

   ⚑ flag

Analytics

1. 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 RevenueCat
   Metronome—none0/10

   Evidence shows Metronome stores raw billing/revenue-recognition data and can export data to a warehouse for building reports with 'your favorite data tools' — i.e., analytics are explicitly bolted-on via external BI, not computed natively as MRR/churn/cohort/LTV dashboards. No evidence of native MRR, churn, cohort retention, or LTV metrics computed inside Metronome itself.

   • [claimed-docs] “Metronome stores all of the raw data necessary to manage complex revenue recognition for usage-based business models.”
   • [claimed-docs] “Metronome can send your sandbox and production data directly to your data warehouse, giving you the flexibility to build reports and dashboa…”

   proof ↗⚑ flag

   RevenueCat~partialclaimed6/10

   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.”

   proof ↗⚑ flag

Gl sync

1. 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 drawn
   Metronome—none0/10

   Evidence shows Metronome can export data to a data warehouse and has a native Stripe integration, and stores revenue-recognition data, but there is no mention of any QuickBooks, Xero, NetSuite, or general ERP/GL sync capability. Missing for 10: any documented QuickBooks/Xero/NetSuite connector or GL export mapping, evidence of automated journal-entry sync, and confirmation that finance teams avoid manual CSV reconciliation.

   • [claimed-docs] “Metronome stores all of the raw data necessary to manage complex revenue recognition for usage-based business models.”
   • [claimed-docs] “Metronome can send your sandbox and production data directly to your data warehouse, giving you the flexibility to build reports and dashboa…”
   • [claimed-docs] “Use Metronome’s native Stripe integration to invoice your customers with Stripe. ... Metronome automatically creates a corresponding invoice…”

   proof ↗⚑ flag

   RevenueCat—none0/10

   Evidence shows RevenueCat offers scheduled data exports to cloud storage/email and webhooks, but nothing about direct sync of invoices, payments, or revenue recognition entries into QuickBooks, Xero, or NetSuite ERPs.

   ⚑ flag

Revrec reports

1. 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 Metronome
   Metronome~partialclaimed4/10

   Metronome has a dedicated revenue-recognition doc claiming it stores raw data needed to manage complex revenue recognition for usage-based models, and supports data export to warehouses for building custom reports, but the evidence never explicitly mentions ASC 606/IFRS 15 compliance, deferred revenue schedules, or audit-ready recognition reports as a built-in output. missing for 10: explicit ASC 606/IFRS 15 framing, deferred revenue schedule generation details, audit-ready report examples/screenshots, independent corroboration from finance teams.

   • [claimed-docs] “Metronome stores all of the raw data necessary to manage complex revenue recognition for usage-based business models.”
   • [claimed-docs] “Metronome can send your sandbox and production data directly to your data warehouse, giving you the flexibility to build reports and dashboa…”

   proof ↗⚑ flag

   RevenueCat—none0/10

   Evidence 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.

   ⚑ flag

Lifecycle api

1. developerCreate, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboard

   weight 3 · round to Metronome
   Metronome~partialprobed6/10

   Docs confirm an API-driven subscription lifecycle (pricing changes, trials, upgrades/downgrades, seat changes) and a published OpenAPI spec, supporting programmatic management without a dashboard. However, explicit create/pause/cancel endpoint documentation and hands-on confirmation of pause/cancel specifically are not shown. missing for 10: explicit docs/examples for 'pause' and 'cancel' subscription actions, independent developer confirmation of full lifecycle via API alone.

   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”
   • [claimed-docs] “Understand how to change the number of seats on a subscription, monitor active balance, and poll history of edits.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.metronome.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   RevenueCat~partialprobed4/10

   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…”

   proof ↗⚑ flag

Lifecycle events

1. developerEvery subscription state change — renewal, upgrade, payment failure, cancellation — emits a webhook or event my systems can act on reliably

   weight 2 · round drawn
   Metronome~partialclaimed5/10

   Metronome does support webhooks triggered by events like contract creation, threshold reached, and invoice finalized (metronome-docs-4), and separately supports subscription lifecycle management for upgrades/downgrades/trials (metronome-docs-6) and Stripe invoicing for payment (metronome-docs-5). However, the evidence never confirms webhook events specifically for renewal, upgrade, payment failure, or cancellation as named in the story — only a partial overlapping set of triggers is documented. Missing for 10: explicit webhook event types for renewal/upgrade/payment-failure/cancellation, reliability guarantees (retries, delivery guarantees), and independent confirmation of webhook coverage.

   • [claimed-docs] “Metronome sends an HTTP POST request to that URL when certain events occur, such as a contract being created, a threshold being reached or a…”
   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”
   • [claimed-docs] “Use Metronome’s native Stripe integration to invoice your customers with Stripe. ... Metronome automatically creates a corresponding invoice…”
   • [claimed-docs] “Understand how to change the number of seats on a subscription, monitor active balance, and poll history of edits.”

   proof ↗⚑ flag

   RevenueCat~partialcommunity5/10

   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.”

   proof ↗⚑ flag

Self serve

1. founderMy customers can upgrade, downgrade, or cancel themselves through a hosted portal or embeddable components, without a support ticket

   weight 2 · round to Metronome
   Metronome~partialclaimed4/10

   Metronome exposes APIs to manage subscription lifecycle (upgrades, downgrades, trials, seat changes) and offers a customizable in-product billing dashboard, implying some embeddable UI capability, but there is no explicit evidence of a hosted customer self-service portal or turnkey embeddable components for customers to upgrade/downgrade/cancel themselves without engineering work or a support ticket. missing for 10: dedicated hosted customer portal, prebuilt embeddable upgrade/downgrade/cancel UI components, evidence of self-service cancellation flow.

   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”
   • [claimed-docs] “Build trust with a transparent customer journey. Customize your in-product billing dashboard to provide”
   • [claimed-docs] “Understand how to change the number of seats on a subscription, monitor active balance, and poll history of edits.”

   proof ↗⚑ flag

   RevenueCat—none0/10

   The 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.”

   proof ↗⚑ flag

Trials promos

1. 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 drawn
   Metronome~partialclaimed3/10

   Docs confirm Metronome supports managing free trials as part of subscription lifecycle management, but there is no evidence of coupons, promotion codes, automatic conversion mechanics, or card-network-mandated trial-end notifications. missing for 10: coupons/promo code support, explicit automatic trial-to-paid conversion flow, and trial-end notification/reminder functionality.

   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”

   proof ↗⚑ flag

   RevenueCat~partialcommunity3/10

   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.”

   proof ↗⚑ flag

Event ingestion

1. developerStream high-volume usage events — API calls, tokens, compute-seconds — into a metering pipeline with idempotent ingestion and backdating support

   weight 3 · round to Metronome
   Metronome~partialclaimed5/10

   Docs confirm a dedicated /ingest endpoint capable of very high throughput (110k events/sec) plus an event explorer for pipeline inspection, covering the 'stream high-volume usage events' part of the story. However, the evidence pack contains no mention of idempotent ingestion (e.g., idempotency keys/dedup) or backdating support for events. Missing for 10: explicit documentation of idempotent event ingestion and backdated event timestamp support.

   • [claimed-docs] “Send usage events to Metronome through the /ingest endpoint or by connecting Metronome to Segment.”
   • [claimed-docs] “Metronome's infrastructure supports up to 110,000 events per second (6.6 million events per minute) without requiring pre-aggregation or rol…”
   • [claimed-docs] “The Metronome UI offers direct access to inspect your event pipeline through our dedicated event explorer.”

   proof ↗⚑ flag

   RevenueCat—none0/10

   RevenueCat 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…”

   proof ↗⚑ flag

Pricing models

1. 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 Metronome
   Metronome~partialclaimed6/10

   Docs show support for enterprise deal structures (commitments, credits, one-time charges), subscription lifecycle management, and seat-based billing, all configurable without custom code (metronome-docs-6, -13, -14, -7). However, no explicit documentation confirms specific pricing structures like tiered, volume, graduated, or per-unit rate cards, or how overage is billed as distinct from commitments. missing for 10: explicit doc evidence of tiered/volume/graduated/per-unit pricing structures, explicit overage billing mechanics beyond commitments, independent corroboration of no-code configurability

   • [claimed-docs] “Use the Metronome API to manage your customer's subscription lifecycle including pricing changes, free trials, upgrades, and downgrades.”
   • [claimed-docs] “Set up Metronome to support enterprise deal requirements like prepaid and postpaid commitments, negotiated discounts, one-time charges, cont…”
   • [claimed-docs] “Set up Metronome to allow customers to purchase a batch of credits upfront, with auto-recharge or gated access when credits run out.”
   • [claimed-docs] “Understand how to change the number of seats on a subscription, monitor active balance, and poll history of edits.”

   proof ↗⚑ flag

   RevenueCat—none0/10

   RevenueCat'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.

   ⚑ flag

Usage visibility

1. 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 Metronome
   Metronome~partialclaimed6/10

   Metronome supports webhooks for threshold-reached events, an in-product billing dashboard for customer-facing transparency, and an event explorer for internal inspection of usage data, which together cover real-time visibility and alerting infrastructure. However, there's no explicit documentation of a unified 'current-cycle usage and accrued cost' real-time dashboard for internal ops teams (vs customer-facing), nor detail on configuring specific cost thresholds/alert rules beyond generic webhook triggers. Missing for 10: dedicated ops-facing real-time cost/usage dashboard, granular threshold-configuration UI/API details, and independent/hands-on confirmation that alerts fire reliably before invoicing.

   • [claimed-docs] “Metronome sends an HTTP POST request to that URL when certain events occur, such as a contract being created, a threshold being reached or a…”
   • [claimed-docs] “Build trust with a transparent customer journey. Customize your in-product billing dashboard to provide”
   • [claimed-docs] “The Metronome UI offers direct access to inspect your event pipeline through our dedicated event explorer.”

   proof ↗⚑ flag

   RevenueCat—none0/10

   The 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.)

   ⚑ flag