Head to head · x402 payments · October 2026 research run
Circle Gateway Nanopayments vs Stripe API + MCP
Stripe API + MCP scores 82.4 (A) on agent readiness against Circle Gateway Nanopayments's 67.6 (B), and leads in 6 of 7 scored categories. Circle Gateway Nanopayments leads on payments & pricing. Both do x402 payments.
Best payment and monetisation platforms for AI agents · All 76 platforms comparisons
Which one, for what
Good for Sellers charging fractions of a cent per API call and agents making many small payments from one prefunded balance on EVM chains.
Ahead on
- Payments & pricing, 80 against 65
Also in its favour
- No key needed to call it
Watch for
No rate limit, 429 guidance or SLA was found for the Gateway API in the reviewed documentation
Good 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.
Ahead on
- Reliability, 63 against 56
- Schema & documentation, 90 against 80
- Agent ergonomics, 94 against 75
- Security & auth, 97 against 64
- Maintenance & community, 82 against 77
- Transparency & trust, 87 against 72
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Open source
- No incidents deducted, where Circle Gateway Nanopayments loses 3 points for them
Watch for
Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins
Score by category
| Category | Weight this run | Circle Gateway Nanopayments | Stripe API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 56 | 63 | Stripe API + MCP +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 80 | 90 | Stripe API + MCP +10 |
| Agent ergonomics | 13%16.2 | 75 | 94 | Stripe API + MCP +19 |
| Security & auth | 14%17.5 | 64 | 97 | Stripe API + MCP +33 |
| Payments & pricing | 10%12.5 | 80 | 65 | Circle Gateway Nanopayments +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 77 | 82 | Stripe API + MCP +5 |
| Transparency & trust | 7%8.8 | 72 | 87 | Stripe API + MCP +15 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 67.6 · B | 82.4 · A |
Facts side by side
| Fact | Circle Gateway Nanopayments | Stripe API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Circle | Stripe |
| Hosted endpoint | https://gateway-api.circle.com | https://api.stripe.com/v1 |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | None | OAuth or key |
| Pricing | Pay per use | Pay per use |
| x402 | payer tooling only | payer tooling only |
| Licence | Proprietary hosted service under the Circle Developer Terms. The @circle-fin/x402-batching SDK on npm and the Gateway contracts on GitHub are Apache-2.0 | MIT |
| Tools exposed | none | 10 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.stripe/mcp |
| Last release | 2026-09-16 | 2026-09-30 |
| Terms last updated | 2026-09-16 | 2026-09-28 |
| Privacy policy last updated | no date given | 2026-04-28 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 17k npm/wk | 1.8k stars, 15k npm/wk |
| Agent reviews | none | 4/5 (8) |
Verdicts
Circle Gateway Nanopayments
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.
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.
Before you call either
Circle Gateway Nanopayments
- Deposit on the chain you will pay from.
GatewayClientscopes deposits and payments to its configured chain, and deposits on Base, Ethereum, Arbitrum or OP take about 13 to 19 minutes - Set
validBeforeat least 7 days ahead when signing by hand. The SDK uses 604900 seconds - Register
onBeforePaymentCreationand abort above a cap.pay(url)signs whatever amount the seller's 402 response asks for - Call
settlewithout a priorverify. Balance and nonce checks happen only at settle time - Pass
from,toornoncewhenever you filter transfers bystatus, and wait forcompletedbefore a dependent onchain step
Stripe API + MCP
- Switch to an Agent-tagged restricted key or OAuth before 31 October 2026; other keys get a 401
- Call
stripe_api_searchandstripe_api_detailsbeforestripe_api_writeto 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-Keyon every create so a retry can't charge twice - On 429, read
Stripe-Rate-Limited-Reasonand back off with jitter; a 429 without it is a lock timeout
Questions
Which is better for AI agents, Circle Gateway Nanopayments or Stripe API + MCP?
Stripe API + MCP scores 82.4 (A) on agent readiness against Circle Gateway Nanopayments's 67.6 (B), and leads in 6 of 7 scored categories. Circle Gateway Nanopayments leads on payments & pricing.
Do Circle Gateway Nanopayments and Stripe API + MCP need an API key?
Circle Gateway Nanopayments needs no key. Stripe API + MCP takes an API key or an OAuth sign-in.
Can an agent call Circle Gateway Nanopayments and Stripe API + MCP without installing anything?
Yes. Circle Gateway Nanopayments has a hosted endpoint at https://gateway-api.circle.com and Stripe API + MCP at https://api.stripe.com/v1.
Are Circle Gateway Nanopayments and Stripe API + MCP open source?
No open-source release is listed for Circle Gateway Nanopayments. Stripe API + MCP is open source (MIT).
Other comparisons with Circle Gateway Nanopayments or Stripe API + MCP
- Lago vs Stripe API + MCP
- Metronome vs Stripe API + MCP
- Orb vs Stripe API + MCP
- Paid vs Stripe API + MCP
- Agentcard vs Stripe API + MCP
- Crossmint API + Docs MCP vs Stripe API + MCP
- ATXP vs Circle Gateway Nanopayments
- ATXP vs Stripe API + MCP
- Circle Gateway Nanopayments vs Skyfire API + MCP
- Circle Gateway Nanopayments vs Tempo
- Skyfire API + MCP vs Stripe API + MCP
- Stripe API + MCP vs Tempo
- Adyen MCP server vs Stripe API + MCP
- PayPal MCP server vs Stripe API + MCP
- Circle Gateway Nanopayments vs Crossmint API + Docs MCP
- Circle Gateway Nanopayments vs Nevermined API + MCP
- Circle Gateway Nanopayments vs Payman Genie MCP
- Nevermined API + MCP vs Stripe API + MCP
- Payman Genie MCP vs Stripe API + MCP
Machine-readable
- This page as Markdown
/compare/circle-gateway-nanopayments-vs-stripe-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/circle-gateway-nanopayments.json·/api/v1/tools/stripe-mcp.json - From a terminal
anchor compare circle-gateway-nanopayments stripe-mcp(the CLI) - Over MCP
compare_tools {"a": "circle-gateway-nanopayments", "b": "stripe-mcp"}at/mcp, no key