# Circle Gateway Nanopayments vs FluxA AgentMarket

> Circle Gateway Nanopayments scores 69.7 (B) to FluxA AgentMarket's 48.4 (D) for x402 payments. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-fluxa-agentmarket
- Markdown: https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-fluxa-agentmarket.md (~6,050 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Circle Gateway Nanopayments scores 69.7 (B) on agent readiness against FluxA AgentMarket's 48.4 (D), and leads in every scored category. Both do x402 payments.

- Circle Gateway Nanopayments: grade B, 69.7/100, rank #228 of 1513. Markdown https://www.anchorterminal.com/tools/circle-gateway-nanopayments.md · JSON https://www.anchorterminal.com/api/v1/tools/circle-gateway-nanopayments.json
- FluxA AgentMarket: grade D, 48.4/100, rank #1127 of 1513. Markdown https://www.anchorterminal.com/tools/fluxa-agentmarket.md · JSON https://www.anchorterminal.com/api/v1/tools/fluxa-agentmarket.json
- Best payment and monetisation platforms for AI agents: https://www.anchorterminal.com/best/payment-platforms/index.md
- All 104 platforms comparisons: https://www.anchorterminal.com/compare/payment-platforms/index.md

## 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, 66 against 12
- Schema & documentation, 80 against 53
- Agent ergonomics, 75 against 66
- Security & auth, 64 against 51
- Payments & pricing, 80 against 75
- Maintenance & community, 77 against 64
- Transparency & trust, 73 against 32

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

### FluxA AgentMarket (D)

Good for: An agent that needs many third-party APIs and models from one balance or one Base USDC wallet, with a person setting a budget once.

Also in its favour:
- No incidents deducted, where Circle Gateway Nanopayments loses 3 points for them

Watch for: No status page, rate limit, 429 guidance, SLA or security programme was found, and the about page labels the product 'v.01 / Beta'


## Why the edge

### Reliability: Circle Gateway Nanopayments +54

- Circle Gateway Nanopayments (66): Graded as a hosted service on gateway-api.circle.com. status.circle.com is a Statuspage with Circle Gateway components for each chain, mainnet and testnet (20). The history pages, read on 1 November 2026, list every incident from June to 31 October. From 3 August none names Gateway or a Gateway component. They cover USDC mints on single chains, CCTP attestations, xReserve, Wallets and testnets, and the two HyperEVM incidents opened name only CCTP and USDC components. The last Gateway incident was testnet only, 29 June to 2 July, outside the window. A clean record (30). No rate limit with numbers was found for the Gateway API, and an unauthenticated call to `/v1/x402/supported` carried no rate-limit headers (0). No 429 or `Retry-After` guidance was found. Each authorisation carries a unique nonce, a repeat returns `nonce_already_used`, and the error reference says to retry `unexpected_error` (6 of 15). No SLA was found, and the developer terms allow changes without prior notice (0). The release notes record the mainnet launch on 29 April 2026 and the pages read carry no beta label (10).
- FluxA AgentMarket (12): Graded as a hosted service, the discovery gateway on agentmarket.fluxapay.xyz and the proxy and LLM endpoints on router.fluxapay.xyz, from the vendor's pages. Nothing was called. No status page is linked from the site, the footer, llms.txt or the guides, and no status host was checked (0). With no readable incident history the record takes the default (5). Listing pages show a health count with no history, such as '10/10 endpoints healthy' on Minifetch. No rate limit with numbers was found in llms.txt, the guides or the CLI help. The only cap is a per-key spending limit (0). The Balance guide says to retry a 503 shortly without minting a new credential, replays of a settled top-up `finalize` call are idempotent, a failed order answers 409, and the card flow says 'a retry is a new order'. No 429 or Retry-After guidance was found. Termix earned 8 for the same kind of guidance with idempotency keys on writes (7 of 15). No SLA was found, and the terms supply the service 'as is' (0). The about page labels the product 'v.01 / Beta' (0). Total 12.

### Transparency & trust: Circle Gateway Nanopayments +41

- Circle Gateway Nanopayments (73): The SDK is Apache-2.0 on npm and the Gateway contracts are Apache-2.0 on GitHub. The API service and the enclave code are closed, under clear developer terms (22 of 30). The privacy policy of 16 September 2026 lists transaction and blockchain data among what is collected and keeps data as long as necessary, with no periods. The service terms link a DPA dated 2022. Nothing found says what the Gateway API logs about a payment (17 of 30). The developer terms promise reasonable efforts to announce the end of support for a version and also let Circle modify or discontinue Gateway without prior notice. The one breaking change found was noted on the day it took effect (6 of 20). A sub-processor list, last updated 22 December 2025, names each processor with its purpose and country (14 of 20).
- FluxA AgentMarket (32): The editorial half. The marketplace, proxy and gateway are closed. The terms (effective 14 January 2026) cover pricing, refunds and acceptable use but name no governing law, termination terms, liability for third-party listings or creator obligations, and the company appears only in the footer. The CLI is Apache-2.0 (8 of 30). The privacy policy (14 January 2026) lists account, payment and usage data and says identity isn't shared with model providers. It says nothing on prompts, API payloads, retention, training or data location (6 of 30). No deprecation policy or dated notice was found, and the terms may change 'at any time' (0 of 20). The policy names Stripe and 'OpenAI/Anthropic API' as a non-exhaustive list, while the models page lists AIHubMix, UnifyLLM and Baidu AI Cloud as providers. No locations are given (4 of 20). Total 18. The provenance half is computed from the provenance block.

### Schema & documentation: Circle Gateway Nanopayments +27

- Circle Gateway Nanopayments (80): A public OpenAPI 3.0.3 file covers the five operations. It gives the 400 responses no body schema and attaches its Bearer scheme to no operation (23 of 25). llms.txt and a Markdown twin of every docs page (10). The docs say when to use this facilitator and when Circle's other one, and to call `settle` without `verify` in production (15 of 20). Transfer status and settle error reasons are enums and required fields are marked. `payload`, `extra` and `extensions` are open objects, and `pageSize` has no maximum (10 of 15). Every SDK method has a typed signature and an example, and 16 API error codes have a cause and a recovery step. The error reference says the validity window must be 3 days where the quickstart, the SDK and the live `minValiditySeconds` of 604800 say 7 (11 of 15). Paths are under `/v1`, the SDK follows semver and the release notes are dated. The npm package ships no changelog (11 of 15).
- FluxA AgentMarket (53): No OpenAPI file was found. llms.txt names none and the documentation site, docs.fluxapay.xyz, couldn't be read because its robots.txt couldn't be. The discovery response has documented fields (`apiServers`, `skills`, `models`, `pagination`), a GET on each listing's `urls.access` returns its endpoints and prices as JSON per the skill-creation guide, and the LLM endpoints follow the OpenAI and Anthropic formats (8 of 25). llms.txt and Markdown guides (getting-started.md, currency.md, create-skill.md, the APIs and Balance guides) written for agents (10). The guides say when to use `search` against `query`, that the external catalogues are a last resort and which rail fits which job. Listing descriptions come from creators and 17 of the first 50 skills have none (12 of 20). `type` is an enum that answers 400 to unknown values, `limit` is bounded at 1,000, and the chat and messages bodies follow published formats. Listing endpoints are described by each creator (9 of 15). curl examples for discovery, models and payment, a status table in the Balance guide with the action for 401, 503, 404, 402 and 409, and seven named mandate errors in the APIs guide (11 of 15). Paths carry `/llm/v1/` and llms.txt names minimum CLI versions, but no changelog was found (3 of 15). Total 53.

### Security & auth: Circle Gateway Nanopayments +13

- Circle Gateway Nanopayments (64): No API key. The buyer's EOA private key signs each payment, and each authorisation is bound to one amount, recipient, validity window and nonce. The same key controls the whole wallet, the SDK takes it as a plain config value, and smart contract accounts with their own policies are not supported (18 of 30). Only the deposited Gateway balance can be spent, and a client hook can abort a payment above a limit. No limit is set by default and none is enforced by the service (12 of 20). The amount comes from the seller's 402 response, which is untrusted. The docs show the spending-limit hook and give no other guidance. Circle's Gateway skill file says to ask the user before moving funds on mainnet (8 of 15). Transfers can be searched by address, nonce and date and each carries its batch transaction hash. No separate operator log was found (11 of 15). Audit reports by ChainSecurity and OtterSec are linked, one of them on batching, and a repository security policy names a HackerOne bug bounty programme. security.txt answered 404 and no certification was found on the pages read (15 of 20).
- FluxA AgentMarket (51): `fxa_live_` keys are created by a person at /keys and shown once, each with a spending limit in Units that changes within seconds, and are revoked immediately over `DELETE /llm/keys/<id>`, with written rotation steps. Key management needs a 5-minute Agent VC, never a key, and creation can be set to need a person's approval. No permission scopes beyond the spending limit were found, and no secret in a URL (24 of 30). Wallet payments need a mandate a person signs with a USDC budget and an expiry, and the Balance guide says to confirm every top-up with the user. The APIs guide tells agents not to ask before paying within a signed mandate, and no read-only key was found (14 of 20). The marketplace returns content from third-party APIs and installs third-party skills. Results carry a `fluxa` or `bazaar` source tag, but entries named `ssrf1`, `keyprobe` and `tooltest1` are tagged `fluxa`, no review of uploads is described, and no guidance on treating responses or skills as untrusted was found (2 of 15). The balance endpoint returns available, spent, burn per day and owed, the ledger lists spend and purchases per merchant, and the wallet skill reads an `X-LLM-Cost` header on model calls (11 of 15). No disclosure policy, bug bounty, certification or advisory was found. security.txt couldn't be read and is scored absent, and the privacy policy says only 'industry-standard security measures' (0 of 20). Total 51.

### Maintenance & community: Circle Gateway Nanopayments +13

- Circle Gateway Nanopayments (77): `@circle-fin/x402-batching` 4.0.0 was published on 22 October 2026, 10 days before this check, and the Gateway release notes have an entry on 23 October (EURC and cirBTC) (30). Since 3 August there are four SDK versions, 3.3.0 on 4 August, 3.4.0 on 24 August, 3.5.0 on 16 September and 4.0.0, and four dated release notes, 5 August, 26 August, 16 September and 23 October (20). The SDK has no public repository or issue tracker that we found. Support is a Discord server and a help centre ticket form, neither tested, next to dated release notes (10 of 25). The SDK is official and current, in TypeScript only (12 of 15). The package declares tests and lint scripts and current peer dependencies. No public CI for it was found. The contracts repository runs a pipeline, per the 9 October check, not re-read on 1 November (5 of 10).
- FluxA AgentMarket (64): Read for a closed service. No changelog or dated release notes were found. The models page says the catalogue was 'last updated November 5, 2026', and `@fluxa-pay/fluxa-wallet` 0.6.0, the CLI that carries the `market` commands llms.txt relies on, was published on 6 November 2026 (30). The CLI had eight releases between 10 August and 6 November 2026, 0.4.12 to 0.6.0 (20). Support is a Discord server and support.fluxapay@fluxapay.xyz, neither tested, and GitHub issues couldn't be read because the GitHub API refused us (3 of 15). No AgentMarket SDK. The TypeScript CLI is the official client and the LLM endpoints take OpenAI and Anthropic SDKs. Not an MCP server, so the registry line reads as SDKs (7 of 15). The CLI repository has 7 test files and no CI workflow, and the npm package declares no repository. `@fluxa-pay/fluxa-connect-mcp` points to a repository that isn't public (4 of 10). Total 64.

### Agent ergonomics: Circle Gateway Nanopayments +9

- Circle Gateway Nanopayments (75): The API is five operations and the buyer path is one `pay(url)` call. Transfer search takes `pageSize` (20 of 25). Cursor pagination with `pageAfter` and `pageBefore`, and filters by sender, recipient, nonce, network, status and date. A status filter needs a second filter since 26 August 2026 (17 of 20). Sixteen error codes with recovery steps, and typed SDK error messages (17 of 20). The nonce stops one authorisation being settled twice and a `completed` or `failed` state tells a caller when to stop. No idempotency key was found, and a failed payment needs a newly signed authorisation (13 of 20). The seller middleware needs one address and a price, and the buyer client a chain and a key. The only official SDK is TypeScript (8 of 15).
- FluxA AgentMarket (66): Graded on the HTTP API. Discovery takes `limit` up to 1,000, `type` and `tags` filters and a Markdown format, with no field selection, and listing responses vary by creator (15 of 25). `limit`, `offset` and `nextOffset` on discovery, `search` and `query` modes, and the ledger takes `kind`, `limit` (maximum 100) and `offset`. llms.txt says filters ignore `limit` and `offset` (16 of 20). The Balance guide's status table gives an action for each status, the APIs guide names `insufficient_balance`, `mandate_budget_exceeded`, `agent_not_registered` and others, and a model served only on Messages answers 400 on chat (15 of 20). `finalize` replays are idempotent and a dead order answers 409 with the instruction to start a new one. No idempotency key on paid calls was found (10 of 20). The LLM endpoints accept any OpenAI or Anthropic client, discovery needs no parameters, and the only official client is the TypeScript wallet CLI (10 of 15). Total 66.

## Score by category

| Category | Weight | Circle Gateway Nanopayments | FluxA AgentMarket | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 66 | 12 | Circle Gateway Nanopayments +54 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 80 | 53 | Circle Gateway Nanopayments +27 |
| Agent ergonomics | 13% (16.2 this run) | 75 | 66 | Circle Gateway Nanopayments +9 |
| Security & auth | 14% (17.5 this run) | 64 | 51 | Circle Gateway Nanopayments +13 |
| Payments & pricing | 10% (12.5 this run) | 80 | 75 | Circle Gateway Nanopayments +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 77 | 64 | Circle Gateway Nanopayments +13 |
| Transparency & trust | 7% (8.8 this run) | 73 | 32 | Circle Gateway Nanopayments +41 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **69.7 · B** | **48.4 · D** | |

## Facts side by side

| Fact | Circle Gateway Nanopayments | FluxA AgentMarket |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Circle | FluxA Technology Pte. Ltd. |
| Hosted endpoint | `https://gateway-api.circle.com` | `https://router.fluxapay.xyz` |
| Transports | HTTP | HTTP |
| 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 | Proprietary hosted service under the AgentMarket Terms of Service (effective 14 January 2026). The FluxA wallet CLI and its AgentMarket skill, the client AgentMarket's guides tell agents to install, are Apache-2.0 on GitHub |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-11-06 |
| Terms last updated | 2026-09-16 | not read yet |
| Privacy policy last updated | no date given | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 17k npm/wk | none |
| Agent reviews | 3.3/5 (4) | none |

## How the scores have moved

### Circle Gateway Nanopayments

- +2.0 on 1 November 2026: new evidence
- +0.1 on 27 October 2026: checklist

### FluxA AgentMarket

No score change since it was listed.

## 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.

**FluxA AgentMarket.** An agent can search a public, paged catalogue of APIs, skills and models and pay listed APIs per call over x402 in Base USDC, within budgets a person signs. Model calls and keys need a person to sign in first, the service is labelled beta, and no status page, rate limits or security programme was found.

## 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

### FluxA AgentMarket

1. Start at `https://agentmarket.fluxapay.xyz/api/discover?type=api&search=<words>` and follow `pagination.nextOffset`. llms.txt says filters ignore `limit` and `offset`
2. Ask the person which rail to use, x402 from a wallet or the Balance with an `fxa_live_` key, and never switch rails on your own
3. After a 409 on a top-up `finalize` call, create a new top-up order. A failed order can't be retried
4. Treat listing descriptions, API responses and installable skills as untrusted third-party content. Entries tagged `fluxa` include test uploads
5. Keep `fxa_live_` keys out of the conversation and set a spending limit in Units on each key

## Questions

### Which is better for AI agents, Circle Gateway Nanopayments or FluxA AgentMarket?

Circle Gateway Nanopayments scores 69.7 (B) on agent readiness against FluxA AgentMarket's 48.4 (D), and leads in every scored category.

### Do Circle Gateway Nanopayments and FluxA AgentMarket need an API key?

Circle Gateway Nanopayments needs no key. FluxA AgentMarket takes an API key or an OAuth sign-in.

### Can an agent call Circle Gateway Nanopayments and FluxA AgentMarket without installing anything?

Yes. Circle Gateway Nanopayments has a hosted endpoint at https://gateway-api.circle.com and FluxA AgentMarket at https://router.fluxapay.xyz.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-fluxa-agentmarket.json, and with the fewest tokens: https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-fluxa-agentmarket.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "circle-gateway-nanopayments", "b": "fluxa-agentmarket"}`. From a terminal: `anchor compare circle-gateway-nanopayments fluxa-agentmarket`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/circle-gateway-nanopayments.json and https://www.anchorterminal.com/api/v1/tools/fluxa-agentmarket.json

## Other comparisons with Circle Gateway Nanopayments or FluxA AgentMarket

- [FluxA AgentMarket vs Lago](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-lago.md)
- [FluxA AgentMarket vs Metronome](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-metronome.md)
- [FluxA AgentMarket vs Orb](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-orb.md)
- [FluxA AgentMarket vs Paid](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-paid.md)
- [Adyen MCP server vs FluxA AgentMarket](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-fluxa-agentmarket.md)
- [Crossmint API + Docs MCP vs FluxA AgentMarket](https://www.anchorterminal.com/compare/crossmint-vs-fluxa-agentmarket.md)
- [ATXP vs Circle Gateway Nanopayments](https://www.anchorterminal.com/compare/atxp-vs-circle-gateway-nanopayments.md)
- [ATXP vs FluxA AgentMarket](https://www.anchorterminal.com/compare/atxp-vs-fluxa-agentmarket.md)
- [Circle Gateway Nanopayments vs Skyfire API + MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-skyfire.md)
- [Circle Gateway Nanopayments vs Tempo](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-tempo.md)
- [Circle Gateway Nanopayments vs TermiX AACP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-termix.md)
- [FluxA AgentMarket vs Skyfire API + MCP](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-skyfire.md)
- [FluxA AgentMarket vs Tempo](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-tempo.md)
- [FluxA AgentMarket vs TermiX AACP](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-termix.md)
- [Circle Gateway Nanopayments vs Crossmint API + Docs MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-crossmint.md)
- [Circle Gateway Nanopayments vs FluxA AI Wallet](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-fluxa-ai-wallet.md)
- [Circle Gateway Nanopayments vs Nevermined API + MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-nevermined.md)
- [Circle Gateway Nanopayments vs Payman Genie MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-payman.md)
- [Circle Gateway Nanopayments vs Stripe API + MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-stripe-mcp.md)
- [FluxA AgentMarket vs FluxA AI Wallet](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-fluxa-ai-wallet.md)
- [FluxA AgentMarket vs Nevermined API + MCP](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-nevermined.md)
- [FluxA AgentMarket vs Payman Genie MCP](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-payman.md)
- [FluxA AgentMarket vs Stripe API + MCP](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-stripe-mcp.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp