Recurly vs Metronome
Recurly
Recurly, Inc.
Metronome wins · 13–14 (23 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to RecurlyA live llms.txt is confirmed via direct probe (HTTP 200) at docs.recurly.com/llms.txt, and Recurly also documents a public MCP server (Compass) that connects AI dev tools directly to its documentation and API knowledge, giving agents a first-party structured path to Recurly's docs. missing for 10: independent/community confirmation of agents actually using these endpoints successfully.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.recurly.com/llms.txt # Recurly Documentation Documentation > Welcome to the Recurly Documentation …”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
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.
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnRecurly offers a full REST API and official client libraries (Ruby, Node, Python, .NET, Java, PHP, Go) which could be scripted headlessly in CI, but there is no explicit documentation of a CLI, CI/CD examples, or automation-focused tooling for headless/agentic workflows. missing for 10: explicit CI/headless usage examples, a documented CLI tool, evidence of non-interactive/automation-first design beyond generic API/SDK availability.
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [claimed-docs] “The Recurly Native Mobile SDKs allow you to integrate recurrent payments in your existing Android or iOS apps in a matter of minutes.”
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…”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round drawnRecurlynone0/10Evidence only shows Recurly publishing its own MCP server (Compass) so external AI tools can query Recurly's docs/API — this is Recurly acting as an MCP server provider, not as a client that can plug in and use other MCP servers' tools. No evidence Recurly itself can consume/plug in external MCP servers.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
Metronomenone0/10Metronome is a usage-based billing platform; no evidence anywhere in the pack mentions MCP servers or plugging tool integrations into an AI agent context. This is an applicable axis for a SaaS platform (it could ship an MCP server), but there is no evidence of one, so it is 'none' rather than 'na'.
ai-native userConnect an agent via an official MCP server
weight 3 · round to RecurlyRecurly ships an official 'Compass' MCP server that connects AI dev tools directly to Recurly's documentation and API knowledge, confirmed both in docs and via a live probe of the docs page. However, evidence only describes it as a documentation/knowledge connector, not a full agentic interface for performing billing actions (e.g., managing subscriptions, invoices) via MCP. Missing for 10: evidence of MCP tool-calling for actual account/subscription operations, independent hands-on validation of the MCP server in use.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
Metronomenone0/10No evidence of an official MCP server for Metronome; docs cover REST API, webhooks, integrations, and llms.txt/openapi probes but nothing about MCP support.
ai-native userUse an official CLI
weight 2 · round drawnRecurlynone0/10No evidence of an official Recurly CLI; documentation instead references client libraries (Ruby, Node.js, Python, etc.), mobile SDKs, and an MCP server for AI tools, but nothing about a command-line interface.
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [claimed-docs] “The Recurly Native Mobile SDKs allow you to integrate recurrent payments in your existing Android or iOS apps in a matter of minutes.”
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
ai-native userDrive the product through a documented public API
weight 3 · round drawnRecurly documents a full public API with official client libraries in seven languages, entitlements checkable via API, and even an MCP server (Compass) exposing API/doc knowledge to AI tools, indicating strong API-first, AI-accessible design. missing for 10: independent developer corroboration of API robustness/rate limits and no evidence of API versioning or webhooks documentation depth.
- [claimed-docs] “Entitlements can be applied across platforms (web, mobile, and app stores) and checked in real time via the Recurly API.”
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.recurly.com/llms.txt # Recurly Documentation Documentation > Welcome to the Recurly Documentation …”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
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”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnRecurlynone0/10No evidence of scoped or least-privilege API key/credential issuance for agents; the MCP server (recurly-docs-12, recurly-probe-2) only connects AI tools to documentation, not scoped API credentials, and no API key management or permission-scoping docs are present.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
Metronomenone0/10Metronome'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.”
ai-native userBuild against official SDKs
weight 2 · round to RecurlyRecurly documents official client libraries across seven languages (Ruby, Node.js, Python, .NET, Java, PHP, Go) plus native mobile SDKs for iOS/Android, giving AI-native developers a solid multi-language SDK surface, and an official Compass MCP server ties AI tools into its API docs. Missing for 10: independent hands-on developer confirmation of SDK quality/reliability and no explicit mention of AI-specific SDK tooling beyond the MCP docs connector.
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [claimed-docs] “The Recurly Native Mobile SDKs allow you to integrate recurrent payments in your existing Android or iOS apps in a matter of minutes.”
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
Metronomenone0/10The 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”
ai-native userSubscribe to events via webhooks
weight 2 · round to MetronomeThe only mention of webhooks in the evidence pack is an indirect community comparison noting Recurly automates retention 'without needing to implement webhooks' for dunning, implying webhook functionality exists, but no first-party documentation, API reference, or event-list evidence describes how to subscribe to or configure webhooks. Missing for 10: official webhook API/docs, list of subscribable events, setup instructions, and any AI-agent-specific webhook integration guidance.
- [community] “Comparing Stripe and Recurly: It's faster to get going with Stripe (no merchant account required) but Recurly appears to offer more automate…”
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…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round drawnRecurlynone0/10No evidence Recurly generates AI-driven insights or suggestions from a merchant's own subscription/billing data; the only AI-related feature (Compass MCP) merely connects AI dev tools to documentation/API knowledge, not to account data analytics.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
Metronomenone0/10Evidence 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.
ai-native userSet up automations that run autonomously in the background
weight 2 · round to RecurlyRecurly ships built-in autonomous background processes—dunning campaigns (up to 50 targeted campaigns), automatic backup payment method fallback, and involuntary churn recovery tools—that run without manual intervention once configured. However, there is no evidence of a general-purpose automation/workflow builder, triggers, or agent-configurable rules engine that an AI-native user could set up beyond these fixed billing-retention features. Missing for 10: a configurable automation/rules engine, evidence of user-defined triggers/actions beyond dunning, and any AI-agent-specific automation tooling.
- [claimed-docs] “merchants on Professional and Elite plans can create up to 50 targeted campaigns for different customer segments or plans”
- [claimed-docs] “Involuntary churn happens when customers are lost due to factors outside their intent — expired cards, bank changes, or failed payments. Rec…”
- [claimed-docs] “Let customers designate a backup payment method so service continues automatically if their primary payment fails.”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnRecurlynone0/10Recurly is a subscription billing platform; evidence shows an MCP server for connecting AI dev tools to documentation/API knowledge, but nothing indicates a built-in AI assistant within the product that users can delegate tasks to.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
ai-native userOperate the product with natural-language commands
weight 2 · round to RecurlyRecurly's Compass MCP server lets AI dev tools query Recurly's documentation and API knowledge, which is a step toward AI-native/agentic interaction, but the evidence describes it as a knowledge/docs connector rather than a natural-language interface for actually executing billing operations (e.g., changing subscriptions, issuing credits) end-to-end. Missing for 10: evidence of natural-language command execution for actual account/subscription actions, hands-on proof of the MCP server performing operations (not just doc lookup), and any client-facing chat/NL interface.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
Metronomenone0/10No 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.
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnRecurlynone0/10Evidence shows client libraries, SDKs, an MCP server for docs/API knowledge, and an llms.txt file, but there is no mention of an interactive API reference with runnable/live-executable examples (e.g., a try-it-now console). Missing for 10: interactive API console, runnable code examples, in-browser execution/testing of API calls.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.recurly.com/llms.txt # Recurly Documentation Documentation > Welcome to the Recurly Documentation …”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
Metronomenone0/10Evidence 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.”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to MetronomeRecurlynone0/10The evidence pack shows official client libraries, mobile SDKs, an llms.txt file, and an MCP server, but no mention of a downloadable OpenAPI/Swagger spec or any machine-readable API schema file. Since Recurly is an API-based product, this axis clearly applies, but there is no evidence of the specific capability requested.
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.recurly.com/llms.txt # Recurly Documentation Documentation > Welcome to the Recurly Documentation …”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
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.
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to MetronomeRecurlynone0/10No evidence pack item mentions a sandbox, test/dev environment, or test API keys for Recurly; documentation covers subscription changes, billing, and MCP tooling but not isolated test environments. Missing for 10: any mention of sandbox/test mode, test credentials, or separation from production data.
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…”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnRecurlynone0/10The evidence pack covers subscription features, client libraries, and an MCP server, but contains no documentation of API versioning schemes or a deprecation policy. Missing for 10: any mention of API version headers/URLs, changelog, or a documented deprecation/sunset policy.
Metronomenone0/10Evidence 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”
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 MetronomeRecurly's docs mention bulk data import/export to populate accounts and analyze records, which implies some bulk operation support, and API client libraries could theoretically be used to script batch changes. However, there is no explicit documentation of a bulk-update/bulk-cancel/bulk-modify API for subscriptions, invoices, or entitlements, nor any AI-native tooling for orchestrating such bulk actions. missing for 10: explicit bulk subscription/invoice update API, bulk operation endpoints or SDK examples, evidence of AI-driven or agentic bulk workflows, independent confirmation of bulk import scale/performance.
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Import customer data to populate accounts and records across your Recurly account.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
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”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to MetronomeRecurly ships built-in automated responses to specific billing events—dunning campaigns triggered by failed payments (up to 50 targeted campaigns) and automatic fallback to backup payment methods—but these are pre-defined behaviors within fixed billing workflows, not a general-purpose rule engine where users define arbitrary event→action logic. Missing for 10: a configurable trigger/condition/action framework (e.g., custom webhooks-driven rules, if-this-then-that automation builder) and evidence of user-defined (not just Recurly-provided) automation logic.
- [claimed-docs] “merchants on Professional and Elite plans can create up to 50 targeted campaigns for different customer segments or plans”
- [claimed-docs] “Involuntary churn happens when customers are lost due to factors outside their intent — expired cards, bank changes, or failed payments. Rec…”
- [claimed-docs] “Let customers designate a backup payment method so service continues automatically if their primary payment fails.”
- [community] “Comparing Stripe and Recurly: It's faster to get going with Stripe (no merchant account required) but Recurly appears to offer more automate…”
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…”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to RecurlyRecurly's core product is built around recurring billing cycles that run automatically (subscription renewals, usage-based billing at cycle end, dunning email campaigns), which functions as a domain-specific recurring workflow engine, but it offers no general-purpose job/task scheduler an AI-native user could configure for arbitrary recurring workflows. Missing for 10: a generic scheduling/automation API or cron-like mechanism for arbitrary AI-driven tasks, and any evidence of AI-agent-triggered scheduling beyond built-in billing cycles.
- [claimed-docs] “Recurly's usage-based billing model lets you charge customers at the end of each billing cycle based on their actual consumption”
- [claimed-docs] “merchants on Professional and Elite plans can create up to 50 targeted campaigns for different customer segments or plans”
- [claimed-docs] “Involuntary churn happens when customers are lost due to factors outside their intent — expired cards, bank changes, or failed payments. Rec…”
- [claimed-docs] “Recurly bills only the difference during an immediate change when the underlying plan is unchanged.”
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 drawnRecurly exposes a full REST API and client libraries covering subscription changes, credits, and invoices (recurly-docs-1, -2, -9, -13), which could technically be driven by an agent. However, the only AI-specific surface documented, Recurly Compass MCP, is explicitly a documentation/knowledge connector for AI dev tools, not an operational interface for executing billing actions (recurly-docs-12, recurly-probe-2), and there is no evidence of scoped/restricted API keys or permission models designed for autonomous agent use. Missing for 10: an agent-oriented action interface (e.g., MCP server or agent SDK) that can actually invoke billing operations, and documentation of scoped/least-privilege API credentials for agent access.
- [claimed-docs] “Recurly gives you full control over how and when subscription changes take effect. Upgrade or downgrade a plan, adjust quantity or price, ad…”
- [claimed-docs] “Recurly bills only the difference during an immediate change when the underlying plan is unchanged.”
- [claimed-docs] “Credit invoices give every credit its own distinct invoice — separate from charge invoices.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
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”
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 MetronomeRecurly exposes a REST API and official client libraries that could let an agent fetch account/invoice/subscription data, and entitlements are described as checkable in real time via the API. However, the only AI-agent integration evidenced (Compass MCP) is explicitly scoped to documentation and API knowledge, not live billing-state queries, and there is no evidence of dedicated endpoints/reports for MRR, delinquent-account lists, or renewal forecasts that an agent could query directly. missing for 10: evidence of an MCP or agent-facing endpoint returning MRR/delinquency/renewal data, documentation of a reporting/analytics API for these metrics, independent confirmation of agent-driven billing queries working in practice.
- [claimed-docs] “Recurly Compass MCP connects your AI development tools directly to Recurly's documentation and API knowledge.”
- [claimed-docs] “Entitlements can be applied across platforms (web, mobile, and app stores) and checked in real time via the Recurly API.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [claimed-docs] “Modify invoice details post-issuance — including account notes, due dates, PO numbers, customer notes, and terms — to keep records accurate.”
- [probe] “official MCP server documented at https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server”
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”
Billing math — stories about billing math in this arenaBilling math
Stories about billing math in this arena
Billing cycles
ops userControl billing anchors and cycles — calendar vs anniversary billing, alignment across a customer's subscriptions, custom invoice dates
weight 2 · round to RecurlyEvidence only shows post-issuance invoice detail edits (due dates, PO numbers, terms) via recurly-docs-10, which loosely touches 'custom invoice dates' but doesn't address billing anchor/cycle configuration. No documentation covers calendar-vs-anniversary billing modes or aligning billing cycles across a customer's multiple subscriptions. Missing for 10: explicit billing anchor/cycle-start configuration, calendar vs anniversary billing toggle, cross-subscription date alignment tooling, and any independent/hands-on confirmation of these mechanics.
- [claimed-docs] “Modify invoice details post-issuance — including account notes, due dates, PO numbers, customer notes, and terms — to keep records accurate.”
Metronomenone0/10The 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.
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 drawnRecurly's docs confirm mid-cycle changes are billed as prorated differences and that credits get their own separate, dedicated invoices, plus invoices can be amended post-issuance for record accuracy — supporting the core proration/credit reconciliation need. However, there's no documented breakdown of the proration math formula, no explicit audit trail feature, and no evidence (first-party or independent) that invoice reconciliation is verified to the penny in practice. Missing for 10: detailed proration calculation documentation, explicit audit-log/traceability feature, and independent verification of penny-accurate reconciliation.
- [claimed-docs] “Recurly bills only the difference during an immediate change when the underlying plan is unchanged.”
- [claimed-docs] “Credit invoices give every credit its own distinct invoice — separate from charge invoices.”
- [claimed-docs] “Modify invoice details post-issuance — including account notes, due dates, PO numbers, customer notes, and terms — to keep records accurate.”
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…”
Dunning recovery — stories about dunning recovery in this arenaDunning recovery
Stories about dunning recovery in this arena
Card recovery
ops userExpiring or replaced cards update themselves — network account updater, backup payment methods, and hosted update-payment pages
weight 2 · round to RecurlyDocs confirm backup payment methods and general 'tools to proactively catch and resolve' involuntary churn from expired cards/failed payments, but the evidence pack never explicitly names or documents a network account updater feature or hosted update-payment pages. missing for 10: explicit documentation of account updater integration, explicit hosted update-payment page feature, and any hands-on confirmation these self-heal expiring cards.
- [claimed-docs] “Involuntary churn happens when customers are lost due to factors outside their intent — expired cards, bank changes, or failed payments. Rec…”
- [claimed-docs] “Let customers designate a backup payment method so service continues automatically if their primary payment fails.”
Metronomenone0/10Metronome 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…”
Dunning comms
ops userConfigure automated dunning sequences — branded emails, in-app banners, grace periods, and final-state rules like cancel vs unpaid
weight 2 · round to RecurlyDocs confirm dunning campaigns (up to 50 targeted campaigns) and proactive involuntary-churn tools like backup payment methods, and community evidence corroborates automated dunning emails as a differentiator vs competitors. However, there's no documentation of branded email customization, in-app banners, configurable grace periods, or final-state rules distinguishing cancel vs unpaid outcomes. missing for 10: branded email templates/customization, in-app banner support, grace period configuration, and cancel-vs-unpaid final-state rule settings.
- [claimed-docs] “merchants on Professional and Elite plans can create up to 50 targeted campaigns for different customer segments or plans”
- [claimed-docs] “Involuntary churn happens when customers are lost due to factors outside their intent — expired cards, bank changes, or failed payments. Rec…”
- [claimed-docs] “Let customers designate a backup payment method so service continues automatically if their primary payment fails.”
- [community] “Comparing Stripe and Recurly: It's faster to get going with Stripe (no merchant account required) but Recurly appears to offer more automate…”
- [community] “Chargify finally has statements. Recurly has a large emphasis on making sure your customers are retained -- so much so that they added their…”
Metronomenone0/10Evidence 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.”
Smart retries
finance leadFailed renewal payments are retried automatically on an ML- or schedule-optimized cadence that measurably recovers involuntary churn
weight 3 · round to RecurlyRecurly documents dunning management and involuntary-churn tools like targeted campaigns and backup payment methods, and community commentary notes Recurly's automated retention/dunning emails as a differentiator, but there is no evidence of ML-optimized or schedule-optimized retry cadence logic, nor any quantified recovery-rate/churn-reduction metrics. missing for 10: documentation of the actual retry scheduling/ML logic behind payment retries, evidence of adaptive or optimized cadence (vs simple campaign rules), and third-party or first-party data on measurable involuntary churn recovery.
- [claimed-docs] “merchants on Professional and Elite plans can create up to 50 targeted campaigns for different customer segments or plans”
- [claimed-docs] “Involuntary churn happens when customers are lost due to factors outside their intent — expired cards, bank changes, or failed payments. Rec…”
- [claimed-docs] “Let customers designate a backup payment method so service continues automatically if their primary payment fails.”
- [community] “Comparing Stripe and Recurly: It's faster to get going with Stripe (no merchant account required) but Recurly appears to offer more automate…”
- [community] “Chargify finally has statements. Recurly has a large emphasis on making sure your customers are retained -- so much so that they added their…”
Metronomenone0/10Evidence 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.”
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 RecurlyRecurly's docs explicitly describe an entitlements feature that can be checked in real time via the Recurly API across platforms, matching the core of the story. Missing for 10: detailed documentation of how entitlements are attached to specific plans, explicit SDK-level (not just API) entitlement-check examples, and independent/hands-on confirmation of this specific feature.
- [claimed-docs] “Entitlements can be applied across platforms (web, mobile, and app stores) and checked in real time via the Recurly API.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
Metronomenone0/10Evidence 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.
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 MetronomeRecurlynone0/10Docs only describe changing an individual subscription's plan/price/add-ons (recurly-docs-1, recurly-docs-2); there is no mention of versioned plan definitions, grandfathering existing subscribers on old pricing, or bulk/cohort migration tooling for moving groups of subscribers to new pricing.
- [claimed-docs] “Recurly gives you full control over how and when subscription changes take effect. Upgrade or downgrade a plan, adjust quantity or price, ad…”
- [claimed-docs] “Recurly bills only the difference during an immediate change when the underlying plan is unchanged.”
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.”
Invoicing tax — stories about invoicing tax in this arenaInvoicing tax
Stories about invoicing tax in this arena
Invoices
ops userThe platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automatically
weight 2 · round to RecurlyDocs confirm invoice modification (notes, due dates, PO numbers, terms), separate credit invoices, and account/record-keeping features, implying automated invoice generation and delivery, but there is no explicit evidence of sequential/compliant numbering rules, custom field configuration on invoices, memo fields, or receipt generation/delivery workflows. missing for 10: explicit documentation of sequential invoice numbering compliance, custom fields on invoices, memo support, automatic receipt generation/delivery, and independent confirmation of these features working as described.
- [claimed-docs] “Credit invoices give every credit its own distinct invoice — separate from charge invoices.”
- [claimed-docs] “Modify invoice details post-issuance — including account notes, due dates, PO numbers, customer notes, and terms — to keep records accurate.”
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
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.…”
Multi currency
finance leadBill customers in their local currency with per-currency price points and consolidated reporting in my home currency
weight 2 · round drawnRecurlynone0/10None of the evidence items mention multi-currency pricing, per-currency price points, or consolidated home-currency reporting — the pack covers subscription changes, usage billing, dunning, entitlements, invoices, and general community commentary, none of which address currency handling. This is a fair capability to expect from a billing platform, so absence of evidence yields 'none' rather than 'na'.
Metronomenone0/10The 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.
Tax
finance leadSales tax, VAT, and GST are calculated on every invoice — natively or through a first-class tax integration — with the right registrations and rates
weight 2 · round drawnRecurlynone0/10The evidence pack contains no mention of tax calculation, VAT/GST handling, tax registrations, or any first-party or third-party tax integration (e.g., Avalara, TaxJar) — invoicing/credit/dunning features are covered but tax compliance is entirely absent. missing for 10: any documentation of sales tax/VAT/GST calculation, tax registration management, or tax engine integration.
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 drawnRecurly docs mention a general 'Data Imports and Exports' feature for populating accounts and keeping compliance records, and a community comment specifically praises Recurly's gateway for supporting 'credit card portability' to another provider. However, there is no vendor documentation detailing bulk export of subscriptions, invoices, or usage records, nor an official description of the payment-method portability mechanism (it's only referenced anecdotally by a user, not documented by Recurly). Missing for 10: explicit docs on invoice/usage-record export formats and scope, official documentation of stored payment-method portability/migration tooling, and any independent verification that a full data export actually contains all subscription/invoice/usage history.
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Import customer data to populate accounts and records across your Recurly account.”
- [community] “I am in the process of integrating Recurly into my existing business... I want all the subscription management features Recurly provides. Fu…”
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…”
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 drawnRecurly's docs mention generic data import/export tools (recurly-docs-11, recurly-docs-15) and a community comment notes Recurly's gateway offers 'credit card portability' (recurly-comm-7), suggesting some support for migrating billing data and card credentials. However, there is no documentation of a structured migration workflow, PCI-compliant card tokenization/transfer process, or assurance that live subscriptions migrate without customer disruption. missing for 10: explicit migration/onboarding documentation, PCI-compliant card data transfer mechanics, evidence of seamless customer experience during migration.
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Import customer data to populate accounts and records across your Recurly account.”
- [community] “I am in the process of integrating Recurly into my existing business... I want all the subscription management features Recurly provides. Fu…”
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…”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round drawnDocs show broad API coverage of core subscription, invoicing, entitlements, and data import/export features (recurly-docs-1,8,10,11) alongside official client libraries (recurly-docs-13), suggesting most UI actions are API-accessible. However, there is no explicit statement of full UI/API parity, and some UI-only features like dunning campaign configuration (recurly-docs-5) aren't confirmed as API-manageable. Missing for 10: an explicit parity guarantee or comprehensive API reference mapping every UI action, and independent confirmation that all UI-configurable settings (e.g., dunning campaigns) are exposed via API.
- [claimed-docs] “Recurly gives you full control over how and when subscription changes take effect. Upgrade or downgrade a plan, adjust quantity or price, ad…”
- [claimed-docs] “Entitlements can be applied across platforms (web, mobile, and app stores) and checked in real time via the Recurly API.”
- [claimed-docs] “Modify invoice details post-issuance — including account notes, due dates, PO numbers, customer notes, and terms — to keep records accurate.”
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
- [claimed-docs] “merchants on Professional and Elite plans can create up to 50 targeted campaigns for different customer segments or plans”
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”
ai-native userExport all of my data in open formats and leave
weight 3 · round to MetronomeRecurly documents a data-imports-and-exports feature for populating accounts and keeping records, and community mentions note credit-card portability, suggesting some data can be extracted, but there is no evidence of a comprehensive, open-format (CSV/JSON) full-account export or an official data-portability/exit process. missing for 10: explicit open-format export documentation, full account data export scope, and confirmation of easy migration/exit workflow.
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Import customer data to populate accounts and records across your Recurly account.”
- [community] “I am in the process of integrating Recurly into my existing business... I want all the subscription management features Recurly provides. Fu…”
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”
ai-native userRead the product's source under an open license
weight 2 · round drawnRecurlynone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
ai-native userSelf-host the core product
weight 3 · round drawnRecurlynone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnRecurlynone0/10No evidence in the pack mentions data residency, regional storage options, or geographic data control for Recurly; this is a fair axis for a SaaS billing platform handling customer/payment data, but absence of evidence means 'none'.
Metronomenone0/10No 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.
ai-native userControl data retention and deletion
weight 2 · round drawnRecurlynone0/10Evidence covers subscription management, billing, invoicing, imports/exports and an MCP docs connector, but nothing addresses data retention policies, deletion requests, or privacy/GDPR-style controls for AI-native users. missing for 10: data retention policy documentation, data deletion/right-to-erasure mechanisms, privacy compliance controls (GDPR/CCPA), evidence of user-initiated data deletion API or workflow.
Metronomenone0/10Metronome 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.
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 drawnRecurlynone0/10The evidence pack covers subscription changes, dunning, entitlements, invoicing, and data import/export, but contains no mention of MRR, churn, cohort retention, or LTV analytics/reporting dashboards computed from billing data. Missing for 10: any documentation of built-in revenue/retention analytics, cohort or LTV reporting, or dashboards distinct from raw data export.
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Import customer data to populate accounts and records across your Recurly account.”
Metronomenone0/10Evidence 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…”
Gl sync
finance leadInvoices, payments, and recognition entries sync to my general ledger or ERP — QuickBooks, Xero, NetSuite — so the close doesn't need CSV surgery
weight 2 · round drawnRecurlynone0/10The evidence pack shows generic data import/export capability but no mention of specific GL/ERP integrations (QuickBooks, Xero, NetSuite) or revenue recognition sync. Missing for 10: any documentation of accounting/ERP connectors, revenue recognition automation, or close-process integration.
- [claimed-docs] “Use it to populate your account, analyze performance and customer behavior, and keep records for compliance.”
- [claimed-docs] “Import customer data to populate accounts and records across your Recurly account.”
Metronomenone0/10Evidence 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…”
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 MetronomeRecurlynone0/10Evidence covers subscriptions, invoicing, dunning, entitlements, and data import/export for general compliance, but nothing addresses ASC 606/IFRS 15 deferred revenue schedules or audit-ready recognition reporting specifically. Absence of evidence for this applicable billing-platform capability means it can't be credited as delivered.
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…”
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 drawnDocs confirm a documented API for changing subscriptions (upgrade/downgrade, quantity/price, add-ons) with official client libraries in 7 languages, supporting programmatic subscription management. However, the evidence never explicitly documents 'create' or 'pause'/'cancel' endpoints—only mid-cycle change operations are detailed, so full lifecycle coverage is inferred rather than shown directly. Missing for 10: explicit documentation of subscription creation and cancellation/pause API calls, and any hands-on developer confirmation of the full lifecycle working end-to-end via API alone.
- [claimed-docs] “Recurly gives you full control over how and when subscription changes take effect. Upgrade or downgrade a plan, adjust quantity or price, ad…”
- [claimed-docs] “Recurly bills only the difference during an immediate change when the underlying plan is unchanged.”
- [claimed-docs] “Official Client Libraries ### Ruby ... ### Node.js ... ### Python ... ### Dotnet ... ### Java ... ### PHP ... ### Go”
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”
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 MetronomeRecurlynone0/10The evidence pack contains no documentation of Recurly's webhook or event system for subscription lifecycle changes (renewal, upgrade, payment failure, cancellation). The only indirect mention is a community comment noting dunning emails work 'without needing to implement webhooks,' which implies webhooks exist as an option but provides no detail on reliability, event types, or delivery guarantees.
- [community] “Comparing Stripe and Recurly: It's faster to get going with Stripe (no merchant account required) but Recurly appears to offer more automate…”
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.”
Self serve
founderMy customers can upgrade, downgrade, or cancel themselves through a hosted portal or embeddable components, without a support ticket
weight 2 · round to RecurlyDocs confirm customers can change plans (upgrade/downgrade, add-ons, proration) via Recurly's subscription APIs, implying self-service capability, but no direct evidence of a hosted customer portal or embeddable UI components for self-cancel/upgrade, nor explicit mention of eliminating support tickets. missing for 10: explicit hosted portal documentation, embeddable component/widget evidence, self-service cancellation flow.
- [claimed-docs] “Recurly gives you full control over how and when subscription changes take effect. Upgrade or downgrade a plan, adjust quantity or price, ad…”
- [claimed-docs] “Recurly bills only the difference during an immediate change when the underlying plan is unchanged.”
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.”
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 MetronomeRecurlynone0/10The evidence pack contains no documentation of free trials, coupons/promotion codes, automatic trial-to-paid conversion, or card-network-mandated trial-end notifications. Related dunning/involuntary-churn features are covered, but none address trial or coupon lifecycle specifically. missing for 10: docs on free trial setup, coupon/promo code creation, automatic trial conversion, and trial-end notification compliance.
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.”
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 MetronomeRecurly documents usage-based billing where usage-based add-ons are reported and billed at the end of a cycle (recurly-docs-3, recurly-docs-4), showing basic support for metering usage into billing, but there is no evidence of a high-volume streaming ingestion API, idempotency keys/idempotent ingestion, or explicit backdating support for usage events. Missing for 10: evidence of a streaming/bulk usage ingestion endpoint, documented idempotency guarantees for usage events, and backdating/timestamp-adjustment support for late-arriving usage records.
- [claimed-docs] “Recurly's usage-based billing model lets you charge customers at the end of each billing cycle based on their actual consumption”
- [claimed-docs] “Measured units describe the usage tracked by a usage-based add-on and enable consistent reporting across multiple add-ons and plans.”
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.”
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 MetronomeRecurly's docs confirm usage-based billing with measured units and flexible subscription/add-on changes (recurly-docs-1, recurly-docs-3, recurly-docs-4), which supports basic per-unit and subscription-plus-usage hybrid billing without code. However, the evidence never explicitly documents tiered, volume, or graduated pricing structures, nor named 'commitment' or 'overage' billing mechanics as configurable models. missing for 10: explicit tiered/volume/graduated pricing tier configuration docs, explicit commitment and overage billing mechanics, independent confirmation these complex pricing combos work without custom code.
- [claimed-docs] “Recurly gives you full control over how and when subscription changes take effect. Upgrade or downgrade a plan, adjust quantity or price, ad…”
- [claimed-docs] “Recurly's usage-based billing model lets you charge customers at the end of each billing cycle based on their actual consumption”
- [claimed-docs] “Measured units describe the usage tracked by a usage-based add-on and enable consistent reporting across multiple add-ons and plans.”
- [claimed-docs] “Credit invoices give every credit its own distinct invoice — separate from charge invoices.”
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.”
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 MetronomeRecurlynone0/10Recurly's docs mention usage-based billing that charges at the end of the billing cycle and 'measured units' for reporting, but there is no evidence of real-time current-cycle usage/cost dashboards, customer-facing usage views, or threshold/alert mechanisms to warn before an invoice is generated.
- [claimed-docs] “Recurly's usage-based billing model lets you charge customers at the end of each billing cycle based on their actual consumption”
- [claimed-docs] “Measured units describe the usage tracked by a usage-based add-on and enable consistent reporting across multiple add-ons and plans.”
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.”
Not comparable on these axes
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableRecurlynone0/10No evidence of version control, review workflows, or rollback for automations/workflows in Recurly; the docs cover subscription/billing config changes, dunning campaigns, and an MCP server for documentation access, but none describe versioning, audit/review, or rollback of automations themselves.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableRecurlyn/aRecurly is a subscription billing/payments platform, not an AI model or AI product that trains on user data; the axis of preventing data use for AI training does not apply to its category.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableRecurlyn/aRecurly is a subscription billing platform, not an AI agent/tool whose telemetry or usage-tracking opt-out would be a meaningful axis for AI-native users; this consumer-privacy-style story doesn't map to its product category.
Metronomen/aMetronome is a usage-based billing platform for its customers' end-users; the story concerns opting out of the vendor's own product telemetry/usage tracking, which is a category mismatch for a billing/metering product whose core function is customer usage tracking. No evidence pack item addresses a telemetry opt-out for the product itself.