{
  "data": {
    "a": {
      "slug": "circle-gateway-nanopayments",
      "name": "Circle Gateway Nanopayments",
      "vendor": "Circle",
      "vendorUrl": "https://www.circle.com",
      "kind": "http-api",
      "category": "payment-platforms",
      "summary": "Circle 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.",
      "url": "https://www.anchorterminal.com/tools/circle-gateway-nanopayments",
      "markdownUrl": "https://www.anchorterminal.com/tools/circle-gateway-nanopayments.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/circle-gateway-nanopayments.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/circle-gateway-nanopayments.json",
      "repo": "https://github.com/circlefin/evm-gateway-contracts",
      "license": "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",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://gateway-api.circle.com",
      "packages": [
        {
          "registry": "npm",
          "name": "@circle-fin/x402-batching"
        }
      ],
      "auth": "none",
      "authNotes": "No API key or account on the self-managed route. A buyer signs each payment as an EIP-3009 `TransferWithAuthorization` with an EOA private key, and a seller supplies only a receiving address. The SDK's facilitator client sends no credential by default and accepts optional headers. The OpenAPI file defines a Bearer key scheme and applies it to no operation. The Circle Wallets route in the buyer quickstart needs a Circle Console account, an API key and an entity secret. Smart contract accounts are not supported.",
      "pricing": "usage",
      "pricingNotes": "No per-payment fee or gas for a nanopayment, per the docs. The buyer pays chain gas once for the deposit. Crosschain withdrawals carry a 0.005% transfer fee plus a gas fee by source chain, from $0.001 to $1.00, and same-chain withdrawals carry no transfer fee. Testnets work with faucet USDC and no account. No subscription or card. The developer terms say Gateway fees are communicated through the API and may change (checked 2026-10-09).",
      "priceSummary": "0.01% fee",
      "where": "hosted",
      "x402": {
        "level": "partial",
        "evidence": "Circle runs the facilitator. Sellers using `createGatewayMiddleware` or `BatchFacilitatorClient` answer `402 Payment Required` with a `PAYMENT-REQUIRED` header and settle through `POST /v1/x402/settle` on gateway-api.circle.com, under the x402 `exact` scheme with `extra.name` set to `GatewayWalletBatched`. Circle's own API is not paid over x402 (https://developers.circle.com/gateway-nanopayments; https://developers.circle.com/openapi/gateway-nanopayments.yaml, checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 16895,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://developers.circle.com/gateway-nanopayments",
      "llmsTxt": "https://developers.circle.com/llms.txt",
      "openapi": "https://developers.circle.com/openapi/gateway-nanopayments.yaml",
      "capabilities": [
        "payments.x402",
        "payments.stablecoin"
      ],
      "tags": [
        "hosted",
        "usage-based",
        "x402",
        "facilitator",
        "stablecoins",
        "usdc",
        "micropayments",
        "batched-settlement",
        "non-custodial",
        "keyless",
        "openapi",
        "llms-txt",
        "typescript",
        "open-source-sdk"
      ],
      "lastRelease": "2026-09-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 67.6,
        "grade": "B",
        "agentReady": false,
        "rank": 247,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 5,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 75,
          "maintenance": 77,
          "payments": 80,
          "reliability": 56,
          "schema": 80,
          "security": 64,
          "transparency": 72
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": -3,
        "negativeNotes": [
          "26 August 2026. `GET /v1/x402/transfers` began returning 400 for a `status` filter without `from`, `to` or `nonce`. Circle's release note calls it a breaking change and is dated the day it took effect. No earlier notice was found in the release notes (https://developers.circle.com/release-notes/gateway-2026). Documented, so the smallest deduction."
        ],
        "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.",
        "bestFor": "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",
          "The batching contracts were audited by OtterSec (report dated 10 June 2026), and the Gateway contracts are Apache-2.0 on GitHub",
          "Deposits sit in a non-custodial contract, with a withdrawal path that needs no Circle API after a 7-day delay"
        ],
        "weaknesses": [
          "No rate limit, 429 guidance or SLA was found for the Gateway API in the reviewed documentation",
          "From 26 August 2026 a `status` filter alone on `GET /v1/x402/transfers` returns 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",
          "The official SDK is TypeScript only and no public source repository for it was found",
          "The error reference says the validity window must be at least 3 days. The seller quickstart and the SDK source say 7 days",
          "The developer terms let Circle change or discontinue Gateway without prior notice and change its fees at its discretion"
        ],
        "agentNotes": [
          "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",
          "Set `validBefore` at least 7 days ahead when signing by hand. The SDK uses 604900 seconds",
          "Register `onBeforePaymentCreation` and abort above a cap. `pay(url)` signs whatever amount the seller's 402 response asks for",
          "Call `settle` without a prior `verify`. Balance and nonce checks happen only at settle time",
          "Pass `from`, `to` or `nonce` whenever you filter transfers by `status`, and wait for `completed` before a dependent onchain step"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 67.6
          }
        ],
        "editorialScores": {
          "ergonomics": 75,
          "maintenance": 77,
          "payments": 80,
          "reliability": 56,
          "schema": 80,
          "security": 64,
          "transparency": 59
        },
        "provenanceScore": 84
      },
      "connect": {
        "install": "npm install @circle-fin/x402-batching"
      },
      "letme": {
        "capability": "https://letme.dev/payments.x402",
        "tool": "https://letme.dev/circle-gateway-nanopayments"
      },
      "sameCompany": [
        "circle-wallets"
      ],
      "area": "payments",
      "unitPrices": [
        {
          "item": "Batched nanopayment",
          "unit": "tx",
          "usd": 0,
          "note": "no per-payment fee or gas for buyer or seller, per the docs. The deposit costs chain gas once"
        },
        {
          "item": "Crosschain withdrawal transfer fee",
          "unit": "pct",
          "usd": 0.005,
          "note": "0.5 basis points. Not charged on same-chain withdrawals"
        },
        {
          "item": "Gateway gas fee, Base as source chain",
          "unit": "tx",
          "usd": 0.01,
          "note": "by source chain, from $0.001 on Sei and Unichain to $1.00 on Ethereum"
        },
        {
          "item": "Forwarding Service fee",
          "unit": "tx",
          "usd": 0.05,
          "note": "optional, plus a forwarding gas fee"
        }
      ],
      "provenance": {
        "legalEntity": "Circle Technology Services, LLC",
        "domain": "circle.com",
        "domainRegistered": "1999-04-09",
        "endpointOnVendorDomain": true,
        "terms": "https://console.circle.com/legal/developer-terms",
        "privacy": "https://www.circle.com/legal/privacy-policy",
        "statusPage": "https://status.circle.com",
        "changelog": "https://developers.circle.com/release-notes/gateway-2026",
        "securityTxt": "none",
        "checked": "2026-10-09",
        "notes": [
          "The Developer Terms of Service (last updated 16 September 2026) are a contract with Circle Technology Services, LLC and name Gateway as a Permissionless Product. They say committed USDC stays the user's property and that Circle may modify or discontinue Permissionless Products without prior notice.",
          "The Privacy Policy (last updated 16 September 2026) is from Circle Internet Group, Inc. and its subsidiaries and links a sub-processor list last updated 22 December 2025.",
          "The API hosts are gateway-api.circle.com and gateway-api-testnet.circle.com, on the vendor's domain.",
          "status.circle.com is an Atlassian Statuspage with Circle Gateway components for each chain. It has no component named for nanopayments or x402.",
          "www.circle.com/.well-known/security.txt answered 404. The SECURITY.md in github.com/circlefin/skills names a bug bounty programme at hackerone.com/circle-bbp.",
          "RDAP for circle.com gives a registration date of 1999-04-09."
        ],
        "score": 84
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/circle-gateway-nanopayments.json",
      "live": {
        "slug": "circle-gateway-nanopayments",
        "probe": {
          "target": "https://gateway-api.circle.com",
          "method": "get",
          "lastAt": "2026-10-10T02:54:50.922122134Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 152,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 147,
          "p95ms24h": 1147,
          "samples24h": 115,
          "samples30d": 115,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 85,
              "ok": 85
            },
            {
              "date": "2026-10-10",
              "probes": 30,
              "ok": 30
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.circle.com",
          "indicator": "major",
          "summary": "Partial System Outage",
          "checkedAt": "2026-10-10T02:49:58.631998243Z"
        },
        "versions": [
          {
            "registry": "npm",
            "name": "@circle-fin/x402-batching",
            "version": "3.5.0",
            "seenAt": "2026-10-09T16:45:07.952774661Z"
          }
        ],
        "githubStars": 10,
        "npmWeekly": 16895,
        "pages": [
          {
            "url": "https://developers.circle.com/release-notes/gateway-2026",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-09T18:35:33.753415397Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "6ef7c495e029"
          },
          {
            "url": "https://www.circle.com/legal/privacy-policy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-09T18:49:03.821925211Z",
            "changedAt": "2026-10-09T18:49:03.821925211Z",
            "fingerprint": "0b638ffd6762"
          },
          {
            "url": "https://console.circle.com/legal/developer-terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-09T18:34:17.88745813Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "06bed5753aaf"
          }
        ],
        "updatedAt": "2026-10-10T02:54:50.922122134Z"
      }
    },
    "answer": "Tempo scores 76.6 (BB) on agent readiness against Circle Gateway Nanopayments's 67.6 (B), and leads in 5 of 7 scored categories. Circle Gateway Nanopayments leads on transparency \u0026 trust.",
    "b": {
      "slug": "tempo",
      "name": "Tempo",
      "vendor": "Tempo",
      "vendorUrl": "https://tempo.xyz",
      "kind": "http-api",
      "category": "payment-platforms",
      "summary": "A payments-first Layer 1 chain incubated by Stripe and Paradigm, live on mainnet since 2026-03-18.",
      "url": "https://www.anchorterminal.com/tools/tempo",
      "markdownUrl": "https://www.anchorterminal.com/tools/tempo.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tempo.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tempo.json",
      "repo": "https://github.com/tempoxyz/tempo",
      "license": "MIT OR Apache-2.0",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.tempo.xyz/v1",
      "packages": [
        {
          "registry": "npm",
          "name": "viem"
        },
        {
          "registry": "npm",
          "name": "mppx"
        },
        {
          "registry": "pypi",
          "name": "pympp"
        }
      ],
      "auth": "mixed",
      "authNotes": "Public RPC (rpc.tempo.xyz) and most read endpoints of api.tempo.xyz answer without a key, within a per-IP limit. Those same endpoints accept MPP payment credentials (`Authorization: Payment`) instead of a key. Project-scoped API keys (`tempo:sk:` for production, `tempo_sandbox:sk:` for non-mainnet) carry scopes such as `data:read`, optional IP allowlists, and are required for endpoints such as webhook management. Payments are signed by the paying wallet.",
      "pricing": "usage",
      "pricingNotes": "No platform fee for using the chain. Transaction fees are paid in any supported USD stablecoin, with a dynamic base fee capped at about $0.0006 for a 50,000-gas transfer and a floor around $0.00003. Fees can be sponsored by a fee payer, billed through the Tempo API Console. API calls are free within quota; over quota, anonymous endpoints answer 402 and can be paid per request over MPP, and keyed usage is billed in the console, with no published price for either. Stripe charges its own fees when it settles MPP payments on Tempo (https://tempo.xyz/developers/docs/protocol/fees).",
      "priceSummary": "$0.0006 / tx",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "Tempo's own API takes MPP, not x402, on its anonymous endpoints (https://tempo.xyz/developers/docs/api/rate-limits). MPP itself added acceptance of x402 exact payments on EVM chains in June 2026 (https://mpp.dev/blog/evm-x402-support).",
        "endpoints": []
      },
      "toolCount": 4,
      "popularity": {
        "githubStars": 1029,
        "npmWeekly": 209447,
        "pypiWeekly": null,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://tempo.xyz/developers/docs",
      "llmsTxt": "https://tempo.xyz/developers/llms.txt",
      "openapi": "https://api.tempo.xyz/openapi.json",
      "capabilities": [
        "payments.stablecoin",
        "payments.metering"
      ],
      "tags": [
        "hosted",
        "open-source",
        "mcp",
        "llms-txt",
        "openapi",
        "stablecoin",
        "typescript",
        "free-tier"
      ],
      "lastRelease": "2026-09-24",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 76.6,
        "grade": "BB",
        "agentReady": true,
        "rank": 27,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 2,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 78,
          "maintenance": 88,
          "payments": 80,
          "reliability": 71,
          "schema": 88,
          "security": 70,
          "transparency": 63
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-01"
        },
        "negative": 0,
        "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.",
        "bestFor": "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",
          "Published rate limits with `RateLimit-*` and `Retry-After` headers, one error envelope and cursor pagination",
          "Open-source node under MIT or Apache-2.0 with seven releases since 22 July and a dated changelog"
        ],
        "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",
          "Breaking network upgrades every two to four weeks, with mainnet activation as soon as three days after release",
          "No published price for API usage or per-request MPP payments"
        ],
        "agentNotes": [
          "Send `Authorization: Payment` up front to pay per request; a 402 after quota carries the challenge in `WWW-Authenticate`",
          "Read `RateLimit-Remaining` and `RateLimit-Reset` rather than hardcoding the 20 or 100 a minute defaults",
          "Pass `chainId=testnet` with a sandbox key; a sandbox key sent to mainnet is ignored and the call drops to the anonymous limit",
          "Use `tempo request --dry-run` before paying an MPP endpoint to see the cost",
          "Branch on `error.code`, never on `error.message`"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 8,
        "avgRating": 3.1,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 76.6
          }
        ],
        "editorialScores": {
          "ergonomics": 78,
          "maintenance": 88,
          "payments": 80,
          "reliability": 71,
          "schema": 88,
          "security": 70,
          "transparency": 50
        },
        "provenanceScore": 76
      },
      "connect": {
        "http": "curl https://api.tempo.xyz/v1/blocks",
        "claudeCode": "claude mcp add --transport http tempo https://mcp.tempo.xyz",
        "config": {
          "mcpServers": {
            "tempo": {
              "url": "https://mcp.tempo.xyz"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/payments.stablecoin",
        "tool": "https://letme.dev/tempo"
      },
      "area": "payments",
      "unitPrices": [
        {
          "item": "Transfer fee cap",
          "unit": "tx",
          "usd": 0.0006,
          "note": "base-fee cap for a 50,000-gas transfer; floor around $0.00003"
        }
      ],
      "provenance": {
        "legalEntity": "Tempo Labs Inc.",
        "domain": "tempo.xyz",
        "domainRegistered": "2017-11-09",
        "domainNote": "tempo.xyz was registered in 2017, before Tempo was founded in 2025, and transferred in September 2025. The privacy policy names Tempo Labs Inc. dba Tempo; no terms of service page was found.",
        "endpointOnVendorDomain": true,
        "terms": "",
        "privacy": "https://tempo.xyz/privacy-policy/",
        "statusPage": "https://status.tempo.xyz",
        "changelog": "https://tempo.xyz/developers/docs/changelog",
        "securityTxt": "none",
        "checked": "2026-09-30",
        "score": 76
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/tempo.json",
      "live": {
        "slug": "tempo",
        "probe": {
          "target": "https://api.tempo.xyz/v1",
          "method": "get",
          "lastAt": "2026-10-10T02:55:12.957983471Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 190,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 213,
          "p95ms24h": 364,
          "samples24h": 249,
          "samples30d": 2466,
          "days": [
            {
              "date": "2026-09-30",
              "probes": 35,
              "ok": 35
            },
            {
              "date": "2026-10-01",
              "probes": 276,
              "ok": 276
            },
            {
              "date": "2026-10-02",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-03",
              "probes": 271,
              "ok": 271
            },
            {
              "date": "2026-10-04",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-05",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-06",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-07",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-08",
              "probes": 268,
              "ok": 268
            },
            {
              "date": "2026-10-09",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-10",
              "probes": 30,
              "ok": 30
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.tempo.xyz",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-10T00:51:19.580977221Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "tempoxyz/tempo",
            "version": "tempo-primitives@1.16.0",
            "released": "2026-10-06",
            "seenAt": "2026-10-09T17:23:58.10804858Z"
          },
          {
            "registry": "npm",
            "name": "mppx",
            "version": "0.13.4",
            "seenAt": "2026-10-09T17:23:56.599451125Z"
          },
          {
            "registry": "npm",
            "name": "viem",
            "version": "2.57.4",
            "seenAt": "2026-10-09T17:23:55.790295075Z"
          },
          {
            "registry": "pypi",
            "name": "pympp",
            "version": "0.11.0",
            "released": "2026-08-28",
            "seenAt": "2026-10-09T17:23:57.984335557Z"
          }
        ],
        "githubStars": 1030,
        "npmWeekly": 6495477,
        "pypiWeekly": 420380,
        "securityTxt": {
          "url": "https://tempo.xyz/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-09T15:39:17.658003872Z"
        },
        "llmsTxt": {
          "url": "https://tempo.xyz/developers/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-09T14:02:53.270049124Z"
        },
        "domain": {
          "domain": "tempo.xyz",
          "registered": "2017-11-09",
          "source": "https://rdap.centralnic.com/xyz/domain/tempo.xyz",
          "checkedAt": "2026-10-04T13:08:55.633115434Z"
        },
        "pages": [
          {
            "url": "https://tempo.xyz/developers/docs/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-09T18:46:37.684534437Z",
            "changedAt": "2026-10-09T18:46:37.684534437Z",
            "fingerprint": "c9d51740aad3"
          },
          {
            "url": "https://tempo.xyz/privacy-policy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-09T18:46:40.193474976Z",
            "changedAt": "2026-10-07T18:10:02.234680476Z",
            "fingerprint": "ab4f2727a67b"
          }
        ],
        "updatedAt": "2026-10-10T02:55:12.957983471Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Circle",
        "b": "Tempo",
        "name": "Vendor"
      },
      {
        "a": "https://gateway-api.circle.com",
        "b": "https://api.tempo.xyz/v1",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP, Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "None",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "payer tooling only",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "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",
        "b": "MIT OR Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "4",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-09-16",
        "b": "2026-09-24",
        "name": "Last release"
      },
      {
        "a": "2026-09-16",
        "b": "no document linked",
        "name": "Terms last updated"
      },
      {
        "a": "no date given",
        "b": "2026-07-31",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "17k npm/wk",
        "b": "1k stars, 209k npm/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3.1/5 (8)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Tempo scores 76.6 (BB) on agent readiness against Circle Gateway Nanopayments's 67.6 (B), and leads in 5 of 7 scored categories. Circle Gateway Nanopayments leads on transparency \u0026 trust.",
        "question": "Which is better for AI agents, Circle Gateway Nanopayments or Tempo?"
      },
      {
        "answer": "Circle Gateway Nanopayments needs no key. Tempo takes an API key or an OAuth sign-in.",
        "question": "Do Circle Gateway Nanopayments and Tempo need an API key?"
      },
      {
        "answer": "Yes. Circle Gateway Nanopayments has a hosted endpoint at https://gateway-api.circle.com and Tempo at https://api.tempo.xyz/v1.",
        "question": "Can an agent call Circle Gateway Nanopayments and Tempo without installing anything?"
      },
      {
        "answer": "No open-source release is listed for Circle Gateway Nanopayments. Tempo is open source (MIT OR Apache-2.0).",
        "question": "Are Circle Gateway Nanopayments and Tempo open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Transparency \u0026 trust, 72 against 63"
        ],
        "also": [
          "No key needed to call it"
        ],
        "goodFor": "Sellers charging fractions of a cent per API call and agents making many small payments from one prefunded balance on EVM chains.",
        "slug": "circle-gateway-nanopayments",
        "watchFor": "No rate limit, 429 guidance or SLA was found for the Gateway API in the reviewed documentation"
      },
      {
        "aheadOn": [
          "Reliability, 71 against 56",
          "Schema \u0026 documentation, 88 against 80",
          "Security \u0026 auth, 70 against 64",
          "Maintenance \u0026 community, 88 against 77"
        ],
        "also": [
          "Agent-ready, a grade of BB or better",
          "Open source",
          "No incidents deducted, where Circle Gateway Nanopayments loses 3 points for them"
        ],
        "goodFor": "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.",
        "slug": "tempo",
        "watchFor": "The API versioning page says endpoints are not yet stable and may change without notice"
      }
    ],
    "job": {
      "capability": "payments.stablecoin",
      "name": "Stablecoin payments"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/lago-vs-tempo.json",
        "title": "Lago vs Tempo",
        "url": "https://www.anchorterminal.com/compare/lago-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/metronome-vs-tempo.json",
        "title": "Metronome vs Tempo",
        "url": "https://www.anchorterminal.com/compare/metronome-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/orb-vs-tempo.json",
        "title": "Orb vs Tempo",
        "url": "https://www.anchorterminal.com/compare/orb-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/paid-vs-tempo.json",
        "title": "Paid vs Tempo",
        "url": "https://www.anchorterminal.com/compare/paid-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/atxp-vs-circle-gateway-nanopayments.json",
        "title": "ATXP vs Circle Gateway Nanopayments",
        "url": "https://www.anchorterminal.com/compare/atxp-vs-circle-gateway-nanopayments"
      },
      {
        "json": "https://www.anchorterminal.com/compare/atxp-vs-tempo.json",
        "title": "ATXP vs Tempo",
        "url": "https://www.anchorterminal.com/compare/atxp-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-skyfire.json",
        "title": "Circle Gateway Nanopayments vs Skyfire API + MCP",
        "url": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-skyfire"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crossmint-vs-tempo.json",
        "title": "Crossmint API + Docs MCP vs Tempo",
        "url": "https://www.anchorterminal.com/compare/crossmint-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nevermined-vs-tempo.json",
        "title": "Nevermined API + MCP vs Tempo",
        "url": "https://www.anchorterminal.com/compare/nevermined-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/skyfire-vs-tempo.json",
        "title": "Skyfire API + MCP vs Tempo",
        "url": "https://www.anchorterminal.com/compare/skyfire-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo.json",
        "title": "Stripe API + MCP vs Tempo",
        "url": "https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-crossmint.json",
        "title": "Circle Gateway Nanopayments vs Crossmint API + Docs MCP",
        "url": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-crossmint"
      },
      {
        "json": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-nevermined.json",
        "title": "Circle Gateway Nanopayments vs Nevermined API + MCP",
        "url": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-nevermined"
      },
      {
        "json": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-payman.json",
        "title": "Circle Gateway Nanopayments vs Payman Genie MCP",
        "url": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-payman"
      },
      {
        "json": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-stripe-mcp.json",
        "title": "Circle Gateway Nanopayments vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-stripe-mcp"
      }
    ],
    "scores": [
      {
        "by": 15,
        "circle-gateway-nanopayments": 56,
        "edge": "tempo",
        "key": "reliability",
        "name": "Reliability",
        "tempo": 71,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 8,
        "circle-gateway-nanopayments": 80,
        "edge": "tempo",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "tempo": 88,
        "weight": 13
      },
      {
        "by": 3,
        "circle-gateway-nanopayments": 75,
        "edge": "tempo",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "tempo": 78,
        "weight": 13
      },
      {
        "by": 6,
        "circle-gateway-nanopayments": 64,
        "edge": "tempo",
        "key": "security",
        "name": "Security \u0026 auth",
        "tempo": 70,
        "weight": 14
      },
      {
        "by": 0,
        "circle-gateway-nanopayments": 80,
        "edge": "",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "tempo": 80,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 11,
        "circle-gateway-nanopayments": 77,
        "edge": "tempo",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "tempo": 88,
        "weight": 7
      },
      {
        "by": 9,
        "circle-gateway-nanopayments": 72,
        "edge": "circle-gateway-nanopayments",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "tempo": 63,
        "weight": 7
      }
    ],
    "summary": "Tempo scores 76.6 (BB) on agent readiness against Circle Gateway Nanopayments's 67.6 (B), and leads in 5 of 7 scored categories. Circle Gateway Nanopayments leads on transparency \u0026 trust. Both do stablecoin payments.",
    "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.",
      "tempo": "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-tempo",
    "json": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-tempo.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-tempo.md",
    "slim": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-tempo.min.md"
  },
  "markdown": "Tempo scores 76.6 (BB) on agent readiness against Circle Gateway Nanopayments's 67.6 (B), and leads in 5 of 7 scored categories. Circle Gateway Nanopayments leads on transparency \u0026 trust. Both do stablecoin payments.\n\n- Circle Gateway Nanopayments: grade B, 67.6/100, rank #247 of 950. Markdown https://www.anchorterminal.com/tools/circle-gateway-nanopayments.md · JSON https://www.anchorterminal.com/api/v1/tools/circle-gateway-nanopayments.json\n- Tempo: grade BB, 76.6/100, rank #27 of 950. Markdown https://www.anchorterminal.com/tools/tempo.md · JSON https://www.anchorterminal.com/api/v1/tools/tempo.json\n- Best payment and monetisation platforms for AI agents: https://www.anchorterminal.com/best/payment-platforms/index.md\n- All 76 platforms comparisons: https://www.anchorterminal.com/compare/payment-platforms/index.md\n\n## Which one, for what\n\n### Circle Gateway Nanopayments (B)\n\nGood for: Sellers charging fractions of a cent per API call and agents making many small payments from one prefunded balance on EVM chains.\n\nAhead on:\n- Transparency \u0026 trust, 72 against 63\n\nAlso in its favour:\n- No key needed to call it\n\nWatch for: No rate limit, 429 guidance or SLA was found for the Gateway API in the reviewed documentation\n\n### Tempo (BB)\n\nGood 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.\n\nAhead on:\n- Reliability, 71 against 56\n- Schema \u0026 documentation, 88 against 80\n- Security \u0026 auth, 70 against 64\n- Maintenance \u0026 community, 88 against 77\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Open source\n- No incidents deducted, where Circle Gateway Nanopayments loses 3 points for them\n\nWatch for: The API versioning page says endpoints are not yet stable and may change without notice\n\n\n## Score by category\n\n| Category | Weight | Circle Gateway Nanopayments | Tempo | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 56 | 71 | Tempo +15 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 88 | Tempo +8 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 78 | Tempo +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 64 | 70 | Tempo +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 80 | 80 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 77 | 88 | Tempo +11 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 63 | Circle Gateway Nanopayments +9 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **67.6 · B** | **76.6 · BB** | |\n\n## Facts side by side\n\n| Fact | Circle Gateway Nanopayments | Tempo |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Circle | Tempo |\n| Hosted endpoint | `https://gateway-api.circle.com` | `https://api.tempo.xyz/v1` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | None | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | payer tooling only | no |\n| 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 OR Apache-2.0 |\n| Tools exposed | none | 4 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-16 | 2026-09-24 |\n| Terms last updated | 2026-09-16 | no document linked |\n| Privacy policy last updated | no date given | 2026-07-31 |\n| Customer content may train models | not found in the text |  |\n| Terms restrict automated access | not found in the text |  |\n| Terms restrict benchmarking | yes |  |\n| Terms or service can change without notice | yes |  |\n| Arbitration or class-action waiver | yes |  |\n| Popularity | 17k npm/wk | 1k stars, 209k npm/wk |\n| Agent reviews | none | 3.1/5 (8) |\n\n## Verdicts\n\n**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.\n\n**Tempo.** 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.\n\n## Before you call either\n\n### Circle Gateway Nanopayments\n\n1. 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\n2. Set `validBefore` at least 7 days ahead when signing by hand. The SDK uses 604900 seconds\n3. Register `onBeforePaymentCreation` and abort above a cap. `pay(url)` signs whatever amount the seller's 402 response asks for\n4. Call `settle` without a prior `verify`. Balance and nonce checks happen only at settle time\n5. Pass `from`, `to` or `nonce` whenever you filter transfers by `status`, and wait for `completed` before a dependent onchain step\n\n### Tempo\n\n1. Send `Authorization: Payment` up front to pay per request; a 402 after quota carries the challenge in `WWW-Authenticate`\n2. Read `RateLimit-Remaining` and `RateLimit-Reset` rather than hardcoding the 20 or 100 a minute defaults\n3. Pass `chainId=testnet` with a sandbox key; a sandbox key sent to mainnet is ignored and the call drops to the anonymous limit\n4. Use `tempo request --dry-run` before paying an MPP endpoint to see the cost\n5. Branch on `error.code`, never on `error.message`\n\n## Questions\n\n### Which is better for AI agents, Circle Gateway Nanopayments or Tempo?\n\nTempo scores 76.6 (BB) on agent readiness against Circle Gateway Nanopayments's 67.6 (B), and leads in 5 of 7 scored categories. Circle Gateway Nanopayments leads on transparency \u0026 trust.\n\n### Do Circle Gateway Nanopayments and Tempo need an API key?\n\nCircle Gateway Nanopayments needs no key. Tempo takes an API key or an OAuth sign-in.\n\n### Can an agent call Circle Gateway Nanopayments and Tempo without installing anything?\n\nYes. Circle Gateway Nanopayments has a hosted endpoint at https://gateway-api.circle.com and Tempo at https://api.tempo.xyz/v1.\n\n### Are Circle Gateway Nanopayments and Tempo open source?\n\nNo open-source release is listed for Circle Gateway Nanopayments. Tempo is open source (MIT OR Apache-2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-tempo.json, and with the fewest tokens: https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-tempo.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"circle-gateway-nanopayments\", \"b\": \"tempo\"}`. From a terminal: `anchor compare circle-gateway-nanopayments tempo`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/circle-gateway-nanopayments.json and https://www.anchorterminal.com/api/v1/tools/tempo.json\n\n## Other comparisons with Circle Gateway Nanopayments or Tempo\n\n- [Lago vs Tempo](https://www.anchorterminal.com/compare/lago-vs-tempo.md)\n- [Metronome vs Tempo](https://www.anchorterminal.com/compare/metronome-vs-tempo.md)\n- [Orb vs Tempo](https://www.anchorterminal.com/compare/orb-vs-tempo.md)\n- [Paid vs Tempo](https://www.anchorterminal.com/compare/paid-vs-tempo.md)\n- [ATXP vs Circle Gateway Nanopayments](https://www.anchorterminal.com/compare/atxp-vs-circle-gateway-nanopayments.md)\n- [ATXP vs Tempo](https://www.anchorterminal.com/compare/atxp-vs-tempo.md)\n- [Circle Gateway Nanopayments vs Skyfire API + MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-skyfire.md)\n- [Crossmint API + Docs MCP vs Tempo](https://www.anchorterminal.com/compare/crossmint-vs-tempo.md)\n- [Nevermined API + MCP vs Tempo](https://www.anchorterminal.com/compare/nevermined-vs-tempo.md)\n- [Skyfire API + MCP vs Tempo](https://www.anchorterminal.com/compare/skyfire-vs-tempo.md)\n- [Stripe API + MCP vs Tempo](https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo.md)\n- [Circle Gateway Nanopayments vs Crossmint API + Docs MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-crossmint.md)\n- [Circle Gateway Nanopayments vs Nevermined API + MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-nevermined.md)\n- [Circle Gateway Nanopayments vs Payman Genie MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-payman.md)\n- [Circle Gateway Nanopayments vs Stripe API + MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-stripe-mcp.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-10",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Circle Gateway Nanopayments vs Tempo",
        "url": ""
      }
    ],
    "description": "Tempo scores 76.6 (BB) to Circle Gateway Nanopayments's 67.6 (B) for stablecoin payments. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Circle Gateway Nanopayments B 67.6",
      "Tempo BB 76.6",
      "scores"
    ],
    "h1": "Circle Gateway Nanopayments vs Tempo",
    "image": "https://www.anchorterminal.com/assets/og/compare-circle-gateway-nanopayments-vs-tempo.png",
    "path": "/compare/circle-gateway-nanopayments-vs-tempo",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Circle Gateway Nanopayments vs Tempo for AI agents (2026)",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-tempo"
  },
  "tokens": {
    "markdown": 2350,
    "slim": 780
  },
  "version": 1
}