How agents use L402 today, and where it's going.
Now:
• Paid API access, one call at a time
• Monetized MCP servers (via Aperture)
• Pay-per-query data feeds
• LLM inference without an account
• Content unlocks behind a sats paywall
Next 2-3 years:
• Agent-to-agent commerce. Payment is the handshake.
• Per-second compute, GPU, and bandwidth
• Autonomous SaaS replacement. No more subscriptions.
• Real-world bookings settled in sats
• Macaroons replace API keys industry-wide
5 years out:
• Machine-native marketplaces. Agents are buyers AND sellers.
• Streaming micropayments per token, per frame, per step
• Identity = on-chain settlement history. No KYC.
• Programmable contracts between agents
• L402 becomes the default rail. Like TCP/IP for commerce.
And my favourite = agents will hire humans to access real-world actions. For instance, if an agent needs to have a live customer service feature for its users (because now agents run entire businesses themselves) then it will hire a call center via a programable macaroon L402 payment specifying exact details of the scope needed from the humans/call center.
-> pretty cool
The throughline:
As agents get more autonomous, the unit of commerce shrinks and friction has to approach zero.
Only Lightning math works at that scale.