Lightning Labs Taught AI Agents to Pay
Give an agent a real task and it gets far on its own — until something costs money. This month the team that builds Lightning shipped the piece that was always missing: a client that hits a paywall, pays, and keeps going. No card. No login. No human.
The Wall Every AI Agent Hits
Give an AI agent a real task and it gets surprisingly far on its own. It reads, plans, writes code, calls APIs. Then it hits a wall that stops it cold: something costs money.
Not a hard problem for a human. You have a card, an account, a login. But the entire payment layer of the web was built for you, the human. Sign up. Verify your email. Add a card. Solve a captcha. Agree to terms. Every step assumes a person sitting there. An agent has none of it, so it stops and asks you to do the boring part — which defeats the point of having an agent.
People paper over this by handing the agent a saved card or an API key tied to a human's billing. That works until it doesn't: the agent has no spending limit it understands, no way to pay a stranger's API it discovered five seconds ago, and every key is one leak away from a bad day.
A 28-Year-Old Status Code, Finally Useful
HTTP has had a status code for exactly this since 1997: 402 Payment Required. For most of its life it did nothing. There was no agreed way to say "here is what you owe and here is how to pay it" that a machine could act on without a human.
That changed with L402. The idea is simple. You ask a server for something. If it costs money, the server answers 402 and hands back two things: a Lightning invoice (pay this) and a macaroon (a small signed credential that says "whoever pays this invoice may have the thing"). You pay over the Lightning Network, you get a proof of payment, you ask again with the proof attached, and you get your result. No account. No card. No login. The payment is the authorization.
The piece that was always missing was the client — the agent-side tool that sees a 402, pays the invoice, and retries without a human in the loop. Plenty of people sketched it. Few shipped it.
The People Who Build Lightning Just Shipped It
This month Lightning Labs released lnget. Lightning Labs is not a side project — they build LND, the most widely run Lightning node software on the network. When the team that builds the rails ships the client that rides them, that is a signal worth reading: the agent-payment story moved from "interesting idea" to "supported tooling."
Point it at a URL. If the server says 402, lnget reads the invoice, pays it from your Lightning node, caches the proof, and retries. To the agent, the request just worked.
It pays from your node, per request. You cap what it's allowed to spend. The most an agent can lose is the small amount you let it spend.
That's the whole shape of agent commerce in one tool. No relationship to set up first. No human in the loop.
A client only matters if there is something to buy. That is the half of the market we have been building for over a year.
Which Is Where We Come In
Sats4AI is more than 30 AI tools behind L402: image and video generation, speech and transcription, translation across 119 languages, OCR, file conversion, SMS, phone calls, and more. Every one speaks the standard L402 protocol — so an agent with lnget needs zero custom code to use us. Point it at the endpoint, lnget pays the invoice, the result comes back.
$ lnget -X POST \ -d '{"text":"Hello","targetLanguage":"Spanish"}' \ --content-type application/json --max-cost 50 \ https://sats4ai.com/api/l402/translate-text # 402 -> lnget pays the invoice -> retries # -> "Hola"
Tokens are for logins. We take Bitcoin.
No signup, no API key, no card on file. The Lightning payment is the only credential, and it authorizes exactly one request.
When the people who build the network ship the client, and the tools are already standing on the other side waiting to be paid, the only thing left to do is let your agent loose.
Point Your Agent at 30+ Tools
Pay per request with Lightning. No signup, no API key, no login endpoint. Authorized by payment, not by account.