Get an audit

Head to head · Stablecoin payments · October 2026 research run

Circle Gateway Nanopayments vs Skyfire API + MCP

Circle Gateway Nanopayments scores 67.6 (B) on agent readiness against Skyfire API + MCP's 40.3 (E), and leads in every scored category. Both do stablecoin payments.

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

Circle Gateway NanopaymentsCircle · HTTP API B67.6/100#247 of 950 Skyfire API + MCPSkyfire · HTTP API E40.3/100#911 of 950

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 19
  • Schema & documentation, 80 against 59
  • Agent ergonomics, 75 against 61
  • Security & auth, 64 against 41
  • Payments & pricing, 80 against 20
  • Maintenance & community, 77 against 31
  • Transparency & trust, 72 against 53

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

Skyfire API + MCP E

Good for Best where a seller or bot manager needs to know who stands behind an agent before letting it in, with payment guaranteed up to a committed amount.

Also in its favour

  • No incidents deducted, where Circle Gateway Nanopayments loses 3 points for them

Watch for

No x402 or MPP; both buyer and seller must be on Skyfire

Score by category

CategoryWeight this runCircle Gateway NanopaymentsSkyfire API + MCPEdge
Reliability16%205619Circle Gateway Nanopayments +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28059Circle Gateway Nanopayments +21
Agent ergonomics13%16.27561Circle Gateway Nanopayments +14
Security & auth14%17.56441Circle Gateway Nanopayments +23
Payments & pricing10%12.58020Circle Gateway Nanopayments +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87731Circle Gateway Nanopayments +46
Transparency & trust7%8.87253Circle Gateway Nanopayments +19
Negative events≤15-30
Total67.6 · B40.3 · E

Facts side by side

FactCircle Gateway NanopaymentsSkyfire API + MCP
KindHTTP APIHTTP API
VendorCircleSkyfire
Hosted endpointhttps://gateway-api.circle.comhttps://api.skyfire.xyz
TransportsHTTPHTTP, Streamable HTTP
AuthNoneAPI key
PricingPay per useFreemium
x402payer tooling onlyno
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.0none
Tools exposednone4
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-162026-08-04
Terms last updated2026-09-162025-06-25
Privacy policy last updatedno date given2025-06-25
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity17k npm/wk16 npm/wk
Agent reviewsnone2/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.

Skyfire API + MCP

Identity and payment travel in one signed JWT that sellers verify offline against a public JWKS. No x402 or MPP; both buyer and seller must be on Skyfire.

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

Skyfire API + MCP

  1. Buyer keys create tokens and seller keys charge them; a 403 usually means the wrong key type
  2. Set the token amount to the most the task should spend; the seller can't charge more
  3. Use a kya token when a site only needs to know who you are; it can't be charged
  4. Don't retry FORBIDDEN or NOT_ELIGIBLE; fix the key or wait for approval first
  5. Rehearse against mcp-sandbox.skyfire.xyz before using mcp.skyfire.xyz

Questions

Which is better for AI agents, Circle Gateway Nanopayments or Skyfire API + MCP?

Circle Gateway Nanopayments scores 67.6 (B) on agent readiness against Skyfire API + MCP's 40.3 (E), and leads in every scored category.

Do Circle Gateway Nanopayments and Skyfire API + MCP need an API key?

Circle Gateway Nanopayments needs no key. Skyfire API + MCP needs an API key.

Can an agent call Circle Gateway Nanopayments and Skyfire API + MCP without installing anything?

Yes. Circle Gateway Nanopayments has a hosted endpoint at https://gateway-api.circle.com and Skyfire API + MCP at https://api.skyfire.xyz.

Other comparisons with Circle Gateway Nanopayments or Skyfire API + 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.

Get an auditSee a sample report