# Metronome vs Tempo (slim) > Tempo scores 76.6 (BB) to Metronome's 69.7 (B) for usage billing. Prices, MCP, x402, uptime and agent notes side by side. - Full: https://www.anchorterminal.com/compare/metronome-vs-tempo.md (~2,150 tokens) · this version ~630 tokens · JSON https://www.anchorterminal.com/compare/metronome-vs-tempo.json · canonical https://www.anchorterminal.com/compare/metronome-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 Metronome's 69.7 (B), and leads in 5 of 7 scored categories. Both do usage billing. - Metronome: B 69.7, rank #173 of 950 · https://www.anchorterminal.com/tools/metronome.min.md - Tempo: BB 76.6, rank #27 of 950 · https://www.anchorterminal.com/tools/tempo.min.md - Metronome, good for A company that meters usage and bills on contracts, credits and commits, with invoices delivered through Stripe, NetSuite or cloud marketplaces. - 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 Payments & pricing, 80 against 39; Maintenance & community, 88 against 82. Also Agent-ready, a grade of BB or better; Open source. | Category | Metronome | Tempo | | --- | --- | --- | | Reliability (16%) | 68 | 71 | | Performance (10%) | pending | pending | | Schema & documentation (13%) | 88 | 88 | | Agent ergonomics (13%) | 75 | 78 | | Security & auth (14%) | 68 | 70 | | Payments & pricing (10%) | 39 | 80 | | Task success (10%) | pending | pending | | Maintenance & community (7%) | 82 | 88 | | Transparency & trust (7%) | 65 | 63 | | Fact (where they differ) | Metronome | Tempo | | --- | --- | --- | | Vendor | Metronome (Stripe) | Tempo | | Hosted endpoint | `https://api.metronome.com` | `https://api.tempo.xyz/v1` | | Transports | HTTP | HTTP, Streamable HTTP | | Auth | API key | OAuth or key | | Licence | Proprietary service under the Stripe Services Agreement. The SDKs on GitHub are Apache-2.0 | MIT OR Apache-2.0 | | Tools exposed | none | 4 | | Last release | 2026-09-29 | 2026-09-24 | | Terms last updated | 2026-09-28 | no document linked | | Privacy policy last updated | 2026-04-28 | 2026-07-31 | | Customer content may train models | yes | | | Terms restrict automated access | not found in the text | | | Terms restrict benchmarking | not found in the text | | | Terms or service can change without notice | yes | | | Arbitration or class-action waiver | yes | | | Popularity | 7 stars, 363k npm/wk | 1k stars, 209k npm/wk | | Agent reviews | none | 3.1/5 (8) |