Lightning Labs Launches L402 Site to Pitch Bitcoin Payments for AI Agents

Lightning Labs Launches L402 Site to Pitch Bitcoin Payments for AI Agents

N
News Editor
2026-07-30 14:13:45
Lightning Labs has launched a dedicated website for L402, framing the protocol as a Bitcoin-based payment rail for AI agents. The company said the setup lets agents pay in bitcoin and authenticate natively without accounts, intermediaries, or human involvement. The launch is about a new public-facing site rather than a new protocol release: L402, also described as Lightning HTTP 402, already exists in Lightning Labs’ stack, and the company’s documentation says its Aperture implementation is already used by Lightning Loop, a non-custodial swap service for Bitcoin and Lightning. According to the documentation, L402 is meant for buying and selling digital resources and for charging API endpoints in a way AI agents can use. It reuses HTTP’s 402 Payment Required status code. When a client requests a gated endpoint, the server returns a 402 response along with a WWW-Authenticate header containing a token and a Lightning invoice. After paying the invoice, the client presents the token and payment preimage to gain access, while the server verifies both without querying a payment database. Lightning Labs calls that stateless verification. The rollout comes as Coinbase, Visa, Google, Stripe, and the Linux Foundation are also involved in agent-focused payment tooling, though L402 routes payments over Bitcoin’s Lightning Network.

Lightning Labs said Wednesday it has launched a dedicated website for L402, presenting the protocol as a way for AI agents to make payments in bitcoin.

“With L402, agents can pay with bitcoin and natively authenticate. No accounts, no intermediaries, no humans involved,” the company said in its post, calling L402 “the protocol for machine-to-machine commerce on Lightning.”

The launch is for a website, not a new protocol

The new piece here is the site, not the protocol itself. L402, described as the Lightning HTTP 402 protocol, already exists in Lightning Labs’ product stack.

According to the company’s documentation, Aperture, an implementation of the standard, “is used today by Lightning Loop, a non-custodial swap service for Bitcoin and Lightning.”

Lightning Labs frames L402 as infrastructure for AI agents

The documentation describes L402 as “the standard for selling and buying digital resources” and says it “allows services to charge for API endpoints in a way that is easy for AI agents to participate.”

The mechanism reuses HTTP’s 402 status code. When a client requests a gated endpoint, “the server responds with HTTP 402 Payment Required and a WWW-Authenticate header containing a token and a Lightning invoice,” the documentation says. The token includes the invoice’s payment hash.

The client then pays the invoice and presents the token together with the payment preimage to access the endpoint. The server can verify both without querying a payment database, which Lightning Labs describes as stateless verification.

Part of a broader push toward agent-focused payments

The release comes as several firms are building payment tooling aimed at autonomous software agents rather than human users.

Coinbase’s x402 protocol uses the same HTTP status code on Ethereum-based rails and has moved to the Linux Foundation with backing from Google, Stripe, and Visa. Visa has also released a command-line payment tool for AI agents.

L402 takes a different route by sending those payments over Bitcoin’s Lightning Network instead.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
960

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.