Niches · Pay-per-call protocols

Confirm a payment settled, recover an unknown outcome and keep a receipt

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

0companies, full fit
4companies, fit with a limit
24companies carry the tag
12share of the category's work
3first-hand accounts

What counts as done

The agent can tell from documented fields whether the payment settled, look it up by transaction or idempotency key before paying again, and keep a receipt a third party can verify (transaction hash, preimage or signed credential).

How agents ask for it: did that payment go through, retry without paying twice, show me the receipts for this run, prove I paid for this

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.

ListingWhy
ACK-Pay (Agent Commerce Kit) D
Catena Labs, Inc.
Receipts are W3C Verifiable Credentials signed by a Receipt Service and verifiable offline against its DID. The docs show an Ed25519Signature2020 proof while the verifier accepts only JwtProof2020 (acc-24, open), and there are no settlement status codes or idempotency key. source
L402 C
Lightning Labs, Inc.
The preimage proves payment to anyone (sha256 matches the payment hash), and lnget caches tokens per domain so a later call reuses the paid credential. Handling of an in-flight or timed-out Lightning payment before retrying is not documented. source
Machine Payments Protocol (MPP) A
Tempo and Stripe
Payment proofs MUST be single-use, concurrent requests with one credential MUST settle once, and Payment-Receipt carries status, method, timestamp and a tx hash or invoice reference. Receipts exist only on success, and Idempotency-Key for paid POSTs is a SHOULD, so a lookup before re-paying depends on the server. source
x402 A
x402, a Series of LF Projects, LLC
SettleResponse carries success, errorReason and the transaction hash, settlement_pending is non-terminal with the broadcast hash required, and the payment-identifier extension is an idempotency key. The extension is optional, and facilitator-unavailability semantics are undefined (acc-25). source

What stops agents finishing

  • no idempotency key or replay rule, so a sequential retry pays twice
  • receipt format in docs differs from what the verifier accepts

Around it

Before: pay-per-call.pay-and-retry. After: agent-observability.cost-report, accounting.record-expense.

Where this comes from

Weight 12 of 100 in Pay-per-call protocols: 3 of 25 accounts (acc-17, acc-24, acc-25), two of them implementer issues; set low because few users report reaching this step

The same as data: /api/v1/use-cases/pay-per-call.settle-and-prove.json, or the MCP tool get_use_case with id pay-per-call.settle-and-prove. Other jobs in this category: /api/v1/niches?category=pay-per-call.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.