Niches · Pay-per-call protocols
Pay for one API call that answers 402 and get the response
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
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. No docs we read state these figures, so they don't count against a listing here.
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 4
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.
| Listing | Why |
|---|---|
| ACK-Pay (Agent Commerce Kit) D 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. source |
| L402 C 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. source |
| Machine Payments Protocol (MPP) A 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). source |
| x402 A 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). source |
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
The same as data: /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. Other jobs in this category: /api/v1/niches?category=pay-per-call.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.