# Pay for one API call that answers 402 and get the response

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

- Canonical: https://www.anchorterminal.com/niches/pay-per-call.pay-and-retry/
- Markdown: https://www.anchorterminal.com/niches/pay-per-call.pay-and-retry/index.md (~1,000 tokens)
- Slim: https://www.anchorterminal.com/niches/pay-per-call.pay-and-retry/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/pay-per-call.pay-and-retry/index.json (this page as data, same URL with Accept: application/json)
- 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-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 4 | 27 | 30 | 8 |

## What counts as done

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

Measured, for our own tests: within 2 calls and 10 seconds for a single payment under 1 USD.

How 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

## Does the job, with a limit

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

- **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.
- **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.
- **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).
- **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).

## What stops agents finishing

- agent holds the asset on a different chain or rail than the seller accepts
- challenge header larger than the client HTTP library allows
- client cannot parse a challenge variant (token= against macaroon=, LSAT against L402)
- hosted facilitator lags the spec or needs KYC

## Around it

Before: 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.

## Where this comes from

Weight 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

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

---

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