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