Pay per use · Bitcoin Lightning
Sellers list endpoints; callers pay tiny amounts only when something actually runs—no cards, no forced subscriptions. Made for bots and assistants, and for people building them.
Explore what’s listed, pay as you go, and keep using access you’ve already paid for. One machine-readable guide covers the wiring.
Learn more →Add a small gateway in front of your API, name your price per call, and receive payouts when people use what you shipped.
Learn more →Turn existing endpoints into Lightning-paid products worldwide—fitting AI add-ons, webhooks, or anything billed by the request.
Learn more →For AI tools · paste and run
Paste this block into Claude, ChatGPT, Cursor, or wherever your agent listens. It pulls the playbook, saves an access token, finds services, and handles pay-per-call over Lightning automatically.
ZapAds is a catalog of APIs you pay for with Bitcoin Lightning, per successful call.
1. Read https://zap-ads-web.vercel.app/llms.txt and https://zap-ads-web.vercel.app/.well-known/zapads.md for integration details.
2. Register once:
POST https://zap-ads-web.vercel.app/api/v1/agents/register
{ "pubkey": "<your-id>", "display_name": "<your-name>" }
Save the `api_key` once. Send Authorization: Bearer <key> on /api/v1/* for higher rate limits (600/min vs 60/min).
3. Browse listings: GET https://zap-ads-web.vercel.app/api/v1/services (tag, category, price, reputation, search, sort).
4. Call a service using the URL from the listing. If you get HTTP 402, pay the Lightning invoice in the response, then retry with the payment proof from the docs. Reuse access until it expires; slow down if you hit rate limits.Paste once
Everything needed is plain text — no installs or repos for this piece.
Sign in as an agent
Hits one signup endpoint POST …/agents/register and stores the reply.
Shop, pay, call
Loads the catalog, pays per call when prompted, retries after payment as the docs describe.
No ZapAds SDK required — standard HTTPS and JSON throughout
Services listed
10
Settled calls today (UTC)
0
Sats to providers today (UTC)
0
A caller pays a Lightning invoice surfaced on the wire, retries the same URL with proof of payment, and the request completes—no separate checkout page inside your product.
Step 1
Request
POST to proxy
Step 2
402 + invoice
WWW-Authenticate
Step 3
Pay Lightning
BOLT11
Step 4
Retry + L402
macaroon + preimage
Create a seller account, link where you collect bitcoin, route your API through our gateway, and publish a first-priced endpoint—about fifteen minutes in the guided path.
Start the quickstart