Rank #1 of 7 in Billing & Subscriptions
Try itExperimental
See what an agent can do with Lago before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s https://api.getlago.com/api/v1/customers # hosted API, keyless → {"status":401,"error":"Unauthorized"}recorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Billing agent access — stories about billing agent access in this arenaBilling agent accessevidence →
Stories about billing agent access in this arena
Billing math — stories about billing math in this arenaBilling mathevidence →
Stories about billing math in this arena
Dunning recovery — stories about dunning recovery in this arenaDunning recoveryevidence →
Stories about dunning recovery in this arena
Entitlements — stories about entitlements in this arenaEntitlementsevidence →
Stories about entitlements in this arena
Invoicing tax — stories about invoicing tax in this arenaInvoicing taxevidence →
Stories about invoicing tax in this arena
Migration portability — stories about migration portability in this arenaMigration portabilityevidence →
Stories about migration portability in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Revenue recognition — stories about revenue recognition in this arenaRevenue recognitionevidence →
Stories about revenue recognition in this arena
Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycleevidence →
Stories about subscription lifecycle in this arena
Usage metering — stories about usage metering in this arenaUsage meteringevidence →
Stories about usage metering in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 3 free · 0 paid · 0 enterprise · 33 not stated in evidence
Follow the green: where the map greys out is where Lago stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓9/10
unlocks → Scoped API keys
Subscribe to events via webhooks
✓7/10
Build against official SDKs
~5/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
✓9/10
Rely on versioned APIs with a documented deprecation policy
✓8/10
Test against a sandbox environment without touching production data
~4/10
Explore an interactive API reference with runnable examples
~5/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~5/10
unlocks → MCP client
Operate the product with natural-language commands
~6/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
~5/10
Set up automations that run autonomously in the background
~6/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Billing agent access — stories about billing agent access in this arenaBilling agent access
Stories about billing agent access in this arena
An agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissions
~7/10
An agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directly
✓8/10
Billing math — stories about billing math in this arenaBilling math
Stories about billing math in this arena
Control billing anchors and cycles — calendar vs anniversary billing, alignment across a customer's subscriptions, custom invoice dates
—0/10
Mid-cycle upgrades and downgrades are prorated with documented, auditable math — credits, partial periods, and invoice line items that reconcile to the penny
~3/10
Dunning recovery — stories about dunning recovery in this arenaDunning recovery
Stories about dunning recovery in this arena
Expiring or replaced cards update themselves — network account updater, backup payment methods, and hosted update-payment pages
—–
Configure automated dunning sequences — branded emails, in-app banners, grace periods, and final-state rules like cancel vs unpaid
~4/10
Failed renewal payments are retried automatically on an ML- or schedule-optimized cadence that measurably recovers involuntary churn
~4/10
Entitlements — stories about entitlements in this arenaEntitlements
Stories about entitlements in this arena
Features and limits are modeled as entitlements attached to plans, and my application can check a customer's entitlements at runtime via API or SDK
~3/10
Change pricing without breaking existing subscribers — versioned plans, grandfathering, and bulk migration tools for moving cohorts to new prices
~3/10
Invoicing tax — stories about invoicing tax in this arenaInvoicing tax
Stories about invoicing tax in this arena
The platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automatically
~4/10
Bill customers in their local currency with per-currency price points and consolidated reporting in my home currency
—–
Sales tax, VAT, and GST are calculated on every invoice — natively or through a first-class tax integration — with the right registrations and rates
—–
Migration portability — stories about migration portability in this arenaMigration portability
Stories about migration portability in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Openness
Self-host the core product
✓8/10
unlocks → No AI training
Export all of my data in open formats and leave
~6/10
unlocks → Migrate live subscriptions in from a spreadsheet or a competing platform — including PCI-compliant card data transfer — without customers noticing
Do everything through the API that I can do in the UI
~7/10
Read the product's source under an open license
✓7/10
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Revenue recognition — stories about revenue recognition in this arenaRevenue recognition
Stories about revenue recognition in this arena
I get MRR, churn, cohort retention, and LTV analytics computed from the billing source of truth, not a bolted-on BI export
—0/10
Invoices, payments, and recognition entries sync to my general ledger or ERP — QuickBooks, Xero, NetSuite — so the close doesn't need CSV surgery
—–
Revenue is recognized on an ASC 606 / IFRS 15 basis — deferred revenue schedules and audit-ready recognition reports straight from billing data
—0/10
Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycle
Stories about subscription lifecycle in this arena
Create, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboard
~6/10
Every subscription state change — renewal, upgrade, payment failure, cancellation — emits a webhook or event my systems can act on reliably
~6/10
My customers can upgrade, downgrade, or cancel themselves through a hosted portal or embeddable components, without a support ticket
—0/10
Run free trials, coupons, and promotion codes with automatic conversion to paid — including trial-end notifications required by card-network rules
—–
Usage metering — stories about usage metering in this arenaUsage metering
Stories about usage metering in this arena
Stream high-volume usage events — API calls, tokens, compute-seconds — into a metering pipeline with idempotent ingestion and backdating support
~5/10
Price with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom code
~5/10
Customers and my team can see current-cycle usage and accrued cost in real time, with thresholds and alerts before an invoice surprises anyone
~5/10
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 9/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 5/10 | Tprobed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 4/10 | Cclaimed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | fullfree | 8/10 | Xcommunity | |
An agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissions G Agent operations | ai-native user | Billing agent access — stories about billing agent access in this arenaBilling agent access | 3 | partial | 7/10 | Tprobed | |
Create, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboard C Lifecycle api | developer | Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycle | 3 | partial | 6/10 | Tprobed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 6/10 | Tprobed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 5/10 | Cclaimed | |
Price with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom code G Pricing models | finance lead | Usage metering — stories about usage metering in this arenaUsage metering | 3 | partial | 5/10 | Tprobed | |
Stream high-volume usage events — API calls, tokens, compute-seconds — into a metering pipeline with idempotent ingestion and backdating support C Event ingestion | developer | Usage metering — stories about usage metering in this arenaUsage metering | 3 | partial | 5/10 | Cclaimed | |
Failed renewal payments are retried automatically on an ML- or schedule-optimized cadence that measurably recovers involuntary churn C Smart retries | finance lead | Dunning recovery — stories about dunning recovery in this arenaDunning recovery | 3 | partial | 4/10 | Cclaimed | |
Features and limits are modeled as entitlements attached to plans, and my application can check a customer's entitlements at runtime via API or SDK C Entitlement checks | developer | Entitlements — stories about entitlements in this arenaEntitlements | 3 | partial | 3/10 | Cclaimed | |
Mid-cycle upgrades and downgrades are prorated with documented, auditable math — credits, partial periods, and invoice line items that reconcile to the penny C Proration | finance lead | Billing math — stories about billing math in this arenaBilling math | 3 | partial | 3/10 | Xcommunity | |
Migrate live subscriptions in from a spreadsheet or a competing platform — including PCI-compliant card data transfer — without customers noticing C Import | ops user | Migration portability — stories about migration portability in this arenaMigration portability | 3 | none | 0/10 | ||
Revenue is recognized on an ASC 606 / IFRS 15 basis — deferred revenue schedules and audit-ready recognition reports straight from billing data G Revrec reports | finance lead | Revenue recognition — stories about revenue recognition in this arenaRevenue recognition | 3 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
An agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directly G Agent queries | ai-native user | Billing agent access — stories about billing agent access in this arenaBilling agent access | 2 | full | 8/10 | Tprobed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 7/10 | Tprobed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | fullfree | 7/10 | Tprobed | |
Every subscription state change — renewal, upgrade, payment failure, cancellation — emits a webhook or event my systems can act on reliably C Lifecycle events | developer | Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycle | 2 | partial | 6/10 | Cclaimed | |
Customers and my team can see current-cycle usage and accrued cost in real time, with thresholds and alerts before an invoice surprises anyone C Usage visibility | ops user | Usage metering — stories about usage metering in this arenaUsage metering | 2 | partial | 5/10 | Cclaimed | |
Configure automated dunning sequences — branded emails, in-app banners, grace periods, and final-state rules like cancel vs unpaid C Dunning comms | ops user | Dunning recovery — stories about dunning recovery in this arenaDunning recovery | 2 | partial | 4/10 | Cclaimed | |
Export every subscription, invoice, and usage record — and port stored payment methods out to another provider — if I choose to leave G Export | finance lead | Migration portability — stories about migration portability in this arenaMigration portability | 2 | partial | 4/10 | Cclaimed | |
The platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automatically C Invoices | ops user | Invoicing tax — stories about invoicing tax in this arenaInvoicing tax | 2 | partial | 4/10 | Cclaimed | |
Change pricing without breaking existing subscribers — versioned plans, grandfathering, and bulk migration tools for moving cohorts to new prices G Plan versioning | ops user | Entitlements — stories about entitlements in this arenaEntitlements | 2 | partial | 3/10 | Cclaimed | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partialfree | 3/10 | Cclaimed | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 3/10 | Cclaimed | |
Control billing anchors and cycles — calendar vs anniversary billing, alignment across a customer's subscriptions, custom invoice dates G Billing cycles | ops user | Billing math — stories about billing math in this arenaBilling math | 2 | none | 0/10 | ||
I get MRR, churn, cohort retention, and LTV analytics computed from the billing source of truth, not a bolted-on BI export G Analytics | founder | Revenue recognition — stories about revenue recognition in this arenaRevenue recognition | 2 | none | 0/10 | ||
My customers can upgrade, downgrade, or cancel themselves through a hosted portal or embeddable components, without a support ticket C Self serve | founder | Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycle | 2 | none | 0/10 | ||
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
Bill customers in their local currency with per-currency price points and consolidated reporting in my home currency G Multi currency | finance lead | Invoicing tax — stories about invoicing tax in this arenaInvoicing tax | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Expiring or replaced cards update themselves — network account updater, backup payment methods, and hosted update-payment pages C Card recovery | ops user | Dunning recovery — stories about dunning recovery in this arenaDunning recovery | 2 | none | untested | none yet | |
Invoices, payments, and recognition entries sync to my general ledger or ERP — QuickBooks, Xero, NetSuite — so the close doesn't need CSV surgery C Gl sync | finance lead | Revenue recognition — stories about revenue recognition in this arenaRevenue recognition | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Run free trials, coupons, and promotion codes with automatic conversion to paid — including trial-end notifications required by card-network rules C Trials promos | ops user | Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycle | 2 | none | untested | none yet | |
Sales tax, VAT, and GST are calculated on every invoice — natively or through a first-class tax integration — with the right registrations and rates C Tax | finance lead | Invoicing tax — stories about invoicing tax in this arenaInvoicing tax | 2 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 43 stories with headroom
What would move Lago’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
The 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.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
Missing: any privacy policy statement, opt-out mechanism, or data-training exclusion clause.
Revenue recognition — stories about revenue recognition in this arenaRevenue is recognized on an ASC 606 / IFRS 15 basis — deferred revenue schedules and audit-ready recognition reports straight from billing data
nonemoves PA Scoreimpact 30
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.
Migration portability — stories about migration portability in this arenaMigrate live subscriptions in from a spreadsheet or a competing platform — including PCI-compliant card data transfer — without customers noticing
nonemoves PA Scoreimpact 30
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.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
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.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
partialq5/10moves Built-in AIimpact 22.5
Missing: evidence of a general conversational assistant UI, breadth of tasks beyond dunning, independent/hands-on confirmation of the Dunning Agent actually operating in production.
Entitlements — stories about entitlements in this arenaFeatures and limits are modeled as entitlements attached to plans, and my application can check a customer's entitlements at runtime via API or SDK
partialq3/10moves PA Scoreimpact 21
Missing: aPI reference for entitlement endpoints, SDK code samples for checking a customer's entitlements at runtime, plan-to-entitlement modeling details.
Billing math — stories about billing math in this arenaMid-cycle upgrades and downgrades are prorated with documented, auditable math — credits, partial periods, and invoice line items that reconcile to the penny
partialq3/10moves PA Scoreimpact 21
Missing: explicit proration algorithm documentation, sample invoice line items showing credits/partial periods, and any audit or reconciliation guarantee.
Showing the top 8 of 43 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map7 surfaces · 36 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs33 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Use an official CLI
- Drive the product through a documented public API
- Build against official SDKs
- Subscribe to events via webhooks
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Explore an interactive API reference with runnable examples
- Test against a sandbox environment without touching production data
- Rely on versioned APIs with a documented deprecation policy
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- An agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissions
- An agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directly
- Mid-cycle upgrades and downgrades are prorated with documented, auditable math — credits, partial periods, and invoice line items that reconcile to the penny
- Configure automated dunning sequences — branded emails, in-app banners, grace periods, and final-state rules like cancel vs unpaid
- Failed renewal payments are retried automatically on an ML- or schedule-optimized cadence that measurably recovers involuntary churn
- Change pricing without breaking existing subscribers — versioned plans, grandfathering, and bulk migration tools for moving cohorts to new prices
- The platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automatically
- Export every subscription, invoice, and usage record — and port stored payment methods out to another provider — if I choose to leave
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Self-host the core product
- Choose where my data is stored (region/residency)
- Create, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboard
- Every subscription state change — renewal, upgrade, payment failure, cancellation — emits a webhook or event my systems can act on reliably
- Stream high-volume usage events — API calls, tokens, compute-seconds — into a metering pipeline with idempotent ingestion and backdating support
- Price with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom code
- Customers and my team can see current-cycle usage and accrued cost in real time, with thresholds and alerts before an invoice surprises anyone
Developers docs14 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Operate the product with natural-language commands
- Explore an interactive API reference with runnable examples
- Download a machine-readable API spec (OpenAPI or equivalent)
- Rely on versioned APIs with a documented deprecation policy
- An agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissions
- An agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directly
- Export every subscription, invoice, and usage record — and port stored payment methods out to another provider — if I choose to leave
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Create, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboard
OpenAPI spec11 stories
- Point an agent at llms.txt or agent-oriented docs
- Drive the product through a documented public API
- Build against official SDKs
- Explore an interactive API reference with runnable examples
- Download a machine-readable API spec (OpenAPI or equivalent)
- Rely on versioned APIs with a documented deprecation policy
- An agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissions
- An agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directly
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Create, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboard
Platform docs10 stories
- Configure automated dunning sequences — branded emails, in-app banners, grace periods, and final-state rules like cancel vs unpaid
- Failed renewal payments are retried automatically on an ML- or schedule-optimized cadence that measurably recovers involuntary churn
- Features and limits are modeled as entitlements attached to plans, and my application can check a customer's entitlements at runtime via API or SDK
- The platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automatically
- Export every subscription, invoice, and usage record — and port stored payment methods out to another provider — if I choose to leave
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Stream high-volume usage events — API calls, tokens, compute-seconds — into a metering pipeline with idempotent ingestion and backdating support
- Price with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom code
- Customers and my team can see current-cycle usage and accrued cost in real time, with thresholds and alerts before an invoice surprises anyone
llms.txt4 stories
- Point an agent at llms.txt or agent-oriented docs
- Drive the product through a documented public API
- Read the product's source under an open license
- Price with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom code
GitHub README3 stories
Hacker News3 stories
- Mid-cycle upgrades and downgrades are prorated with documented, auditable math — credits, partial periods, and invoice line items that reconcile to the penny
- Self-host the core product
- Price with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom code
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s https://api.getlago.com/api/v1/customers # hosted API, keyless → {"status":401,"error":"Unauthorized"}reproduced$ curl -s https://api.getlago.com/api/v1/customers # hosted API, [redacted]less → {"status":401,"error":"Unauthorized"}
{"status":401,"error":"Unauthorized"}
$curl -s -X POST https://getlago.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # keyless MCP initialize completes — serverInfo comes backreproduced$ curl -s -X POST https://getlago.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # [redacted]less MCP initialize completes — serverInfo comes back
{"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":false},"resources":{"listChanged":false}},"serverInfo":{"name":"Lago Agent Discovery","version":"1.0.0"},"instructions":"Use this read-only server to discover Lago capabilities and canonical public developer resources. Use https://docs.getlago.com/mcp for full documentation search."}}
$curl -s https://swagger.getlago.com/openapi.yaml | head -3reproduced$ curl -s https://swagger.getlago.com/openapi.yaml | head -3 openapi: 3.1.0 info: title: Lago API documentation
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
6 of 16 testable claims verified · 3 contradicted → integrity 0/100
16 distinct capability claims found in Lago’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
6
Verified
7
Unverified
3
Contradicted
23
Undersold
Verified (6)
“API v1 follows a documented additive-change compatibility policy for clients”
Rely on versioned APIs with a documented deprecation policyfullproof ↗
“Provides AI assistants like Claude direct access to Lago's billing data”
“A Dunning Agent reads a customer's invoice/payment/dispute history to inform collections decisions”
An agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directlyfullproof ↗
“Self-hosted Lago can be run easily via Docker”
“Usage charges can be updated by either engineers via API or non-engineers via a no-code UI”
Do everything through the API that I can do in the UIpartialproof ↗
“Publishes an OpenAPI 3.1 schema for generating clients, inspecting typed operations, or exposing actions to AI agents”
Download a machine-readable API spec (OpenAPI or equivalent)fullproof ↗
Unverified (7)
“CLI has a generated command for every API endpoint”
“Event ingestion deduplicates repeated events so they're billed only once”
Stream high-volume usage events — API calls, tokens, compute-seconds — into a metering pipeline with idempotent ingestion and backdating supportpartialproof ↗
“Invoices can be downloaded or built into custom templates via the invoice object”
The platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automaticallypartialproof ↗
“Webhooks support an HMAC signing option with a shorter header and no payload size limit”
“Billing can be combined with feature flags to reduce engineering overhead on entitlement logic”
Features and limits are modeled as entitlements attached to plans, and my application can check a customer's entitlements at runtime via API or SDKpartialproof ↗
“Overdue, partially paid, or unpaid invoices can be filtered and tracked”
Configure automated dunning sequences — branded emails, in-app banners, grace periods, and final-state rules like cancel vs unpaidpartialproof ↗
“A local sandbox script spins up a disposable organization to test pricing scenarios without touching production”
Test against a sandbox environment without touching production datapartialproof ↗
Contradicted (3)
“Customers can upgrade or downgrade their plan at any time”
My customers can upgrade, downgrade, or cancel themselves through a hosted portal or embeddable components, without a support ticketnoneproof ↗
“Yearly plans bill subscription fees annually while usage charges can be billed monthly or annually”
Control billing anchors and cycles — calendar vs anniversary billing, alignment across a customer's subscriptions, custom invoice datesnoneproof ↗
“Custom per-customer dashboards can be built, filtered, and exported to CSV”
I get MRR, churn, cohort retention, and LTV analytics computed from the billing source of truth, not a bolted-on BI exportnoneproof ↗
Undersold (23)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Explore an interactive API reference with runnable examplespartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
An agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissionspartialproof ↗
Mid-cycle upgrades and downgrades are prorated with documented, auditable math — credits, partial periods, and invoice line items that reconcile to the pennypartialproof ↗
Failed renewal payments are retried automatically on an ML- or schedule-optimized cadence that measurably recovers involuntary churnpartialproof ↗
Change pricing without breaking existing subscribers — versioned plans, grandfathering, and bulk migration tools for moving cohorts to new pricespartialproof ↗
Export every subscription, invoice, and usage record — and port stored payment methods out to another provider — if I choose to leavepartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
Choose where my data is stored (region/residency)partialproof ↗
Create, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboardpartialproof ↗
Every subscription state change — renewal, upgrade, payment failure, cancellation — emits a webhook or event my systems can act on reliablypartialproof ↗
Price with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom codepartialproof ↗
Customers and my team can see current-cycle usage and accrued cost in real time, with thresholds and alerts before an invoice surprises anyonepartialproof ↗
Business model
The AGPLv3 core is free to self-host; Lago Premium (cloud or self-hosted) is quote-only with dunning, tax, and progressive-billing add-ons — no public rate card.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
