{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/pay-per-call.pay-and-retry/",
    "json": "https://www.anchorterminal.com/niches/pay-per-call.pay-and-retry/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/pay-per-call.pay-and-retry/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/pay-per-call.pay-and-retry/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 | 4 | 27 | 30 | 8 |\n\n## What counts as done\n\nThe agent parses the 402, pays once in an asset it holds, retries the same request (including POST with a body) and receives a 2xx response with a receipt or transaction reference, without a person stepping in.\n\nMeasured, for our own tests: within 2 calls and 10 seconds for a single payment under 1 USD.\n\nHow agents ask for it: call this paid API; get the data even if it costs a few cents; use this x402 endpoint; pay the invoice and fetch the result\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- **ACK-Pay (Agent Commerce Kit) (Catena Labs, Inc.)**: A server returns a signed Payment Request with options (USDC on Base, Stripe and others), the client pays through the named Payment Service and retries with a receipt credential. The docs use example.com services and name no public Payment or Receipt Service to pay through.\n- **L402 (Lightning Labs, Inc.)**: The 402 carries a macaroon and BOLT 11 invoice, the client pays for the preimage and retries with Authorization: L402 macaroon:preimage, and lnget supports -X POST -d. An open lnget issue shows a POST with a body never invoking payment (acc-18), and lnget needs the agent's own lnd node.\n- **Machine Payments Protocol (MPP) (Tempo and Stripe)**: A server answers 402 with WWW-Authenticate: Payment naming method, intent and request; mppx pays Tempo, Stripe card tokens and other methods and returns a Payment-Receipt with a reference. mppx had a critical payment-bypass advisory in March 2026, and 13 of 25 directory services did not respond when tested (acc-07).\n- **x402 (x402, a Series of LF Projects, LLC)**: Clients decode PAYMENT-REQUIRED, sign, retry with PAYMENT-SIGNATURE (POST shown) and read PAYMENT-RESPONSE with the transaction hash. Open issues report 402 headers past Node's 16 KB limit (acc-11) and a tutorial facilitator on legacy network ids (acc-15), and one payer's USDC sat on the wrong network (acc-04).\n\n## What stops agents finishing\n\n- agent holds the asset on a different chain or rail than the seller accepts\n- challenge header larger than the client HTTP library allows\n- client cannot parse a challenge variant (token= against macaroon=, LSAT against L402)\n- hosted facilitator lags the spec or needs KYC\n\n## Around it\n\nBefore: search.find-api, pay-per-call.discover-payable-service, agent-wallets.fund-and-cap. After: document-extraction.parse-response, pay-per-call.settle-and-prove.\n\n## Where this comes from\n\nWeight 30 of 100 in Pay-per-call protocols: 8 of 25 accounts (buyers paying or failing to pay a 402); the most common first-hand job across the x402, MPP and L402 threads and issues\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/pay-per-call.pay-and-retry.json, or the MCP tool get_use_case with id pay-per-call.pay-and-retry. 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": "Pay for one API call that answers 402 and get the response",
        "url": ""
      }
    ],
    "description": "Pay for one API call that answers 402 and get the response: 0 companies fully do it, 4 with a limit, 27 carry the tag. Every listing in Pay-per-call protocols with the reason and a source.",
    "facts": null,
    "h1": "Pay for one API call that answers 402 and get the response",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/pay-per-call.pay-and-retry/",
    "published": "",
    "section": "agents",
    "title": "Pay for one API call that answers 402 and get the response | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/pay-per-call.pay-and-retry/"
  },
  "tokens": {
    "markdown": 1000,
    "slim": 280
  },
  "version": 1
}
