Lago vs Metronome
open-source · hosted-paid · enterprise-custom
·usage-based · free-tier · enterprise-custom
Lago wins · 25–10 (15 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 LagoLago has a confirmed live llms.txt at the root domain (HTTP 200) plus a docs-specific llms.txt index and .md-formatted doc pages, explicitly designed for agent consumption, alongside an OpenAPI schema and MCP server for programmatic access. This directly satisfies pointing an agent at agent-oriented docs, with only independent third-party confirmation of agent usage missing for a perfect score. Missing for 10: independent/hands-on verification that an agent successfully consumes these files end-to-end.
- [probe] “PROBE llms.txt: HTTP 200 at https://getlago.com/llms.txt # Lago > Lago is the open-source billing platform for usage-based, subscription-ba…”
- [probe] “PROBE docs-md: HTTP 200 at https://getlago.com/docs/api-reference/intro.md > ## Documentation Index > Fetch the complete documentation index…”
- [probe] “PROBE openapi: HTTP 200 at https://getlago.com/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://getlago.com/docs/guide/ai-agents/mcp-server”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
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 LagoLago is self-hostable via Docker (docs-11), fully API/CLI-driven with a generated command for every endpoint (docs-1) and an OpenAPI 3.1 schema for scripting/client generation (docs-16), and the GitHub repo contains a script that spins up a disposable local Lago instance and runs automated pricing scenarios (gh-1), all consistent with headless/CI automation. However there is no explicit CI/headless-mode documentation, example CI pipeline config, or independent report of running Lago fully headless in a pipeline. Missing for 10: dedicated CI/headless-mode docs, a documented CI pipeline example, and independent confirmation of headless automated runs.
- [claimed-docs] “Docker is the easiest way to get started with the self-hosted version of Lago.”
- [claimed-docs] “Every endpoint in this reference has a generated command.”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
- [github] “It starts the Lago version that matches this checkout, creates a disposable local organization, and prices three illustrative AI requests.”
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 drawnLagonone0/10The evidence shows Lago exposes its own MCP server so external AI assistants can access Lago's billing data (lago-docs-9, lago-probe-4) and has AI agents (Dunning Agent) that read Lago's own account data (lago-docs-10) — this is Lago acting as an MCP server/tool provider, not as a client that plugs in external MCP servers to gain new tools. No evidence shows Lago's agents or platform consuming/connecting to third-party MCP servers.
- [claimed-docs] “provides AI assistants (like Claude) with direct access to Lago’s billing data.”
- [claimed-docs] “The Dunning Agent reads the account first: twelve months of invoices and payments, the disputes, the provider status.”
- [probe] “official MCP server documented at https://getlago.com/docs/guide/ai-agents/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 LagoLago is not itself an AI agent but a billing platform, so publishing an official MCP server is a fair axis; docs explicitly confirm a dedicated MCP server giving AI assistants like Claude direct access to Lago's billing data, plus a probe confirming the page exists. Missing for 10: independent/hands-on third-party verification of the MCP server working in practice.
- [claimed-docs] “provides AI assistants (like Claude) with direct access to Lago’s billing data.”
- [probe] “official MCP server documented at https://getlago.com/docs/guide/ai-agents/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 to LagoDocs mention that 'every endpoint in this reference has a generated command,' implying an official CLI exists, but there is no dedicated CLI documentation, install instructions, or AI-native framing (e.g., LLM-friendly usage, agent integration) beyond this single line. Missing for 10: explicit CLI install/setup docs, AI-native use-case description, independent confirmation of CLI usage.
- [claimed-docs] “Every endpoint in this reference has a generated command.”
ai-native userDrive the product through a documented public API
weight 3 · round to LagoLago publishes a full public API reference with generated commands per endpoint, an OpenAPI 3.1 schema (verified live at /openapi.json), explicit versioning/stability guarantees, and docs/llms.txt aimed at AI-native consumption; it even documents an MCP server exposing billing data to AI agents. This is strong first-party and probe-verified evidence of a documented, machine-consumable public API. Missing for 10: independent third-party developer testimonials specifically about API usage/integration experience (community evidence is mostly about billing product value, not API DX).
- [claimed-docs] “Every endpoint in this reference has a generated command.”
- [claimed-docs] “Clients should tolerate additive changes within v1, including new response fields, enum values, endpoints, optional request fields, and webh…”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
- [probe] “PROBE llms.txt: HTTP 200 at https://getlago.com/llms.txt # Lago > Lago is the open-source billing platform for usage-based, subscription-ba…”
- [probe] “PROBE docs-md: HTTP 200 at https://getlago.com/docs/api-reference/intro.md > ## Documentation Index > Fetch the complete documentation index…”
- [probe] “PROBE openapi: HTTP 200 at https://getlago.com/openapi.json — contains "openapi" key”
- [claimed-docs] “provides AI assistants (like Claude) with direct access to Lago’s billing data.”
- [probe] “official MCP server documented at https://getlago.com/docs/guide/ai-agents/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 drawnLagonone0/10Lago's docs describe an MCP server and API access for AI agents but provide no evidence of scoped or least-privilege API key/credential issuance (e.g., role-based keys, permission scopes) for agents; existing docs only mention general API keys and OpenAPI schema access without granular scoping controls.
- [claimed-docs] “provides AI assistants (like Claude) with direct access to Lago’s billing data.”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
- [probe] “official MCP server documented at https://getlago.com/docs/guide/ai-agents/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 LagoLago publishes an OpenAPI 3.1 spec and API reference with per-endpoint generated commands, explicitly positioned for generating clients or exposing actions to AI agents, but the evidence never names concrete official first-party SDKs (e.g., language libraries) beyond spec-generated clients. missing for 10: named official SDK packages/libraries, independent developer confirmation of SDK usage, versioning/maintenance details for SDKs.
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
- [claimed-docs] “Every endpoint in this reference has a generated command.”
- [probe] “PROBE openapi: HTTP 200 at https://getlago.com/openapi.json — contains "openapi" key”
- [claimed-docs] “Clients should tolerate additive changes within v1, including new response fields, enum values, endpoints, optional request fields, and webh…”
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 drawnLago documents a webhook system with HMAC signing options (lago-docs-7) and explicit API versioning guarantees for webhook event types (lago-docs-8), meaning any consumer—including an AI agent—can subscribe to billing events via webhooks. missing for 10: a full catalog/list of supported webhook event types, and independent/hands-on confirmation of webhook reliability in production use.
- [claimed-docs] “The second is `HMAC`, which features a shorter payload header and no size restrictions.”
- [claimed-docs] “Clients should tolerate additive changes within v1, including new response fields, enum values, endpoints, optional request fields, and webh…”
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 to LagoLago documents specific AI-agent features—an MCP server that gives assistants like Claude direct access to billing data, and a 'Dunning Agent' that reads 12 months of invoices/payments/disputes to inform actions—showing some in-product AI analysis of data. However, this is narrow (payment collection) rather than a general AI-insights/suggestions layer across revenue analytics, plans, or usage data. missing for 10: evidence of AI-generated insights/suggestions surfaced in the main product UI (e.g., revenue analytics, plan optimization), independent/hands-on confirmation the Dunning Agent's outputs are used, and broader scope beyond dunning/collections.
- [claimed-docs] “provides AI assistants (like Claude) with direct access to Lago’s billing data.”
- [claimed-docs] “The Dunning Agent reads the account first: twelve months of invoices and payments, the disputes, the provider status.”
- [probe] “official MCP server documented at https://getlago.com/docs/guide/ai-agents/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 LagoLago documents a Dunning Agent that autonomously reads account/invoice/payment history and presumably acts on overdue accounts, plus an MCP server exposing billing data to AI agents like Claude, showing some autonomous background automation capability. However, evidence doesn't show a general-purpose automation/agent-builder framework, scheduling, or independent confirmation of the Dunning Agent running unattended in production. missing for 10: broader autonomous automation framework beyond dunning agent, independent/hands-on verification of autonomous background operation, details on triggering/scheduling/monitoring these agents.
- [claimed-docs] “provides AI assistants (like Claude) with direct access to Lago’s billing data.”
- [claimed-docs] “The Dunning Agent reads the account first: twelve months of invoices and payments, the disputes, the provider status.”
- [probe] “official MCP server documented at https://getlago.com/docs/guide/ai-agents/mcp-server”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to LagoLago ships an 'AI agents' documentation section describing a built-in Dunning Agent that autonomously reads invoices, disputes, and payment provider status to act on overdue accounts, and an MCP server that gives external AI assistants (e.g., Claude) direct access to billing data. This shows some built-in agentic delegation for a specific task (dunning/collections), but there's no evidence of a general-purpose in-product AI assistant users can converse with or delegate arbitrary tasks to. missing for 10: evidence of a general conversational assistant UI, breadth of tasks beyond dunning, independent/hands-on confirmation of the Dunning Agent actually operating in production.
- [claimed-docs] “provides AI assistants (like Claude) with direct access to Lago’s billing data.”
- [claimed-docs] “The Dunning Agent reads the account first: twelve months of invoices and payments, the disputes, the provider status.”
- [probe] “official MCP server documented at https://getlago.com/docs/guide/ai-agents/mcp-server”
ai-native userOperate the product with natural-language commands
weight 2 · round to LagoLago documents an official MCP server that gives AI assistants like Claude direct access to billing data, plus specialized AI agents (e.g., Dunning Agent) that read account data and OpenAPI schema exposure for AI agents to invoke billing actions — enabling natural-language operation via connected AI assistants. However, this is mediated through external assistants/MCP rather than a built-in NL command interface, and there's no independent/hands-on evidence of actual NL command execution or the breadth of supported commands. Missing for 10: hands-on/independent verification of NL command execution, a native in-product chat/command interface, and documentation of the full range of commands executable via natural language.
- [claimed-docs] “provides AI assistants (like Claude) with direct access to Lago’s billing data.”
- [claimed-docs] “The Dunning Agent reads the account first: twelve months of invoices and payments, the disputes, the provider status.”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
- [probe] “official MCP server documented at https://getlago.com/docs/guide/ai-agents/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 to LagoDocs confirm a generated command for every endpoint and an OpenAPI 3.1 schema (lago-docs-1, lago-docs-16, lago-probe-3), suggesting a structured, code-snippet-rich API reference, but there is no evidence of an in-browser 'try it out' or runnable execution feature. Missing for 10: explicit interactive 'run this request' UI, hands-on confirmation of executability, and independent corroboration of the reference's interactivity.
- [claimed-docs] “Every endpoint in this reference has a generated command.”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
- [probe] “PROBE openapi: HTTP 200 at https://getlago.com/openapi.json — contains "openapi" key”
- [probe] “PROBE docs-md: HTTP 200 at https://getlago.com/docs/api-reference/intro.md > ## Documentation Index > Fetch the complete documentation index…”
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 drawnLago publishes an OpenAPI 3.1 schema (openapi.json returns 200 with an 'openapi' key) and docs explicitly state it can be used to generate clients, inspect typed operations, or expose actions to an AI agent. missing for 10: no independent third-party corroboration of the spec's completeness or usage beyond vendor docs/probe.
- [probe] “PROBE openapi: HTTP 200 at https://getlago.com/openapi.json — contains "openapi" key”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
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 drawnLago's self-hosted Docker setup and the GitHub quick-start script that spins up a 'disposable local organization' for testing suggest a way to try Lago without touching production data, but there is no documented dedicated sandbox/test-mode with separate test API keys as many billing platforms provide. Missing for 10: explicit sandbox/test-mode documentation, test vs. live API key separation, and hands-on confirmation that test data is fully isolated from production billing.
- [github] “It starts the Lago version that matches this checkout, creates a disposable local organization, and prices three illustrative AI requests.”
- [claimed-docs] “Docker is the easiest way to get started with the self-hosted version of Lago.”
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 to LagoLago documents an explicit API versioning policy (v1) specifying that clients should tolerate additive changes like new fields, enums, endpoints, and webhook event types, indicating a stable versioned API contract with deprecation-safe evolution rules, and backs this with a published OpenAPI 3.1 schema. Missing for 10: an explicit deprecation/sunset timeline policy (e.g., how long old versions are supported) and independent/community confirmation of version stability in practice.
- [claimed-docs] “Clients should tolerate additive changes within v1, including new response fields, enum values, endpoints, optional request fields, and webh…”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
- [probe] “PROBE openapi: HTTP 200 at https://getlago.com/openapi.json — contains "openapi" key”
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 MetronomeLagonone0/10No evidence describes bulk/batch endpoints or batch operations (e.g., bulk invoice creation, bulk customer updates) in Lago's API or UI; documentation only mentions per-endpoint commands and general API access. Missing for 10: any mention of batch/bulk API endpoints, batch job status, or UI batch-select actions.
- [claimed-docs] “Every endpoint in this reference has a generated command.”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
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 drawnLago documents webhooks that fire on billing events (lago-docs-7) and a dedicated 'Dunning Agent' that reads account state (invoices, payments, disputes) and presumably acts on overdue-payment events (lago-docs-10), which together resemble event-triggered automation. However, there is no documented general-purpose rule/condition engine letting users define arbitrary 'if event X then action Y' logic beyond these specific built-in agents/webhooks. Missing for 10: a configurable rules/conditions UI or API for arbitrary triggers, and evidence of multiple event types beyond dunning/webhooks.
- [claimed-docs] “The second is `HMAC`, which features a shorter payload header and no size restrictions.”
- [claimed-docs] “The Dunning Agent reads the account first: twelve months of invoices and payments, the disputes, the provider status.”
- [claimed-docs] “provides AI assistants (like Claude) with direct access to Lago’s billing data.”
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 LagoLago's core billing engine inherently runs recurring cycles (monthly/yearly subscription billing) and the Dunning Agent appears to run periodic checks over invoices/payments, which is a recurring automated workflow, but there is no documented feature letting an AI-native user define or schedule arbitrary recurring jobs/workflows via API or agent. missing for 10: explicit job/workflow scheduler, cron-like API, user-configurable recurrence for AI agent tasks beyond built-in billing cycles.
- [claimed-docs] “Yearly: subscription fees are billed on a yearly basis and charges can be billed monthly or annually.”
- [claimed-docs] “The Dunning Agent reads the account first: twelve months of invoices and payments, the disputes, the provider status.”
- [claimed-docs] “provides AI assistants (like Claude) with direct access to Lago’s billing data.”
Billing agent access — stories about billing agent access in this arenaBilling agent access
Stories about billing agent access in this arena
Agent operations
ai-native userAn agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissions
weight 3 · round to LagoLago exposes a full REST API (every endpoint has a generated command) plus an OpenAPI 3.1 schema explicitly positioned for exposing billing actions to AI agents, and ships a documented MCP server giving AI assistants direct access to billing data, with a working example (Dunning Agent) reading account/invoice data. Subscription assignment and plan upgrade/downgrade are documented API-driven flows, supporting the 'create a subscription, change a plan' part of the story. Missing for 10: no explicit documentation of scoped/permissioned API keys or credit-application endpoints for agents, and no independent hands-on report of an agent actually performing these billing operations end-to-end.
- [claimed-docs] “Every endpoint in this reference has a generated command.”
- [claimed-docs] “Customers have the flexibility to easily upgrade or downgrade their plan at any given moment.”
- [claimed-docs] “provides AI assistants (like Claude) with direct access to Lago’s billing data.”
- [claimed-docs] “The Dunning Agent reads the account first: twelve months of invoices and payments, the disputes, the provider status.”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
- [probe] “PROBE openapi: HTTP 200 at https://getlago.com/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://getlago.com/docs/guide/ai-agents/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 LagoLago ships an official MCP server explicitly described as giving AI assistants 'direct access to Lago's billing data' (lago-docs-9, lago-probe-4), plus a documented OpenAPI schema explicitly positioned for 'exposing billing actions to an AI agent' (lago-docs-16), and a Dunning Agent example that reads a customer's invoices, payments and disputes (lago-docs-10) — directly matching the story of an agent querying billing state like delinquency and invoices. Missing for 10: explicit worked examples/queries for MRR aggregation and upcoming-renewal lookups via the MCP server, and independent (non-vendor) confirmation that these agent queries work in practice.
- [claimed-docs] “provides AI assistants (like Claude) with direct access to Lago’s billing data.”
- [claimed-docs] “The Dunning Agent reads the account first: twelve months of invoices and payments, the disputes, the provider status.”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
- [probe] “official MCP server documented at https://getlago.com/docs/guide/ai-agents/mcp-server”
- [probe] “PROBE openapi: HTTP 200 at https://getlago.com/openapi.json — contains "openapi" key”
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 drawnLagonone0/10The evidence pack shows general plan/subscription docs (yearly billing, upgrades/downgrades) but never addresses calendar vs anniversary billing anchors, cross-subscription date alignment, or custom invoice date overrides — the specific billing-math controls this story asks about.
- [claimed-docs] “Yearly: subscription fees are billed on a yearly basis and charges can be billed monthly or annually.”
- [claimed-docs] “In the “Overview” tab, click “Add a plan” on the right”
- [claimed-docs] “Customers have the flexibility to easily upgrade or downgrade their plan at any given moment.”
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 MetronomeLago documents that customers can upgrade/downgrade plans at any time (lago-docs-4) and has dedicated subscription/plan docs, implying some proration handling, but no evidence shows documented proration formulas, credit line-item detail, or penny-level invoice reconciliation. A community question about upgrade/downgrade tracking (lago-comm-3) goes unanswered in the evidence pack. Missing for 10: explicit proration algorithm documentation, sample invoice line items showing credits/partial periods, and any audit or reconciliation guarantee.
- [claimed-docs] “Customers have the flexibility to easily upgrade or downgrade their plan at any given moment.”
- [claimed-docs] “In the “Overview” tab, click “Add a plan” on the right”
- [community] “User describes building an internal billing tool after bad experiences with Recurly and ChargeBee for B2B/B2E usage-based billing, discounts…”
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 drawnLagonone0/10No evidence in the pack mentions network account updater, backup payment methods, or hosted update-payment pages; Lago's dunning docs focus on invoice/dispute tracking and an AI dunning agent, not card-updating mechanics.
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 LagoLago documents dunning-adjacent capabilities: a 'cash-collection' feature to spot overdue/unpaid invoices via filters (lago-docs-13) and a 'Dunning Agent' that reads invoices, payments, disputes, and provider status (lago-docs-10). However, there is no evidence of configurable branded emails, in-app banners, grace periods, or explicit cancel-vs-unpaid final-state rules. Missing for 10: branded email templates, in-app banner UI, grace period configuration, explicit final-state (cancel/unpaid) rule settings, and independent confirmation of the dunning workflow in practice.
- [claimed-docs] “Spot overdue, partially paid or unpaid invoices with filters to never lose track of what you’re owed.”
- [claimed-docs] “The Dunning Agent reads the account first: twelve months of invoices and payments, the disputes, the provider status.”
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 LagoLago documents cash-collection tooling to flag overdue/unpaid invoices and an AI 'Dunning Agent' that reads account history (invoices, payments, disputes, provider status), implying some automated dunning capability, but there is no documented ML- or schedule-optimized retry cadence, no explicit retry logic, and no metrics on churn recovery. Missing for 10: explicit description of automated retry scheduling/cadence optimization, evidence of ML-driven timing, and quantified recovery/churn-reduction outcomes.
- [claimed-docs] “The Dunning Agent reads the account first: twelve months of invoices and payments, the disputes, the provider status.”
- [claimed-docs] “Spot overdue, partially paid or unpaid invoices with filters to never lose track of what you’re owed.”
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 LagoLago has a dedicated entitlements platform page combining billing and feature flags, confirming the concept exists, but the evidence pack contains no detail on how entitlements are attached to plans nor concrete API/SDK examples for runtime entitlement checks. missing for 10: API reference for entitlement endpoints, SDK code samples for checking a customer's entitlements at runtime, plan-to-entitlement modeling details.
- [claimed-docs] “Combine billing and feature flags to avoid bugs and dependencies, reduce complexity and lower and engineering overhead.”
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 MetronomeDocs show basic plan/subscription management (assign plan, upgrade/downgrade) but no explicit mention of plan versioning, grandfathering existing subscribers, or bulk cohort migration tools. missing for 10: explicit versioned-plan mechanism, grandfathering documentation, bulk/cohort migration tooling or API endpoints.
- [claimed-docs] “In the “Overview” tab, click “Add a plan” on the right”
- [claimed-docs] “Customers have the flexibility to easily upgrade or downgrade their plan at any given moment.”
- [claimed-docs] “Yearly: subscription fees are billed on a yearly basis and charges can be billed monthly or annually.”
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 LagoLago's docs confirm core invoicing functionality (downloadable invoices, customizable invoice templates) and cash-collection tracking of overdue invoices, showing invoicing is a first-class feature, but the evidence pack contains no mention of credit notes, receipts, sequential numbering, custom fields, or memos, nor confirmation of fully automated delivery to customers. missing for 10: credit note support, receipt generation, sequential invoice numbering, custom fields/memos on invoices, automatic delivery mechanism confirmation.
- [claimed-docs] “You can download invoices or use the invoice object to create your own invoice template.”
- [claimed-docs] “Spot overdue, partially paid or unpaid invoices with filters to never lose track of what you’re owed.”
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 drawnLagonone0/10No evidence in the pack addresses multi-currency billing, per-currency price points, or consolidated home-currency reporting; docs cover plans, invoicing, dunning, and revenue analytics but never mention currency handling or FX consolidation. Missing for 10: any documentation of multi-currency price points, currency conversion/consolidation logic, and reporting rollups in a base currency.
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 drawnLagonone0/10No evidence pack item mentions tax calculation, VAT/GST/sales tax handling, tax registrations, tax rates, or integrations with tax engines (e.g., Avalara, Stripe Tax, TaxJar). The docs cover invoicing, plans, subscriptions, and dunning but never address tax compliance. Missing for 10: any mention of native tax calculation, tax rate/registration management, or a first-class 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 to MetronomeLago's API/OpenAPI schema and CSV export for analytics (lago-docs-15, lago-docs-16, lago-docs-1) mean a finance lead could theoretically pull subscription, invoice, and usage data out via API, and self-hosting (lago-docs-11) avoids lock-in of infrastructure. However, there is no documented bulk-export or migration tool, no explicit invoice/subscription/usage-record export workflow, and payment methods are held by external providers (Stripe etc.) rather than Lago itself, so 'porting stored payment methods' isn't addressed at all. Missing for 10: dedicated data-export/migration documentation, explicit payment-method portability mechanism, and any hands-on evidence of a successful migration off Lago.
- [claimed-docs] “Build custom dashboards per customer, filter any way you want and export to CSV.”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
- [claimed-docs] “Every endpoint in this reference has a generated command.”
- [claimed-docs] “You can download invoices or use the invoice object to create your own invoice template.”
- [claimed-docs] “Docker is the easiest way to get started with the self-hosted version of Lago.”
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 MetronomeLagonone0/10No evidence in the pack describes any migration tooling, bulk-import from spreadsheets, or PCI-compliant card-data transfer capability; the API/docs cover plan assignment and event ingestion but nothing about importing live subscriptions from another platform. Community comments even suggest Lago does not itself handle payment/PCI processing (lago-comm-8), reinforcing the absence of this capability.
- [community] “"If I still have to pay the processing fees, what's the advantage here? Having to maintain my own payments stack (and PCI compliance) sounds…”
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 to LagoLago's docs show an API-first design: every endpoint has a generated CLI/code sample (lago-docs-1), a full OpenAPI 3.1 schema is available (lago-docs-16, lago-probe-3), and specific UI actions like usage-charge updates are explicitly available via both API and no-code UI (lago-docs-14). This implies strong API/UI parity but there is no explicit vendor claim or independent audit confirming 100% parity across every UI workflow (e.g., dunning, revenue analytics dashboards). missing for 10: an explicit 'everything in the UI is available via API' statement, and independent/community confirmation of full parity across all UI features.
- [claimed-docs] “Every endpoint in this reference has a generated command.”
- [claimed-docs] “Both non-engineers and engineers can update usage charges via API or Lago’s no-code UI.”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
- [probe] “PROBE openapi: HTTP 200 at https://getlago.com/openapi.json — contains "openapi" key”
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 LagoLago's open-source/self-hosted nature (Docker deployment), open API (OpenAPI 3.1 schema, full REST reference), and CSV export of analytics/invoices give users real data-portability levers, and self-hosting means the underlying database is always in the user's own control. However there is no documented single 'export all account data' or account-closure/migration feature — only piecemeal exports (invoices, revenue analytics CSV, API access to individual objects). Missing for 10: a dedicated full-account data export/backup tool, explicit data-portability/migration documentation, and independent confirmation of a clean 'leave' workflow.
- [claimed-docs] “Docker is the easiest way to get started with the self-hosted version of Lago.”
- [claimed-docs] “You can download invoices or use the invoice object to create your own invoice template.”
- [claimed-docs] “Build custom dashboards per customer, filter any way you want and export to CSV.”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
- [probe] “PROBE openapi: HTTP 200 at https://getlago.com/openapi.json — contains "openapi" key”
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 to LagoLago's docs and GitHub explicitly describe it as an open-source billing platform with a public source repository (getlago/lago), and the llms.txt probe confirms this framing, satisfying the 'read source under open license' story. Missing for 10: explicit citation of the specific license name/file (e.g., AGPL) and independent verification of license terms beyond the 'open-source' label.
ai-native userSelf-host the core product
weight 3 · round to LagoDocs explicitly cover self-hosting via Docker with a dedicated guide, and community comments confirm self-hosting is a real, used option ('self-hosting is not an issue', 'a self-hosted option fits our culture'). Missing for 10: independent hands-on report of running the full self-hosted stack in production, and more detail on self-hosted feature parity/limitations vs cloud.
- [claimed-docs] “Docker is the easiest way to get started with the self-hosted version of Lago.”
- [community] “"This looks great... Stripe is awesome but a self-hosted option fits our culture and philosophy a lot better. Will give it a blast when i ge…”
- [community] “"Looks very interesting. We are small shop and self-hosting is not an issue. This neatly fits a requirement we've had for quite some time."”
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 to LagoLago's self-hosted Docker deployment (lago-docs-11) implicitly lets a user control where their data resides by choosing their own infrastructure/region, but there is no explicit documentation of a region-selection feature, data-residency guarantees, or compliance certifications for the managed/cloud offering. missing for 10: explicit data-residency/region-selection feature docs, compliance certifications (e.g., GDPR/SOC2 region controls), managed-cloud region options.
- [claimed-docs] “Docker is the easiest way to get started with the self-hosted version of Lago.”
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 drawnLagonone0/10No evidence in the pack addresses data retention policies, deletion of customer/billing data, or GDPR-style controls; Lago's docs focus on billing, invoicing, and AI agent features but never mention data retention/deletion controls. Missing for 10: documentation on data retention windows, customer data deletion/export mechanisms, and any privacy/GDPR compliance 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 drawnLagonone0/10Lago's docs mention a generic 'revenue-analytics' page with custom dashboards, filters, and CSV export (lago-docs-15), which is closer to the bolted-on BI export the story explicitly wants to avoid, not native MRR/churn/cohort-retention/LTV computation. No evidence pack item shows Lago computing these specific metrics natively from billing data, and a community question in lago-comm-3 explicitly asks whether Lago handles revenue recognition, left unanswered.
- [claimed-docs] “Build custom dashboards per customer, filter any way you want and export to CSV.”
- [community] “User describes building an internal billing tool after bad experiences with Recurly and ChargeBee for B2B/B2E usage-based billing, discounts…”
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 drawnLagonone0/10The evidence pack shows Lago's API, webhooks, invoicing, and OpenAPI schema, but there is no mention of any native or partner integration with QuickBooks, Xero, or NetSuite, nor any revenue-recognition export/sync to a GL/ERP system. Finance-lead close automation is a fair axis for a billing platform, but nothing in the pack demonstrates it.
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 MetronomeLagonone0/10No evidence describes ASC 606/IFRS 15 deferred revenue schedules or audit-ready recognition reports; the closest material (revenue-analytics dashboards/CSV export) is generic reporting, not recognition accounting. A community comment even explicitly asks whether Lago handles revenue recognition, with no documented answer.
- [claimed-docs] “Build custom dashboards per customer, filter any way you want and export to CSV.”
- [community] “User describes building an internal billing tool after bad experiences with Recurly and ChargeBee for B2B/B2E usage-based billing, discounts…”
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 drawnLago's docs cover API-driven subscription creation (assign-plan), upgrades/downgrades, and a full OpenAPI 3.1 schema with generated commands per endpoint, supporting a documented API lifecycle. However, the evidence pack never explicitly documents pause or cancel subscription endpoints, and most subscription guides (e.g., assign-plan) describe dashboard clicks rather than pure API-only flows. Missing for 10: explicit pause/cancel endpoint documentation, and hands-on/independent confirmation that the entire lifecycle can be done via API without the dashboard.
- [claimed-docs] “Every endpoint in this reference has a generated command.”
- [claimed-docs] “In the “Overview” tab, click “Add a plan” on the right”
- [claimed-docs] “Customers have the flexibility to easily upgrade or downgrade their plan at any given moment.”
- [claimed-docs] “Use Lago's OpenAPI 3.1 schema to generate clients, inspect typed operations, or expose billing actions to an AI agent.”
- [probe] “PROBE openapi: HTTP 200 at https://getlago.com/openapi.json — contains "openapi" key”
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 LagoLago documents a webhook system with signing (HMAC) and explicitly treats 'webhook event types' as a versioned API surface, implying granular event types exist, but the evidence never enumerates specific subscription lifecycle events (renewal, upgrade, payment failure, cancellation) or demonstrates delivery reliability guarantees like retries/idempotency for webhooks specifically. missing for 10: explicit list/documentation of subscription lifecycle event types, evidence of webhook delivery reliability (retries, dead-letter, idempotency) beyond event-ingestion dedup which is a different feature.
- [claimed-docs] “The second is `HMAC`, which features a shorter payload header and no size restrictions.”
- [claimed-docs] “Clients should tolerate additive changes within v1, including new response fields, enum values, endpoints, optional request fields, and webh…”
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 MetronomeLagonone0/10Evidence confirms upgrade/downgrade functionality exists (lago-docs-4, lago-docs-3) but only via API or Lago's internal admin UI — there is no mention anywhere in the pack of a customer-facing hosted portal or embeddable self-serve components that end customers could use directly. Community comments even question whether Lago handles full self-serve lifecycle (lago-comm-3), and nothing confirms a portal exists.
- [claimed-docs] “Customers have the flexibility to easily upgrade or downgrade their plan at any given moment.”
- [claimed-docs] “In the “Overview” tab, click “Add a plan” on the right”
- [community] “User describes building an internal billing tool after bad experiences with Recurly and ChargeBee for B2B/B2E usage-based billing, discounts…”
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 MetronomeLagonone0/10No evidence pack items mention free trials, coupons, promotion codes, automatic trial-to-paid conversion, or trial-end notifications required by card-network rules; evidence covers plans, subscriptions, invoicing, webhooks, and AI agents but not this trial/coupon lifecycle. missing for 10: docs on free trials, coupons/promo codes, automatic conversion to paid, 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 drawnLago's docs confirm idempotent event ingestion (dedup on repeated event IDs) and a usage-metering pipeline supporting API-driven event updates, which covers the core ingestion/idempotency claims. However, there is no explicit evidence of backdating support (e.g., specifying a past timestamp for events) or of high-volume streaming architecture/throughput guarantees for API calls, tokens, or compute-seconds use cases. missing for 10: explicit backdating/timestamp-override documentation, evidence of high-volume/streaming ingestion architecture or throughput benchmarks, independent verification of dedup behavior at scale.
- [claimed-docs] “Lago uses it for deduplication: if the same event arrives twice, it is billed once.”
- [claimed-docs] “Both non-engineers and engineers can update usage charges via API or Lago’s no-code UI.”
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 MetronomeLago's own positioning ('usage-based, subscription-based, and hybrid pricing models') and the plan-model/usage-metering docs confirm broad subscription+usage flexibility, and community reviews praise it for handling complex billing without custom code, but the evidence pack never explicitly documents tiered, volume, graduated, or per-unit charge models, nor credits, commitments, or overage handling as distinct configurable features. missing for 10: explicit docs on tiered/volume/graduated/per-unit charge model configuration, credits and commitment mechanics, overage billing rules, and independent confirmation these work without custom code.
- [probe] “PROBE llms.txt: HTTP 200 at https://getlago.com/llms.txt # Lago > Lago is the open-source billing platform for usage-based, subscription-ba…”
- [claimed-docs] “Yearly: subscription fees are billed on a yearly basis and charges can be billed monthly or annually.”
- [claimed-docs] “Both non-engineers and engineers can update usage charges via API or Lago’s no-code UI.”
- [claimed-docs] “Spot overdue, partially paid or unpaid invoices with filters to never lose track of what you’re owed.”
- [community] “"We decided to use Lago with our SaaS. Billing is super complicated and Lago handles everything we need out of the box. Building this stuff …”
- [community] “"Lago is awesome. We'll likely use Lago at my startup (metlo) when we implement full self-serve usage-based billing."”
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 MetronomeLago documents usage-metering and customer-facing analytics dashboards (lago-docs-14, lago-docs-15) and webhooks for event notifications (lago-docs-7), which could support real-time usage visibility, but there is no explicit documentation of configurable usage thresholds or proactive alerting before invoice generation. missing for 10: explicit threshold/alert configuration feature, evidence of real-time cost accrual view distinct from dashboards, confirmation that customers (not just ops) see live usage/cost.
- [claimed-docs] “Both non-engineers and engineers can update usage charges via API or Lago’s no-code UI.”
- [claimed-docs] “Build custom dashboards per customer, filter any way you want and export to CSV.”
- [claimed-docs] “The second is `HMAC`, which features a shorter payload header and no size restrictions.”
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 comparableLagon/aLago is a billing platform, not an automation/workflow builder; there is no concept of 'automations' with versioning, review, or rollback in the evidence pack. This axis is a category error for this product.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableLagonone0/10Lago is a billing platform; evidence covers billing, invoicing, self-hosting, and AI agent integrations (MCP server, dunning agent) but nowhere addresses data-use-for-AI-training opt-outs or privacy controls over model training. Missing for 10: any privacy policy statement, opt-out mechanism, or data-training exclusion clause.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableLagonone0/10No evidence in the pack addresses telemetry, usage tracking, or opt-out settings for Lago itself (self-hosted or cloud). The docs cover billing features, AI agents, and self-hosting setup, but nothing about product analytics/telemetry collection or a way to disable it. Missing for 10: any mention of telemetry collection, an opt-out flag/config, or privacy documentation addressing data sent back to Lago.
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.