{ "data": { "a": { "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" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "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" }, "area": "payments", "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 }, "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" } }, "answer": "Stripe API + MCP scores 82.4 (A) on agent readiness against Lago's 65.7 (B), and leads in 5 of 7 scored categories. Lago leads on reliability and maintenance \u0026 community.", "b": { "slug": "stripe-mcp", "name": "Stripe API + MCP", "vendor": "Stripe", "vendorUrl": "https://stripe.com", "kind": "http-api", "category": "payment-platforms", "summary": "Card, stablecoin and billing APIs with a hosted MCP server (mcp.stripe.com, 10 tools including generic stripe_api_read and stripe_api_write).", "url": "https://www.anchorterminal.com/tools/stripe-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/stripe-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/stripe-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/stripe-mcp.json", "repo": "https://github.com/stripe/ai", "license": "MIT", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.stripe.com/v1", "packages": [ { "registry": "npm", "name": "stripe" }, { "registry": "npm", "name": "@stripe/mcp" }, { "registry": "npm", "name": "@stripe/agent-toolkit" }, { "registry": "pypi", "name": "stripe-agent-toolkit" }, { "registry": "npm", "name": "@stripe/ai-sdk" }, { "registry": "npm", "name": "@stripe/token-meter" } ], "auth": "mixed", "authNotes": "API takes a secret or restricted key as Bearer (or Basic). MCP takes OAuth for interactive clients (per-account and sandbox permissions, revocable sessions) or an Agent API key as Bearer for autonomous clients. Stripe-Account header for Connect platforms. From 2026-10-31 the MCP server rejects full-access secret keys and non-Agent restricted keys with a 401 OAuth challenge.", "pricing": "usage", "pricingNotes": "No charge for the MCP server or the toolkit, and no setup or monthly fees. US cards 2.9% + 30 cents per successful charge. Stablecoin payments 1.5% (including conversion, screening and gas sponsorship). Billing 0.7% of billing volume, or from $620 a month on a one-year contract. Shared payment tokens for agent card payments cost $0.15 per token issued. Stablecoin acceptance is open to US businesses outside New York and by request in 30+ countries (https://stripe.com/pricing).", "priceSummary": "2.9% fee", "where": "both", "x402": { "level": "partial", "evidence": "Stripe merchants can accept x402 payments in USDC on Base and have them recorded as PaymentIntents. The MCP server and the Stripe API themselves don't take x402 payment (https://docs.stripe.com/payments/machine/x402).", "endpoints": [] }, "toolCount": 10, "popularity": { "githubStars": 1848, "npmWeekly": 15284, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.stripe.com/agents", "llmsTxt": "https://docs.stripe.com/llms.txt", "openapi": "https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.json", "registryName": "com.stripe/mcp", "capabilities": [ "payments.card", "payments.stablecoin", "payments.x402", "payments.metering", "payments.checkout", "payments.payouts" ], "tags": [ "official", "hosted", "local", "open-source", "oauth", "confirmation", "mcp", "llms-txt", "openapi", "stablecoin", "x402", "webhooks", "typescript", "python" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 82.4, "grade": "A", "agentReady": true, "rank": 5, "ranked": true, "rankOf": 950, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 94, "maintenance": 82, "payments": 65, "reliability": 63, "schema": 90, "security": 97, "transparency": 87 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-10-04" }, "negative": 0, "verdict": "One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat. Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins.", "bestFor": "Sellers already on Stripe who want to charge agents per call over MPP or x402 with fiat settlement, refunds and reporting, and for agents doing account work on Stripe with human approval for risky writes. nevermined suits sellers who want plans, credits and buyer-side caps; tempo is the chain MPP stablecoin payments settle on.", "strengths": [ "One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat", "OAuth with per-account and per-environment permissions, Agent-tagged restricted keys, and revocable sessions", "Human approval for sensitive `stripe_api_write` actions such as refunds and outbound payments", "Rate limits, 429 reasons, backoff guidance and idempotency keys all documented", "Public OpenAPI spec, dated API versions and a HackerOne bug bounty" ], "weaknesses": [ "Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins", "Stablecoin acceptance needs manual approval, excludes New York and is by email request outside the US", "Generic `stripe_api_read` and `stripe_api_write` tools push method choice and parameters onto the agent", "The official MCP registry entry is 0.2.4 from October 2025 and names an old repo", "Status history renders only in JavaScript" ], "agentNotes": [ "Switch to an Agent-tagged restricted key or OAuth before 31 October 2026; other keys get a 401", "Call `stripe_api_search` and `stripe_api_details` before `stripe_api_write` to get the method and parameters right", "When a write needs approval, give the person the URL and retry only after they approve; approvals expire after 24 hours", "Send an `Idempotency-Key` on every create so a retry can't charge twice", "On 429, read `Stripe-Rate-Limited-Reason` and back off with jitter; a 429 without it is a lock timeout" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 8, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "A", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 82.4 } ], "editorialScores": { "ergonomics": 94, "maintenance": 82, "payments": 65, "reliability": 63, "schema": 90, "security": 97, "transparency": 78 }, "provenanceScore": 95 }, "connect": { "http": "curl https://api.stripe.com/v1/balance -H \"Authorization: Bearer $STRIPE_SECRET_KEY\"", "claudeCode": "claude mcp add --transport http stripe https://mcp.stripe.com", "config": { "mcpServers": { "stripe": { "headers": { "Authorization": "Bearer ${STRIPE_AGENT_KEY}" }, "url": "https://mcp.stripe.com" } } } }, "letme": { "capability": "https://letme.dev/payments.card", "tool": "https://letme.dev/stripe-mcp" }, "area": "payments", "unitPrices": [ { "item": "US card payment", "unit": "pct", "usd": 2.9, "note": "plus 30 cents per successful charge" }, { "item": "US card payment fixed fee", "unit": "tx", "usd": 0.3 }, { "item": "Stablecoin payment", "unit": "pct", "usd": 1.5 }, { "item": "Billing", "unit": "pct", "usd": 0.7, "note": "of billing volume" } ], "provenance": { "legalEntity": "Stripe, LLC", "domain": "stripe.com", "domainRegistered": "1995-09-12", "domainNote": "stripe.com was registered in 1995, before Stripe bought it.", "endpointOnVendorDomain": true, "terms": "https://stripe.com/legal/ssa", "privacy": "https://stripe.com/privacy", "statusPage": "https://status.stripe.com", "changelog": "https://docs.stripe.com/changelog", "securityTxt": "valid", "checked": "2026-09-30", "score": 95 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/stripe-mcp.json", "live": { "slug": "stripe-mcp", "probe": { "target": "https://api.stripe.com/v1", "method": "get", "lastAt": "2026-10-10T03:53:45.616747435Z", "lastOk": true, "lastStatus": 404, "lastMs": 59, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 56, "p95ms24h": 124, "samples24h": 249, "samples30d": 3430, "days": [ { "date": "2026-09-27", "probes": 132, "ok": 132 }, { "date": "2026-09-28", "probes": 285, "ok": 285 }, { "date": "2026-09-29", "probes": 286, "ok": 286 }, { "date": "2026-09-30", "probes": 286, "ok": 286 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.stripe.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:51:18.159348435Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.stripe/mcp", "version": "0.2.4", "seenAt": "2026-10-10T03:11:32.438759038Z" }, { "registry": "npm", "name": "@stripe/agent-toolkit", "version": "0.9.0", "seenAt": "2026-10-09T17:22:23.136555078Z" }, { "registry": "npm", "name": "@stripe/ai-sdk", "version": "0.1.3", "seenAt": "2026-10-09T17:22:25.502513825Z" }, { "registry": "npm", "name": "@stripe/mcp", "version": "0.3.3", "seenAt": "2026-10-09T17:22:21.151998994Z" }, { "registry": "npm", "name": "@stripe/token-meter", "version": "0.1.0", "seenAt": "2026-10-09T17:22:27.344205843Z" }, { "registry": "npm", "name": "stripe", "version": "23.0.0", "seenAt": "2026-10-09T17:22:20.89644214Z" }, { "registry": "pypi", "name": "stripe-agent-toolkit", "version": "0.7.0", "released": "2026-02-12", "seenAt": "2026-10-09T17:22:25.305272702Z" } ], "githubStars": 1866, "npmWeekly": 23282402, "pypiWeekly": 2172, "securityTxt": { "url": "https://stripe.com/.well-known/security.txt", "state": "valid", "expires": "2026-12-31T23:59:00.000Z", "checkedAt": "2026-10-09T15:40:09.920948203Z" }, "llmsTxt": { "url": "https://docs.stripe.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:51.241783072Z" }, "domain": { "domain": "stripe.com", "registered": "1995-09-12", "source": "https://rdap.verisign.com/com/v1/domain/stripe.com", "checkedAt": "2026-10-04T13:06:58.944197161Z" }, "pages": [ { "url": "https://docs.stripe.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:38:24.633373695Z", "changedAt": "2026-10-07T18:05:30.851845677Z", "fingerprint": "1accebcd47a8" }, { "url": "https://docs.stripe.com/mcp", "kind": "deprecations", "status": 200, "checkedAt": "2026-10-09T18:38:28.452313533Z", "changedAt": "2026-10-08T18:19:33.638425552Z", "fingerprint": "73c755c5cd0f" }, { "url": "https://stripe.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:24:56.248781585Z", "changedAt": "2026-10-08T18:24:56.248781585Z", "fingerprint": "73ea5b705ed5" }, { "url": "https://stripe.com/legal/ssa", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:24:51.983854093Z", "changedAt": "2026-10-08T18:24:51.983854093Z", "fingerprint": "43483f64e8ca" } ], "mcpTools": { "url": "https://mcp.stripe.com", "checkedAt": "2026-09-29T21:56:38.06237447Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-09-28T21:55:54.756223507Z" }, "updatedAt": "2026-10-10T03:53:45.616747435Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Get Lago Corp.", "b": "Stripe", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.stripe.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "payer tooling only", "name": "x402" }, { "a": "AGPL-3.0 (platform). The MCP server and agent SDKs are MIT. Premium capabilities and Lago Cloud are commercial", "b": "MIT", "name": "Licence" }, { "a": "none", "b": "10", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "com.stripe/mcp", "name": "MCP registry" }, { "a": "2026-10-07", "b": "2026-09-30", "name": "Last release" }, { "a": "no document linked", "b": "2026-09-28", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-04-28", "name": "Privacy policy last updated" }, { "a": "", "b": "yes", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "11k stars, 48k npm/wk", "b": "1.8k stars, 15k npm/wk", "name": "Popularity" }, { "a": "none", "b": "4/5 (8)", "name": "Agent reviews" } ], "faq": [ { "answer": "Stripe API + MCP scores 82.4 (A) on agent readiness against Lago's 65.7 (B), and leads in 5 of 7 scored categories. Lago leads on reliability and maintenance \u0026 community.", "question": "Which is better for AI agents, Lago or Stripe API + MCP?" }, { "answer": "Lago needs an API key. Stripe API + MCP takes an API key or an OAuth sign-in.", "question": "Do Lago and Stripe API + MCP need an API key?" }, { "answer": "No hosted endpoint is listed for Lago. Stripe API + MCP has a hosted endpoint at https://api.stripe.com/v1.", "question": "Can an agent call Lago and Stripe API + MCP without installing anything?" }, { "answer": "Yes. Lago is open source (AGPL-3.0 (platform). The MCP server and agent SDKs are MIT. Premium capabilities and Lago Cloud are commercial). Stripe API + MCP is open source (MIT).", "question": "Are Lago and Stripe API + MCP open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 86 against 63", "Maintenance \u0026 community, 91 against 82" ], "also": null, "goodFor": "A team that wants usage metering, plans, wallets and invoicing under its own control and can run PostgreSQL and Redis.", "slug": "lago", "watchFor": "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" }, { "aheadOn": [ "Agent ergonomics, 94 against 71", "Security \u0026 auth, 97 against 37", "Payments \u0026 pricing, 65 against 50", "Transparency \u0026 trust, 87 against 59" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install", "Runs on your own machine", "No incidents deducted, where Lago loses 3 points for them" ], "goodFor": "Sellers already on Stripe who want to charge agents per call over MPP or x402 with fiat settlement, refunds and reporting, and for agents doing account work on Stripe with human approval for risky writes. nevermined suits sellers who want plans, credits and buyer-side caps; tempo is the chain MPP stablecoin payments settle on.", "slug": "stripe-mcp", "watchFor": "Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins" } ], "job": { "capability": "payments.metering", "name": "Usage billing" }, "others": [ { "json": "https://www.anchorterminal.com/compare/atxp-vs-lago.json", "title": "ATXP vs Lago", "url": "https://www.anchorterminal.com/compare/atxp-vs-lago" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-metronome.json", "title": "Lago vs Metronome", "url": "https://www.anchorterminal.com/compare/lago-vs-metronome" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-nevermined.json", "title": "Lago vs Nevermined API + MCP", "url": "https://www.anchorterminal.com/compare/lago-vs-nevermined" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-orb.json", "title": "Lago vs Orb", "url": "https://www.anchorterminal.com/compare/lago-vs-orb" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-paid.json", "title": "Lago vs Paid", "url": "https://www.anchorterminal.com/compare/lago-vs-paid" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-tempo.json", "title": "Lago vs Tempo", "url": "https://www.anchorterminal.com/compare/lago-vs-tempo" }, { "json": "https://www.anchorterminal.com/compare/metronome-vs-stripe-mcp.json", "title": "Metronome vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/metronome-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/orb-vs-stripe-mcp.json", "title": "Orb vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/orb-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/paid-vs-stripe-mcp.json", "title": "Paid vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/paid-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-lago.json", "title": "Adyen MCP server vs Lago", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-lago" }, { "json": "https://www.anchorterminal.com/compare/agentcard-vs-stripe-mcp.json", "title": "Agentcard vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/agentcard-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/crossmint-vs-lago.json", "title": "Crossmint API + Docs MCP vs Lago", "url": "https://www.anchorterminal.com/compare/crossmint-vs-lago" }, { "json": "https://www.anchorterminal.com/compare/crossmint-vs-stripe-mcp.json", "title": "Crossmint API + Docs MCP vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/crossmint-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-payman.json", "title": "Lago vs Payman Genie MCP", "url": "https://www.anchorterminal.com/compare/lago-vs-payman" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-skyfire.json", "title": "Lago vs Skyfire API + MCP", "url": "https://www.anchorterminal.com/compare/lago-vs-skyfire" }, { "json": "https://www.anchorterminal.com/compare/atxp-vs-stripe-mcp.json", "title": "ATXP vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/atxp-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/skyfire-vs-stripe-mcp.json", "title": "Skyfire API + MCP vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/skyfire-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo.json", "title": "Stripe API + MCP vs Tempo", "url": "https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo" }, { "json": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp.json", "title": "Adyen MCP server vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/paypal-mcp-server-vs-stripe-mcp.json", "title": "PayPal MCP server vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/paypal-mcp-server-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-stripe-mcp.json", "title": "Circle Gateway Nanopayments vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/nevermined-vs-stripe-mcp.json", "title": "Nevermined API + MCP vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/nevermined-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/payman-vs-stripe-mcp.json", "title": "Payman Genie MCP vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/payman-vs-stripe-mcp" } ], "scores": [ { "by": 23, "edge": "lago", "key": "reliability", "lago": 86, "name": "Reliability", "stripe-mcp": 63, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 3, "edge": "stripe-mcp", "key": "schema", "lago": 87, "name": "Schema \u0026 documentation", "stripe-mcp": 90, "weight": 13 }, { "by": 23, "edge": "stripe-mcp", "key": "ergonomics", "lago": 71, "name": "Agent ergonomics", "stripe-mcp": 94, "weight": 13 }, { "by": 60, "edge": "stripe-mcp", "key": "security", "lago": 37, "name": "Security \u0026 auth", "stripe-mcp": 97, "weight": 14 }, { "by": 15, "edge": "stripe-mcp", "key": "payments", "lago": 50, "name": "Payments \u0026 pricing", "stripe-mcp": 65, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 9, "edge": "lago", "key": "maintenance", "lago": 91, "name": "Maintenance \u0026 community", "stripe-mcp": 82, "weight": 7 }, { "by": 28, "edge": "stripe-mcp", "key": "transparency", "lago": 59, "name": "Transparency \u0026 trust", "stripe-mcp": 87, "weight": 7 } ], "summary": "Stripe API + MCP scores 82.4 (A) on agent readiness against Lago's 65.7 (B), and leads in 5 of 7 scored categories. Lago leads on reliability and maintenance \u0026 community. Both do usage billing.", "verdicts": { "lago": "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.", "stripe-mcp": "One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat. Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/lago-vs-stripe-mcp", "json": "https://www.anchorterminal.com/compare/lago-vs-stripe-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/lago-vs-stripe-mcp.md", "slim": "https://www.anchorterminal.com/compare/lago-vs-stripe-mcp.min.md" }, "markdown": "Stripe API + MCP scores 82.4 (A) on agent readiness against Lago's 65.7 (B), and leads in 5 of 7 scored categories. Lago leads on reliability and maintenance \u0026 community. Both do usage billing.\n\n- Lago: grade B, 65.7/100, rank #311 of 950. Markdown https://www.anchorterminal.com/tools/lago.md · JSON https://www.anchorterminal.com/api/v1/tools/lago.json\n- Stripe API + MCP: grade A, 82.4/100, rank #5 of 950. Markdown https://www.anchorterminal.com/tools/stripe-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/stripe-mcp.json\n- 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## Which one, for what\n\n### Lago (B)\n\nGood for: A team that wants usage metering, plans, wallets and invoicing under its own control and can run PostgreSQL and Redis.\n\nAhead on:\n- Reliability, 86 against 63\n- Maintenance \u0026 community, 91 against 82\n\nWatch for: 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\n### Stripe API + MCP (A)\n\nGood for: Sellers already on Stripe who want to charge agents per call over MPP or x402 with fiat settlement, refunds and reporting, and for agents doing account work on Stripe with human approval for risky writes. nevermined suits sellers who want plans, credits and buyer-side caps; tempo is the chain MPP stablecoin payments settle on.\n\nAhead on:\n- Agent ergonomics, 94 against 71\n- Security \u0026 auth, 97 against 37\n- Payments \u0026 pricing, 65 against 50\n- Transparency \u0026 trust, 87 against 59\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n- No incidents deducted, where Lago loses 3 points for them\n\nWatch for: Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins\n\n\n## Score by category\n\n| Category | Weight | Lago | Stripe API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 86 | 63 | Lago +23 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 90 | Stripe API + MCP +3 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 94 | Stripe API + MCP +23 |\n| Security \u0026 auth | 14% (17.5 this run) | 37 | 97 | Stripe API + MCP +60 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 65 | Stripe API + MCP +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 91 | 82 | Lago +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 59 | 87 | Stripe API + MCP +28 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **65.7 · B** | **82.4 · A** | |\n\n## Facts side by side\n\n| Fact | Lago | Stripe API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Get Lago Corp. | Stripe |\n| Hosted endpoint | no (local only) | `https://api.stripe.com/v1` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | payer tooling only |\n| Licence | AGPL-3.0 (platform). The MCP server and agent SDKs are MIT. Premium capabilities and Lago Cloud are commercial | MIT |\n| Tools exposed | none | 10 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `com.stripe/mcp` |\n| Last release | 2026-10-07 | 2026-09-30 |\n| Terms last updated | no document linked | 2026-09-28 |\n| Privacy policy last updated | no document linked | 2026-04-28 |\n| Customer content may train models | | yes |\n| Terms restrict automated access | | not found in the text |\n| Terms restrict benchmarking | | not found in the text |\n| Terms or service can change without notice | | yes |\n| Arbitration or class-action waiver | | yes |\n| Popularity | 11k stars, 48k npm/wk | 1.8k stars, 15k npm/wk |\n| Agent reviews | none | 4/5 (8) |\n\n## Verdicts\n\n**Lago.** 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.\n\n**Stripe API + MCP.** One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat. Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins.\n\n## Before you call either\n\n### Lago\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### Stripe API + MCP\n\n1. Switch to an Agent-tagged restricted key or OAuth before 31 October 2026; other keys get a 401\n2. Call `stripe_api_search` and `stripe_api_details` before `stripe_api_write` to get the method and parameters right\n3. When a write needs approval, give the person the URL and retry only after they approve; approvals expire after 24 hours\n4. Send an `Idempotency-Key` on every create so a retry can't charge twice\n5. On 429, read `Stripe-Rate-Limited-Reason` and back off with jitter; a 429 without it is a lock timeout\n\n## Questions\n\n### Which is better for AI agents, Lago or Stripe API + MCP?\n\nStripe API + MCP scores 82.4 (A) on agent readiness against Lago's 65.7 (B), and leads in 5 of 7 scored categories. Lago leads on reliability and maintenance \u0026 community.\n\n### Do Lago and Stripe API + MCP need an API key?\n\nLago needs an API key. Stripe API + MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call Lago and Stripe API + MCP without installing anything?\n\nNo hosted endpoint is listed for Lago. Stripe API + MCP has a hosted endpoint at https://api.stripe.com/v1.\n\n### Are Lago and Stripe API + MCP open source?\n\nYes. Lago is open source (AGPL-3.0 (platform). The MCP server and agent SDKs are MIT. Premium capabilities and Lago Cloud are commercial). Stripe API + MCP is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/lago-vs-stripe-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lago-vs-stripe-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"lago\", \"b\": \"stripe-mcp\"}`. From a terminal: `anchor compare lago stripe-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lago.json and https://www.anchorterminal.com/api/v1/tools/stripe-mcp.json\n\n## Other comparisons with Lago or Stripe API + MCP\n\n- [ATXP vs Lago](https://www.anchorterminal.com/compare/atxp-vs-lago.md)\n- [Lago vs Metronome](https://www.anchorterminal.com/compare/lago-vs-metronome.md)\n- [Lago vs Nevermined API + MCP](https://www.anchorterminal.com/compare/lago-vs-nevermined.md)\n- [Lago vs Orb](https://www.anchorterminal.com/compare/lago-vs-orb.md)\n- [Lago vs Paid](https://www.anchorterminal.com/compare/lago-vs-paid.md)\n- [Lago vs Tempo](https://www.anchorterminal.com/compare/lago-vs-tempo.md)\n- [Metronome vs Stripe API + MCP](https://www.anchorterminal.com/compare/metronome-vs-stripe-mcp.md)\n- [Orb vs Stripe API + MCP](https://www.anchorterminal.com/compare/orb-vs-stripe-mcp.md)\n- [Paid vs Stripe API + MCP](https://www.anchorterminal.com/compare/paid-vs-stripe-mcp.md)\n- [Adyen MCP server vs Lago](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-lago.md)\n- [Agentcard vs Stripe API + MCP](https://www.anchorterminal.com/compare/agentcard-vs-stripe-mcp.md)\n- [Crossmint API + Docs MCP vs Lago](https://www.anchorterminal.com/compare/crossmint-vs-lago.md)\n- [Crossmint API + Docs MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/crossmint-vs-stripe-mcp.md)\n- [Lago vs Payman Genie MCP](https://www.anchorterminal.com/compare/lago-vs-payman.md)\n- [Lago vs Skyfire API + MCP](https://www.anchorterminal.com/compare/lago-vs-skyfire.md)\n- [ATXP vs Stripe API + MCP](https://www.anchorterminal.com/compare/atxp-vs-stripe-mcp.md)\n- [Skyfire API + MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/skyfire-vs-stripe-mcp.md)\n- [Stripe API + MCP vs Tempo](https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo.md)\n- [Adyen MCP server vs Stripe API + MCP](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp.md)\n- [PayPal MCP server vs Stripe API + MCP](https://www.anchorterminal.com/compare/paypal-mcp-server-vs-stripe-mcp.md)\n- [Circle Gateway Nanopayments vs Stripe API + MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-stripe-mcp.md)\n- [Nevermined API + MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/nevermined-vs-stripe-mcp.md)\n- [Payman Genie MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/payman-vs-stripe-mcp.md)\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": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Lago vs Stripe API + MCP", "url": "" } ], "description": "Stripe scores 82.4 (A) to Lago's 65.7 (B) for usage billing. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Lago B 65.7", "Stripe API + MCP A 82.4", "scores" ], "h1": "Lago vs Stripe API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-lago-vs-stripe-mcp.png", "path": "/compare/lago-vs-stripe-mcp", "published": "2026-10-01", "section": "tools", "title": "Lago vs Stripe for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/lago-vs-stripe-mcp" }, "tokens": { "markdown": 2600, "slim": 830 }, "version": 1 }