$HEADLESS SYSTEMS
03 / Scorecard / Payments

Lago

F
Headless Index
25/100
denominator 60
JAIRF
92.5/100
Agent-Optimized
Verified
AUG 20, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Lago earns Band F in the Payments category of The Headless Index, with a thesis-fit score of 25/100 and a JAIRF rating of 92.5/100 (Agent-Optimized). Its strongest dimension is API-first design intent (10/20); its weakest scored dimension is MCP and agent posture (0/20). Lago publishes a machine-readable OpenAPI specification, which is what lets an agent discover and operate it without human glue code.

Editorial verdict
Lago is not built for machine consumption today. The Headless Index thesis-fit score of 25/100 fails the floor checks of the index, and JAIRF v1.0.0 puts it at 92.5/100 (Level 4, Agent-Optimized). In practice, vendors at this tier are not built for machine consumption today: agents can poke at them, but the dashboard remains the source of truth, and the rest of this verdict explains where Lago lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Lago is open-source usage-based billing positioned as the open alternative to Orb and Metronome. The REST API exposes customers, billable metrics, plans, subscriptions, invoices, credit notes, coupons, add-ons, and analytics. SDKs in Node, Python, Ruby, Java, Go, and PHP. Published OpenAPI specification at github.com/getlago/lago-openapi.[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? Public OpenAPI in the lago-openapi repository. Schema discoverability is reference-class for open-source billing.[2] Driving this product through an agent is not realistic with the current surface: the API exists, but it is not the contract the vendor optimises for. On headless operability: On headless operability, the docs crawl did not produce topic coverage sufficient to score programmatic setup, billing, teams, schema, or CLI workflows. A targeted AI review pass should visit the vendor's docs index and confirm what programmatic surfaces actually exist.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party Lago MCP server. The open-source positioning makes MCP integration straightforward; community work is in early stages.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. On webhooks and events, the docs crawler did not locate a webhooks reference page or events catalog. Editorial review should confirm whether the vendor publishes events at all, and if so whether signing and replay are documented. Net assessment: Lago fails the floor checks of the methodology, with MCP posture[5] as the most acute gap. Any agent integration here will be brittle and short-lived until the vendor invests in machine-readable surfaces. Not currently suitable for agent consumption.
Verdict by Headless Index pipeline (auto)
// AI-drafted from the evidence layer. Editorial review pending.
Scores

Scorecard detail

Headless Index · 5 sub-criteria
API-first design intent10/20
scored

Lago is open-source usage-based billing positioned as the open alternative to Orb and Metronome. The REST API exposes customers, billable metrics, plans, subscriptions, invoices, credit notes, coupons, add-ons, and analytics. SDKs in Node, Python, Ruby, Java, Go, and PHP. Published OpenAPI specification at github.com/getlago/lago-openapi.

signals (5)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPI specPublished, 0 operations
  • −GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
  • +SDKs maintained9 (go, javascript, php, python, ruby, rust); top by stars: getlago/lago-api (423 stars)
  • +npm weekly downloads35.3k across published packages; top: lago-javascript-client @ 35.3k/week
cite (5)
  • openapi.probes_tried@2026-05-20
  • graphql.probes_tried@2026-05-20
  • github.sdks@2026-05-20
  • freshness.most_recent_sdk_commit@2026-05-20
  • github.sdks@2026-05-20
Headless operationUnknown
Unknown

Customers, plans, subscriptions, invoices, billable metrics, credit notes, and coupons are all programmable. The lago CLI is in development. Self-host (Docker, Helm) plus Lago Cloud share the API. Open-source under getlago/lago.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −API operations exposedOpenAPI present but operations could not be counted
  • ·Docs pages crawled0 pages (crawler: none)
  • ·Auth schemes documentedAuth documentation page not reached by crawler
  • ·Setup / quickstart docsNot reached by crawler
  • ·Billing docsNot reached by crawler
  • ·Teams / org docsNot reached by crawler
  • ·CLI docsNot reached by crawler
  • ·Schema / data model docsNot reached by crawler
cite (8)
  • openapi.operations_count@2026-05-20
  • docs.pages_crawled@2026-05-20
  • docs.pages_crawled@2026-05-20
  • docs.topics_found.setup@2026-05-20
  • docs.topics_found.billing@2026-05-20
  • docs.topics_found.teams@2026-05-20
  • docs.topics_found.cli@2026-05-20
  • docs.topics_found.schema@2026-05-20
MCP & agent posture0/20
scored

No first-party Lago MCP server. The open-source positioning makes MCP integration straightforward; community work is in early stages.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −Official MCP serverNone found in vendor's GitHub org or the official MCP registry
  • −Community MCP serversNone found
  • +Agent-friendly SDKs2 TS/JS SDKs available; top: lago-javascript-client (35.3k/week downloads)
cite (3)
  • mcp.registry_query@2026-05-20
  • mcp.github_search_query@2026-05-20
  • github.sdks@2026-05-20
Schema observability5/20
scored

Public OpenAPI in the lago-openapi repository. Schema discoverability is reference-class for open-source billing.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPIPublished at https://raw.githubusercontent.com/getlago/lago-openapi/main/openapi.yaml (OpenAPI undefined, 0 operations)
  • −GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)
cite (2)
  • openapi.probes_tried@2026-05-20
  • graphql.probes_tried@2026-05-20
Webhooks & eventsUnknown
Unknown

Lago webhooks deliver invoice, subscription, and credit events with HMAC signing. Catalog is appropriate for the usage-based-billing lifecycle and pairs naturally with downstream finance automation.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • docs.pages_crawled@2026-05-20
JAIRF · 6 dimensions
FCFoundational Compliance
100/100

Structural validity, standards conformance, and parsability of the OpenAPI specification.

DXJDeveloper Experience & Tooling Compatibility
74.2/100

Documentation clarity, example coverage, response completeness, and ingestion health.

ARAXAI-Readiness & Agent Experience
96.7/100

Semantic clarity, intent expression, datatype specificity, and error standardization.

AUAgent Usability
100/100

Operational composability, complexity comfort, navigation affordances, and safety patterns.

SECSecurity
80/100

Authentication strength, transport security, secret hygiene, and OWASP risk posture.

AIDAI Discoverability
100/100

Descriptive richness, intent phrasing, workflow context, and registry signals.

Band rationale:F band triggered: HeadlessIndex=25

04 / Embed

Show Lago's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Lago mini badge preview
Get embed code
Peers in Payments
UnitF
Headless Index 25/100
TrueLayerF
Headless Index 25/100
Treasury PrimeF
Headless Index 25/100
See full Payments ranking →
FAQ

Lago and agent readiness

Is Lago agent-ready?
Lago scores Band F on The Headless Index and rates Agent-Optimized on JAIRF (92.5/100). Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.
Does Lago publish an OpenAPI spec?
Yes. Lago publishes an OpenAPI specification, scored under JAIRF v1.0.0. A published spec is what makes an API discoverable and callable by agents rather than only by developers reading docs.
What is Lago's Headless Index score?
Lago scores 25/100 on the Headless Index thesis-fit rubric and sits in Band F in the Payments category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.