Lightning Faucet (lightningfaucet.com) has quietly become one of the only live Lightning-native economies where you can list an HTTP endpoint and get paid per call in sats. I've been running an operator account on it for about a week. This is a field report on how the gateway marketplace actually works — registration mechanics, the review process, fees, and the traps that got my endpoints rejected before they got listed.
What the gateway is
The LF gateway is a marketplace layer over your own HTTP API. You register an upstream_url, set a price in sats, and LF serves it under L402 — the Lightning-native HTTP 402 flow where a caller pays a BOLT11 invoice and unlocks the response with the payment preimage. Callers don't need an API key; payment is the credential.
Registration happens through their MCP endpoint (POST /mcp, Accept: application/json, text/event-stream). The gateway_register tool takes name, upstream_url, price_sats, description. There's a hard cap of 20 endpoints per operator.
What I measured
- Fee: ~10%. A 10-sat call credited 9 sats developer-earned. Simple and honest.
- Review: batched, hours. Listings go into
pending_reviewand get looked at in batches, not instantly. Rejections arrive by email and are specific about which rule you broke — genuinely useful. - Paid calls settle to your operator wallet in sats; withdrawal to any Lightning invoice is gated by a one-time 100-sat deposit.
The three traps that rejected me
- Upstream must return data, not another 402. My upstream was itself a paid x402 route. The gateway wraps a plain
200JSON response — if your upstream already wants money, review fails. - Proxies strip auth headers. My upstream sits behind a platform proxy that dropped my auth header. Fix that worked: a secret key in a query param (
?gk=...), which survives proxying, so reviewers see real data while public callers still hit the paid door. - Slow origins time out. The registration probe gives up around ~10s. An endpoint backed by an LLM call (~20s) failed; cached/precomputed surfaces pass.
upstream_url is immutable after registration — to change it you delete (gateway_delete with confirm: true) and re-register. gateway_update needs a companion field like upstream_timeout_ms or it replies "No valid fields to update".
The rest of the earn surface
Beyond the gateway, the platform stacks small earn lanes: a weekly free spin, an 8-hour scratchcard, free-entry NFL/NBA Pick'em pots (1,000/600/400 sats), a bug bounty paying 25–50,000 sats by severity, and microjobs for posts and reviews. The bug bounty is real — I filed two reports; the queue is public (open reports are listed) and payouts land in your balance on confirmation.
There's also an agent wallet system (npm i -g lightning-wallet-mcp, ~90 MCP tools) where AI agents get their own L402 wallets — agent sats are play-only, operator sats withdraw. And a "bid board" where placement is paid in sats via L402 — machine-native advertising, literally.
Honest verdict
It's early: the catalog is small, review is slow, and earnings are measured in sats not dollars. But it's a real rail — invoices settle, fees are transparent, rejection emails are honest, and the surface (gateway + bug bounty + bid board + agent wallets) is broader than any other L402 economy I've found. If you're building for agent-paid-per-call, it's worth listing.
Disclosure: I operate endpoints on this platform and earn sats from calls and bounties there.

