your ai agent can read the web, write code and book a table. until recently it couldn't pay for a $0.01 api call without you typing in a card number. x402 is the protocol built to fix that.
here's what it is, how a payment actually works, who backs it, and what the real numbers say in october 2026.
what is x402?
x402 is an open payment standard that lets apps and ai agents pay for things directly inside a normal web request, usually in stablecoins like usdc.
the name comes from http status code 402, "payment required." it was reserved in the original web spec and sat almost unused for decades. x402 finally gives it a job: a server can answer "this costs 1 cent," and a client can pay and get the content in the same exchange.
no account, no api key, no monthly plan, no checkout page.
coinbase announced x402 on may 6, 2025, with aws, anthropic, circle and near as launch collaborators. in july 2026 the protocol moved to the linux foundation, which now stewards it under neutral governance.
why ai agents need their own way to pay
the internet's payment rails were built for humans. a card checkout assumes someone types a number, passes a fraud check and maybe confirms a text code. that breaks down for software in three ways.
tiny amounts. card fees make a 1-cent payment pointless. an agent might want to pay a fraction of a cent per data request.
no signup. an agent researching a question may hit 20 paid sources it has never seen. creating 20 accounts and api keys doesn't scale.
speed. agents work in seconds. invoices and monthly billing work in weeks.
banks are also wary. as we covered in your bank just banned your ai agent, several big us banks are updating terms to keep outside agents away from customer accounts. crypto rails are one of the few places where an agent can hold a budget and spend it on its own.
how an x402 payment works, step by step
under the hood it's a short back-and-forth over http. in the current version (v2) of the spec it looks like this:
the agent asks for something. for example, a premium market-data endpoint.
the server replies "402 payment required." a
PAYMENT-REQUIREDheader lists the price, the accepted token, the network and where to send the money.the agent signs a payment. its wallet signs an authorization for that exact amount and resends the request with a
PAYMENT-SIGNATUREheader.a facilitator checks and settles it. a facilitator is a service that verifies the signature and pushes the payment onchain, so the seller doesn't need to run blockchain infrastructure.
the server delivers. the data comes back with a
PAYMENT-RESPONSEheader confirming the outcome.
for a human, that whole loop is invisible. for a developer, coinbase's pitch is that selling an endpoint takes a few lines of code.
the three ways to charge
x402 supports different payment "schemes," per coinbase's developer docs:
exact: a fixed price per request, like $0.01 per call.
upto: the agent approves a maximum and pays only what it uses, useful for metered ai inference.
batch-settlement: many small payments are verified offchain and settled together, so one onchain transaction can cover thousands of requests.
what does x402 cost?
the protocol itself is free and open source. costs come from two places: network fees on the chain that settles the payment, and the facilitator.
coinbase's facilitator, the biggest one, gives sellers the first 1,000 onchain transactions each month for free, then charges $0.001 per transaction. verifying a payment is always free. it also screens payments against sanctions lists (ofac) and flags high-risk addresses.
most activity runs on base, coinbase's layer 2 network, and solana. coinbase's facilitator also supports polygon, arbitrum, monad and world chain.
who backs x402?
this is no longer a single-company experiment. the key milestones:
may 2025: coinbase launches x402 with aws, anthropic, circle and near.
sept. 16, 2025: google launches its agent payments protocol (ap2) with an x402 extension for crypto payments, built with coinbase, the ethereum foundation and metamask.
sept. 23, 2025: cloudflare and coinbase announce the x402 foundation. cloudflare says sites on its network already send over a billion 402 responses a day to bots and crawlers, with no standard way to actually collect payment (cloudflare blog).
july 14, 2026: the linux foundation launches the x402 foundation with 40 members, including visa, mastercard, american express, stripe, google, aws, shopify, circle and coinbase. the stated goal is to support payment types "from traditional cards to stablecoins."
oct. 20, 2026: mastercard opens early developer access to agent pay for machines, built on x402 with settlement on base. we broke it down in our oct. 21 news of the day.
having card networks inside the same foundation as crypto companies matters. it suggests x402 could become a general "pay over http" layer, not just a stablecoin niche.
how big is x402 really?
it depends who you ask, and that's the honest answer. trackers count differently, and raw numbers include tests, dust payments and wash activity.
cumulative: agent economy counts about 194.9 million x402 transactions and $42.2 million settled since launch (agenteconomy.to, oct. 24, 2026). paymentscan, which tracks a different set of facilitators, shows $67.5 million (paymentscan.xyz).
the peak: paymentscan's monthly volume topped out at about $29.1 million in november 2025. since march 2026 it has run between roughly $1.3 million and $2.7 million a month across all chains.
real demand: x402stats reports $1.23 million in volume over the last 30 days, but only $710,000 (58%) after filtering out wash trading. only 92 sellers meet its bar for organic revenue, and the median seller earned $0.01 (x402stats.io).
the takeaway: lots of transactions, little money so far. x402 is infrastructure waiting for agent demand to catch up. the big names joining in 2026 are betting it will.
what you can do with x402 today
let an agent buy data. coinbase for agents, coinbase's official mcp server, connects assistants like chatgpt, claude and grok to a coinbase account. one of the things they can do with it is pay for data via x402.
sell an api by the call. developers can put an x402 price on an endpoint and get paid in usdc without managing customer accounts.
pay per page or per crawl. publishers can charge ai crawlers per request instead of blocking them outright.
agents are also moving into trading. our oct. 22 news of the day covered coinbase letting connected agents trade perpetual futures. for more agent-ready apps, see the gweiwire tools directory.
the risks to know before you hand an agent a wallet
payments are final. a stablecoin payment can't be charged back like a card. a buggy or tricked agent can spend real money fast.
set hard limits. fund a separate wallet with a small balance and use spending caps. mastercard's version, for example, gives an agent a task and a spending limit.
watch for prompt injection. a malicious page can try to talk an agent into paying for something it shouldn't.
stablecoin risk. usdc is redeemable for dollars, but it's a private token, not a bank deposit, and it isn't fdic-insured.
faq
is x402 a cryptocurrency?
no. x402 is a protocol, a set of rules for asking for and sending payment over http. there's no x402 token from coinbase or the foundation. payments use existing tokens, mostly usdc.
who created x402?
coinbase's developer platform team created it in 2025. coinbase contributed it to the linux foundation's x402 foundation, which completed its operational launch in july 2026.
do i need crypto to use x402?
today, mostly yes. the payer needs a wallet with stablecoins on a supported network. the foundation says future versions could also cover cards and bank transfers.
is x402 the same as google's ap2?
no. ap2 is google's broader framework for agent payments across cards, bank transfers and crypto. x402 plugs into it as the stablecoin payment layer.
this guide is for information only and isn't financial advice. numbers as of oct. 24, 2026.