{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/pay-per-call.charge-for-endpoint/",
    "json": "https://www.anchorterminal.com/niches/pay-per-call.charge-for-endpoint/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/pay-per-call.charge-for-endpoint/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/pay-per-call.charge-for-endpoint/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 4 | 27 | 25 | 7 |\n\n## What counts as done\n\nUnpaid 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.\n\nHow agents ask for it: charge agents for my API; make crawlers pay per page; add x402 to my endpoint; sell my data per request\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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).\n- **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.\n- **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).\n\n## What stops agents finishing\n\n- few clients pay yet, so a paywall can earn nothing\n- free facilitators that do not publish the transaction\n- middleware that misroutes prices behind a mounted router\n\n## Around it\n\nBefore: infrastructure.deploy-api. After: pay-per-call.discover-payable-service, payment-platforms.meter-and-invoice.\n\n## Where this comes from\n\nWeight 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\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Put a per-call price on an API or page and get paid",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": null,
    "h1": "Put a per-call price on an API or page and get paid",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/pay-per-call.charge-for-endpoint/",
    "published": "",
    "section": "agents",
    "title": "Put a per-call price on an API or page and get paid | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/pay-per-call.charge-for-endpoint/"
  },
  "tokens": {
    "markdown": 900,
    "slim": 280
  },
  "version": 1
}
