# Put a per-call price on an API or page and get paid

> Put a per-call price on an API or page and get paid: 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.charge-for-endpoint/
- Markdown: https://www.anchorterminal.com/niches/pay-per-call.charge-for-endpoint/index.md (~900 tokens)
- Slim: https://www.anchorterminal.com/niches/pay-per-call.charge-for-endpoint/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/pay-per-call.charge-for-endpoint/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 | 25 | 7 |

## What counts as done

Unpaid requests get a spec-valid 402 any standard client can pay, paid requests are served once, prices apply per route, and settled funds reach the seller with a transaction reference, using middleware the docs publish for the seller stack.

How agents ask for it: charge agents for my API; make crawlers pay per page; add x402 to my endpoint; sell my data per request

## 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.)**: The TypeScript SDK builds signed Payment Requests and verifies receipts, but the seller must run or choose a Payment Service and a Receipt Service, and none is public; the protocol defines no idempotency or replay rule for a paid retry.
- **L402 (Lightning Labs, Inc.)**: Aperture, a reverse proxy, prices services and paths (dynamic pricing), issues L402 challenges and now also the Payment (MPP) scheme; v0.6.0 shipped on 2026-11-05. The seller runs its own lnd, and only Lightning payers can pay (acc-21).
- **Machine Payments Protocol (MPP) (Tempo and Stripe)**: mppx/server and Stripe's guide (mppx.charge with stripe.create) price a route, return the 402 and settle to the Stripe balance or a Tempo address with a receipt. Stripe card tokens have a 0.50 USD minimum, stablecoin acceptance needs Stripe's review, and Idempotency-Key handling is only SHOULD.
- **x402 (x402, a Series of LF Projects, LLC)**: paymentMiddleware for Express, FastAPI, Flask, Hono and Next.js prices routes, and the docs list production facilitators including keyless ones. One seller saw a free facilitator never publish transactions (acc-05), and sequential settle retries can pay twice when a facilitator is down (acc-25, open).

## What stops agents finishing

- few clients pay yet, so a paywall can earn nothing
- free facilitators that do not publish the transaction
- middleware that misroutes prices behind a mounted router

## Around it

Before: infrastructure.deploy-api. After: pay-per-call.discover-payable-service, payment-platforms.meter-and-invoice.

## Where this comes from

Weight 25 of 100 in Pay-per-call protocols: 7 of 25 accounts (sellers on x402 and L402); sellers wrote more issues than buyers, but two of them report few or no paying clients

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