{ "data": { "similar": [ { "grade": "A", "json": "https://www.anchorterminal.com/tools/stripe-mcp.json", "name": "Stripe API + MCP", "score": 82.4, "shared": [ "payments.card", "payments.metering" ], "slug": "stripe-mcp" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/nevermined.json", "name": "Nevermined API + MCP", "score": 70.8, "shared": [ "payments.card", "payments.metering" ], "slug": "nevermined" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/orb.json", "name": "Orb", "score": 66.5, "shared": [ "payments.metering", "payments.card" ], "slug": "orb" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/paid.json", "name": "Paid", "score": 55.1, "shared": [ "payments.metering", "payments.card" ], "slug": "paid" }, { "grade": "E", "json": "https://www.anchorterminal.com/tools/atxp.json", "name": "ATXP", "score": 42.9, "shared": [ "payments.metering", "payments.card" ], "slug": "atxp" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/tempo.json", "name": "Tempo", "score": 76.6, "shared": [ "payments.metering" ], "slug": "tempo" } ], "tool": { "slug": "lago", "name": "Lago", "vendor": "Get Lago Corp.", "vendorUrl": "https://getlago.com", "kind": "http-api", "category": "payment-platforms", "summary": "Lago is open-source billing software from Get Lago Corp. for usage metering, subscriptions, prepaid credits and invoicing. It is self-hosted under AGPL-3.0 or bought as Lago Cloud, and driven through a REST API, SDKs, a CLI and an MCP server.", "url": "https://www.anchorterminal.com/tools/lago", "markdownUrl": "https://www.anchorterminal.com/tools/lago.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lago.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lago.json", "repo": "https://github.com/getlago/lago", "license": "AGPL-3.0 (platform). The MCP server and agent SDKs are MIT. Premium capabilities and Lago Cloud are commercial", "transports": [ "http" ], "packages": [ { "registry": "oci", "name": "getlago/lago" }, { "registry": "pypi", "name": "lago-python-client" }, { "registry": "npm", "name": "lago-javascript-client" }, { "registry": "go", "name": "github.com/getlago/lago-go-client" } ], "auth": "api-key", "authNotes": "The REST API takes an organisation API key as a Bearer token. On a self-hosted instance a person signs up in the local UI and copies the key from the Developers section, or the Compose files create the organisation and key from `LAGO_CREATE_ORG` and `LAGO_ORG_API_KEY`. The free edition has one key with full access, which can be rotated. More keys need a Premium licence and per-resource `read`, `write` or `read_write` permissions need an enterprise add-on. No OAuth flow exists.", "pricing": "freemium", "pricingNotes": "The open-source edition is free to self-host under AGPL-3.0, with no card or account. Lago Cloud and Premium self-hosted are sold by custom quote. The pricing summary states a five-figure minimum annual commitment for Cloud and publishes no rate. It also says a Cloud free trial is available, which the docs FAQ contradicts. No sandbox exists, so tests run on a separate instance or organisation (https://getlago.com/pricing.md, checked 2026-10-09).", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402. Lago's llms.txt says direct x402 and general agent-wallet support are not available. Stripe Shared Payment Token collection is a public preview behind a feature flag (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 10665, "npmWeekly": 48093, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://getlago.com/docs/welcome", "llmsTxt": "https://getlago.com/docs/llms.txt", "openapi": "https://swagger.getlago.com/openapi.yaml", "capabilities": [ "payments.metering", "payments.card" ], "tags": [ "open-source", "self-hosted", "agpl", "openapi", "llms-txt", "webhooks", "mcp", "cli", "python", "typescript", "ruby", "go", "docker", "soc2" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 65.7, "grade": "B", "agentReady": false, "rank": 311, "ranked": true, "rankOf": 950, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 91, "payments": 50, "reliability": 86, "schema": 87, "security": 37, "transparency": 59 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 86, "points": 17.2, "reason": "Read with the local-software lines, on the open-source edition an owner runs. Lago Cloud is sold by quote with a five-figure minimum annual commitment, so it is not the surface an agent can start on. Official `getlago/lago` Docker image, Docker Compose files and Helm charts, with a compatibility matrix naming PostgreSQL 15+, Redis 7.x or Valkey 7.2+ and Kubernetes 1.26+ for the latest release (20). Public CI with 2,605 spec files in getlago/lago-api, and the five latest runs of the spec workflow on main, on 8 and 9 October 2026, all passed (25). The main repository has 28 open issues and pull requests against 10,665 stars. About 16 are issues, and several bug reports from 2024 and 2025 carry a stale label with no fix, among them installation, sign-up and CORS problems (17 of 25). Versions follow v1.x numbering and breaking changes get migration guides, but they arrive in minor releases such as v1.50.0, and GitHub release notes are lists of pull requests with no changelog file (9 of 15). Version 1.55.0, past 1.0 (15)." }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 87, "points": 14.14, "reason": "A public OpenAPI 3.1 description in getlago/lago-openapi, version 1.55.0, with 217 operations on 136 paths, 339 schemas and 76 webhook events (25). llms.txt on the site and the docs, a full-text docs export and a Markdown twin of each page (10). Every operation has an operation ID, and 94 of 217 have a description longer than 80 characters. The docs index says when to use the docs and the event pages explain retries, while few operations say when not to use them (13 of 20). The file has 372 enums and 787 required lists, with free-form event `properties` and metadata (13 of 15). About 2,000 examples, and an errors page with named codes. No operation documents a 429 response although the rate-limit page describes one (13 of 15). The path is versioned `/api/v1`, a versioning and deprecation page exists, the description's version follows each release, and the product changelog is dated by month (13 of 15)." }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 71, "points": 11.54, "reason": "Graded on the REST API. List calls take `page` and `per_page`, with a default of 100 in most cases. No field selection or summary view was found (13 of 25). Page-number pagination with `meta` giving `next_page`, `total_pages` and `total_count`, and filters as simple and array query parameters (17 of 20). Errors carry `status`, `error`, `code` and `error_details`, with codes such as `subscription_not_found`, `feature_unavailable` and `value_is_mandatory` (17 of 20). Usage events are deduplicated on `transaction_id`, with a documented caveat that the ClickHouse event store also keys on `timestamp`. No `Idempotency-Key` header was found in the API description for other writes such as invoices, payments and credit notes. The CLI has `--dry-run` and asks before destructive commands. The MCP server sets no readOnlyHint or destructiveHint (10 of 20). Official SDKs for Python, JavaScript, Ruby and Go, each tagged v1.55.0, and a CLI generated from the API description (14 of 15)." }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 37, "points": 6.48, "reason": "Scored on the free self-hosted edition. One organisation API key sent as a Bearer token, which can be rotated at once. Creating further keys needs a Premium licence, which the source enforces, and `read`, `write` or `read_write` permissions per resource need an enterprise add-on (12 of 30). With no scopes in the free edition, least privilege is not available. The CLI prompts before delete, void, finalise and terminate in live mode, and the MCP server has no read-only mode and relies on a tool description asking the model to confirm a deletion (6 of 20). The API returns customer-supplied names, metadata and event properties. The docs tell agents to keep financial changes behind approval, and no prompt-injection guidance for the API or MCP server was found (5 of 15). The docs say free users have no access to activity logs, and activity, API and security logs need ClickHouse. The owner keeps its own server logs (4 of 15). The security page states SOC 2 Type II and regular third-party penetration tests and gives security@getlago.com. security.txt returned 404, neither repository has a security policy file, GitHub lists no published advisories for getlago/lago or getlago/lago-api, no bounty was found and the trust centre could not be read (10 of 20)." }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 50, "points": 6.25, "reason": "Read with the self-hosted rule. No x402, MPP or L402. Lago's own llms.txt says direct x402 and general agent-wallet support are not available, and its Stripe Shared Payment Token support is a public preview behind a feature flag for collecting a merchant's invoices (0). The open-source edition is free. Lago Cloud and Premium have no public price, only a stated five-figure minimum annual commitment and a custom quote, so half marks (10). Free to run with no card (20). An owner can install it without a sales contact, and the Docker Compose files accept `LAGO_CREATE_ORG` and `LAGO_ORG_API_KEY` to create the organisation and key at start-up, as read in the repository (20)." }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 91, "points": 7.96, "reason": "v1.55.0 was tagged on 7 October 2026, two days before the check (30). Six tags fall in the 90 days to 9 October, from v1.51.0 on 27 July (20). The API repository's last 100 commits span 24 September to 9 October 2026. Recent issues in the main repository have three to six comments, while a feature request of 24 September has none and several older bug reports are marked stale (17 of 25). The Python, Ruby and Go SDKs carry a v1.55.0 tag, as does the JavaScript SDK, and the CLI is at v1.0.2 (15). CI is green, Renovate and Dependabot updates are merged, and the MCP server's images are rebuilt on hardened bases as of 6 October (9 of 10)." }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 59, "points": 5.16, "note": "editorial 77, provenance 41", "reason": "The platform is AGPL-3.0, and the MCP server and agent SDKs are MIT. Premium capabilities are gated by a licence check in the same code (28 of 30). Data in a self-hosted instance stays with the owner. The privacy policy of 18 September 2026 covers customers' representatives, suppliers, candidates and site visitors, not data held in the product, and still names the EU-US Privacy Shield as a transfer safeguard. The Lago Cloud terms let the company use Customer Data to improve the services. No public DPA or sub-processor list was found (15 of 30). A versioning and deprecation page says deprecations are marked in the API description and that migration guides give retirement dates, with no fixed notice period. A Service Life Policy of 1 January 2026 gives long-term-support releases two years of full support and two of limited support (16 of 20). Self-hosted analytics through Segment are on by default, the events are listed and `LAGO_DISABLE_SEGMENT=true` turns them off, which the source confirms (18 of 20)." } ], "assessment": { "date": "2026-10-09", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "Graded on the REST API. List calls take `page` and `per_page`, with a default of 100 in most cases. No field selection or summary view was found (13 of 25). Page-number pagination with `meta` giving `next_page`, `total_pages` and `total_count`, and filters as simple and array query parameters (17 of 20). Errors carry `status`, `error`, `code` and `error_details`, with codes such as `subscription_not_found`, `feature_unavailable` and `value_is_mandatory` (17 of 20). Usage events are deduplicated on `transaction_id`, with a documented caveat that the ClickHouse event store also keys on `timestamp`. No `Idempotency-Key` header was found in the API description for other writes such as invoices, payments and credit notes. The CLI has `--dry-run` and asks before destructive commands. The MCP server sets no readOnlyHint or destructiveHint (10 of 20). Official SDKs for Python, JavaScript, Ruby and Go, each tagged v1.55.0, and a CLI generated from the API description (14 of 15).", "maintenance": "v1.55.0 was tagged on 7 October 2026, two days before the check (30). Six tags fall in the 90 days to 9 October, from v1.51.0 on 27 July (20). The API repository's last 100 commits span 24 September to 9 October 2026. Recent issues in the main repository have three to six comments, while a feature request of 24 September has none and several older bug reports are marked stale (17 of 25). The Python, Ruby and Go SDKs carry a v1.55.0 tag, as does the JavaScript SDK, and the CLI is at v1.0.2 (15). CI is green, Renovate and Dependabot updates are merged, and the MCP server's images are rebuilt on hardened bases as of 6 October (9 of 10).", "payments": "Read with the self-hosted rule. No x402, MPP or L402. Lago's own llms.txt says direct x402 and general agent-wallet support are not available, and its Stripe Shared Payment Token support is a public preview behind a feature flag for collecting a merchant's invoices (0). The open-source edition is free. Lago Cloud and Premium have no public price, only a stated five-figure minimum annual commitment and a custom quote, so half marks (10). Free to run with no card (20). An owner can install it without a sales contact, and the Docker Compose files accept `LAGO_CREATE_ORG` and `LAGO_ORG_API_KEY` to create the organisation and key at start-up, as read in the repository (20).", "reliability": "Read with the local-software lines, on the open-source edition an owner runs. Lago Cloud is sold by quote with a five-figure minimum annual commitment, so it is not the surface an agent can start on. Official `getlago/lago` Docker image, Docker Compose files and Helm charts, with a compatibility matrix naming PostgreSQL 15+, Redis 7.x or Valkey 7.2+ and Kubernetes 1.26+ for the latest release (20). Public CI with 2,605 spec files in getlago/lago-api, and the five latest runs of the spec workflow on main, on 8 and 9 October 2026, all passed (25). The main repository has 28 open issues and pull requests against 10,665 stars. About 16 are issues, and several bug reports from 2024 and 2025 carry a stale label with no fix, among them installation, sign-up and CORS problems (17 of 25). Versions follow v1.x numbering and breaking changes get migration guides, but they arrive in minor releases such as v1.50.0, and GitHub release notes are lists of pull requests with no changelog file (9 of 15). Version 1.55.0, past 1.0 (15).", "schema": "A public OpenAPI 3.1 description in getlago/lago-openapi, version 1.55.0, with 217 operations on 136 paths, 339 schemas and 76 webhook events (25). llms.txt on the site and the docs, a full-text docs export and a Markdown twin of each page (10). Every operation has an operation ID, and 94 of 217 have a description longer than 80 characters. The docs index says when to use the docs and the event pages explain retries, while few operations say when not to use them (13 of 20). The file has 372 enums and 787 required lists, with free-form event `properties` and metadata (13 of 15). About 2,000 examples, and an errors page with named codes. No operation documents a 429 response although the rate-limit page describes one (13 of 15). The path is versioned `/api/v1`, a versioning and deprecation page exists, the description's version follows each release, and the product changelog is dated by month (13 of 15).", "security": "Scored on the free self-hosted edition. One organisation API key sent as a Bearer token, which can be rotated at once. Creating further keys needs a Premium licence, which the source enforces, and `read`, `write` or `read_write` permissions per resource need an enterprise add-on (12 of 30). With no scopes in the free edition, least privilege is not available. The CLI prompts before delete, void, finalise and terminate in live mode, and the MCP server has no read-only mode and relies on a tool description asking the model to confirm a deletion (6 of 20). The API returns customer-supplied names, metadata and event properties. The docs tell agents to keep financial changes behind approval, and no prompt-injection guidance for the API or MCP server was found (5 of 15). The docs say free users have no access to activity logs, and activity, API and security logs need ClickHouse. The owner keeps its own server logs (4 of 15). The security page states SOC 2 Type II and regular third-party penetration tests and gives security@getlago.com. security.txt returned 404, neither repository has a security policy file, GitHub lists no published advisories for getlago/lago or getlago/lago-api, no bounty was found and the trust centre could not be read (10 of 20).", "transparency": "The platform is AGPL-3.0, and the MCP server and agent SDKs are MIT. Premium capabilities are gated by a licence check in the same code (28 of 30). Data in a self-hosted instance stays with the owner. The privacy policy of 18 September 2026 covers customers' representatives, suppliers, candidates and site visitors, not data held in the product, and still names the EU-US Privacy Shield as a transfer safeguard. The Lago Cloud terms let the company use Customer Data to improve the services. No public DPA or sub-processor list was found (15 of 30). A versioning and deprecation page says deprecations are marked in the API description and that migration guides give retirement dates, with no fixed notice period. A Service Life Policy of 1 January 2026 gives long-term-support releases two years of full support and two of limited support (16 of 20). Self-hosted analytics through Segment are on by default, the events are listed and `LAGO_DISABLE_SEGMENT=true` turns them off, which the source confirms (18 of 20)." }, "sources": [ { "what": "site index for agents, read as data", "url": "https://getlago.com/llms.txt", "seen": "2026-10-09" }, { "what": "docs index for agents", "url": "https://getlago.com/docs/llms.txt", "seen": "2026-10-09" }, { "what": "full-text docs export, the source for the API standards, errors, pagination, rate limits, versioning, API keys, audit logs, MCP, Docker and tracking pages", "url": "https://getlago.com/docs/llms-full.txt", "seen": "2026-10-09" }, { "what": "pricing summary", "url": "https://getlago.com/pricing.md", "seen": "2026-10-09" }, { "what": "pricing page", "url": "https://getlago.com/pricing", "seen": "2026-10-09" }, { "what": "authentication guide", "url": "https://getlago.com/auth.md", "seen": "2026-10-09" }, { "what": "testing and sandbox guide", "url": "https://getlago.com/sandbox.md", "seen": "2026-10-09" }, { "what": "page for coding agents", "url": "https://getlago.com/for-agents.md", "seen": "2026-10-09" }, { "what": "legal centre", "url": "https://getlago.com/legal", "seen": "2026-10-09" }, { "what": "Lago Cloud Terms and Conditions", "url": "https://getlago.com/legal/lago-cloud-terms", "seen": "2026-10-09" }, { "what": "Lago Self-Hosted Terms and Conditions (Premium plans)", "url": "https://getlago.com/legal/lago-self-hosted-terms", "seen": "2026-10-09" }, { "what": "Service Life Policy", "url": "https://getlago.com/legal/eosl-policy", "seen": "2026-10-09" }, { "what": "privacy policy", "url": "https://getlago.com/legal/privacy-policy", "seen": "2026-10-09" }, { "what": "security page", "url": "https://getlago.com/security", "seen": "2026-10-09" }, { "what": "status page for Lago Cloud", "url": "https://status.getlago.com/", "seen": "2026-10-09" }, { "what": "main repository, tags, licence, Compose files and README", "url": "https://github.com/getlago/lago", "seen": "2026-10-09" }, { "what": "API repository, CI workflows, spec files and telemetry switch", "url": "https://github.com/getlago/lago-api", "seen": "2026-10-09" }, { "what": "OpenAPI 3.1 description, read as the file in the repository", "url": "https://github.com/getlago/lago-openapi", "seen": "2026-10-09" }, { "what": "MCP server source, README and changelog", "url": "https://github.com/getlago/lago-agent-toolkit", "seen": "2026-10-09" }, { "what": "stars and open issue count", "url": "https://api.github.com/repos/getlago/lago", "seen": "2026-10-09" }, { "what": "open issues and pull requests", "url": "https://api.github.com/repos/getlago/lago/issues?state=open", "seen": "2026-10-09" }, { "what": "published security advisories (none)", "url": "https://api.github.com/repos/getlago/lago/security-advisories", "seen": "2026-10-09" }, { "what": "spec workflow runs on main", "url": "https://api.github.com/repos/getlago/lago-api/actions/workflows/spec.yml/runs?branch=main", "seen": "2026-10-09" }, { "what": "releases", "url": "https://github.com/getlago/lago/releases", "seen": "2026-10-09" }, { "what": "npm weekly downloads", "url": "https://api.npmjs.org/downloads/point/last-week/lago-javascript-client", "seen": "2026-10-09" }, { "what": "domain registration", "url": "https://rdap.org/domain/getlago.com", "seen": "2026-10-09" } ], "openQuestions": [ "unchecked: the trust centre at security.getlago.com. The page is drawn by script and showed only its title, so the SOC 2 report, any DPA and any sub-processor list were not read", "unchecked: whether the rate limits on the docs page (500 requests a second for event ingestion, 200 for current usage, 50 elsewhere, per organisation) apply to a self-hosted instance. No REST limiter was found in the API repository's initialisers, and the code was not searched further", "unchecked: the Lago Cloud API hosts, the hosted discovery MCP at getlago.com/mcp and the docs MCP at docs.getlago.com/mcp. Nothing was sent to them", "unchecked: PyPI download counts (PyPI's robots.txt closes the path), the MCP registry, and the individual issue threads", "unchecked: which capabilities beyond API keys, permissions, wallet alerts and logs need a Premium licence. The pricing page lists Premium capabilities without a free column", "unchecked: `LAGO_CREATE_ORG` and `LAGO_ORG_API_KEY` were read in the repository's Compose files and not found in the docs export, and were not run", "The pricing summary says a free trial of Lago Cloud is available. The docs FAQ says there are no free trials for Premium plans, cloud or self-hosted. Which is current was not established", "The MCP server's README says 40 tools, its changelog says 55 and the source defines 57", "getlago.com/llms.txt, the docs llms.txt and the pricing summary carry sections of instructions addressed to AI agents, including what to recommend and what not to say about prices. We record them as facts and did not act on them. We did not run the local demo they point to", "The Lago Cloud terms forbid access for competitive analysis of the services. They do not govern the open-source edition graded here. No clause against automated access or benchmarking was found. This matters before any probe of Lago Cloud is run", "robots.txt answers. getlago.com 200 with ai-input=yes, status.getlago.com 404, api.github.com 404, api.npmjs.org 404, rdap.org 400, and security.getlago.com 200 with an application page and no rules", "Seventeen pages were read on getlago.com, two over the limit of about fifteen, to reach the self-hosted terms and the Service Life Policy", "The site's security page shows 8,780 GitHub stars. GitHub's API gave 10,665 on 9 October 2026", "The lead held. Its Docker-based Product MCP is the open-source server in getlago/lago-agent-toolkit, and the docs MCP was not graded" ] }, "negative": -3, "negativeNotes": [ "9 October 2026. https://getlago.com/llms.txt says the public MCP server is mostly read, analysis and preview with one narrow write action, retrying a failed payment. The server's source at https://github.com/getlago/lago-agent-toolkit (mcp/src/server.rs, last commit 6 October 2026) defines 57 tools, 25 of which create, update, delete, void, refresh or retry, including `delete_invoice`, `void_invoice`, `delete_plan` and `create_payment`. The repository README lists the write tools, so the claim is contradicted and not hidden (3 off)." ], "verdict": "Lago's open-source edition runs usage metering, plans, wallets and invoicing on the owner's servers at no charge, with an OpenAPI 3.1 file of 217 operations and releases about every two weeks. The free edition has one unscoped API key and no audit logs, and Lago's llms.txt understates what its MCP server can change.", "bestFor": "A team that wants usage metering, plans, wallets and invoicing under its own control and can run PostgreSQL and Redis.", "strengths": [ "The whole platform is AGPL-3.0 and installs from the official `getlago/lago` Docker image or Helm charts, with no software fee", "Public OpenAPI 3.1 description with 217 operations, 339 schemas and 76 webhook events, plus llms.txt, a full-text docs export and Markdown twins", "Six tagged releases between 27 July and 7 October 2026, and the five latest test runs on the API's main branch passed on 8 and 9 October", "Usage events are deduplicated on `transaction_id`, so a retried event is billed once when it is resent unchanged", "Self-hosted analytics are listed event by event and switched off with `LAGO_DISABLE_SEGMENT=true`, which the source confirms" ], "weaknesses": [ "The free edition has one organisation API key with full access. Creating more keys needs a Premium licence and per-resource permissions need an enterprise add-on", "Activity logs are closed to free users, and activity, API and security logs also need ClickHouse", "Lago's llms.txt says the MCP server has one write action. Its source defines 57 tools, 25 of which create, update, delete, void or retry, with no read-only mode", "Lago Cloud and Premium have no public price. The pricing summary states a five-figure minimum annual commitment and a custom quote", "The pricing summary says a Lago Cloud free trial is available, and the docs FAQ says Premium plans have no free trial", "No security.txt, repository security policy or published advisory was found, and the privacy policy does not cover data held in the product" ], "agentNotes": [ "Call `\u003cyour Lago API origin\u003e/api/v1` with `Authorization: Bearer \u003ckey\u003e`. On Lago Cloud the hosts are `api.getlago.com` and `api.eu.getlago.com`", "Send every usage event with a deterministic `transaction_id` and an explicit `timestamp`, and resend the same payload on retry. On the ClickHouse event store a changed timestamp is billed again", "Expect 422 `value_already_exist` for a repeated event on the Postgres event store. Treat it as success for a retry", "Page with `page` and `per_page` and read `meta.next_page` and `meta.total_count`. The default page size is 100 in most cases", "Treat the free edition's API key as full access. It can void invoices and terminate subscriptions, so keep it out of prompts and ask a person before financial changes", "Before giving an assistant the MCP server, note that it includes `delete_invoice`, `void_invoice`, `delete_plan` and `create_payment` and sets no read-only annotations" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 65.7 } ], "editorialScores": { "ergonomics": 71, "maintenance": 91, "payments": 50, "reliability": 86, "schema": 87, "security": 37, "transparency": 77 }, "provenanceScore": 41 }, "connect": { "install": "docker run -d --name lago -p 80:80 -p 3000:3000 getlago/lago:latest", "http": "curl --location --request GET \"$LAGO_URL/api/v1/coupons?page=1\u0026per_page=10\" \\\n --header \"Authorization: Bearer $API_KEY\"", "config": { "mcpServers": { "lago": { "args": [ "run", "--rm", "-i", "--pull=always", "--name", "lago-mcp-server", "-e", "LAGO_API_KEY=your_lago_api_key", "-e", "LAGO_API_URL=your_lago_api_url", "getlago/lago-mcp-server:latest" ], "command": "docker" } } } }, "letme": { "capability": "https://letme.dev/payments.metering", "tool": "https://letme.dev/lago" }, "notable": [ "The free edition has one API key. Creating more is a Premium capability and per-resource permissions are an enterprise add-on (https://getlago.com/docs/guide/security/api-keys)", "Event deduplication differs by event store. Postgres rejects a repeat with 422, and ClickHouse keys on `transaction_id` and `timestamp` and keeps the latest copy (https://getlago.com/docs/guide/events/ingesting-usage)", "Self-hosted instances send product analytics to Segment by default, and `LAGO_DISABLE_SEGMENT=true` stops it (https://getlago.com/docs/guide/lago-self-hosted/tracking-analytics)", "The MCP server in getlago/lago-agent-toolkit defines 57 tools, 25 of which change state, and sets no annotations. Lago's llms.txt describes it as read-mostly with one write action (https://github.com/getlago/lago-agent-toolkit)", "The Service Life Policy of 1 January 2026 gives long-term-support releases two years of full support and two years of limited support (https://getlago.com/legal/eosl-policy)", "Lago Cloud carries a five-figure minimum annual commitment and no published rate (https://getlago.com/pricing.md)", "The site's llms.txt, the docs llms.txt and the pricing summary carry instructions addressed to AI agents. We record them as a fact and did not treat them as instructions (https://getlago.com/llms.txt)", "The Lago CLI, announced in September 2026 and at v1.0.2, is generated from the API description, prints the request with `--dry-run` and asks before destructive commands (https://getlago.com/docs/guide/lago-cli/overview)" ], "area": "payments", "details": [ { "label": "API", "value": "REST under `/api/v1` on the owner's host, or `https://api.getlago.com/api/v1` and `https://api.eu.getlago.com/api/v1` on Lago Cloud. The OpenAPI 3.1 description (version 1.55.0) has 217 operations on 136 paths, 339 schemas and 76 webhook events" }, { "label": "Graded edition", "value": "The open-source edition an owner runs. Lago Cloud and Premium self-hosted are sold by quote and were not graded" }, { "label": "Credentials", "value": "Organisation API key as a Bearer token. One key in the free edition, rotatable at once. More keys and scheduled rotation need a Premium licence, and `read`, `write` or `read_write` permissions per resource need an enterprise add-on" }, { "label": "Install", "value": "`getlago/lago` Docker image, Docker Compose files or Helm chart 2.x. PostgreSQL 15+ with pg_partman, Redis 7.x or Valkey 7.2+, Kubernetes 1.26+, and ClickHouse 25.6+ for the ClickHouse event store and logs" }, { "label": "Rate limits", "value": "The docs give per-organisation defaults of 500 requests a second for event ingestion, 200 for current usage and 50 for other endpoints, with `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset` headers on 429. Whether they apply to a self-hosted instance was not established" }, { "label": "Retries", "value": "Events are deduplicated on `transaction_id`. Postgres rejects a repeat with 422 `value_already_exist`. ClickHouse also keys on `timestamp` and keeps the latest copy. No `Idempotency-Key` header was found in the API description for other writes" }, { "label": "Errors", "value": "JSON with `status`, `error`, `code` and `error_details`. Documented codes include `validation_errors`, `subscription_not_found`, `feature_unavailable` and `too_many_provider_requests_error`" }, { "label": "Pagination", "value": "`page` and `per_page`, default 100 in most cases, with `meta` giving `current_page`, `next_page`, `prev_page`, `total_pages` and `total_count`" }, { "label": "SDKs", "value": "Python `lago-python-client`, JavaScript `lago-javascript-client`, Ruby `lago-ruby-client` and Go `lago-go-client`, each with a v1.55.0 tag. The Lago CLI is at v1.0.2 and the Python agent SDK at v0.3.1" }, { "label": "MCP server", "value": "Rust server `lago-mcp-server` 0.2.1 from getlago/lago-agent-toolkit, MIT, run as a Docker image over stdio with `LAGO_API_KEY` and `LAGO_API_URL`. 57 tools in the source, 25 of which change state. No annotations and no read-only mode" }, { "label": "Webhooks", "value": "76 event types. Signed with a JWT by default or HMAC, in `X-Lago-Signature` with `X-Lago-Signature-Algorithm`, and each delivery carries `X-Lago-Unique-Key`" }, { "label": "Payment collection", "value": "Lago is not a payment processor. Invoices are collected through Stripe, Adyen, GoCardless and other processors. Stripe Shared Payment Token collection is a public preview behind a feature flag" }, { "label": "Telemetry", "value": "Product analytics go to Segment by default, with the events listed in the docs and no invoice amounts collected, per Lago. `LAGO_DISABLE_SEGMENT=true` turns them off. The CLI sends no telemetry, per the changelog" }, { "label": "Audit", "value": "Activity logs, API logs and security logs exist for paid tiers and need ClickHouse. Free users have no access to activity logs" }, { "label": "Support life", "value": "Long-term-support releases get two years of full support and two years of limited support under the Service Life Policy of 1 January 2026. Other releases are outside it" } ], "provenance": { "legalEntity": "Get Lago Corp.", "domain": "getlago.com", "domainRegistered": "2020-11-27", "endpointOnVendorDomain": false, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://getlago.com/docs/changelog/product", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The privacy policy and the Lago Cloud terms name Get Lago Corp., 1111B S Governors Ave #7455, Dover, DE 19904, United States, company number 86-3963083.", "No terms link is given because the edition graded is AGPL-3.0 software the owner runs. The Lago Self-Hosted Terms and Conditions (updated 9 March 2024) say they apply to self-hosted Premium plans, and the Lago Cloud terms apply through an order form.", "No privacy link is given. The privacy policy (updated 18 September 2026) covers customers' representatives, suppliers, candidates and site visitors, and does not address data held in a self-hosted instance or the Segment analytics it sends.", "The API answers on the owner's own host. Lago Cloud answers at api.getlago.com and api.eu.getlago.com.", "status.getlago.com, on incident.io, covers the US and EU Lago Cloud clusters only, so no status page is recorded for the graded edition.", "getlago.com/.well-known/security.txt returned 404. The security page gives security@getlago.com.", "RDAP for getlago.com gives a registration date of 2020-11-27 and Gandi SAS as registrar." ], "score": 41, "checks": [ { "check": "Legal entity named", "value": "Get Lago Corp.", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "getlago.com, registered 2020-11-27 (5 years)", "points": 11, "max": 15, "state": "part" }, { "check": "Endpoint on the vendor's domain", "value": " is not on getlago.com", "points": 0, "max": 15, "state": "no" }, { "check": "Terms of service", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Privacy policy", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Status page", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lago.json", "live": { "slug": "lago", "versions": [ { "registry": "github", "name": "getlago/lago", "version": "v1.55.0", "released": "2026-10-07", "seenAt": "2026-10-09T17:01:07.029964093Z" }, { "registry": "npm", "name": "lago-javascript-client", "version": "1.55.0", "seenAt": "2026-10-09T17:01:06.180706665Z" }, { "registry": "pypi", "name": "lago-python-client", "version": "1.55.0", "released": "2026-10-07", "seenAt": "2026-10-09T17:01:05.951391418Z" } ], "githubStars": 10667, "npmWeekly": 48093, "pypiWeekly": 4510, "pages": [ { "url": "https://getlago.com/docs/changelog/product", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:39:49.512530703Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "37091c8d6eb7" }, { "url": "https://getlago.com/pricing.md", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:39:51.811950235Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b4af57318431" } ], "updatedAt": "2026-10-09T18:39:51.811950235Z" } }, "verify": { "accepts": "a page on getlago.com or one of its subdomains, or the README of github.com/getlago/lago", "badgeUrl": "https://www.anchorterminal.com/badges/lago.svg", "body": { "slug": "lago", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/lago", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/lago\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/lago.svg\" alt=\"Lago on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Lago on Anchor Terminal](https://www.anchorterminal.com/badges/lago.svg)](https://www.anchorterminal.com/tools/lago)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/lago\"\u003eLago on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/lago", "json": "https://www.anchorterminal.com/tools/lago.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/lago.md", "slim": "https://www.anchorterminal.com/tools/lago.min.md" }, "markdown": "## Overview\n\n**Grade B · 65.7/100 · rank #311 of 950 · #8 in Payment \u0026 monetisation platforms · not agent-ready · confidence medium**\n\n\n## Assessment\n\nLago's open-source edition runs usage metering, plans, wallets and invoicing on the owner's servers at no charge, with an OpenAPI 3.1 file of 217 operations and releases about every two weeks. The free edition has one unscoped API key and no audit logs, and Lago's llms.txt understates what its MCP server can change.\n\n## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Get Lago Corp. (https://getlago.com) |\n| Kind | HTTP API |\n| Category | Payment \u0026 monetisation platforms (https://www.anchorterminal.com/categories/payment-platforms) |\n| Transport | HTTP |\n| Auth | API key · The REST API takes an organisation API key as a Bearer token. On a self-hosted instance a person signs up in the local UI and copies the key from the Developers section, or the Compose files create the organisation and key from `LAGO_CREATE_ORG` and `LAGO_ORG_API_KEY`. The free edition has one key with full access, which can be rotated. More keys need a Premium licence and per-resource `read`, `write` or `read_write` permissions need an enterprise add-on. No OAuth flow exists. |\n| Pricing | Freemium (Freemium) · The open-source edition is free to self-host under AGPL-3.0, with no card or account. Lago Cloud and Premium self-hosted are sold by custom quote. The pricing summary states a five-figure minimum annual commitment for Cloud and publishes no rate. It also says a Cloud free trial is available, which the docs FAQ contradicts. No sandbox exists, so tests run on a separate instance or organisation (https://getlago.com/pricing.md, checked 2026-10-09). |\n| x402 | No · No x402, MPP or L402. Lago's llms.txt says direct x402 and general agent-wallet support are not available. Stripe Shared Payment Token collection is a public preview behind a feature flag (checked 2026-10-09). |\n| Licence | AGPL-3.0 (platform). The MCP server and agent SDKs are MIT. Premium capabilities and Lago Cloud are commercial |\n| Packages | oci: `getlago/lago`; pypi: `lago-python-client`; npm: `lago-javascript-client`; go: `github.com/getlago/lago-go-client` |\n| Source | https://github.com/getlago/lago |\n| Docs | https://getlago.com/docs/welcome |\n| llms.txt | https://getlago.com/docs/llms.txt |\n| Last release | 2026-10-07 |\n| GitHub stars | 10,665 (as of 2026-10-09) |\n| npm downloads / week | 48,093 |\n| API | REST under `/api/v1` on the owner's host, or `https://api.getlago.com/api/v1` and `https://api.eu.getlago.com/api/v1` on Lago Cloud. The OpenAPI 3.1 description (version 1.55.0) has 217 operations on 136 paths, 339 schemas and 76 webhook events |\n| Graded edition | The open-source edition an owner runs. Lago Cloud and Premium self-hosted are sold by quote and were not graded |\n| Credentials | Organisation API key as a Bearer token. One key in the free edition, rotatable at once. More keys and scheduled rotation need a Premium licence, and `read`, `write` or `read_write` permissions per resource need an enterprise add-on |\n| Install | `getlago/lago` Docker image, Docker Compose files or Helm chart 2.x. PostgreSQL 15+ with pg_partman, Redis 7.x or Valkey 7.2+, Kubernetes 1.26+, and ClickHouse 25.6+ for the ClickHouse event store and logs |\n| Rate limits | The docs give per-organisation defaults of 500 requests a second for event ingestion, 200 for current usage and 50 for other endpoints, with `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset` headers on 429. Whether they apply to a self-hosted instance was not established |\n| Retries | Events are deduplicated on `transaction_id`. Postgres rejects a repeat with 422 `value_already_exist`. ClickHouse also keys on `timestamp` and keeps the latest copy. No `Idempotency-Key` header was found in the API description for other writes |\n| Errors | JSON with `status`, `error`, `code` and `error_details`. Documented codes include `validation_errors`, `subscription_not_found`, `feature_unavailable` and `too_many_provider_requests_error` |\n| Pagination | `page` and `per_page`, default 100 in most cases, with `meta` giving `current_page`, `next_page`, `prev_page`, `total_pages` and `total_count` |\n| SDKs | Python `lago-python-client`, JavaScript `lago-javascript-client`, Ruby `lago-ruby-client` and Go `lago-go-client`, each with a v1.55.0 tag. The Lago CLI is at v1.0.2 and the Python agent SDK at v0.3.1 |\n| MCP server | Rust server `lago-mcp-server` 0.2.1 from getlago/lago-agent-toolkit, MIT, run as a Docker image over stdio with `LAGO_API_KEY` and `LAGO_API_URL`. 57 tools in the source, 25 of which change state. No annotations and no read-only mode |\n| Webhooks | 76 event types. Signed with a JWT by default or HMAC, in `X-Lago-Signature` with `X-Lago-Signature-Algorithm`, and each delivery carries `X-Lago-Unique-Key` |\n| Payment collection | Lago is not a payment processor. Invoices are collected through Stripe, Adyen, GoCardless and other processors. Stripe Shared Payment Token collection is a public preview behind a feature flag |\n| Telemetry | Product analytics go to Segment by default, with the events listed in the docs and no invoice amounts collected, per Lago. `LAGO_DISABLE_SEGMENT=true` turns them off. The CLI sends no telemetry, per the changelog |\n| Audit | Activity logs, API logs and security logs exist for paid tiers and need ClickHouse. Free users have no access to activity logs |\n| Support life | Long-term-support releases get two years of full support and two years of limited support under the Service Life Policy of 1 January 2026. Other releases are outside it |\n| Capabilities | payments.metering, payments.card |\n| Tags | open-source, self-hosted, agpl, openapi, llms-txt, webhooks, mcp, cli, python, typescript, ruby, go, docker, soc2 |\n| JSON | https://www.anchorterminal.com/api/v1/tools/lago.json |\n\n## Score breakdown (methodology v0.4, October 2026 research run)\n\nAssessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 86 | 17.2 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 87 | 14.1 |\n| Agent ergonomics | 13% | 16.2 | 71 | 11.5 |\n| Security \u0026 auth | 14% | 17.5 | 37 | 6.5 |\n| Payments \u0026 pricing | 10% | 12.5 | 50 | 6.2 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 91 | 8.0 |\n| Transparency \u0026 trust (editorial 77, provenance 41) | 7% | 8.8 | 59 | 5.2 |\n| Negative events | up to −15 | up to −15 | 9 October 2026. https://getlago.com/llms.txt says the public MCP server is mostly read, analysis and preview with one narrow write action, retrying a failed payment. The server's source at https://github.com/getlago/lago-agent-toolkit (mcp/src/server.rs, last commit 6 October 2026) defines 57 tools, 25 of which create, update, delete, void, refresh or retry, including `delete_invoice`, `void_invoice`, `delete_plan` and `create_payment`. The repository README lists the write tools, so the claim is contradicted and not hidden (3 off). | -3 |\n| **Total** | | | | **65.7 → B** |\n\n### Why each score\n\n- Reliability 86: Read with the local-software lines, on the open-source edition an owner runs. Lago Cloud is sold by quote with a five-figure minimum annual commitment, so it is not the surface an agent can start on. Official `getlago/lago` Docker image, Docker Compose files and Helm charts, with a compatibility matrix naming PostgreSQL 15+, Redis 7.x or Valkey 7.2+ and Kubernetes 1.26+ for the latest release (20). Public CI with 2,605 spec files in getlago/lago-api, and the five latest runs of the spec workflow on main, on 8 and 9 October 2026, all passed (25). The main repository has 28 open issues and pull requests against 10,665 stars. About 16 are issues, and several bug reports from 2024 and 2025 carry a stale label with no fix, among them installation, sign-up and CORS problems (17 of 25). Versions follow v1.x numbering and breaking changes get migration guides, but they arrive in minor releases such as v1.50.0, and GitHub release notes are lists of pull requests with no changelog file (9 of 15). Version 1.55.0, past 1.0 (15).\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 87: A public OpenAPI 3.1 description in getlago/lago-openapi, version 1.55.0, with 217 operations on 136 paths, 339 schemas and 76 webhook events (25). llms.txt on the site and the docs, a full-text docs export and a Markdown twin of each page (10). Every operation has an operation ID, and 94 of 217 have a description longer than 80 characters. The docs index says when to use the docs and the event pages explain retries, while few operations say when not to use them (13 of 20). The file has 372 enums and 787 required lists, with free-form event `properties` and metadata (13 of 15). About 2,000 examples, and an errors page with named codes. No operation documents a 429 response although the rate-limit page describes one (13 of 15). The path is versioned `/api/v1`, a versioning and deprecation page exists, the description's version follows each release, and the product changelog is dated by month (13 of 15).\n- Agent ergonomics 71: Graded on the REST API. List calls take `page` and `per_page`, with a default of 100 in most cases. No field selection or summary view was found (13 of 25). Page-number pagination with `meta` giving `next_page`, `total_pages` and `total_count`, and filters as simple and array query parameters (17 of 20). Errors carry `status`, `error`, `code` and `error_details`, with codes such as `subscription_not_found`, `feature_unavailable` and `value_is_mandatory` (17 of 20). Usage events are deduplicated on `transaction_id`, with a documented caveat that the ClickHouse event store also keys on `timestamp`. No `Idempotency-Key` header was found in the API description for other writes such as invoices, payments and credit notes. The CLI has `--dry-run` and asks before destructive commands. The MCP server sets no readOnlyHint or destructiveHint (10 of 20). Official SDKs for Python, JavaScript, Ruby and Go, each tagged v1.55.0, and a CLI generated from the API description (14 of 15).\n- Security \u0026 auth 37: Scored on the free self-hosted edition. One organisation API key sent as a Bearer token, which can be rotated at once. Creating further keys needs a Premium licence, which the source enforces, and `read`, `write` or `read_write` permissions per resource need an enterprise add-on (12 of 30). With no scopes in the free edition, least privilege is not available. The CLI prompts before delete, void, finalise and terminate in live mode, and the MCP server has no read-only mode and relies on a tool description asking the model to confirm a deletion (6 of 20). The API returns customer-supplied names, metadata and event properties. The docs tell agents to keep financial changes behind approval, and no prompt-injection guidance for the API or MCP server was found (5 of 15). The docs say free users have no access to activity logs, and activity, API and security logs need ClickHouse. The owner keeps its own server logs (4 of 15). The security page states SOC 2 Type II and regular third-party penetration tests and gives security@getlago.com. security.txt returned 404, neither repository has a security policy file, GitHub lists no published advisories for getlago/lago or getlago/lago-api, no bounty was found and the trust centre could not be read (10 of 20).\n- Payments \u0026 pricing 50: Read with the self-hosted rule. No x402, MPP or L402. Lago's own llms.txt says direct x402 and general agent-wallet support are not available, and its Stripe Shared Payment Token support is a public preview behind a feature flag for collecting a merchant's invoices (0). The open-source edition is free. Lago Cloud and Premium have no public price, only a stated five-figure minimum annual commitment and a custom quote, so half marks (10). Free to run with no card (20). An owner can install it without a sales contact, and the Docker Compose files accept `LAGO_CREATE_ORG` and `LAGO_ORG_API_KEY` to create the organisation and key at start-up, as read in the repository (20).\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 91: v1.55.0 was tagged on 7 October 2026, two days before the check (30). Six tags fall in the 90 days to 9 October, from v1.51.0 on 27 July (20). The API repository's last 100 commits span 24 September to 9 October 2026. Recent issues in the main repository have three to six comments, while a feature request of 24 September has none and several older bug reports are marked stale (17 of 25). The Python, Ruby and Go SDKs carry a v1.55.0 tag, as does the JavaScript SDK, and the CLI is at v1.0.2 (15). CI is green, Renovate and Dependabot updates are merged, and the MCP server's images are rebuilt on hardened bases as of 6 October (9 of 10).\n- Transparency \u0026 trust 59: The platform is AGPL-3.0, and the MCP server and agent SDKs are MIT. Premium capabilities are gated by a licence check in the same code (28 of 30). Data in a self-hosted instance stays with the owner. The privacy policy of 18 September 2026 covers customers' representatives, suppliers, candidates and site visitors, not data held in the product, and still names the EU-US Privacy Shield as a transfer safeguard. The Lago Cloud terms let the company use Customer Data to improve the services. No public DPA or sub-processor list was found (15 of 30). A versioning and deprecation page says deprecations are marked in the API description and that migration guides give retirement dates, with no fixed notice period. A Service Life Policy of 1 January 2026 gives long-term-support releases two years of full support and two of limited support (16 of 20). Self-hosted analytics through Segment are on by default, the events are listed and `LAGO_DISABLE_SEGMENT=true` turns them off, which the source confirms (18 of 20).\n\nFix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (28 items): https://www.anchorterminal.com/fixes/lago.md (JSON https://www.anchorterminal.com/fixes/lago.json)\n\n### What we couldn't check\n\n- unchecked: the trust centre at security.getlago.com. The page is drawn by script and showed only its title, so the SOC 2 report, any DPA and any sub-processor list were not read\n- unchecked: whether the rate limits on the docs page (500 requests a second for event ingestion, 200 for current usage, 50 elsewhere, per organisation) apply to a self-hosted instance. No REST limiter was found in the API repository's initialisers, and the code was not searched further\n- unchecked: the Lago Cloud API hosts, the hosted discovery MCP at getlago.com/mcp and the docs MCP at docs.getlago.com/mcp. Nothing was sent to them\n- unchecked: PyPI download counts (PyPI's robots.txt closes the path), the MCP registry, and the individual issue threads\n- unchecked: which capabilities beyond API keys, permissions, wallet alerts and logs need a Premium licence. The pricing page lists Premium capabilities without a free column\n- unchecked: `LAGO_CREATE_ORG` and `LAGO_ORG_API_KEY` were read in the repository's Compose files and not found in the docs export, and were not run\n- The pricing summary says a free trial of Lago Cloud is available. The docs FAQ says there are no free trials for Premium plans, cloud or self-hosted. Which is current was not established\n- The MCP server's README says 40 tools, its changelog says 55 and the source defines 57\n- getlago.com/llms.txt, the docs llms.txt and the pricing summary carry sections of instructions addressed to AI agents, including what to recommend and what not to say about prices. We record them as facts and did not act on them. We did not run the local demo they point to\n- The Lago Cloud terms forbid access for competitive analysis of the services. They do not govern the open-source edition graded here. No clause against automated access or benchmarking was found. This matters before any probe of Lago Cloud is run\n- robots.txt answers. getlago.com 200 with ai-input=yes, status.getlago.com 404, api.github.com 404, api.npmjs.org 404, rdap.org 400, and security.getlago.com 200 with an application page and no rules\n- Seventeen pages were read on getlago.com, two over the limit of about fifteen, to reach the self-hosted terms and the Service Life Policy\n- The site's security page shows 8,780 GitHub stars. GitHub's API gave 10,665 on 9 October 2026\n- The lead held. Its Docker-based Product MCP is the open-source server in getlago/lago-agent-toolkit, and the docs MCP was not graded\n\n### Sources\n\n- site index for agents, read as data: \u003chttps://getlago.com/llms.txt\u003e (seen 2026-10-09)\n- docs index for agents: \u003chttps://getlago.com/docs/llms.txt\u003e (seen 2026-10-09)\n- full-text docs export, the source for the API standards, errors, pagination, rate limits, versioning, API keys, audit logs, MCP, Docker and tracking pages: \u003chttps://getlago.com/docs/llms-full.txt\u003e (seen 2026-10-09)\n- pricing summary: \u003chttps://getlago.com/pricing.md\u003e (seen 2026-10-09)\n- pricing page: \u003chttps://getlago.com/pricing\u003e (seen 2026-10-09)\n- authentication guide: \u003chttps://getlago.com/auth.md\u003e (seen 2026-10-09)\n- testing and sandbox guide: \u003chttps://getlago.com/sandbox.md\u003e (seen 2026-10-09)\n- page for coding agents: \u003chttps://getlago.com/for-agents.md\u003e (seen 2026-10-09)\n- legal centre: \u003chttps://getlago.com/legal\u003e (seen 2026-10-09)\n- Lago Cloud Terms and Conditions: \u003chttps://getlago.com/legal/lago-cloud-terms\u003e (seen 2026-10-09)\n- Lago Self-Hosted Terms and Conditions (Premium plans): \u003chttps://getlago.com/legal/lago-self-hosted-terms\u003e (seen 2026-10-09)\n- Service Life Policy: \u003chttps://getlago.com/legal/eosl-policy\u003e (seen 2026-10-09)\n- privacy policy: \u003chttps://getlago.com/legal/privacy-policy\u003e (seen 2026-10-09)\n- security page: \u003chttps://getlago.com/security\u003e (seen 2026-10-09)\n- status page for Lago Cloud: \u003chttps://status.getlago.com/\u003e (seen 2026-10-09)\n- main repository, tags, licence, Compose files and README: \u003chttps://github.com/getlago/lago\u003e (seen 2026-10-09)\n- API repository, CI workflows, spec files and telemetry switch: \u003chttps://github.com/getlago/lago-api\u003e (seen 2026-10-09)\n- OpenAPI 3.1 description, read as the file in the repository: \u003chttps://github.com/getlago/lago-openapi\u003e (seen 2026-10-09)\n- MCP server source, README and changelog: \u003chttps://github.com/getlago/lago-agent-toolkit\u003e (seen 2026-10-09)\n- stars and open issue count: \u003chttps://api.github.com/repos/getlago/lago\u003e (seen 2026-10-09)\n- open issues and pull requests: \u003chttps://api.github.com/repos/getlago/lago/issues?state=open\u003e (seen 2026-10-09)\n- published security advisories (none): \u003chttps://api.github.com/repos/getlago/lago/security-advisories\u003e (seen 2026-10-09)\n- spec workflow runs on main: \u003chttps://api.github.com/repos/getlago/lago-api/actions/workflows/spec.yml/runs?branch=main\u003e (seen 2026-10-09)\n- releases: \u003chttps://github.com/getlago/lago/releases\u003e (seen 2026-10-09)\n- npm weekly downloads: \u003chttps://api.npmjs.org/downloads/point/last-week/lago-javascript-client\u003e (seen 2026-10-09)\n- domain registration: \u003chttps://rdap.org/domain/getlago.com\u003e (seen 2026-10-09)\n\n## Who's behind it (provenance 41/100, checked 2026-10-09)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | Get Lago Corp. | 20/20 |\n| Domain age | getlago.com, registered 2020-11-27 (5 years) | 11/15 |\n| Endpoint on the vendor's domain | is not on getlago.com | 0/15 |\n| Terms of service | not found | 0/10 |\n| Privacy policy | not found | 0/10 |\n| Status page | not found | 0/10 |\n| Changelog | published | 10/10 |\n| security.txt | not found | 0/10 |\n\nThe privacy policy and the Lago Cloud terms name Get Lago Corp., 1111B S Governors Ave #7455, Dover, DE 19904, United States, company number 86-3963083.\n\nNo terms link is given because the edition graded is AGPL-3.0 software the owner runs. The Lago Self-Hosted Terms and Conditions (updated 9 March 2024) say they apply to self-hosted Premium plans, and the Lago Cloud terms apply through an order form.\n\nNo privacy link is given. The privacy policy (updated 18 September 2026) covers customers' representatives, suppliers, candidates and site visitors, and does not address data held in a self-hosted instance or the Segment analytics it sends.\n\nThe API answers on the owner's own host. Lago Cloud answers at api.getlago.com and api.eu.getlago.com.\n\nstatus.getlago.com, on incident.io, covers the US and EU Lago Cloud clusters only, so no status page is recorded for the graded edition.\n\ngetlago.com/.well-known/security.txt returned 404. The security page gives security@getlago.com.\n\nRDAP for getlago.com gives a registration date of 2020-11-27 and Gandi SAS as registrar.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service**. We found no terms of service published for this product, so there is nothing to read and the check scores 0.\n\n\n**Privacy policy**. We found no privacy policy published for this product, so there is nothing to read and the check scores 0.\n\n\n## Live (updated 2026-10-09 18:39 UTC)\n\n- github `getlago/lago` v1.55.0, released 2026-10-07\n- npm `lago-javascript-client` 1.55.0\n- pypi `lago-python-client` 1.55.0, released 2026-10-07\n- Watching changelog \u003chttps://getlago.com/docs/changelog/product\u003e\n- Watching pricing \u003chttps://getlago.com/pricing.md\u003e\n- Always current: https://www.anchorterminal.com/api/v1/live/lago.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Strengths\n\n- The whole platform is AGPL-3.0 and installs from the official `getlago/lago` Docker image or Helm charts, with no software fee\n- Public OpenAPI 3.1 description with 217 operations, 339 schemas and 76 webhook events, plus llms.txt, a full-text docs export and Markdown twins\n- Six tagged releases between 27 July and 7 October 2026, and the five latest test runs on the API's main branch passed on 8 and 9 October\n- Usage events are deduplicated on `transaction_id`, so a retried event is billed once when it is resent unchanged\n- Self-hosted analytics are listed event by event and switched off with `LAGO_DISABLE_SEGMENT=true`, which the source confirms\n\n## Weaknesses\n\n- The free edition has one organisation API key with full access. Creating more keys needs a Premium licence and per-resource permissions need an enterprise add-on\n- Activity logs are closed to free users, and activity, API and security logs also need ClickHouse\n- Lago's llms.txt says the MCP server has one write action. Its source defines 57 tools, 25 of which create, update, delete, void or retry, with no read-only mode\n- Lago Cloud and Premium have no public price. The pricing summary states a five-figure minimum annual commitment and a custom quote\n- The pricing summary says a Lago Cloud free trial is available, and the docs FAQ says Premium plans have no free trial\n- No security.txt, repository security policy or published advisory was found, and the privacy policy does not cover data held in the product\n\n## Before you call it (notes for agents)\n\n1. Call `\u003cyour Lago API origin\u003e/api/v1` with `Authorization: Bearer \u003ckey\u003e`. On Lago Cloud the hosts are `api.getlago.com` and `api.eu.getlago.com`\n2. Send every usage event with a deterministic `transaction_id` and an explicit `timestamp`, and resend the same payload on retry. On the ClickHouse event store a changed timestamp is billed again\n3. Expect 422 `value_already_exist` for a repeated event on the Postgres event store. Treat it as success for a retry\n4. Page with `page` and `per_page` and read `meta.next_page` and `meta.total_count`. The default page size is 100 in most cases\n5. Treat the free edition's API key as full access. It can void invoices and terminate subscriptions, so keep it out of prompts and ask a person before financial changes\n6. Before giving an assistant the MCP server, note that it includes `delete_invoice`, `void_invoice`, `delete_plan` and `create_payment` and sets no read-only annotations\n\n## Connect\n\nInstall:\n\n```bash\ndocker run -d --name lago -p 80:80 -p 3000:3000 getlago/lago:latest\n```\n\nFirst request:\n\n```bash\ncurl --location --request GET \"$LAGO_URL/api/v1/coupons?page=1\u0026per_page=10\" \\\n --header \"Authorization: Bearer $API_KEY\"\n```\n\nMCP client configuration:\n\n```json\n{\n \"mcpServers\": {\n \"lago\": {\n \"args\": [\n \"run\",\n \"--rm\",\n \"-i\",\n \"--pull=always\",\n \"--name\",\n \"lago-mcp-server\",\n \"-e\",\n \"LAGO_API_KEY=your_lago_api_key\",\n \"-e\",\n \"LAGO_API_URL=your_lago_api_url\",\n \"getlago/lago-mcp-server:latest\"\n ],\n \"command\": \"docker\"\n }\n }\n}\n```\n\nThrough letme (picks today, calling later): https://letme.dev/lago. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Stripe API + MCP | A | 82.4 | 5 | payments.card, payments.metering | no | https://www.anchorterminal.com/tools/stripe-mcp.md |\n| Nevermined API + MCP | BB | 70.8 | 142 | payments.card, payments.metering | no | https://www.anchorterminal.com/tools/nevermined.md |\n| Orb | B | 66.5 | 289 | payments.metering, payments.card | no | https://www.anchorterminal.com/tools/orb.md |\n| Paid | C | 55.1 | 669 | payments.metering, payments.card | no | https://www.anchorterminal.com/tools/paid.md |\n| ATXP | E | 42.9 | 887 | payments.metering, payments.card | no | https://www.anchorterminal.com/tools/atxp.md |\n| Tempo | BB | 76.6 | 27 | payments.metering | no | https://www.anchorterminal.com/tools/tempo.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- The free edition has one API key. Creating more is a Premium capability and per-resource permissions are an enterprise add-on (source: \u003chttps://getlago.com/docs/guide/security/api-keys\u003e)\n- Event deduplication differs by event store. Postgres rejects a repeat with 422, and ClickHouse keys on `transaction_id` and `timestamp` and keeps the latest copy (source: \u003chttps://getlago.com/docs/guide/events/ingesting-usage\u003e)\n- Self-hosted instances send product analytics to Segment by default, and `LAGO_DISABLE_SEGMENT=true` stops it (source: \u003chttps://getlago.com/docs/guide/lago-self-hosted/tracking-analytics\u003e)\n- The MCP server in getlago/lago-agent-toolkit defines 57 tools, 25 of which change state, and sets no annotations. Lago's llms.txt describes it as read-mostly with one write action (source: \u003chttps://github.com/getlago/lago-agent-toolkit\u003e)\n- The Service Life Policy of 1 January 2026 gives long-term-support releases two years of full support and two years of limited support (source: \u003chttps://getlago.com/legal/eosl-policy\u003e)\n- Lago Cloud carries a five-figure minimum annual commitment and no published rate (source: \u003chttps://getlago.com/pricing.md\u003e)\n- The site's llms.txt, the docs llms.txt and the pricing summary carry instructions addressed to AI agents. We record them as a fact and did not treat them as instructions (source: \u003chttps://getlago.com/llms.txt\u003e)\n- The Lago CLI, announced in September 2026 and at v1.0.2, is generated from the API description, prints the request with `--dry-run` and asks before destructive commands (source: \u003chttps://getlago.com/docs/guide/lago-cli/overview\u003e)\n\n- #8 of 14 in Best payment and monetisation platforms for AI agents: https://www.anchorterminal.com/best/payment-platforms/index.md\n- All 76 platforms comparisons: https://www.anchorterminal.com/compare/payment-platforms/index.md\n\n## Compare\n\n- [ATXP vs Lago](https://www.anchorterminal.com/compare/atxp-vs-lago.md): E 42.9 vs B 65.7\n- [Lago vs Metronome](https://www.anchorterminal.com/compare/lago-vs-metronome.md): B 65.7 vs B 69.7\n- [Lago vs Nevermined API + MCP](https://www.anchorterminal.com/compare/lago-vs-nevermined.md): B 65.7 vs BB 70.8\n- [Lago vs Orb](https://www.anchorterminal.com/compare/lago-vs-orb.md): B 65.7 vs B 66.5\n- [Lago vs Paid](https://www.anchorterminal.com/compare/lago-vs-paid.md): B 65.7 vs C 55.1\n- [Lago vs Stripe API + MCP](https://www.anchorterminal.com/compare/lago-vs-stripe-mcp.md): B 65.7 vs A 82.4\n- [Lago vs Tempo](https://www.anchorterminal.com/compare/lago-vs-tempo.md): B 65.7 vs BB 76.6\n- [Adyen MCP server vs Lago](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-lago.md): C 60.3 vs B 65.7\n- [Crossmint API + Docs MCP vs Lago](https://www.anchorterminal.com/compare/crossmint-vs-lago.md): B 67.1 vs B 65.7\n- [Lago vs Payman Genie MCP](https://www.anchorterminal.com/compare/lago-vs-payman.md): B 65.7 vs D 52.5\n- [Lago vs Skyfire API + MCP](https://www.anchorterminal.com/compare/lago-vs-skyfire.md): B 65.7 vs E 40.3\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on getlago.com or one of its subdomains, or the README of github.com/getlago/lago. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"lago\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/lago\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/lago.svg\" alt=\"Lago on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Lago on Anchor Terminal](https://www.anchorterminal.com/badges/lago.svg)](https://www.anchorterminal.com/tools/lago)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/lago\"\u003eLago on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Lago is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/lago-dark.png\n- Light: https://www.anchorterminal.com/assets/share/lago-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Payment \u0026 monetisation platforms", "url": "https://www.anchorterminal.com/categories/payment-platforms" }, { "name": "Lago", "url": "" } ], "description": "Lago is open-source billing software from Get Lago Corp. for usage metering, subscriptions, prepaid credits and invoicing. It is self-hosted under AGPL-3.0 or bought as Lago Cloud, and driven through a REST API, SDKs, a CLI and an MCP server.", "facts": [ "rank #311 of 950", "API key auth", "0 desk reviews" ], "h1": "Lago", "image": "https://www.anchorterminal.com/assets/og/tools-lago.png", "path": "/tools/lago", "published": "2026-10-01", "section": "tools", "title": "Lago review (2026): pricing, alternatives and grade B", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/tools/lago" }, "tokens": { "markdown": 8150, "slim": 2030 }, "version": 1 }