An AI agent just bought a real product using Bitcoin over the Lightning Network. $27.67. 38,561 sats. Real merchant. Real order. Completed in ~30 seconds. First live merchant integration using Lightning Enable with Salt of the Earth (@drink_sote). Agent-accessible: drinksote.com

Zero per-transaction fees. A 3-sat data call is economical because the payment settles over Lightning between the buyer's wallet and the seller's wallet. We charge a flat subscription and nothing on the flow.

Core Lightning node runners, this is urgent, upgrade to 26.06.8 now if you haven't already.

Bitcoin

Issue #663 of Your Daily Bitcoin Breakdown newsletter is now live! Check out today’s top stories and a sneak peek at the latest Insights & Analysis and Tools & Projects sections. Full issue available here: btcbnews.com/663

“Permission to spend has to cover the cost of trying, even when there is no result to approve.” This is where L402 fits: agents pay per search, model call or data request as work happens. Settlement is final. Paired with bounded budgets, permission covers the attempt, not only the final purchase.

need people to realise this!

What Mike @lightningenable helped me realize is that stablecoins + L402 is the most powerful combination for AI Agents. Here's what we achieved together between @ambosstech and @lightningenable.

We added a new case study showing Lightning Enable + @ambosstech in action. An AI agent purchased API access over Lightning using both bitcoin and USDT-L, with the payment preimage returned to prove payment and unlock the resource via L402. Thanks to the AMBOSS team for working with us to test the flow and get it running in production. See what you can build with Amboss + Lightning Enable: lightningenable.com/case-stu…

AI agents x Bitcoin x Lightning

This is exactly what an L402 reverse proxy enables. Don’t try to determine whether the caller is human or AI. Price the action. Put L402 in front of any HTTP endpoint and every request can carry an economic cost denominated in sats. AI scales actions; the cost scales with it. That’s what we built Lightning Enable for.

Something significant is happening right now and here is what has unfolded over the past couple of days. Back in Issue #5 I wrote about x402 and L402 as two separate protocols racing to become the payment rail for the AI agent economy. This week Block, the company behind Cash App and Bitkey, joined the x402 Foundation and contributed Bitcoin Lightning Network integration directly into the protocol. Bitcoin Lightning is no longer competing with x402. It is now inside it. The largest open standard for agentic payments, backed by Google, AWS, Cloudflare, Visa, Mastercard, and Stripe, now has a Bitcoin Lightning lane. This is one of the more important developments in the story of where money is going. I wrote about it today on The Route. theroutebtc.beehiiv.com/p/th… Follow on X: @Bitlatethenever AgentRoute Oracle: btcaioracle.com #Bitcoin #LightningNetwork #x402 #AgenticPayments #BTC #Block #L402 Keep learning, building, and stacking, ₿it by ₿it.

It’s time for another round of “what’s the difference between L402 & x402”? I think of it like this… L402 is a bearer token while x402 is a process. Let’s look at the example of an agent paying for an API endpoint. L402 is an access token that includes proof of payment. An agent shows up to an API endpoint looking for some data. The service returns a bearer token with a Lightning invoice. The agent pays that invoice, receives the preimage as proof of payment and adds that preimage to the token, making an L402. The agent then returns to the server to access the data in that API endpoint presenting the L402 to get instant access. But wait, there’s more. As this is a bearer token, an agent can also attenuate that token and sell it, or pass it along to sub-agents, etc. Lots of options. No identity needed, no need for the server to hold on to user data. x402 is a process that focuses more on the broader crypto ecosystem. An agent shows up to that same API endpoint. The server responds with a 402 Payment Required. No bearer token, just payment requirements: how much, in what currency, on which network. The agent creates a payment payload (say, USDC on Base, or now Bitcoin Lightning too), and retries the exact same request with proof of payment attached. A facilitator verifies the proof and the server delivers the data. But the agent doesn't walk away with anything reusable. No token to pass to a sub-agent, no attenuation, no credential. Next time it needs that data, it pays again via the same process. L402 is a protocol that was created by Lightning Labs in 2020. x402 is a protocol that was created by Coinbase in 2025.