{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/payment-platforms.charge-agents-per-call/",
    "json": "https://www.anchorterminal.com/niches/payment-platforms.charge-agents-per-call/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/payment-platforms.charge-agents-per-call/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/payment-platforms.charge-agents-per-call/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 7 | 25 | 17 | 4 |\n\n## What counts as done\n\nAgents using a stock x402 or MPP client (or the platform's documented token) can pay without an account, the seller is paid once per delivered call, funds settle to the seller in a stated time, and onboarding steps and approvals are documented.\n\nHow agents ask for it: let agents pay for my API; charge per MCP tool call; accept x402 and MPP; sell to bots\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **ATXP (Circuit \u0026 Chisel, Inc.)**: @atxp/express's requirePayment prices each MCP tool call in USDC with no user accounts, and earnings show in the account portal. Payers need an ATXP account (an x402 wrapper package exists), and no settlement time or seller fee is stated.\n- **Circle Gateway Nanopayments (Circle Technology Services, LLC)**: createGatewayMiddleware and gateway.require() price routes and answer 402, settling each authorisation with Gateway, and transfers carry a status and transaction hash. Buyers need a prefunded Gateway balance, and onchain settlement is 'periodic' with no stated time before seller funds are withdrawable.\n- **FluxA AgentMarket (FluxA Technology Pte. Ltd.)**: llms.txt says a merchant account can publish an API as a paid x402 endpoint over HTTP, but the publishing guide sits under /console/, which robots.txt disallows, so onboarding, settlement time and payout were not read.\n- **Nevermined API + MCP (Nevermined AG)**: Merchants are paid per call at 1 per cent (stablecoin) or 2 per cent (card) from settlement, but an open conformance report on payments 1.13.0 shows lost-response retries charging twice and most settle failures delivering the resource unpaid (acc-16).\n- **Skyfire API + MCP (Skyfire Systems Inc.)**: Sellers charge a buyer's pay token up to its committed amount with payment guaranteed, settling within about 51 hours (sooner past 1 USD). Only Skyfire tokens work, not stock x402 or MPP, seller services need approval, and one builder was still waiting (acc-17).\n- **Stripe API + MCP (Stripe, LLC)**: Machine payments accept stock MPP and x402 clients and settle to the Stripe balance. Stablecoin acceptance needs Stripe's review and excludes New York, card tokens have a 0.50 USD minimum, x402 mainnet needs a CDP facilitator account, and payout timing 'varies by network'.\n- **Tempo (Tempo Labs Inc.)**: A seller configures an MPP server with recipient, currency and network and any MPP client pays without an account, with a Payment-Receipt returned. The guide leaves retry deduplication to the seller (a receipt covers payment, not delivery), and no seller-side settlement time was read beyond sub-second finality in the index.\n\n- not this job: Adyen MCP server (Adyen N.V.): No x402, MPP or agent token; Adyen's checkout here is sessions and payment links for card and local methods.\n- not this job: Crossmint API + Docs MCP (Crossmint, Inc.): Crossmint is the buyer side for x402 and MPP: Agent Wallets pay endpoints, and no seller paywall, facilitator or settlement route is documented. The n8n node's README describes wallets and checkout, not a paywall.\n- not this job: Lago (Get Lago Corp.): Lago bills a seller's own customers on plans; no x402, MPP or agent payment acceptance.\n- not this job: Metronome (Stripe, LLC): Metronome bills contracted customers on invoices; no x402, MPP or per-call agent payment acceptance.\n- not this job: Orb (Orb, Inc.): No x402 or MPP. pay_invoice can take a Stripe shared payment token, which pays an issued invoice, not a per-call charge.\n- not this job: Paid (Agent Paid Limited): No x402, MPP or agent token; Paid bills a seller's customers through credits, invoices and Stripe checkout.\n- not this job: Payman Genie MCP (Payman AI, Inc.): Genie acts for a person paying from their own accounts; the bridge README describes no seller-side acceptance of x402, MPP or agent payments.\n- not this job: PayPal MCP server (PayPal, Inc.): No x402, MPP or agent payment scheme; orders and invoices are for buyers with PayPal or card checkout.\n- not this job: TermiX AACP (TermiX): Settlement uses TermiX's own escrow contracts per order; no x402 or MPP, so a stock client cannot pay per call.\n\n## What stops agents finishing\n\n- stablecoin acceptance or a bot-friendly merchant account needs manual approval\n- card minimum of 0.50 USD rules out per-call card charges\n- own scheme a stock x402 or MPP client cannot pay\n\n## Around it\n\nBefore: pay-per-call.charge-for-endpoint. After: payment-platforms.meter-and-invoice, accounting.record-revenue.\n\n## Where this comes from\n\nWeight 17 of 100 in Payment \u0026 monetisation platforms: 4 of 23 accounts (acc-08, acc-16, acc-17, acc-18); seller-side x402 accounts sit in the pay-per-call map\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/payment-platforms.charge-agents-per-call.json, or the MCP tool get_use_case with id payment-platforms.charge-agents-per-call. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Accept payments from agents per call or per tool",
        "url": ""
      }
    ],
    "description": "Accept payments from agents per call or per tool: 0 companies fully do it, 7 with a limit, 25 carry the tag. Every listing in Payment \u0026 monetisation platforms with the reason and a source.",
    "facts": null,
    "h1": "Accept payments from agents per call or per tool",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/payment-platforms.charge-agents-per-call/",
    "published": "",
    "section": "agents",
    "title": "Accept payments from agents per call or per tool | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/payment-platforms.charge-agents-per-call/"
  },
  "tokens": {
    "markdown": 1500,
    "slim": 330
  },
  "version": 1
}
