Stripe Billing vs Lago

Agent access

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

   weight 2 · round drawn
   Stripe Billing✓fullprobed9/10

   Stripe hosts an llms.txt at docs.stripe.com/llms.txt (HTTP 200) and markdown-formatted docs (e.g. billing.md), confirming agent-friendly documentation is directly accessible. Missing for 10: independent/third-party confirmation that agents successfully consume these files in practice beyond the probe check.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/billing.md # Billing Create and manage subscriptions, track usage, and issue invoices. …”

   proof ↗⚑ flag

   Lago✓fullprobed9/10

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

   proof ↗⚑ flag

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

   weight 2 · round to Stripe Billing
   Stripe Billing✓fullprobed7/10

   Stripe Billing is fully accessible via API and has a documented CLI for building, testing, and managing integrations from the command line, both of which support headless/CI automation, and webhooks enable event-driven automation flows. Missing for 10: explicit CI pipeline examples (e.g., GitHub Actions) or documented headless-mode flags for the CLI, and independent confirmation of CI usage.

   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
   • [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”

   proof ↗⚑ flag

   Lago~partialclaimed6/10

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Stripe Billing✓fullprobed8/10

   Stripe (parent product of Stripe Billing) documents an official MCP server that lets AI agents interact with the Stripe API, confirmed by both docs and probe evidence. Missing for 10: no independent/community hands-on validation of the MCP server specifically, and no detail on which Billing-specific endpoints/tools are exposed via MCP.

   • [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Lago✓fullprobed8/10

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

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Stripe Billing
   Stripe Billing✓fullprobed8/10

   Stripe documents an official Stripe CLI for building, testing, and managing Stripe integrations from the command line, confirmed by both docs and probe evidence. Missing for 10: independent hands-on community reports specifically about CLI usage/quality (community evidence here focuses on billing fees, not the CLI).

   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Lago~partialclaimed4/10

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Stripe Billing✓fullprobed9/10

   Stripe Billing is fully drivable via the well-documented Subscriptions/Invoicing/Usage-based/Prorations APIs, with webhooks for events and even an official CLI and MCP server for agent-driven access. Missing for 10: no published OpenAPI spec discoverable at standard locations (404s on probe) and no independent hands-on confirmation of full API parity for AI-agent workflows.

   • [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
   • [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
   • [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/billing.md # Billing Create and manage subscriptions, track usage, and issue invoices. …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Lago✓fullprobed9/10

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Billing—none0/10

   The evidence pack shows Stripe's MCP server and CLI for agent integration, but nothing documents scoped or least-privilege API credential issuance for agents (e.g., restricted API keys with granular permissions) — this specific capability is absent from the pack. Missing for 10: documentation of restricted/scoped API key creation, permission granularity controls, and any agent-specific credential-scoping workflow.

   • [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”

   proof ↗⚑ flag

   Lago—none0/10

   Lago'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”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Lago
   Stripe Billing~partialprobed4/10

   The pack shows Stripe exposes a public API, an official CLI, and an MCP server for agent access, and the llms.txt note implies npm-published SDK packages, but there is no explicit documentation of official language SDKs (Node/Python/Ruby/etc.) or SDK-specific guides in the evidence pack. Missing for 10: explicit SDK reference docs/links, language coverage list, and any independent corroboration of SDK quality or agent usage with them.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
   • [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Lago~partialprobed5/10

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

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Stripe Billing✓fullclaimed7/10

   Stripe's docs explicitly describe webhooks pushing real-time event data when things happen in the account, which is the standard mechanism for subscribing to billing-related events (e.g., subscription/invoice lifecycle). Missing for 10: no specifics on which billing event types are supported, no documentation of webhook endpoint management via API, and no agent-specific webhook subscription flow (e.g., via MCP) tying it to the 'AI-native' framing.

   • [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”

   proof ↗⚑ flag

   Lago✓fullclaimed7/10

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

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Lago
   Stripe Billing—none0/10

   Evidence shows only standard analytics dashboards (docs-11) and an MCP server for external agents to call the API (docs-18), but nothing indicating the product itself generates AI-driven insights or suggestions from a merchant's billing data. missing for 10: any AI/ML-generated insights or recommendation features, in-product analysis narratives, or evidence of generative AI surfacing suggestions from billing/subscription data.

   • [claimed-docs] “Monitor overall performance at a glance”
   • [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”

   proof ↗⚑ flag

   Lago~partialprobed5/10

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Billing~partialprobed6/10

   Stripe Billing ships genuine background automations that run autonomously without manual intervention — recurring subscription billing, smart retries for failed payments, and webhook-driven event automation — and it exposes an official MCP server letting AI agents interact with the Billing API, aligning with the AI-native automation story. However, there is no evidence of an AI-native automation/rules builder (e.g., agent-authored workflows, scheduled agent tasks) beyond the MCP connector and the native recurring-billing engine. Missing for 10: dedicated AI-agent workflow/automation builder, evidence of agents autonomously configuring or modifying billing automations, independent hands-on validation of MCP-driven autonomous operation.

   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”
   • [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
   • [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Lago~partialprobed6/10

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

   proof ↗⚑ flag

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

   weight 3 · round to Lago
   Stripe Billing—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Lago~partialprobed5/10

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Billing~partialprobed6/10

   Stripe documents an official MCP server that lets AI agents interact with the Stripe API (which includes Billing endpoints for subscriptions, invoices, etc.), enabling natural-language-driven operation via an AI agent layer. However, this is evidenced only via first-party docs at the general Stripe API level, not Billing-specific NL commands, and there's no independent/hands-on confirmation of it working well for Billing tasks. Missing for 10: Billing-specific natural-language examples, independent/hands-on validation of MCP-driven billing operations, and documented limitations/edge cases.

   • [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Lago~partialprobed6/10

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

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Lago
   Stripe Billing—none0/10

   The evidence pack contains no mention of an interactive API reference with runnable/executable code examples for Stripe Billing; it only covers docs, CLI, MCP server, and general billing features. Absence of evidence for this applicable capability yields 'none'.

   ⚑ flag

   Lago~partialprobed5/10

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

   proof ↗⚑ flag

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

   weight 2 · round to Lago
   Stripe Billing—none0/10

   The evidence pack shows an explicit probe for OpenAPI/Swagger spec files at all standard paths returning 404, and no docs or community item mentions a downloadable OpenAPI/equivalent spec for Stripe Billing's API; only llms.txt and markdown docs endpoints are confirmed, which are not API specs.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/billing.md # Billing Create and manage subscriptions, track usage, and issue invoices. …”

   proof ↗⚑ flag

   Lago✓fullprobed9/10

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

   proof ↗⚑ flag

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

   weight 1 · round to Lago
   Stripe Billing—none0/10

   The evidence pack never mentions a Stripe test mode, sandbox environment, or test API keys — only general docs on billing features, CLI ("build, test, and manage... from the command line"), and MCP server access, none of which document an explicit non-production sandbox for safely testing AI-driven billing workflows. Since sandbox/test-mode support is a mainstream, applicable expectation for a billing platform, its absence here yields 'none' rather than 'na'.

   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Lago~partialclaimed4/10

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

   proof ↗⚑ flag

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

   weight 2 · round to Lago
   Stripe Billing—none0/10

   The evidence pack covers Billing features, pricing, fees, and community reactions but contains no mention of API versioning scheme, version pinning, or a documented deprecation policy for the Stripe API. Missing for 10: any documentation of API version headers, changelog/versioning policy, or deprecation timelines.

   ⚑ flag

   Lago✓fullprobed8/10

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

   proof ↗⚑ flag

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

   weight 2 · round to Stripe Billing
   Stripe Billing~partialprobed5/10

   Stripe Billing exposes a full REST API, CLI, and MCP server that could be scripted for bulk actions, and docs mention importing many existing subscriptions from third-party systems in bulk. However, there is no explicit documentation of batch/bulk endpoints, rate-limit-aware bulk workflows, or AI-agent-specific bulk operation support beyond general API access. Missing for 10: explicit bulk/batch API endpoints, documented bulk operation patterns via CLI/MCP, and independent evidence of successful large-scale bulk usage.

   • [claimed-docs] “You can import existing subscriptions from third-party billing systems (such as Zuora, Recurly, Chargify, or Chargebee) into Stripe Billing.”
   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
   • [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Lago—none0/10

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Stripe Billing~partialclaimed5/10

   Stripe Billing ships built-in automations tied to events (Smart Retries triggers on failed payment events, entitlements auto grant/revoke access) and exposes webhooks so developers can build custom event-triggered actions, satisfying the spirit of 'rules trigger actions on events.' However, there's no documented no-code/rule-builder interface for defining arbitrary trigger-condition-action rules — webhooks require custom code to consume events. Missing for 10: a dedicated rules/automation engine or UI for defining conditional triggers, and evidence of AI-native/agent-configurable rule definition beyond raw webhooks.

   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”
   • [claimed-docs] “Determine when you can grant or revoke product feature access to customers.”
   • [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”

   proof ↗⚑ flag

   Lago~partialclaimed5/10

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

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Stripe Billing
   Stripe Billing~partialprobed6/10

   Stripe Billing's core function is automating recurring billing workflows (subscriptions, trials, retries, prorations) and it exposes an API, CLI, and MCP server that let an AI-native user programmatically create/manage these recurring billing schedules. However, this is scoped to billing/subscription recurrence, not general-purpose job/workflow scheduling, and there's no explicit documentation of a 'subscription schedule' or cron-like workflow orchestration primitive beyond subscriptions/retries. missing for 10: dedicated subscription-schedule/workflow-scheduling docs, independent hands-on confirmation of AI-agent-driven recurring job setup via MCP/CLI.

   • [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
   • [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”
   • [claimed-docs] “Use the Trial Offer API to manage both free and paid introductory periods for your subscriptions with a single API integration.”
   • [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Lago~partialclaimed3/10

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

   proof ↗⚑ flag

Agent operations

1. ai-native userAn agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissions

   weight 3 · round to Lago
   Stripe Billing~partialprobed6/10

   Stripe Billing exposes a full programmatic Subscriptions API (create, change plan, proration preview) and an official MCP server letting AI agents interact with the Stripe API, which supports the 'agent operates billing programmatically' story. However, the evidence never documents scoped/restricted permission controls for agent access, nor explicit 'apply a credit' functionality, so the scoped-permission and credit-specific parts of the story are unevidenced. Missing for 10: documented scoped/restricted API key or permission model for agent use, explicit credit-application API evidence, and independent corroboration of the MCP server's agent workflows.

   • [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
   • [claimed-docs] “You can preview a proration to view the amount before applying the changes.”
   • [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Lago~partialprobed7/10

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

   proof ↗⚑ flag

Agent queries

1. ai-native userAn agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directly

   weight 2 · round to Lago
   Stripe Billing~partialprobed6/10

   Stripe ships an official MCP server explicitly for AI agents to interact with the Stripe API (docs-18, probe-4), which would let an agent query subscriptions, invoices, and customer records directly; docs also show subscription/invoice/analytics APIs (docs-2, docs-8, docs-11) that could back such queries. However, there's no direct evidence the MCP/API surfaces higher-level billing-state metrics like MRR or delinquency status as first-class queryable objects, and analytics is described as dashboard-facing rather than agent-facing. Missing for 10: explicit MCP tool/API documentation for MRR aggregation, delinquent-account flags, and renewal-forecast queries, plus any hands-on agent demo confirming these questions can be answered end-to-end.

   • [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
   • [claimed-docs] “Create, customize, and send a Stripe-hosted invoice from the Dashboard, with no code required.”
   • [claimed-docs] “Monitor overall performance at a glance”

   proof ↗⚑ flag

   Lago✓fullprobed8/10

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

   proof ↗⚑ flag

Billing cycles

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

   weight 2 · round drawn
   Stripe Billing—none0/10

   The evidence pack covers subscriptions, usage-based pricing, prorations, trials, and invoicing generally, but nothing documents billing_cycle_anchor controls, calendar-vs-anniversary billing options, cross-subscription alignment, or custom invoice date setting. Missing for 10: any doc/community mention of billing cycle anchor parameters, alignment across subscriptions, or custom invoice date configuration.

   ⚑ flag

   Lago—none0/10

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

   proof ↗⚑ flag

Proration

1. finance leadMid-cycle upgrades and downgrades are prorated with documented, auditable math — credits, partial periods, and invoice line items that reconcile to the penny

   weight 3 · round to Stripe Billing
   Stripe Billing~partialclaimed5/10

   Stripe docs confirm proration is supported with a preview capability before applying changes, giving finance teams visibility into charges before invoicing, and invoices/line items are generated automatically. However, there is no documented detail on the exact proration math methodology (day-count conventions, rounding rules), no auditable reconciliation reports, and no independent/community evidence confirming penny-level accuracy in practice. missing for 10: detailed documented proration formula/rounding rules, audit trail/reconciliation reporting for finance teams, independent verification of penny-accurate reconciliation.

   • [claimed-docs] “You can preview a proration to view the amount before applying the changes.”
   • [claimed-docs] “Create, customize, and send a Stripe-hosted invoice from the Dashboard, with no code required.”

   proof ↗⚑ flag

   Lago~partialcommunity3/10

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

   proof ↗⚑ flag

Card recovery

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

   weight 2 · round to Stripe Billing
   Stripe Billing~partialclaimed4/10

   Stripe's customer portal (docs-12, docs-13) provides hosted pages where customers can update payment methods, and Smart Retries (docs-5, docs-6) addresses failed payment recovery, but the evidence pack never mentions a network account updater service or backup/secondary payment methods functionality explicitly. missing for 10: explicit documentation of card network account updater, backup payment method fallback logic, and independent confirmation these auto-update cards without customer action.

   • [claimed-docs] “Give your customers the ability to manage their account by setting up a customer portal.”
   • [claimed-docs] “Use the Dashboard to activate the customer portal and optionally customize branding and prefill customer email addresses.”
   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”

   proof ↗⚑ flag

   Lago—none0/10

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

   ⚑ flag

Dunning comms

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

   weight 2 · round drawn
   Stripe Billing~partialclaimed4/10

   Stripe Billing docs confirm automated Smart Retries to recover failed payments, which is the core of dunning automation, but the evidence pack lacks any mention of branded dunning emails, in-app banners, configurable grace periods, or explicit final-state rules (cancel vs. mark-unpaid) that the story requires. missing for 10: branded email templates, in-app banner configuration, grace period settings, explicit cancel-vs-unpaid final state rules.

   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”

   proof ↗⚑ flag

   Lago~partialclaimed4/10

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

   proof ↗⚑ flag

Smart retries

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

   weight 3 · round to Stripe Billing
   Stripe Billing~partialclaimed6/10

   Stripe Billing documents Smart Retries, an automated system that retries failed subscription/invoice payments to reduce involuntary churn, directly matching the story's core ask (docs-5, docs-6). However, evidence doesn't detail ML- or schedule-optimization mechanics, retry cadence customization, or quantified recovery metrics, and community evidence focuses on pricing/fees rather than corroborating recovery effectiveness. Missing for 10: independent/hands-on evidence of measurable churn recovery impact, specifics on the ML/schedule optimization logic, and customer-facing proof of recovered revenue rates.

   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”

   proof ↗⚑ flag

   Lago~partialclaimed4/10

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

   proof ↗⚑ flag

Entitlement checks

1. developerFeatures and limits are modeled as entitlements attached to plans, and my application can check a customer's entitlements at runtime via API or SDK

   weight 3 · round to Stripe Billing
   Stripe Billing~partialclaimed5/10

   Stripe explicitly documents an Entitlements feature for granting/revoking product feature access to customers, matching the story's core idea of feature entitlements tied to products/plans, but the evidence pack gives only a single high-level doc link with no detail on the runtime API/SDK check flow or independent corroboration. missing for 10: specifics on the Entitlements API/SDK call for runtime checks, code examples, and community or hands-on validation of the feature.

   • [claimed-docs] “Determine when you can grant or revoke product feature access to customers.”

   proof ↗⚑ flag

   Lago~partialclaimed3/10

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

   proof ↗⚑ flag

Plan versioning

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

   weight 2 · round to Stripe Billing
   Stripe Billing~partialclaimed4/10

   Stripe docs show proration previews for subscription changes and a tool for importing subscriptions from third-party billing systems, which touch on the mechanics of adjusting pricing without immediately breaking billing, but there is no documentation of explicit 'versioned prices' grandfathering existing subscribers, nor a dedicated bulk cohort-migration tool for moving groups of subscribers to new prices. Missing for 10: explicit grandfathering/versioned-plan documentation, a bulk cohort price-migration API/tool, and independent evidence that ops teams use it this way.

   • [claimed-docs] “You can preview a proration to view the amount before applying the changes.”
   • [claimed-docs] “You can import existing subscriptions from third-party billing systems (such as Zuora, Recurly, Chargify, or Chargebee) into Stripe Billing.”
   • [claimed-docs] “you can set up and integrate different types of usage-based pricing models with your SaaS product.”
   • [claimed-docs] “Determine when you can grant or revoke product feature access to customers.”

   proof ↗⚑ flag

   Lago~partialclaimed3/10

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

   proof ↗⚑ flag

Invoices

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

   weight 2 · round drawn
   Stripe Billing~partialcommunity4/10

   Docs confirm Stripe Billing/Invoicing can create, customize, and automatically send hosted invoices from the Dashboard (stripe-billing-docs-8), but the evidence never explicitly documents sequential invoice numbering, credit notes, receipts, or memo/custom-field compliance details, and a community comment even claims Stripe historically lacked easy 'email invoicing' compared to competitors (stripe-billing-comm-6). missing for 10: explicit documentation of sequential numbering, credit note generation, receipt issuance, and memo/custom field support with independent corroboration that these are compliant and automated end-to-end.

   • [claimed-docs] “Create, customize, and send a Stripe-hosted invoice from the Dashboard, with no code required.”
   • [community] “A team said they were 'writing code to move from stripe to recurly/adyen' citing that 'the analytics/easy plan mgmt and email invoicing in r…”
   • [community] “Confusion among users about what Stripe Billing actually includes: 'I thought Stripe Billing referred to the Customer Portal functionality a…”

   proof ↗⚑ flag

   Lago~partialclaimed4/10

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

   proof ↗⚑ flag

Multi currency

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

   weight 2 · round to Stripe Billing
   Stripe Billing~partialcommunity5/10

   Stripe Billing supports subscriptions and analytics, but a Stripe PM confirmed that multi-currency pricing currently requires creating a separate plan per currency rather than a single price point with per-currency variants, and reporting/analytics is mentioned only generically without evidence of home-currency consolidation across currencies. missing for 10: native single-price multi-currency price points (not per-currency plan duplication), documented consolidated/rollup reporting in home currency across multiple billing currencies, independent confirmation of this workflow.

   • [community] “For multi-currency subscriptions, Stripe PM confirmed you currently need to create a separate plan per currency (e.g. bronze_plan:eur), sinc…”
   • [claimed-docs] “Monitor overall performance at a glance”
   • [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”

   proof ↗⚑ flag

   Lago—none0/10

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

   ⚑ flag

Tax

1. finance leadSales tax, VAT, and GST are calculated on every invoice — natively or through a first-class tax integration — with the right registrations and rates

   weight 2 · round to Stripe Billing
   Stripe Billing✓fullclaimed7/10

   Stripe Tax is documented as a native, first-class feature that automates sales tax, VAT, and GST compliance directly within the Stripe ecosystem (stripe-billing-docs-15), aligning with Stripe Billing's invoicing flow. Missing for 10: independent/hands-on corroboration of tax calculation accuracy and detail on how registrations/rates are managed across multiple jurisdictions beyond the single doc reference.

   • [claimed-docs] “Automate sales tax, VAT, and GST compliance on all your transactions.”
   • [claimed-docs] “Create, customize, and send a Stripe-hosted invoice from the Dashboard, with no code required.”

   proof ↗⚑ flag

   Lago—none0/10

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

   ⚑ flag

Export

1. finance leadExport every subscription, invoice, and usage record — and port stored payment methods out to another provider — if I choose to leave

   weight 2 · round to Lago
   Stripe Billing—none0/10

   Evidence only documents importing subscriptions *into* Stripe from other providers (Zuora, Recurly, etc.) and migrating customer/payment data *to* Stripe — the reverse direction (exporting subscriptions/invoices/usage and porting stored payment methods to another provider) is never documented. Community evidence even shows a team having to 'write code to move from stripe to recurly/adyen' themselves, implying no built-in export/portability tool exists.

   • [claimed-docs] “You can import existing subscriptions from third-party billing systems (such as Zuora, Recurly, Chargify, or Chargebee) into Stripe Billing.”
   • [claimed-docs] “Migrating your customer and payments data to Stripe is a multi-step process.”
   • [community] “A team said they were 'writing code to move from stripe to recurly/adyen' citing that 'the analytics/easy plan mgmt and email invoicing in r…”

   proof ↗⚑ flag

   Lago~partialclaimed4/10

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

   proof ↗⚑ flag

Import

1. ops userMigrate live subscriptions in from a spreadsheet or a competing platform — including PCI-compliant card data transfer — without customers noticing

   weight 3 · round to Stripe Billing
   Stripe Billing~partialclaimed5/10

   Docs explicitly cover importing subscriptions from competing platforms like Zuora, Recurly, Chargify, and Chargebee (docs-10) and a general 'multi-step' customer/payments data migration guide (docs-17), which supports the platform-migration part of the story. However there is no evidence of spreadsheet-based import, no detail on PCI-compliant card data transfer mechanics, and no confirmation that migrated subscriptions continue billing seamlessly without customer-visible disruption. Missing for 10: spreadsheet import support, explicit PCI-compliant card token transfer process, and evidence/testimony that migration is invisible to end customers.

   • [claimed-docs] “You can import existing subscriptions from third-party billing systems (such as Zuora, Recurly, Chargify, or Chargebee) into Stripe Billing.”
   • [claimed-docs] “Migrating your customer and payments data to Stripe is a multi-step process.”

   proof ↗⚑ flag

   Lago—none0/10

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

   proof ↗⚑ flag

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

   weight 2 · round to Lago
   Stripe Billing~partialcommunity6/10

   Stripe's API covers most Billing operations (subscriptions, usage-based pricing, prorations, trials, entitlements, invoicing) and there's also a CLI and MCP server for programmatic/agent access, but some UI-only features are explicitly dashboard-driven with no-code framing (e.g., hosted invoice creation, customer portal branding/activation), and community comments note gaps like easy plan management/analytics parity versus competitors. missing for 10: confirmation that customer portal setup/branding and dashboard-only analytics views are fully API-configurable, independent verification of full UI/API parity, and evidence addressing feature gaps raised by users (e.g., portal customization, analytics).

   • [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
   • [claimed-docs] “you can set up and integrate different types of usage-based pricing models with your SaaS product.”
   • [claimed-docs] “You can preview a proration to view the amount before applying the changes.”
   • [claimed-docs] “Determine when you can grant or revoke product feature access to customers.”
   • [claimed-docs] “Use the Dashboard to activate the customer portal and optionally customize branding and prefill customer email addresses.”
   • [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
   • [community] “A team said they were 'writing code to move from stripe to recurly/adyen' citing that 'the analytics/easy plan mgmt and email invoicing in r…”
   • [community] “Confusion among users about what Stripe Billing actually includes: 'I thought Stripe Billing referred to the Customer Portal functionality a…”

   proof ↗⚑ flag

   Lago~partialprobed7/10

   Lago'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”

   proof ↗⚑ flag

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

   weight 3 · round to Lago
   Stripe Billing—none0/10

   Evidence covers importing/migrating data INTO Stripe Billing (from Zuora, Recurly, etc.) but nothing about exporting a merchant's own subscription/invoice/customer data out in open formats to leave the platform. No documentation of a data export or portability tool for departing customers.

   • [claimed-docs] “You can import existing subscriptions from third-party billing systems (such as Zuora, Recurly, Chargify, or Chargebee) into Stripe Billing.”
   • [claimed-docs] “Migrating your customer and payments data to Stripe is a multi-step process.”

   proof ↗⚑ flag

   Lago~partialprobed6/10

   Lago'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”

   proof ↗⚑ flag

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

   weight 2 · round to Lago
   Stripe Billing—none0/10

   Stripe Billing is a closed-source SaaS product; there is no evidence of any open-licensed source code being available for inspection. Documentation, CLI, and MCP server are all provided, but none imply open-source availability of the underlying product code.

   ⚑ flag

   Lago✓fullprobed7/10

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

   • [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…”
   • [github] “It starts the Lago version that matches this checkout, creates a disposable local organization, and prices three illustrative AI requests.”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Lago
   Stripe Billing—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Lago✓fullcommunity8/10

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

   proof ↗⚑ flag

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

   weight 2 · round to Lago
   Stripe Billing—none0/10

   No evidence in the pack discusses data residency, regional storage options, or data sovereignty controls for Stripe Billing; the axis applies to a payments/data platform like Stripe but is unaddressed here.

   ⚑ flag

   Lago~partialclaimed3/10

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

   proof ↗⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Stripe Billing—none0/10

   The evidence pack covers subscriptions, invoicing, tax, portal, MCP/CLI tooling, and pricing complaints, 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 settings, deletion/erasure APIs, or privacy controls for customer/usage data.

   ⚑ flag

   Lago—none0/10

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

   ⚑ flag

3. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Stripe Billing—none0/10

   Stripe Billing is a payments/subscription platform, not a developer tool with telemetry collection concerns, but no evidence addresses any telemetry/usage-tracking opt-out mechanism for AI-native users interacting with its API, CLI, or MCP server; the evidence pack contains no mention of telemetry at all.

   ⚑ flag

   Lago—none0/10

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

   ⚑ flag

Analytics

1. founderI get MRR, churn, cohort retention, and LTV analytics computed from the billing source of truth, not a bolted-on BI export

   weight 2 · round to Stripe Billing
   Stripe Billing!disputedcontradicted4/10

   Stripe's docs only vaguely reference subscription analytics ('Monitor overall performance at a glance') with no explicit mention of MRR, churn, cohort retention, or LTV computation, and community evidence directly contradicts the claim that Stripe provides adequate built-in analytics, with one team citing lack of analytics as a reason for migrating away from Stripe Billing to Recurly. missing for 10: explicit documentation of MRR/churn/cohort/LTV dashboards, independent confirmation that these metrics are computed natively rather than requiring external BI tools.

   • [claimed-docs] “Monitor overall performance at a glance”
   • [community] “A team said they were 'writing code to move from stripe to recurly/adyen' citing that 'the analytics/easy plan mgmt and email invoicing in r…”

   proof ↗⚑ flag

   Lago—none0/10

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

   proof ↗⚑ flag

Gl sync

1. finance leadInvoices, payments, and recognition entries sync to my general ledger or ERP — QuickBooks, Xero, NetSuite — so the close doesn't need CSV surgery

   weight 2 · round drawn
   Stripe Billing—none0/10

   The evidence pack shows Stripe Billing's revenue recognition module (docs-7) and webhooks (docs-16) but contains no mention of native or documented sync to QuickBooks, Xero, NetSuite, or any ERP/GL system — only generic webhook/API primitives that a team would need to build custom integration on top of. Missing for 10: documented native connectors or partner integrations for QuickBooks/Xero/NetSuite, evidence of automated invoice/payment/rev-rec entry sync to a GL, and any customer account of eliminating manual CSV reconciliation.

   • [claimed-docs] “Simplify your revenue recognition with automated support for global accounting standards”
   • [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
   • [claimed-docs] “Migrating your customer and payments data to Stripe is a multi-step process.”

   proof ↗⚑ flag

   Lago—none0/10

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

   ⚑ flag

Revrec reports

1. finance leadRevenue is recognized on an ASC 606 / IFRS 15 basis — deferred revenue schedules and audit-ready recognition reports straight from billing data

   weight 3 · round to Stripe Billing
   Stripe Billing~partialclaimed5/10

   Stripe has a dedicated Revenue Recognition product that automates deferred revenue schedules per global accounting standards, directly matching the story's core intent, but the evidence pack gives only a single thin doc snippet with no mention of ASC 606/IFRS 15 specifically, no detail on audit-ready reporting outputs, and no independent/community corroboration of its use for finance audits. missing for 10: explicit ASC606/IFRS15 standard mapping, description of audit-ready report generation, independent or hands-on validation of the recognition reports.

   • [claimed-docs] “Simplify your revenue recognition with automated support for global accounting standards”

   proof ↗⚑ flag

   Lago—none0/10

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

   proof ↗⚑ flag

Lifecycle api

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

   weight 3 · round to Stripe Billing
   Stripe Billing✓fullprobed7/10

   Docs confirm subscriptions can be created and updated via the Subscriptions API (including proration previews for changes) and trials/usage-based pricing are API-configurable, plus CLI/webhooks support programmatic workflows without the dashboard. However, explicit documentation of 'pause' and 'cancel' endpoints isn't present in the evidence pack, only implied by general subscription management docs. missing for 10: explicit doc citation for pause-subscription and cancel-subscription API endpoints, independent hands-on confirmation of full lifecycle via API only.

   • [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
   • [claimed-docs] “You can preview a proration to view the amount before applying the changes.”
   • [claimed-docs] “Use the Trial Offer API to manage both free and paid introductory periods for your subscriptions with a single API integration.”
   • [claimed-docs] “you can set up and integrate different types of usage-based pricing models with your SaaS product.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/billing.md # Billing Create and manage subscriptions, track usage, and issue invoices. …”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Lago~partialprobed6/10

   Lago'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”

   proof ↗⚑ flag

Lifecycle events

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

   weight 2 · round to Stripe Billing
   Stripe Billing~partialclaimed7/10

   Docs confirm Stripe pushes real-time webhook events for account changes (stripe-billing-docs-16) and describe automated retry logic for failed payments (stripe-billing-docs-5/6), supporting reliable notification of key lifecycle changes like renewals and payment failures. However, the pack lacks explicit documentation enumerating specific event types for upgrades/downgrades/cancellations or delivery-guarantee details (retries, signing, idempotency) tied directly to subscription state transitions. Missing for 10: explicit list of subscription-lifecycle event types (e.g., customer.subscription.updated/deleted), and evidence of webhook delivery reliability guarantees.

   • [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”

   proof ↗⚑ flag

   Lago~partialclaimed6/10

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

   proof ↗⚑ flag

Self serve

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

   weight 2 · round to Stripe Billing
   Stripe Billing✓fullcommunity8/10

   Stripe docs explicitly describe a hosted Customer Portal that lets customers manage their own accounts (upgrade/downgrade/cancel) with Dashboard-based activation and branding, directly addressing self-service without support tickets. Community evidence corroborates the portal exists though notes some confusion over what's included and general pricing/product complaints unrelated to portal functionality itself. Missing for 10: independent hands-on report specifically confirming self-serve upgrade/downgrade/cancel flows work smoothly in production, and no mention of embeddable pricing-table/components for the same use case.

   • [claimed-docs] “Give your customers the ability to manage their account by setting up a customer portal.”
   • [claimed-docs] “Use the Dashboard to activate the customer portal and optionally customize branding and prefill customer email addresses.”
   • [community] “Confusion among users about what Stripe Billing actually includes: 'I thought Stripe Billing referred to the Customer Portal functionality a…”

   proof ↗⚑ flag

   Lago—none0/10

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

   proof ↗⚑ flag

Trials promos

1. ops userRun free trials, coupons, and promotion codes with automatic conversion to paid — including trial-end notifications required by card-network rules

   weight 2 · round to Stripe Billing
   Stripe Billing~partialcommunity4/10

   Docs confirm a Trial Offer API for free/paid trial periods and subscription automation (stripe-billing-docs-14, stripe-billing-docs-2), and community notes that Stripe emails (e.g., card update notices) are off by default and merchants can use webhooks instead (stripe-billing-comm-7), implying trial-end reminders aren't automatic out-of-the-box. No evidence pack items mention coupons or promotion codes specifically, nor explicit trial-end notification features required by card-network rules. missing for 10: coupon/promotion-code documentation, explicit trial-end notification/reminder feature docs, evidence of automatic trial-to-paid conversion flow, and confirmation of card-network compliance requirements being met.

   • [claimed-docs] “Use the Trial Offer API to manage both free and paid introductory periods for your subscriptions with a single API integration.”
   • [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
   • [community] “Stripe Billing PM stated all customer emails (like credit card update notices) are off by default, matching behavior of other Stripe emails,…”

   proof ↗⚑ flag

   Lago—none0/10

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

   ⚑ flag

Event ingestion

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

   weight 3 · round to Lago
   Stripe Billing~partialclaimed2/10

   The evidence only shows generic usage-based subscription pricing support (stripe-billing-docs-3) with no documentation of a dedicated meter/usage-events API, idempotency keys, backdating of events, or high-volume streaming ingestion mechanics. Missing for 10: explicit meter events API docs, idempotent ingestion mechanism details, backdating/timestamp support evidence, high-volume throughput claims or benchmarks.

   • [claimed-docs] “you can set up and integrate different types of usage-based pricing models with your SaaS product.”

   proof ↗⚑ flag

   Lago~partialclaimed5/10

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

   proof ↗⚑ flag

Pricing models

1. finance leadPrice with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom code

   weight 3 · round drawn
   Stripe Billing~partialcommunity5/10

   Docs confirm Stripe Billing supports usage-based subscription pricing and custom pricing plans without code (stripe-billing-docs-1, stripe-billing-docs-3), and community corroborates per-user/per-usage/per-tier models (stripe-billing-comm-1). However, the evidence never explicitly documents tiered, volume, graduated, or per-unit pricing structures, nor credits, commitments, or overage billing mechanics as named capabilities. Missing for 10: explicit documentation of tiered/volume/graduated/per-unit price types, credits and commitment/overage billing constructs, and any hands-on confirmation these can be combined without custom code.

   • [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
   • [claimed-docs] “you can set up and integrate different types of usage-based pricing models with your SaaS product.”
   • [community] “Stripe Billing supports per-user, per-usage, and per-tier subscription models in an automated recurring billing fashion, covering the 3 stan…”

   proof ↗⚑ flag

   Lago~partialprobed5/10

   Lago'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."”

   proof ↗⚑ flag

Usage visibility

1. ops userCustomers and my team can see current-cycle usage and accrued cost in real time, with thresholds and alerts before an invoice surprises anyone

   weight 2 · round to Lago
   Stripe Billing—none0/10

   Evidence covers usage-based pricing setup, proration previews, and subscription analytics, but there is no mention of real-time usage dashboards for customers/team, configurable usage thresholds, or proactive alerts before invoicing. missing for 10: real-time usage/cost visibility for customers and team, threshold configuration, proactive alerting before invoice generation.

   • [claimed-docs] “you can set up and integrate different types of usage-based pricing models with your SaaS product.”
   • [claimed-docs] “Monitor overall performance at a glance”

   proof ↗⚑ flag

   Lago~partialclaimed5/10

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

   proof ↗⚑ flag