Best of · Payments & protocols
Best payment and monetisation platforms for AI agents
The 10 highest-scoring of 14 payment and monetisation platforms on the Anchor benchmark, with a pick for each need and where each one falls short. Scores come from public evidence, re-checked as vendors change.
- 14 ranked
- 3 agent-ready
- 12 hosted endpoints
- Updated 9 October 2026
Top three
Picks by need
Worked out from the scores, prices and facts, so they change when the research does.
Maintenance & community
Lago B
91/100 on maintenance & community, against 82 for the overall leader.
The shortlist
| # | Tool | Grade | Best for | Price | Where |
|---|---|---|---|---|---|
| 1 | Stripe API + MCP Stripe |
A 82.4 | 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. | 2.9% fee | hosted and local |
| 2 | Tempo Tempo |
BB 76.6 | 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. | $0.0006 / tx | hosted |
| 3 | Nevermined API + MCP Nevermined |
BB 70.8 | Builders who want to charge agents per call or by plan, with fiat and stablecoin rails and caps on the buyer side, and for agents that need one budget across x402 and MPP services. stripe-mcp suits sellers already on Stripe; crossmint and payman suit the spending side. | 1% fee | hosted |
| 4 | Metronome Metronome (Stripe) |
B 69.7 | A company that meters usage and bills on contracts, credits and commits, with invoices delivered through Stripe, NetSuite or cloud marketplaces. | 0.8% fee | hosted |
| 5 | Circle Gateway Nanopayments Circle |
B 67.6 | Sellers charging fractions of a cent per API call and agents making many small payments from one prefunded balance on EVM chains. | 0.01% fee | hosted |
| 6 | Crossmint API + Docs MCP Crossmint |
B 67.1 | Products that let agents spend, especially where a user wants a capped card or a capped stablecoin wallet for an agent, or an agent that buys from ordinary merchant sites. | $0.02 / mo | hosted |
| 7 | Orb Orb, Inc. |
B 66.5 | A software or AI company that bills on usage and needs event metering, plan versioning, prepaid credits, invoicing and revenue reporting behind one API, with Stripe or Adyen collecting the money. | Paid | hosted |
| 8 | Lago Get Lago Corp. |
B 65.7 | A team that wants usage metering, plans, wallets and invoicing under its own control and can run PostgreSQL and Redis. | Freemium | local |
| 9 | Adyen MCP server Adyen N.V. |
C 60.3 | An Adyen merchant's developer or operations staff who want an assistant to create payment links and sessions, look up terminals, webhooks, users and credentials, and change terminal settings, with a person watching writes. | $0.13 / tx | local |
| 10 | PayPal MCP server PayPal |
C 56.3 | A merchant already on PayPal who wants an assistant to draft and send invoices, look up orders and transactions, and manage subscriptions and disputes. | 3.49% fee | hosted and local |
4 more are ranked in the full table.
How to choose
- Fees on small paymentsCheck the fees on each charge, payout and metered unit, since a percentage fee on small agent payments can outweigh the value of the call itself.
- Rails for agent paymentsCheck which rails the platform supports, such as cards, stablecoins and bank transfers, since an agent can only pay on rails it can reach by itself.
- Settlement time for payoutsCheck how long settlement takes for payments and payouts, since the time between a charge and usable funds affects what an agent can spend next.
- Actions without a personCheck which steps, such as approvals, refunds and payouts, need a person in the loop, since any step that does will stall an agent running unattended.
Each one in detail
Stripe API + MCP
A 82.4/100Card, stablecoin and billing APIs with a hosted MCP server (mcp.stripe.com, 10 tools including generic stripe_api_read and stripe_api_write).
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.
Choose it 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.
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_writeactions such as refunds and outbound payments
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_readandstripe_api_writetools push method choice and parameters onto the agent
Price 2.9% feeAuth OAuth or keyx402 partialhosted and local
Tempo
BB 76.6/100A payments-first Layer 1 chain incubated by Stripe and Paradigm, live on mainnet since 2026-03-18.
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.
Choose it 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.
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
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
Price $0.0006 / txAuth OAuth or keyx402 nohosted
Nevermined API + MCP
BB 70.8/100Payments, metering and access control for agents, MCP tools and APIs.
Verdict Fees published without a login, 1% on stablecoins, 2% on cards and 2% for the Router. The x402 paywall settles Nevermined plan tokens, so generic x402 clients need its SDK or API to pay.
Choose it for Builders who want to charge agents per call or by plan, with fiat and stablecoin rails and caps on the buyer side, and for agents that need one budget across x402 and MPP services. stripe-mcp suits sellers already on Stripe; crossmint and payman suit the spending side.
Strengths
- Fees published without a login, 1% on stablecoins, 2% on cards and 2% for the Router
- Delegations cap spend, charge count and duration, revoke with one DELETE, and cards default to a $10.00 ceiling
- Errors carry a stable
BCK.*code, a remediation hint, a docs link and aretryableflag
Weaknesses
- The x402 paywall settles Nevermined plan tokens, so generic x402 clients need its SDK or API to pay
- The first API key needs a person to sign in, and the preferred flow hands the key back in a URL query string
- No published rate limits or SLA
Price 1% feeAuth OAuth or keyx402 partialhosted
Metronome
B 69.7/100Metronome is a hosted usage-based billing platform, part of Stripe. Its REST API ingests usage events, defines billable metrics, rate cards and contracts, and generates invoices, with official SDKs for Python, Node.js, Go, Ruby and Java.
Verdict Metronome's API carries an Idempotency-Key on every POST, a public OpenAPI description of 142 operations, and agentic tokens whose writes wait for a person's approval. Prices for the Startup plan are public. Errors return only a message string, token scopes are set through support, and the status feed lists 13 incidents since 22 July 2026.
Choose it for A company that meters usage and bills on contracts, credits and commits, with invoices delivered through Stripe, NetSuite or cloud marketplaces.
Strengths
- Public OpenAPI 3.0.1 description with 142 operations and 509 schemas, plus llms.txt and a Markdown twin of each docs page
Idempotency-Keyaccepted on every POST for at least 24 hours,uniqueness_keyon contracts and alerts, and eventtransaction_iddeduplication for 34 days- Agentic tokens get
403 AgenticMutationBlockedon writes and queue them at/v1/approval_requestsfor a person to approve or deny
Weaknesses
- Errors are a single
messagestring with no machine-readable code, and the API description documents a 4xx response on 87 of 142 operations - Token scoping by access level, environment or endpoint is set by contacting support. By default a token has its creator's permissions
- The status feed lists 13 incidents between 22 July and 8 October 2026, among them two hours of elevated API and ingest errors on 3 September
Price 0.8% feeAuth API keyx402 nohosted
Circle Gateway Nanopayments
B 67.6/100Circle Gateway Nanopayments is a hosted x402 facilitator that settles gas-free USDC payments as small as $0.000001. Buyers sign offchain authorisations against a Gateway balance, and Circle settles net positions onchain in batches.
Verdict A buyer with an EOA key and a seller with a wallet address can transact with no account or API key, and the settle call returns 16 documented error codes with recovery steps. No rate limit, SLA or 429 guidance was found, and a breaking change to the transfer search took effect on the day its release note is dated.
Choose it for Sellers charging fractions of a cent per API call and agents making many small payments from one prefunded balance on EVM chains.
Strengths
- The SDK's seller middleware and facilitator client need no API key or account, only a wallet address to be paid at
- A public OpenAPI file covers the five facilitator operations, with llms.txt and a Markdown twin of every docs page
- The error reference lists 16 settle and verify codes, each with a cause and a recovery step
Weaknesses
- No rate limit, 429 guidance or SLA was found for the Gateway API in the reviewed documentation
- From 26 August 2026 a
statusfilter alone onGET /v1/x402/transfersreturns 400. The release note is dated the same day - Only EOA signatures work. Smart contract accounts and ERC-1271 signatures are not supported for nanopayments
Price 0.01% feeAuth Nonex402 partialhosted
Crossmint API + Docs MCP
B 67.1/100Wallet, checkout and stablecoin infrastructure with an agent product line.
Verdict Agent Wallets are non-custodial, with spend caps, allowed counterparties and time windows enforced onchain. No published price for onramp, offramp, checkout, Agent Cards or Agent Checkouts.
Choose it for Products that let agents spend, especially where a user wants a capped card or a capped stablecoin wallet for an agent, or an agent that buys from ordinary merchant sites.
Strengths
- Agent Wallets are non-custodial, with spend caps, allowed counterparties and time windows enforced onchain
- Scoped server and client API keys, with each operation's required scope named in the spec
- Idempotency keys on transaction and transfer creation, and cursor or page pagination with date filters
Weaknesses
- No published price for onramp, offramp, checkout, Agent Cards or Agent Checkouts
- Agent Checkouts runs in production only, so the first test spends real money
- Status history is on a JavaScript-only Datadog page, and the docs changelog stops at 11 February 2026
Price $0.02 / moAuth API keyx402 partialhosted
Orb
B 66.5/100Orb is a hosted billing platform for usage-based, seat-based and hybrid pricing. It ingests usage events, computes metrics, and runs plans, subscriptions, prepaid credits and invoices through a REST API with SDKs in six languages.
Verdict Orb suits a company that bills on usage and wants one API for events, plans, credits and invoices. It publishes an OpenAPI 3.1 file, numeric rate limits, idempotency keys and a dry-run header. Every plan is priced on request and access starts with sales. No scope list for API keys or public sub-processor list was found.
Choose it for A software or AI company that bills on usage and needs event metering, plan versioning, prepaid credits, invoicing and revenue reporting behind one API, with Stripe or Adyen collecting the money.
Strengths
- Public OpenAPI 3.1 description with 147 operations and 79 webhook events, plus llms.txt and a Markdown twin of every docs page
Idempotency-Keyon every POST and PATCH for 48 hours, withIdempotent-ReplayedandTransient-Errorresponse headers- A
Dry-Run: Trueheader validates most write requests and returns the would-be result without saving it
Weaknesses
- All three plans (Core, Advanced, Enterprise) show custom pricing only, and the pricing page sends new customers to sales
- No list of API key scopes or a read-only key was found. Keys are created in the web app and revocation is irreversible
- Audit logs are in private preview and limited to the Enterprise plan
Price PaidAuth API keyx402 nohosted
Lago
B 65.7/100Lago 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.
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.
Choose it for 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/lagoDocker 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
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
Price FreemiumAuth API keyx402 nolocal
Adyen MCP server
C 60.3/100Adyen's official MCP server lets an AI client call Adyen's Checkout, Management, Legal Entity Management and Balance Platform APIs with a merchant's API key. It runs locally over stdio through npx @adyen/mcp and is labelled alpha.
Verdict All 38 tools carry read-only, destructive and idempotent annotations, and --tools loads a subset under an API credential limited by roles. The README labels the server alpha, refund_payment and the other POST tools send no idempotency key, and failures come back as plain text without an error flag.
Choose it for An Adyen merchant's developer or operations staff who want an assistant to create payment links and sessions, look up terminals, webhooks, users and credentials, and change terminal settings, with a person watching writes.
Strengths
- All 38 tools carry
readOnlyHint,destructiveHintandidempotentHint, and a test asserts every tool is classified (27 read-only, 11 writes, 6 marked destructive) --toolsloads a named subset, and the README advises a dedicated API credential whose roles match only the tools in use- The server defaults to Adyen's test environment, and live use needs both
--env=LIVEand the account's live URL prefix
Weaknesses
- The README is headed alpha, the package is at 0.6.0, and the server reports itself as version 0.4.0
refund_payment,cancel_paymentandcreate_payment_linkssend noidempotency-keyheader, although Adyen's API accepts one on POST requests- Tool failures return as text such as
Failed to refund payment. Error: ...withoutisError, and no tool reads a payment's refunds
Price $0.13 / txAuth API keyx402 nolocal
PayPal MCP server
C 56.3/100PayPal's official MCP server lets a merchant's AI client work with invoices, orders, refunds, disputes, subscriptions, catalogue products and transaction reports. It runs locally through npx @paypal/mcp or as a hosted server at mcp.paypal.com with a PayPal login.
Verdict The hosted server uses OAuth with PKCE and dynamic client registration, and the local package defaults to the sandbox. No tool carries a read-only or destructive annotation, no confirmation step for refunds or captures was found, and the documented /http streamable HTTP path returned 404 on 8 October 2026 while /mcp answered.
Choose it for A merchant already on PayPal who wants an assistant to draft and send invoices, look up orders and transactions, and manage subscriptions and disputes.
Strengths
- Hosted server at mcp.paypal.com publishes OAuth metadata with authorisation code, PKCE S256, refresh tokens, revocation and dynamic client registration
- The local package starts in the sandbox unless
PAYPAL_ENVIRONMENTisPRODUCTION, and--tools=limits which tools load - Every tool input is a typed schema with enums and range limits, built from zod definitions in the Apache-2.0 toolkit
Weaknesses
- The quickstart gives
/httpfor streamable HTTP. On 8 October 2026 it returned 404 on both hosts, and/mcpreturned the OAuth challenge - Tools are registered without
readOnlyHintordestructiveHint, and no approval step forcreate_refund,pay_orderoraccept_dispute_claimwas found @paypal/mcp1.8.1 dates from 28 October 2025 and selects 28 tool keys, while the toolkit it loads defines 48 tools
Price 3.49% feeAuth OAuth or keyx402 nohosted and local
Head to head
- Stripe API + MCP vs Tempo A 82.4 vs BB 76.6
- Nevermined API + MCP vs Stripe API + MCP BB 70.8 vs A 82.4
- Metronome vs Stripe API + MCP B 69.7 vs A 82.4
- Circle Gateway Nanopayments vs Stripe API + MCP B 67.6 vs A 82.4
- Nevermined API + MCP vs Tempo BB 70.8 vs BB 76.6
- Metronome vs Tempo B 69.7 vs BB 76.6
- Circle Gateway Nanopayments vs Tempo B 67.6 vs BB 76.6
- Metronome vs Nevermined API + MCP B 69.7 vs BB 70.8
- Circle Gateway Nanopayments vs Nevermined API + MCP B 67.6 vs BB 70.8
Questions
What are the highest-rated payment and monetisation platforms for AI agents?
Stripe API + MCP has the highest benchmark score of the 14 ranked payment and monetisation platforms, 82.4 (A). Tempo is second with 76.6 (BB).
How many payment and monetisation platforms are agent-ready?
3 of the 14 ranked here grade BB or better, the bar for agent-ready on the Anchor benchmark.
Which payment and monetisation platforms accept x402 payments?
None of the ranked listings here accepts x402 for its main call yet.
How is this list ranked?
By the Anchor benchmark score out of 100, a weighted mean of the scored categories minus deductions for negative events, from public evidence re-checked as vendors change. Listings cannot pay for a place. The latest assessment behind this page is from 9 October 2026.
How this list is made
The order is the Anchor benchmark score, the same number as on each listing and in the top list. Each listing is graded from public evidence against the benchmark checklist, and the picks above are worked out from those grades, prices and facts. No listing pays for its place, and paid audits or listing help never change a score.
Full ranked table · 76 head-to-head comparisons · Best tools in every category