# Lago vs Tempo (slim)

> Tempo scores 76.6 (BB) to Lago's 65.7 (B) for usage billing. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/lago-vs-tempo.md (~2,300 tokens) · this version ~630 tokens · JSON https://www.anchorterminal.com/compare/lago-vs-tempo.json · canonical https://www.anchorterminal.com/compare/lago-vs-tempo
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-09

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.

- Lago: B 65.7, rank #311 of 950 · https://www.anchorterminal.com/tools/lago.min.md
- Tempo: BB 76.6, rank #27 of 950 · https://www.anchorterminal.com/tools/tempo.min.md
- Lago, good for A team that wants usage metering, plans, wallets and invoicing under its own control and can run PostgreSQL and Redis. Ahead on Reliability, 86 against 71.
- Tempo, good 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. Ahead on Agent ergonomics, 78 against 71; Security & auth, 70 against 37; Payments & 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.

| Category | Lago | Tempo |
| --- | --- | --- |
| Reliability (16%) | 86 | 71 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 88 |
| Agent ergonomics (13%) | 71 | 78 |
| Security & auth (14%) | 37 | 70 |
| Payments & pricing (10%) | 50 | 80 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 91 | 88 |
| Transparency & trust (7%) | 59 | 63 |

| Fact (where they differ) | Lago | Tempo |
| --- | --- | --- |
| Vendor | Get Lago Corp. | Tempo |
| Hosted endpoint | no (local only) | `https://api.tempo.xyz/v1` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Pay per use |
| 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 |
| Tools exposed | none | 4 |
| Read-only variant documented | yes | no |
| Last release | 2026-10-07 | 2026-09-24 |
| Privacy policy last updated | no document linked | 2026-07-31 |
| Popularity | 11k stars, 48k npm/wk | 1k stars, 209k npm/wk |
| Agent reviews | none | 3.1/5 (8) |