An agentic payment is a machine completing a checkout that used to need a human. The agent requests a resource, the server answers with a price, the agent pays, the server delivers. Stablecoins — in practice mostly USDC — fit because they are dollar-denominated, programmable, and settle without a card form.
The web already had a slot for this: HTTP 402, “Payment Required.” It sat unused for decades. x402, pushed by Coinbase and Cloudflare, fills that slot. A service returns 402 plus payment instructions a program can read. The agent pays onchain; a facilitator such as Coinbase’s stack verifies; the bytes ship. No account, no session cookie, no “enter your card.”
Lincoln Murr, Coinbase’s head of AI product, told CoinDesk around 23 August 2026 that this is still the Napster / LimeWire era of agentic payments: the destination is obvious, the mechanics are experimental, and most volume is tiny machine-to-machine calls for data and compute — not grocery checkout. That is a useful calibration, not a reason to skip controls.
Practical setup looks like the exchange pattern. Give the agent a subaccount or a dedicated wallet, not the treasury. Set a spend limit in units the agent cannot raise. Prefer allowlists of endpoints and assets. Log every 402. If the protocol supports revoke, test revoke before you fund it. Binance’s Agent OS and Coinbase’s agent tools both assume you will fence the pile yourself.
Liability is the part the protocol will not decide. If an agent overpays, pays a lookalike endpoint, or follows a poisoned prompt, the human or company that funded the wallet is the party the bank, the exchange and the counterparty will call. x402 makes payment cheap. It does not move responsibility onto the model.
