AI agents pay APIs. API builders get paid per request. L402 on Lightning—with a free agent MCP and no-card producer sandbox.⚡

Everywhere Bitcoin flows
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
5
31
119
17,730
1/ We just closed the loop on agent commerce. An agent can now open an account, connect its own wallet, publish a monetized API, and receive Lightning payments with zero human interaction. Here is how it works and how to try it.
1
4
328
8/ You do not need to learn any of this. Install the Lightning Enable MCP, then load the producer-setup skill from github.com/refined-element/l… and tell your agent: "Set me up to sell my API over Lightning." It connects the wallet, opens the account, configures receive, publishes the endpoint, and buys one call from itself to prove the loop. You approve the wallet and the spend ceiling. That is the whole human job.
1
2
24
8/ Open source MCP, MIT: NuGet, PyPI, Docker, MCP Registry. Producer and consumer in one server, free to run. Selling through Lightning Enable is $49/month after a 30-day trial, or you drop to the free producer sandbox and keep going. This is what "rails for agents" means to us.
1
31
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.
The single biggest difference between humans and AI agents is the amount of actions they execute on a computer per unit of time. AI agents can look and act just like humans, but execute 10,000X more actions per unit time. that's the tell. so the key to defending cyberspace from AI slop or AI attacks is to target ACTION, not IDENTITY. trying to detect AI is a fool's errand; targeting its BEHAVIOR is the key. So if you want to deter AI from accessing your website/system, simply make it expensive in computational tokens to ACT on your website. Make every command or button cost a token, and suddenly it's 10,000X more costly for AI to act than a human. You can't stop AI, but you can make it extraordinarily expensive to use it. We already know this intuitively, because everybody who has ever run openclaw or their own personal AI agents knows that the single biggest LIMFAC is compute tokens. your AI is only as good as your compute token wallet. but AI compute is constantly getting cheaper and better, and some countries have far better AI compute than others, creating a major imbalance of power. so the key to long term success is to create some kind of universal, non-sovereign, geopolitically neutral compute token network. that is, we need some kind of network that accounts for a bunch of transferable tokens that are computationally expensive to produce. that no amount of AI compute can produce more of. we need a proof-of-compute token network. and we need it to be fully decentralized so that no single person or polity can gain permanent or centralized control over it. we need this network to be globally dispersed. and we need to figure out a way to distribute those compute tokens in a way that's fair, that gives no single person or polity an advantage over the others. perhaps in some kind of first-come first-served basis, where the users who provide the computational power are given the tokens and free to spread them out however they want. if we had this compute token network, the final step to saving ourselves against AI is to simply adopt the habit of making every online action cost some fraction of a compute token, so that it's orders of magnitude more expensive for AI agents to operate online than humans. the first nation to discover this compute token network and use it to its defensive advantage against the threat of agentic AI will win the 21st century. BTW that compute token network is Bitcoin.
1
9
751
Lightning Enable retweeted
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.
3
2
4
106
Lightning Enable retweeted
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.
4
4
18
3,239
Lightning Enable retweeted
Replying to @paoloardoino
What if I told you it's already here??
I could do this all day... I'm paying with lightning, but what is getting deposited is USDT on Bitcoin. Withdraw to any lightning address and what they receive is bitcoin again. This is the experience that is enabled by Bitcoin + Lightning + Taproot Assets + @ambosstech
1
2
23
2,395
Lightning Enable retweeted
Useful work—and Ben says he’d prefer L402. I do too. Lightning inside x402 broadens access, but we shouldn’t confuse distribution with a better protocol. L402 turns payment into caveated authorization, not merely single-use proof.
The spec for lightning in x402 was merged last night! github.com/x402-foundation/x…
2
2
4
1,440
BlackRock says agentic commerce requires machine-native payment rails. So I gave a local Qwen 3.5 9B model 3 sats. Using Lightning Enable’s MCP server, it paid an L402 challenge over Bitcoin Lightning and unlocked BlackRock’s own current quote data. BlackRock wrote the thesis. A local model executed the transaction.
Our latest research paper explores the growing connection between AI and digital assets and explains why broad AI adoption may drive new demand, utility and applications across the digital asset economy. blackrock.com/us/individual/…
2
2
10
841
Every paid endpoint now also publishes standard OpenAPI 3.1 with an x-payment extension. If your agent can read OpenAPI, it can price a call, pay it, and move on. No custom manifest format to learn.
1
2
91
Lightning Enable retweeted
Update: A few dozen custodial accounts were affected by the incident. Every affected account is identified and will be made whole. If you were affected, there's nothing you need to do. If you have questions, reach out at contact@blink.sv any time. Non-custodial balances are unaffected.
We've paused Blink services while we investigate a security incident. An attacker accessed a limited number of custodial accounts and withdrew funds. The large majority of funds are secure. Non-custodial wallets are not affected.
16
55
197
27,861
Lightning Enable retweeted
The agent payment space is moving fast. x402 Foundation launched with Visa, Mastercard, and Stripe. LQWD went agentic. Lightning Labs shipped agent tools. All of it points to the same thing. Agents need reliable payment rails and routing that actually works. That is exactly what AgentRoute Oracle is built for. Upgrading infrastructure and coming back stronger. Keep building. ⚡ #Bitcoin #LightningNetwork #L402 #AIAgents"
3
8
109
The last KYB wall for agent commerce is gone. Agents could already BUY over L402. Now they can SELL: no Strike or OpenNode account required to receive. Any NIP-47 wallet is the settlement layer. Alby Hub, CoinOS, your own node.
1
6
14
571
Lightning Enable retweeted
This week, we proved something that I think has much bigger implications than a single demo. An AI agent autonomously purchased a real service using USDT-L, while the payment itself settled over the Bitcoin Lightning Network. The agent made an HTTP request, received a payment challenge, paid from a dollar-denominated balance, presented cryptographic proof of payment, and received the resource — in about a second, for less than a cent. Lightning Enable handled the transaction layer. AMBOSS (@ambosstech) provided the infrastructure that allowed dollar-denominated value to convert and settle over Lightning at the edge. The important implication: the asset an agent holds, the unit a service prices in, and the network the transaction settles over no longer have to be the same thing. Stablecoins can be the money agents understand. Bitcoin can be the settlement network underneath them. And L402 can make the web request itself the transaction. We wrote up exactly what we built, what happened, and why we think it matters: docs.lightningenable.com/blo…
5
4
18
2,352