AI agents and Bitcoin
AI agents are programs that do work on their own and increasingly need to pay for it: an API call, a page of data, a minute of compute. They cannot open a bank account, but they can hold a Bitcoin key and pay over Lightning in amounts far smaller than a card can handle. That is the case for why the next billion Bitcoin users may not be people. It is a strong argument with real caveats.
- 01no bankan agent can't open an account or get a card
- 02a keya 256-bit random number, made in < 1 ms
- 03millisatsLightning splits 1 sat into 1,000
- 04L402payment inside the HTTP request, status 402
05 The next billion Bitcoin users won’t be people.
Based on the video @DocumentingBTC: “Here's why AI will buy all of the bitcoin” ↗ (11 October 2026). Retelling, caveats and graphics are ours; convert the amount to sats: calculator.
The wall: agents have no bank
An agent can write code, book a flight and hire another agent, then fail at the last step: paying. Cards and bank accounts are issued to people and companies after identity checks, and they assume a human is around to approve, dispute and reset passwords. An agent has no passport, no address and no credit history, so today it borrows a human's card or API key and inherits that human's limits.
Bitcoin asks only for a key
To receive bitcoin you need a private key: a 256-bit random number that a computer generates in well under a millisecond. Nobody approves it and nobody can refuse it. The rules are open source and the same for everyone, which matters for software that decides by reading code rather than trusting a brand.
Pay per word: why card fees break
Agents buy in tiny slices: per request, per token, per second. A typical online card fee is about $0.30 plus a percentage. On a $0.0001 request the fixed part alone is 3,000 times the payment, so cards simply cannot price machine-sized purchases; providers bundle them into monthly plans instead.
The Lightning Network moves bitcoin between channels in about a second and counts in millisatoshis: one satoshi split a thousand ways. At around $84,000 per BTC, $0.0001 is roughly 0.12 sat, or about 120 millisats, which Lightning can express and on-chain Bitcoin cannot.
L402: payment inside the web request
L402 revives the web's old HTTP 402 "Payment Required" status. The server answers a request with a Lightning invoice; the agent pays, retries with proof of payment and gets the data. No sign-up and no API key to leak: in Lightning Labs' words, credentials are purchased, not provisioned.
Honest caveats
- Someone still funds the agent. A human or company buys the bitcoin and sets the budget; agents mostly spend it rather than hoard it, so "AI will buy all the bitcoin" is a slogan, not a forecast.
- Routing is not free. The median public Lightning node charges a base fee of about 500 millisats per hop, which is more than a $0.0001 payment. Real sub-cent payments need direct channels, zero-base-fee routes or batching, and most L402 prices today start at a sat or more.
- Lightning needs liquidity and an online node or a provider. Custodial wallets are simpler but bring back an account, and sometimes identity checks.
- Competition is real. Coinbase's x402 uses the same HTTP 402 idea with USDC stablecoins, and Visa, Mastercard and Stripe are building agent-payment products on card rails.
- Safety: an agent with keys can be tricked or buggy. Cap spending, keep keys on a separate signer and start small.
Where this comes from
This article retells, in our own words and with our own caveats, the argument of a two-minute animated video by @DocumentingBTC published on 11 October 2026, "Here's why AI will buy all of the bitcoin". It ends on the line we borrowed for our banner: the next billion Bitcoin users won't be people. Watch the original via the link in References.
See also
- L402L402 is a protocol for paying for web resources with Lightning inside an ordinary HTTP request. The server replies 402 "Payment Required" with an invoice and a token; the client pays, retries with the proof and gets access. It needs no account or API key, which suits software agents.
- Nostr Wallet Connect (NWC)Nostr Wallet Connect (NIP-47) lets an app or an AI agent ask your Lightning wallet to pay or create invoices over encrypted Nostr messages, within a budget you set, without ever holding the wallet's keys.
- CashuCashu is an open-source ecash protocol for Bitcoin. A mint holds bitcoin and issues blinded tokens that are private, instant and can be passed around as plain text; the trade-off is that the mint is custodial.
- x402x402 is an open payment standard started by Coinbase and now run by the x402 Foundation. Like L402 it uses HTTP 402, but it mostly settles in USDC stablecoins on chains such as Base and Solana rather than in bitcoin.
- Lightning NetworkLightning is a payment network built on top of Bitcoin. Two parties lock bitcoin in a shared channel and then pay each other instantly and cheaply off-chain; payments can hop across channels to reach anyone.
- Satoshi (unit)A satoshi, or sat, is the smallest amount of bitcoin: one hundred-millionth of a coin. 1 BTC = 100,000,000 sats.
- Private keyThe secret number that authorises spending. Whoever has it controls the coins.
References
- @DocumentingBTC: "Here's why AI will buy all of the bitcoin" (video, 11 Oct 2026) x.com
- Lightning Labs: L402 protocol documentation docs.lightning.engineering
- Lightning Labs: Lightning Agent Tools (Feb 2026) lightning.engineering
- MDN: 402 Payment Required developer.mozilla.org
- Stripe pricing (2.9% + 30¢ per online card charge, US) stripe.com
- x402: HTTP-native payments (Coinbase) x402.org
- mempool.space Lightning statistics mempool.space