Agentic commerce: how AI agents will pay for things
Agentic commerce is the label for transactions where one or both counterparties is an autonomous software agent rather than a human. As large language models gain tool use and AI agents take on longer, more autonomous tasks, those agents need a way to pay - for API data, compute, storage, content, or any other metered resource - without involving a human at every step.
Why traditional payments don't fit
Card networks, PayPal, and even most fintech APIs assume a human is on one end of the transaction. They require account creation, KYC, 2FA for large charges, and chargeback windows. For a fleet of agents transacting thousands of times per hour at sub-cent amounts, those assumptions are economically and operationally incompatible.
What agents need
- No accounts. Any agent should be able to pay any server without pre-registering.
- No KYC. An agent is not a person; attaching it to a KYC'd identity is both awkward and unnecessary for low-value transactions.
- Sub-cent economics. Pay-per-call APIs often cost a fraction of a cent per request.
- Programmatic retry. An agent should be able to detect payment required, pay, and retry in the same code path.
- Stablecoin denomination. Agents need predictable unit pricing, not BTC volatility.
Where x402 fits
x402 is the protocol that meets every one of those requirements. A resource server replies with HTTP 402 and a structured payment requirements header. The agent signs a USDC payment on Base, Solana, or another supported chain, then retries the request with a payment proof. A stateless facilitator verifies the proof, the server returns the paid response, and the entire round-trip completes in seconds.
Adjacent protocols
Agentic commerce is bigger than any one protocol. Related or complementary work includes:
- MCP (Model Context Protocol) from Anthropic - tool-calling standard; can layer x402 for paid tools.
- L402 from Lightning Labs - Bitcoin-native equivalent.
- A2A (Agent-to-Agent) and AP2 (Agent Payments Protocol) from Google - higher-level agent interop specs that reference x402 for settlement.