Niches · Pay-per-call protocols
Put a per-call price on an API or page and get paid
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
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 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. | 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. source |
| L402 C 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). source |
| Machine Payments Protocol (MPP) A 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. source |
| x402 A 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). source |
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
The same as data: /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. 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.