{
  "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": "Tempo scores 76.6 (BB) on agent readiness against Lago's 65.7 (B), and leads in 5 of 7 scored categories. Lago leads on reliability.",
    "b": {
      "slug": "tempo",
      "name": "Tempo",
      "vendor": "Tempo",
      "vendorUrl": "https://tempo.xyz",
      "kind": "http-api",
      "category": "payment-platforms",
      "summary": "A payments-first Layer 1 chain incubated by Stripe and Paradigm, live on mainnet since 2026-03-18.",
      "url": "https://www.anchorterminal.com/tools/tempo",
      "markdownUrl": "https://www.anchorterminal.com/tools/tempo.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tempo.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tempo.json",
      "repo": "https://github.com/tempoxyz/tempo",
      "license": "MIT OR Apache-2.0",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.tempo.xyz/v1",
      "packages": [
        {
          "registry": "npm",
          "name": "viem"
        },
        {
          "registry": "npm",
          "name": "mppx"
        },
        {
          "registry": "pypi",
          "name": "pympp"
        }
      ],
      "auth": "mixed",
      "authNotes": "Public RPC (rpc.tempo.xyz) and most read endpoints of api.tempo.xyz answer without a key, within a per-IP limit. Those same endpoints accept MPP payment credentials (`Authorization: Payment`) instead of a key. Project-scoped API keys (`tempo:sk:` for production, `tempo_sandbox:sk:` for non-mainnet) carry scopes such as `data:read`, optional IP allowlists, and are required for endpoints such as webhook management. Payments are signed by the paying wallet.",
      "pricing": "usage",
      "pricingNotes": "No platform fee for using the chain. Transaction fees are paid in any supported USD stablecoin, with a dynamic base fee capped at about $0.0006 for a 50,000-gas transfer and a floor around $0.00003. Fees can be sponsored by a fee payer, billed through the Tempo API Console. API calls are free within quota; over quota, anonymous endpoints answer 402 and can be paid per request over MPP, and keyed usage is billed in the console, with no published price for either. Stripe charges its own fees when it settles MPP payments on Tempo (https://tempo.xyz/developers/docs/protocol/fees).",
      "priceSummary": "$0.0006 / tx",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "Tempo's own API takes MPP, not x402, on its anonymous endpoints (https://tempo.xyz/developers/docs/api/rate-limits). MPP itself added acceptance of x402 exact payments on EVM chains in June 2026 (https://mpp.dev/blog/evm-x402-support).",
        "endpoints": []
      },
      "toolCount": 4,
      "popularity": {
        "githubStars": 1029,
        "npmWeekly": 209447,
        "pypiWeekly": null,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://tempo.xyz/developers/docs",
      "llmsTxt": "https://tempo.xyz/developers/llms.txt",
      "openapi": "https://api.tempo.xyz/openapi.json",
      "capabilities": [
        "payments.stablecoin",
        "payments.metering"
      ],
      "tags": [
        "hosted",
        "open-source",
        "mcp",
        "llms-txt",
        "openapi",
        "stablecoin",
        "typescript",
        "free-tier"
      ],
      "lastRelease": "2026-09-24",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 76.6,
        "grade": "BB",
        "agentReady": true,
        "rank": 27,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 2,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 78,
          "maintenance": 88,
          "payments": 80,
          "reliability": 71,
          "schema": 88,
          "security": 70,
          "transparency": 63
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-01"
        },
        "negative": 0,
        "verdict": "api.tempo.xyz accepts MPP on its anonymous endpoints, so an agent can pay per request without an account. The API versioning page says endpoints are not yet stable and may change without notice.",
        "bestFor": "Builders who want to settle MPP payments in stablecoins at fractions of a cent, or agents that need chain data and can pay per request without an account.",
        "strengths": [
          "api.tempo.xyz accepts MPP on its anonymous endpoints, so an agent can pay per request without an account",
          "Transaction fees capped around $0.0006 for a transfer and payable in any supported USD stablecoin, with sponsorship",
          "Scoped API keys with rotation, revocation, IP allowlists and hashed storage",
          "Published rate limits with `RateLimit-*` and `Retry-After` headers, one error envelope and cursor pagination",
          "Open-source node under MIT or Apache-2.0 with seven releases since 22 July and a dated changelog"
        ],
        "weaknesses": [
          "The API versioning page says endpoints are not yet stable and may change without notice",
          "No terms of service found for the API, console, CLI or MCP server",
          "No active bug bounty while audits continue",
          "Breaking network upgrades every two to four weeks, with mainnet activation as soon as three days after release",
          "No published price for API usage or per-request MPP payments"
        ],
        "agentNotes": [
          "Send `Authorization: Payment` up front to pay per request; a 402 after quota carries the challenge in `WWW-Authenticate`",
          "Read `RateLimit-Remaining` and `RateLimit-Reset` rather than hardcoding the 20 or 100 a minute defaults",
          "Pass `chainId=testnet` with a sandbox key; a sandbox key sent to mainnet is ignored and the call drops to the anonymous limit",
          "Use `tempo request --dry-run` before paying an MPP endpoint to see the cost",
          "Branch on `error.code`, never on `error.message`"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 8,
        "avgRating": 3.1,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 76.6
          }
        ],
        "editorialScores": {
          "ergonomics": 78,
          "maintenance": 88,
          "payments": 80,
          "reliability": 71,
          "schema": 88,
          "security": 70,
          "transparency": 50
        },
        "provenanceScore": 76
      },
      "connect": {
        "http": "curl https://api.tempo.xyz/v1/blocks",
        "claudeCode": "claude mcp add --transport http tempo https://mcp.tempo.xyz",
        "config": {
          "mcpServers": {
            "tempo": {
              "url": "https://mcp.tempo.xyz"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/payments.stablecoin",
        "tool": "https://letme.dev/tempo"
      },
      "area": "payments",
      "unitPrices": [
        {
          "item": "Transfer fee cap",
          "unit": "tx",
          "usd": 0.0006,
          "note": "base-fee cap for a 50,000-gas transfer; floor around $0.00003"
        }
      ],
      "provenance": {
        "legalEntity": "Tempo Labs Inc.",
        "domain": "tempo.xyz",
        "domainRegistered": "2017-11-09",
        "domainNote": "tempo.xyz was registered in 2017, before Tempo was founded in 2025, and transferred in September 2025. The privacy policy names Tempo Labs Inc. dba Tempo; no terms of service page was found.",
        "endpointOnVendorDomain": true,
        "terms": "",
        "privacy": "https://tempo.xyz/privacy-policy/",
        "statusPage": "https://status.tempo.xyz",
        "changelog": "https://tempo.xyz/developers/docs/changelog",
        "securityTxt": "none",
        "checked": "2026-09-30",
        "score": 76
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/tempo.json",
      "live": {
        "slug": "tempo",
        "probe": {
          "target": "https://api.tempo.xyz/v1",
          "method": "get",
          "lastAt": "2026-10-10T04:41:06.334772745Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 178,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 212,
          "p95ms24h": 348,
          "samples24h": 248,
          "samples30d": 2484,
          "days": [
            {
              "date": "2026-09-30",
              "probes": 35,
              "ok": 35
            },
            {
              "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": 48,
              "ok": 48
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.tempo.xyz",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-10T00:51:19.580977221Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "tempoxyz/tempo",
            "version": "tempo-primitives@1.16.0",
            "released": "2026-10-06",
            "seenAt": "2026-10-09T17:23:58.10804858Z"
          },
          {
            "registry": "npm",
            "name": "mppx",
            "version": "0.13.4",
            "seenAt": "2026-10-09T17:23:56.599451125Z"
          },
          {
            "registry": "npm",
            "name": "viem",
            "version": "2.57.4",
            "seenAt": "2026-10-09T17:23:55.790295075Z"
          },
          {
            "registry": "pypi",
            "name": "pympp",
            "version": "0.11.0",
            "released": "2026-08-28",
            "seenAt": "2026-10-09T17:23:57.984335557Z"
          }
        ],
        "githubStars": 1030,
        "npmWeekly": 6495477,
        "pypiWeekly": 420380,
        "securityTxt": {
          "url": "https://tempo.xyz/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-09T15:39:17.658003872Z"
        },
        "llmsTxt": {
          "url": "https://tempo.xyz/developers/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-09T14:02:53.270049124Z"
        },
        "domain": {
          "domain": "tempo.xyz",
          "registered": "2017-11-09",
          "source": "https://rdap.centralnic.com/xyz/domain/tempo.xyz",
          "checkedAt": "2026-10-04T13:08:55.633115434Z"
        },
        "pages": [
          {
            "url": "https://tempo.xyz/developers/docs/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-09T18:46:37.684534437Z",
            "changedAt": "2026-10-09T18:46:37.684534437Z",
            "fingerprint": "c9d51740aad3"
          },
          {
            "url": "https://tempo.xyz/privacy-policy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-09T18:46:40.193474976Z",
            "changedAt": "2026-10-07T18:10:02.234680476Z",
            "fingerprint": "ab4f2727a67b"
          }
        ],
        "updatedAt": "2026-10-10T04:41:06.334772745Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Get Lago Corp.",
        "b": "Tempo",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "https://api.tempo.xyz/v1",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP, Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "AGPL-3.0 (platform). The MCP server and agent SDKs are MIT. Premium capabilities and Lago Cloud are commercial",
        "b": "MIT OR Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "4",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-07",
        "b": "2026-09-24",
        "name": "Last release"
      },
      {
        "a": "no document linked",
        "b": "no document linked",
        "name": "Terms last updated"
      },
      {
        "a": "no document linked",
        "b": "2026-07-31",
        "name": "Privacy policy last updated"
      },
      {
        "a": "",
        "b": "",
        "name": "Customer content may train models"
      },
      {
        "a": "",
        "b": "",
        "name": "Terms restrict automated access"
      },
      {
        "a": "",
        "b": "",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "",
        "b": "",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "",
        "b": "",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "11k stars, 48k npm/wk",
        "b": "1k stars, 209k npm/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3.1/5 (8)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Tempo scores 76.6 (BB) on agent readiness against Lago's 65.7 (B), and leads in 5 of 7 scored categories. Lago leads on reliability.",
        "question": "Which is better for AI agents, Lago or Tempo?"
      },
      {
        "answer": "Lago needs an API key. Tempo takes an API key or an OAuth sign-in.",
        "question": "Do Lago and Tempo need an API key?"
      },
      {
        "answer": "No hosted endpoint is listed for Lago. Tempo has a hosted endpoint at https://api.tempo.xyz/v1.",
        "question": "Can an agent call Lago and Tempo 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). Tempo is open source (MIT OR Apache-2.0).",
        "question": "Are Lago and Tempo open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 86 against 71"
        ],
        "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, 78 against 71",
          "Security \u0026 auth, 70 against 37",
          "Payments \u0026 pricing, 80 against 50"
        ],
        "also": [
          "Agent-ready, a grade of BB or better",
          "A hosted endpoint, with nothing to install",
          "No incidents deducted, where Lago loses 3 points for them"
        ],
        "goodFor": "Builders who want to settle MPP payments in stablecoins at fractions of a cent, or agents that need chain data and can pay per request without an account.",
        "slug": "tempo",
        "watchFor": "The API versioning page says endpoints are not yet stable and may change without notice"
      }
    ],
    "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-stripe-mcp.json",
        "title": "Lago vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/lago-vs-stripe-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/metronome-vs-tempo.json",
        "title": "Metronome vs Tempo",
        "url": "https://www.anchorterminal.com/compare/metronome-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/orb-vs-tempo.json",
        "title": "Orb vs Tempo",
        "url": "https://www.anchorterminal.com/compare/orb-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/paid-vs-tempo.json",
        "title": "Paid vs Tempo",
        "url": "https://www.anchorterminal.com/compare/paid-vs-tempo"
      },
      {
        "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/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/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-tempo.json",
        "title": "ATXP vs Tempo",
        "url": "https://www.anchorterminal.com/compare/atxp-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-tempo.json",
        "title": "Circle Gateway Nanopayments vs Tempo",
        "url": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crossmint-vs-tempo.json",
        "title": "Crossmint API + Docs MCP vs Tempo",
        "url": "https://www.anchorterminal.com/compare/crossmint-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nevermined-vs-tempo.json",
        "title": "Nevermined API + MCP vs Tempo",
        "url": "https://www.anchorterminal.com/compare/nevermined-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/skyfire-vs-tempo.json",
        "title": "Skyfire API + MCP vs Tempo",
        "url": "https://www.anchorterminal.com/compare/skyfire-vs-tempo"
      },
      {
        "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"
      }
    ],
    "scores": [
      {
        "by": 15,
        "edge": "lago",
        "key": "reliability",
        "lago": 86,
        "name": "Reliability",
        "tempo": 71,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 1,
        "edge": "tempo",
        "key": "schema",
        "lago": 87,
        "name": "Schema \u0026 documentation",
        "tempo": 88,
        "weight": 13
      },
      {
        "by": 7,
        "edge": "tempo",
        "key": "ergonomics",
        "lago": 71,
        "name": "Agent ergonomics",
        "tempo": 78,
        "weight": 13
      },
      {
        "by": 33,
        "edge": "tempo",
        "key": "security",
        "lago": 37,
        "name": "Security \u0026 auth",
        "tempo": 70,
        "weight": 14
      },
      {
        "by": 30,
        "edge": "tempo",
        "key": "payments",
        "lago": 50,
        "name": "Payments \u0026 pricing",
        "tempo": 80,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 3,
        "edge": "lago",
        "key": "maintenance",
        "lago": 91,
        "name": "Maintenance \u0026 community",
        "tempo": 88,
        "weight": 7
      },
      {
        "by": 4,
        "edge": "tempo",
        "key": "transparency",
        "lago": 59,
        "name": "Transparency \u0026 trust",
        "tempo": 63,
        "weight": 7
      }
    ],
    "summary": "Tempo scores 76.6 (BB) on agent readiness against Lago's 65.7 (B), and leads in 5 of 7 scored categories. Lago leads on reliability. 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.",
      "tempo": "api.tempo.xyz accepts MPP on its anonymous endpoints, so an agent can pay per request without an account. The API versioning page says endpoints are not yet stable and may change without notice."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/lago-vs-tempo",
    "json": "https://www.anchorterminal.com/compare/lago-vs-tempo.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/lago-vs-tempo.md",
    "slim": "https://www.anchorterminal.com/compare/lago-vs-tempo.min.md"
  },
  "markdown": "Tempo scores 76.6 (BB) on agent readiness against Lago's 65.7 (B), and leads in 5 of 7 scored categories. Lago leads on reliability. 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- Tempo: grade BB, 76.6/100, rank #27 of 950. Markdown https://www.anchorterminal.com/tools/tempo.md · JSON https://www.anchorterminal.com/api/v1/tools/tempo.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 71\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### Tempo (BB)\n\nGood for: Builders who want to settle MPP payments in stablecoins at fractions of a cent, or agents that need chain data and can pay per request without an account.\n\nAhead on:\n- Agent ergonomics, 78 against 71\n- Security \u0026 auth, 70 against 37\n- Payments \u0026 pricing, 80 against 50\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where Lago loses 3 points for them\n\nWatch for: The API versioning page says endpoints are not yet stable and may change without notice\n\n\n## Score by category\n\n| Category | Weight | Lago | Tempo | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 86 | 71 | Lago +15 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 88 | Tempo +1 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 78 | Tempo +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 37 | 70 | Tempo +33 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 80 | Tempo +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 91 | 88 | Lago +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 59 | 63 | Tempo +4 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **65.7 · B** | **76.6 · BB** | |\n\n## Facts side by side\n\n| Fact | Lago | Tempo |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Get Lago Corp. | Tempo |\n| Hosted endpoint | no (local only) | `https://api.tempo.xyz/v1` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | AGPL-3.0 (platform). The MCP server and agent SDKs are MIT. Premium capabilities and Lago Cloud are commercial | MIT OR Apache-2.0 |\n| Tools exposed | none | 4 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-07 | 2026-09-24 |\n| Terms last updated | no document linked | no document linked |\n| Privacy policy last updated | no document linked | 2026-07-31 |\n| Customer content may train models |  |  |\n| Terms restrict automated access |  |  |\n| Terms restrict benchmarking |  |  |\n| Terms or service can change without notice |  |  |\n| Arbitration or class-action waiver |  |  |\n| Popularity | 11k stars, 48k npm/wk | 1k stars, 209k npm/wk |\n| Agent reviews | none | 3.1/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**Tempo.** api.tempo.xyz accepts MPP on its anonymous endpoints, so an agent can pay per request without an account. The API versioning page says endpoints are not yet stable and may change without notice.\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### Tempo\n\n1. Send `Authorization: Payment` up front to pay per request; a 402 after quota carries the challenge in `WWW-Authenticate`\n2. Read `RateLimit-Remaining` and `RateLimit-Reset` rather than hardcoding the 20 or 100 a minute defaults\n3. Pass `chainId=testnet` with a sandbox key; a sandbox key sent to mainnet is ignored and the call drops to the anonymous limit\n4. Use `tempo request --dry-run` before paying an MPP endpoint to see the cost\n5. Branch on `error.code`, never on `error.message`\n\n## Questions\n\n### Which is better for AI agents, Lago or Tempo?\n\nTempo scores 76.6 (BB) on agent readiness against Lago's 65.7 (B), and leads in 5 of 7 scored categories. Lago leads on reliability.\n\n### Do Lago and Tempo need an API key?\n\nLago needs an API key. Tempo takes an API key or an OAuth sign-in.\n\n### Can an agent call Lago and Tempo without installing anything?\n\nNo hosted endpoint is listed for Lago. Tempo has a hosted endpoint at https://api.tempo.xyz/v1.\n\n### Are Lago and Tempo 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). Tempo is open source (MIT OR Apache-2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/lago-vs-tempo.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lago-vs-tempo.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"lago\", \"b\": \"tempo\"}`. From a terminal: `anchor compare lago tempo`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lago.json and https://www.anchorterminal.com/api/v1/tools/tempo.json\n\n## Other comparisons with Lago or Tempo\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 Stripe API + MCP](https://www.anchorterminal.com/compare/lago-vs-stripe-mcp.md)\n- [Metronome vs Tempo](https://www.anchorterminal.com/compare/metronome-vs-tempo.md)\n- [Orb vs Tempo](https://www.anchorterminal.com/compare/orb-vs-tempo.md)\n- [Paid vs Tempo](https://www.anchorterminal.com/compare/paid-vs-tempo.md)\n- [Adyen MCP server vs Lago](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-lago.md)\n- [Crossmint API + Docs MCP vs Lago](https://www.anchorterminal.com/compare/crossmint-vs-lago.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 Tempo](https://www.anchorterminal.com/compare/atxp-vs-tempo.md)\n- [Circle Gateway Nanopayments vs Tempo](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-tempo.md)\n- [Crossmint API + Docs MCP vs Tempo](https://www.anchorterminal.com/compare/crossmint-vs-tempo.md)\n- [Nevermined API + MCP vs Tempo](https://www.anchorterminal.com/compare/nevermined-vs-tempo.md)\n- [Skyfire API + MCP vs Tempo](https://www.anchorterminal.com/compare/skyfire-vs-tempo.md)\n- [Stripe API + MCP vs Tempo](https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo.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 Tempo",
        "url": ""
      }
    ],
    "description": "Tempo scores 76.6 (BB) to Lago's 65.7 (B) for usage billing. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Lago B 65.7",
      "Tempo BB 76.6",
      "scores"
    ],
    "h1": "Lago vs Tempo",
    "image": "https://www.anchorterminal.com/assets/og/compare-lago-vs-tempo.png",
    "path": "/compare/lago-vs-tempo",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Lago vs Tempo for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/lago-vs-tempo"
  },
  "tokens": {
    "markdown": 2300,
    "slim": 630
  },
  "version": 1
}