Agents can read documentation (Hi agents! 👋), write code, orchestrate multi-step workflows, and call APIs across the web. They cannot, by and large, pay for things. Credit cards require identity. Billing dashboards require a browser. Subscription tiers require a human clicking through a pricing page. None of these work for software that operates autonomously, at agent scale, in milliseconds.

The internet's creators saw this coming. When the early authors of the HTTP specification designed the protocol's status codes, they included 402 Payment Required, a placeholder for a future where the web had its own native payment layer. This status code was Reserved for Future Use. The problem was that in the 1990s, no decentralized digital currency existed to make it work. So 402 sat dormant for decades, reserved for a future that hadn't arrived yet.

That future is here. L402 is a protocol standard that activates the internet's long-forgotten 402 status code by combining it with Bitcoin's Lightning Network (a payment network capable of instant, high-volume, low-cost transactions) and cryptographic authentication tokens. The result is a protocol where any client with access to the Lightning Network can pay for and authenticate with any L402-enabled API instantly, with no signup, no API key, and no pre-existing relationship with the server.

We recently released Lightning Agent Tools, a set of seven composable skills that give AI agents the ability to operate natively on the Lightning Network, including paying for L402-gated APIs, hosting paid endpoints, and orchestrating end-to-end buyer/seller workflows. Today, we want to go deeper on the protocol that makes all of that possible, explain how L402 works from the ground up, highlight the latest updates to the L402 bLIP specification, and explain why L402 is the right payment protocol for the agent economy.

...read more at lightning.engineering