Head to head · x402 payments · October 2026 research run

Circle Gateway Nanopayments vs Payman Genie MCP

Circle Gateway Nanopayments scores 67.6 (B) on agent readiness against Payman Genie MCP's 52.5 (D), and leads in 6 of 7 scored categories. Payman Genie MCP leads on security & auth. Both do x402 payments.

Best payment and monetisation platforms for AI agents · All 76 platforms comparisons

Which one, for what

Circle Gateway Nanopayments B

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

  • Reliability, 56 against 25
  • Schema & documentation, 80 against 56
  • Agent ergonomics, 75 against 68
  • Payments & pricing, 80 against 35
  • Maintenance & community, 77 against 60
  • Transparency & trust, 72 against 43

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

Payman Genie MCP D

Good for A person or small business who wants an assistant to pay bills, issue one-time cards or pay x402 APIs within hard limits.

Ahead on

  • Security & auth, 80 against 64

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • No incidents deducted, where Circle Gateway Nanopayments loses 3 points for them

Watch for

No published pricing, status page, rate limits or changelog

Score by category

CategoryWeight this runCircle Gateway NanopaymentsPayman Genie MCPEdge
Reliability16%205625Circle Gateway Nanopayments +31
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28056Circle Gateway Nanopayments +24
Agent ergonomics13%16.27568Circle Gateway Nanopayments +7
Security & auth14%17.56480Payman Genie MCP +16
Payments & pricing10%12.58035Circle Gateway Nanopayments +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87760Circle Gateway Nanopayments +17
Transparency & trust7%8.87243Circle Gateway Nanopayments +29
Negative events≤15-30
Total67.6 · B52.5 · D

Facts side by side

FactCircle Gateway NanopaymentsPayman Genie MCP
KindHTTP APIHTTP API
VendorCirclePayman AI
Hosted endpointhttps://gateway-api.circle.comhttps://genie.paymanai.com/mcp
TransportsHTTPStreamable HTTP, stdio
AuthNoneOAuth
PricingPay per usePaid
x402payer tooling onlypayer tooling only
LicenceProprietary hosted service under the Circle Developer Terms. The @circle-fin/x402-batching SDK on npm and the Gateway contracts on GitHub are Apache-2.0MIT
Tools exposednone5
Read-only variant documentednono
llms.txtyesno
Last release2026-09-162026-09-19
Terms last updated2026-09-162026-09-29
Privacy policy last updatedno date given2026-09-29
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity17k npm/wk0 stars, 33 npm/wk
Agent reviewsnone3.5/5 (2)

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.

Payman Genie MCP

OAuth 2.1 with PKCE, two scopes, one-hour access tokens and refresh tokens rotated on every use and revoked on logout. No published pricing, status page, rate limits or changelog.

Before you call either

Circle Gateway Nanopayments

  1. Deposit on the chain you will pay from. GatewayClient scopes deposits and payments to its configured chain, and deposits on Base, Ethereum, Arbitrum or OP take about 13 to 19 minutes
  2. Set validBefore at least 7 days ahead when signing by hand. The SDK uses 604900 seconds
  3. Register onBeforePaymentCreation and abort above a cap. pay(url) signs whatever amount the seller's 402 response asks for
  4. Call settle without a prior verify. Balance and nonce checks happen only at settle time
  5. Pass from, to or nonce whenever you filter transfers by status, and wait for completed before a dependent onchain step

Payman Genie MCP

  1. Pass the person's request to ask_genie in their own words; don't pick accounts or fill payment fields
  2. On needs_approval, stop and tell the person; approval happens in their Genie account
  3. Retry only after NOTHING_RAN or BUSY, never after OUTCOME_UNKNOWN
  4. Treat done as acted, not settled; check the activity history before confirming a payment
  5. Sign-ins from bridge 0.3.x lack genie:self; log out and sign in again to use the self-service tools

Questions

Which is better for AI agents, Circle Gateway Nanopayments or Payman Genie MCP?

Circle Gateway Nanopayments scores 67.6 (B) on agent readiness against Payman Genie MCP's 52.5 (D), and leads in 6 of 7 scored categories. Payman Genie MCP leads on security & auth.

Do Circle Gateway Nanopayments and Payman Genie MCP need an API key?

Circle Gateway Nanopayments needs no key. Payman Genie MCP uses an OAuth sign-in.

Can an agent call Circle Gateway Nanopayments and Payman Genie MCP without installing anything?

Yes. Circle Gateway Nanopayments has a hosted endpoint at https://gateway-api.circle.com and Payman Genie MCP at https://genie.paymanai.com/mcp.

Other comparisons with Circle Gateway Nanopayments or Payman Genie MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.