# Check the price and payee and stay inside a budget before paying

> Check the price and payee and stay inside a budget before paying: 0 companies fully do it, 3 with a limit, 24 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.cap-and-check/
- Markdown: https://www.anchorterminal.com/niches/pay-per-call.cap-and-check/index.md (~950 tokens)
- Slim: https://www.anchorterminal.com/niches/pay-per-call.cap-and-check/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/pay-per-call.cap-and-check/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 | 3 | 24 | 18 | 4 |

## What counts as done

The client refuses to sign when amount, asset or payee differ from what was expected or the task budget is spent, reports why in a machine-readable way, and keeps a record of every payment made in the task.

Measured, for our own tests: an inflated 402 (10 times the expected price) is refused in a test.

How agents ask for it: don't spend more than a dollar on this; only pay if it costs what the docs say; set a budget for this research task; stop if the price changes

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

- **L402 (Lightning Labs, Inc.)**: lnget refuses invoices above --max-cost (default 1000 sats) and fees above --max-fee (default 10), and the spec tells clients to abandon excessive invoices. A cap is per invoice with no per-task budget, failures are only 401 or 402, and an inflated 402 below the default cap would be paid.
- **Machine Payments Protocol (MPP) (Tempo and Stripe)**: The spec says clients MUST check amount, recipient, currency and validity and never trust description, and mppx sessions take a deposit ceiling. No per-payment or per-task client cap is documented for charges, and one builder found no standard budget before payment (acc-08).
- **x402 (x402, a Series of LF Projects, LLC)**: spendControls defaults to a 1 USD per-payment ceiling on known assets and policies can drop accepts with an unexpected payTo, with reasons like recipient_mismatch. No per-task budget exists, and a black-box test paid a server that inflated the price tenfold under the cap (acc-10, open).

- not this job: ACK-Pay (Agent Commerce Kit) (Catena Labs, Inc.): Amount, currency and recipient sit in the signed request, but the SDK has no per-payment or per-task cap, open issue 222 says expiresAt is never enforced, and error taxonomy is left to implementers.

## What stops agents finishing

- client signs whatever amount the 402 asks for unless the caller sets a cap
- spend budgets sit outside the spec, so each client implements its own
- retries and rephrased queries each trigger a new paid call

## Around it

Before: agent-wallets.fund-and-cap. After: pay-per-call.pay-and-retry, agent-observability.cost-report.

## Where this comes from

Weight 18 of 100 in Pay-per-call protocols: 4 of 25 accounts (acc-01, acc-08, acc-09, acc-10); every buyer thread raised budgets, and the x402 overcharge test is the most discussed client bug read

As data: https://www.anchorterminal.com/api/v1/use-cases/pay-per-call.cap-and-check.json, or the MCP tool get_use_case with id pay-per-call.cap-and-check. 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
