Overview Chainalysis put a number on something that had been largely unmeasured. In its annual report on the North American crypto economy, published October 14, the firm counted more than 138 millionOverview Chainalysis put a number on something that had been largely unmeasured. In its annual report on the North American crypto economy, published October 14, the firm counted more than 138 million
What Is x402? How AI Agents Use Stablecoins to Pay for APIs and Services
Overview
Chainalysis put a number on something that had been largely unmeasured. In its annual report on the North American crypto economy, published October 14, the firm counted more than 138 million x402 transactions on Base by the close of its study period, which covers the twelve months ending July 1, 2026, with the micropayment analysis extended to the sixteen months ending September 2026. The size distribution matters more than the count. Over 87% of those payments fell between one hundredth of a cent and a dime, with one to ten cents the most common band.
Volume like that is not produced by people clicking buttons, and it cannot run on card rails, where a ten-cent payment costs more to process than it is worth. What generates 138 million micropayments is a different kind of buyer: AI agents calling APIs, purchasing inference and pulling data on their own. They need a payment rail that settles in milliseconds, costs almost nothing per transaction, and requires neither an account nor an API key. x402 is the protocol built for that, and it starts from a status code that sat unused in the HTTP standard for three decades.
One clarification belongs up front, because it is the single most common misreading. x402 is an open payment protocol, not a token. It has no official token, and settlement happens in stablecoins such as USDC.
Key Takeaways
Almost every one of those 138 million transactions was a micropayment. Chainalysis found more than 87% of x402 payments landed between one hundredth of a cent and ten cents, a range that simply does not work on card networks.
x402 revives the HTTP 402 status code. A server answers an unpaid request with 402 Payment Required, attaching the price, the recipient and the accepted assets, and the client signs and retries, all within HTTP.
It is multi-chain, with Base as the main production environment. Per Coinbase's developer documentation, the CDP facilitator currently supports Base, Polygon, Arbitrum, World and Solana, and any ERC-20 asset on the EVM side.
Enterprise adoption has already started. Amazon Web Services built x402 natively into the preview of Bedrock AgentCore Payments, letting agents pay in stablecoins when a resource returns 402.
Spending control is part of the design rather than a patch. Time-bound limits, the upto scheme that settles only what is used, batch settlement and a wallet architecture that keeps private keys away from the agent together define the risk boundary.
Governance now sits with a neutral body. The Linux Foundation announced the x402 Foundation on April 2, with Coinbase, Cloudflare and Stripe as initial developers.
There is no x402 token. Tokens trading under the x402 banner are third-party projects with no value-capture relationship to the protocol.
A Status Code That Sat Unused for Three Decades
What HTTP 402 Was Meant to Do
HTTP defines a set of status codes to describe the outcome of a request. 404 says the resource does not exist, 403 says access is forbidden, and 402 says Payment Required. That code was reserved in the standard and never given an execution layer, for a straightforward reason: the early web had no settlement method that worked across borders, handled trivially small amounts cheaply, and could be completed by software without a human in the loop. Cards need accounts, authorization and a fixed cost per transaction, which fits poorly with the high-frequency, stateless, tiny-value nature of an HTTP request.
So the web took two other routes. One was advertising, trading attention for content. The other was subscriptions and API keys, trading an account relationship for access. Both carried the last twenty years of internet commerce, and both assume the payer is a person with an identity, an account and a card.
Turning 402 Into an Executable Flow
Coinbase defines x402 in its launch documentation as an open standard that leverages the original HTTP 402 Payment Required status code to put stablecoin payments directly into web interactions. The flow is not complicated. The client requests a resource, the server responds with 402 plus the price, the recipient and the accepted payment options, the client signs a payment and retries, the server has a facilitator verify it, performs the work, has the facilitator settle on-chain, then returns the resource with a payment confirmation attached.
What matters is that no human appears anywhere in that sequence. The official x402 whitepaper frames the goal as removing API keys, accounts and subscriptions so that payment becomes part of the request itself. It also sets out the comparison with card rails: an on-chain transaction on Base settles in roughly 200 milliseconds with gas around $0.0001, against a typical card cost of $0.30 plus 2.9%. That gap is what makes a ten-cent payment viable on one rail and impossible on the other.
Why Agents Need a Payment Rail of Their Own
The Account Model Does Not Fit Machines
A human reaching a paid service registers, adds a card, receives credentials and keeps them. The model assumes a persistent party. An agent works differently, often calling a dozen services it has never touched before in the course of a single task, using each once. Registering and adding a card for every one-off call fails on both time and operational cost, while handing a set of long-lived API keys to autonomous software creates a permissions problem that is hard to contain.
x402 answers by reducing payment from a relationship to a single transaction. The official FAQ notes that the protocol is permissionless, that any web API or content provider, crypto-native or not, can integrate it, and that anyone can run a facilitator. For sellers that means charging without building an account system. For agents it means paying without creating one.
Micropayments Become Viable Again
The Chainalysis size distribution is the clearest evidence for that claim. When over 87% of payments sit between one hundredth of a cent and ten cents, the fixed cost of the payment system becomes the decisive variable. A ten-cent transaction cannot absorb thirty cents of fixed fees, but it can absorb $0.0001 of gas. Coinbase's documentation puts facilitator costs at zero for the first 1,000 transactions each month and $0.001 per transaction after that, with on-chain gas separate.
That cost structure changes how things get priced. APIs need not be sold as monthly subscriptions or bundles and can charge per call, data services need not impose minimum spends, and a single inference can be billed on tokens actually consumed. Circle, quoted in the Chainalysis report, frames the division cleanly: card rails for consumer-prompted agent payments, stablecoin rails for machine-to-machine settlement.
What Agents Are Actually Buying
Categories and Geography
Chainalysis found that agents mostly buy machine-readable information and capability: code review, financial intelligence, data and search APIs, plus agent frameworks and tool catalogs. Model inference is among the largest categories, and the data shows AI agents paying other AI agents.
The geographic split is pronounced. US-funded wallets account for about 30% of geolocatable agent-to-service transactions overall, but 88.1% in model inference, 41.8% in agent frameworks and tool catalogs, and 23.2% in data and search APIs. Chinese-linked wallets are the mirror image, at 0.1% of model inference and roughly 90% of security and code-analysis transactions. CoinDesk's coverage of the report quotes Chainalysis head of research Eric Jardine suggesting that Chinese developers may lean more on open-weight models and therefore buy less metered inference, while cautioning that he would not go so far as to say open-source AI is starving Asia's on-chain inference market.
Wallet Behavior Says More Than Volume
The maturity signal sits in the timing data. The median age of a wallet at its first x402 payment fell from 73 days in late 2025 to 18 minutes in the third quarter of 2026. The share of wallets making a first payment within an hour of funding rose from 4% to 67% over the same comparison. Wallets receiving additional funding within 30 days of first being funded rose from 70.6% to 89.3%.
The move from 73 days to 18 minutes describes a change in what a wallet is for. Seventy-three days is a human opening an account and waiting on a decision. Eighteen minutes is a payment module provisioned as part of a task and put to work immediately. Hoolie Tejwani of Coinbase Ventures, quoted in the report, puts it as AI agents becoming economic actors where every agent is effectively a new user of the blockchain.
It is worth adding that the report also notes early x402 activity was dominated by memecoin speculation, PING among them, before that heat faded. Separating today's transaction mix from that phase is a prerequisite for reading the data properly.
The Stack Underneath
Chains, Assets and Schemes
x402 is designed to be chain and asset neutral. The whitepaper states that the protocol is built to support any stablecoin, digital asset or blockchain. In implementation, Coinbase's documentation lists CDP facilitator mainnet support for Base, Polygon, Arbitrum, World and Solana, with the exact, upto and batch-settlement schemes on EVM networks and exact on Solana.
On assets, EVM networks can accept any ERC-20 through Permit2 and support EIP-3009 tokens such as USDC and EURC, while Solana covers SPL and Token-2022. USDC dominates in practice for reasons that are not hard to see: native issuance across chains, a stable peg and an issuer on a defined regulatory path. Stablecoin rules therefore feed directly into which assets this rail can use, and the specifics of the US framework are set out in our breakdown of the GENIUS Act proposals and what they mean for USDT and USDC.
Enterprise Infrastructure Picks It Up
What moved x402 beyond crypto-native usage was cloud integration. AWS explains in the Bedrock AgentCore Payments preview announcement that the feature lets agents autonomously pay for APIs, MCP servers, web content and other agents, with the platform handling wallet authentication, transaction execution, spending governance and observability. When a resource returns HTTP 402, AgentCore negotiates x402 and pays in stablecoins without interrupting the agent's reasoning. Developers can connect a Coinbase CDP wallet or a Stripe Privy wallet.
Coinbase's May 7 post adds the execution detail: settlement on Base in USDC takes roughly 200 milliseconds at less than a fraction of a cent per transaction, and agents reach thousands of x402 services through Coinbase MCP in AgentCore Gateway, with the AWS announcement citing over 10,000 x402 endpoints available via the Bazaar MCP server.
Governance has also moved beyond a single company. The Linux Foundation announced the x402 Foundation in its April 2 press release, with Coinbase, Cloudflare and Stripe as initial developers and announced participants including AWS, Circle, Google, Mastercard, Microsoft, Polygon Labs, Shopify, Solana Foundation and Visa.
Settlement between machines is already denominated in stablecoins. Follow the asset doing the settling on the USDC spot market
Agent Wallets and Spending Limits
The Agent Never Holds the Key
Handing payment authority to autonomous software raises key management first. The architecture Coinbase describes for AgentCore handles wallet authentication, transaction signing and payment in a single API call, and states plainly that the agent does not have access to private keys. Even if an agent's reasoning is compromised, what it can reach is a delegated signing capability rather than control of the wallet.
Limits at Both the Platform and Protocol Layer
Spending control exists on two levels. At the platform level, AWS provides session-level spending limits and says they are enforced at the infrastructure layer, while Coinbase's example is a time-bound allowance such as one dollar expiring in five minutes. At the protocol level, the upto scheme lets a client authorize a ceiling and be charged only for actual usage, and batch-settlement applies a per-request maximum before clearing in bulk.
The security model separates duties as well. Per the official FAQ, buyers sign every PaymentPayload, a facilitator that tampers with a transaction cannot settle it, and sellers never hold the buyer's key. On compliance, Coinbase says its CDP facilitator applies sanctions and illicit-finance risk controls to every transaction.
Irreversibility Is a Real Constraint
Payments under the exact scheme cannot be reversed, which is inherent to on-chain settlement and the sharpest difference from card networks. The FAQ treats refunds as a business-logic problem, with merchant-initiated refunds or batch-settlement withdrawals as the available routes. For enterprises that means dispute handling has to be built into the application, because the payment network will not provide it.
x402 Is Not a Token, and What Actually Drives This Market
Separate the Protocol From the Tickers
x402 has no official token. Value capture does not run through an issuance, settlement happens in stablecoins such as USDC, and neither the whitepaper nor the documentation contains a native token design. Odaily's April 7 review found that tokens grouped into the so-called x402 ecosystem, including PING as the first token minted through the protocol, the autonomous-agent project Daydreams and the payment-verification project PAYAI, were mostly down 80% to 98% from their highs, partly because narrative heat ran ahead of real on-chain adoption. Protocol adoption and the price of anything named after x402 are not mechanically linked.
The Risks Worth Tracking
Transaction count is the figure most likely to be misread. Chainalysis did not publish a total dollar value for the 138 million payments, and given the size distribution, the overwhelming majority were worth less than a dime. Treating count growth as economic growth overstates the current scale of this rail considerably.
Concentration is the second risk. Activity is heavily centered on Base and clustered in a handful of service categories, so congestion, downtime or a policy change on one chain transmits straight through. Regulation is the third, since agent-initiated cross-border payments have little settled precedent in anti-money-laundering, sanctions screening or tax treatment, and tighter stablecoin rules change which assets and which parties can use the rail. Last is agent security itself. Once prompt injection becomes an attack surface that can trigger spending, the limit is the final gate, and the quality of that gate depends entirely on the developer.
Three Paths Forward
In an infrastructure case, cloud and payment incumbents keep integrating, x402 becomes one of the default ways agents buy paid services, volume keeps climbing while ticket sizes stay tiny, and the value accrues to stablecoin settlement scale and the facilitator service layer.
In a competing-standards case, x402 runs in parallel with card-network agent payment schemes and other protocols, with consumer-prompted payments staying on cards and machine-to-machine settlement moving to stablecoins, which is the division Circle describes in the report.
In a contraction case, tighter regulation or a security incident cools enterprise appetite, growth stalls and the ecosystem retreats into a few verticals. Note that even a healthy protocol does not imply healthy third-party tokens bearing its name, and the two should be assessed separately.
The Watchlist
The figures worth following are transaction count and size distribution in the next Chainalysis report, which will show whether micropayments are migrating toward larger amounts; the protocol's version cadence and new chain support under Linux Foundation governance; whether AWS moves its preview to general availability and whether another major cloud provider follows; and USDC issuance and circulation across chains, since that is the fuel this rail actually runs on.
Exclusive View from James Mitchell
For James Mitchell, the most telling figure in the report is not 138 million but the collapse in median wallet age at first payment from 73 days to 18 minutes. Transaction counts can be inflated by one application looping through calls, but the timing structure reveals what a wallet is for. Seventy-three days describes an account a person opened while waiting on a decision. Eighteen minutes describes a payment module provisioned as part of a task. That is the shift from an account a human holds to a component software uses, and once it happens, growth stops depending on user acquisition and starts depending on how many agents get deployed.
Two misreadings look likely. The first ties protocol adoption to token prices. x402 has no official token, USDC is the settlement asset, and third-party tokens carrying the name are mostly down 80% to 98% from their highs. Those two curves diverged over the past year, and there is no reason to expect them to converge. The second uses transaction count as a proxy for economic size. With more than 87% of payments under ten cents, total flow is far smaller than the headline count suggests, and the metric that matters is whether the size distribution moves up, meaning agents start buying more expensive services rather than buying the same cheap ones more often.
The variable most worth watching is the depth of enterprise adoption. The AWS integration remains in preview, and the distance from preview to general availability, and from availability to enterprises loosening spending authority in production, runs through procurement, audit and risk management. If a second major cloud provider ships comparable integration over the next few quarters, or AWS promotes the feature to general availability with wider regional coverage, the nature of this rail changes from a crypto-native use case to enterprise infrastructure. If integration stays in preview indefinitely, growth stays inside the crypto-native agent ecosystem.
Across assets, the implication may be larger for stablecoins than for crypto markets generally. Machine-to-machine settlement is a genuinely new category of demand, independent of speculative sentiment and market cycles, scaling instead with agent deployment. If it keeps expanding, stablecoins move from being a trading medium and a risk-off instrument to being the settlement layer of a machine economy, which is precisely the part regulators care most about and are most likely to write rules for first. Whether adoption or the regulatory framework moves faster will shape what this rail looks like over the next several years.
FAQ
What exactly is x402?
x402 is an open internet payment protocol created by Coinbase and contributed to the x402 Foundation under the Linux Foundation. It revives HTTP's long-dormant 402 Payment Required status code: a server answers an unpaid request with 402 and attaches the price, the recipient address and the accepted assets, the client signs a payment and retries, and a facilitator verifies and settles on-chain. The whole exchange happens at the HTTP layer, with no account, subscription or API key required.
Does x402 have its own token?
No. x402 is a protocol rather than an asset, neither the documentation nor the whitepaper contains a native token design, and settlement uses stablecoins such as USDC. Tokens marketed as part of an x402 ecosystem are third-party projects with no value-capture relationship to the protocol. Odaily's April review found PING, Daydreams and PAYAI mostly down 80% to 98% from their highs during a period when protocol transaction counts were still rising.
Why can't AI agents just use credit cards?
The cost structure does not fit. More than 87% of x402 payments fall between one hundredth of a cent and ten cents, while a typical card charges $0.30 plus 2.9% per transaction, so a ten-cent payment cannot carry the fixed cost. Card payments also depend on accounts, stored credentials and human authorization, and agents routinely call services they have never touched before, making an account relationship per one-off call operationally impractical.
Which blockchains and assets does x402 support?
The protocol is designed to be chain and asset neutral. Coinbase's documentation lists CDP facilitator mainnet support for Base, Polygon, Arbitrum, World and Solana. On assets, EVM networks can accept any ERC-20 via Permit2 and support EIP-3009 tokens such as USDC and EURC, while Solana covers SPL and Token-2022 tokens. USDC is the most common settlement asset in practice, and Base currently carries the bulk of the volume.
Over what period were the 138 million transactions recorded?
The Chainalysis report covers the twelve months ending July 1, 2026, with the micropayment size analysis extended to the sixteen months ending September 2026 because x402 is so new. Within that window the firm counted more than 138 million x402 transactions on Base. Two caveats apply: no corresponding dollar total was published, and the figures capture identifiable x402 activity rather than the global AI payments market.
Is it safe to let an agent spend on its own?
Safety depends on limits and key isolation being in place. In Coinbase's architecture the agent never touches private keys and can only exercise a delegated signing capability, AWS enforces session-level spending limits at the infrastructure layer, and the protocol's upto scheme caps authorization while settling only actual usage. However, payments under the exact scheme are irreversible, refunds must be handled in business logic, and prompt injection remains a live attack surface, so the configured limit effectively defines the maximum loss.
Are enterprises using x402 already?
A major cloud provider has integrated it. The preview of AWS Bedrock AgentCore Payments builds in x402 natively, letting agents pay for APIs, MCP servers, web content and other agents, with a choice of a Coinbase CDP wallet or a Stripe Privy wallet. Coinbase reports settlement on Base in USDC at roughly 200 milliseconds and access to over 10,000 x402 endpoints through the Bazaar MCP server. The feature is still in preview with limited regional coverage.
How should an investor think about this sector?
The practical approach is to separate protocol adoption from token narratives. Growth in x402 shows up as stablecoin settlement volume and demand for infrastructure services, not as value capture by any particular token. The indicators that matter are whether payment sizes drift upward, whether enterprise integrations move from preview to general availability, whether chain support expands, and how stablecoin regulation develops, since that determines which assets the rail can use and which parties can use it.
Disclaimer
The information above is provided for general market and technical analysis only and does not constitute investment advice, financial advice, legal advice, tax advice or a recommendation to trade. Prices of crypto assets, equities and other related financial assets can fluctuate sharply, and past performance, technical indicators and on-chain data do not guarantee future results. The transaction data, protocol specifications, integration milestones and governance arrangements cited here reflect publicly available information at the time of publication, and protocol versions, supported networks and platform features may change at any time, so the latest official documentation should be treated as authoritative. Readers should conduct their own research and make decisions based on their own financial circumstances, investment objectives and risk tolerance, consulting a qualified professional where appropriate. The MEXC Crypto Pulse team accepts no liability for any direct or indirect loss arising from the use of this information.
About the Author
James Mitchell specializes in technical analysis, market trends, and trading strategies for both Bitcoin and altcoins. Based in London, he has over 10 years of experience in financial markets. Before joining MEXC Learn, James worked as a senior analyst at a leading European investment firm, where he developed expertise in risk management and quantitative trading. His transition to cryptocurrency markets began in 2017, and he has since become recognized for his data-driven approach. He holds a Master's degree in Financial Economics from the London School of Economics. His analytical approach combines traditional technical analysis with on-chain metrics to provide readers with actionable insights.
Areas of Expertise: Technical Analysis, Market Trends and Cycles, Trading Strategies, Bitcoin and Altcoin Analysis, Risk Management.
Research References
Want the fastest access to MEXC's latest updates? Join our official Telegram group now!
Account Verification: Understand KYC | How to Complete KYC
Market Opportunity
4 Price(4)
$0.013318
$0.013318$0.013318
USD
4 (4) Live Price Chart
The articles shared on this page are sourced from public platforms and are provided for reference only. They do not represent the position or views of MEXC. All rights belong to James Mitchell. If you believe any content infringes upon the rights of a third party, please contact [email protected] for prompt removal. MEXC does not guarantee the accuracy, completeness, or timeliness of any content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be interpreted as a recommendation or endorsement by MEXC. For expert insights and in-depth analysis, visit MEXC Learn.
Latest Updates on 4
View More
Robinhood Stock Tokens Hit $10.4B: Is DeFi Repricing Equities?
Robinhood Stock Tokens have generated approximately $10.4 billion in spot DEX trading volume over the past 30 days, highlighting how quickly tokenized equity exposure is moving from brokerage-style access into crypto-native market infrastructure. The figure measures trading turnover rather than capital invested, TVL or underlying equity ownership, but its scale is still notable because activity is increasingly taking place through decentralized exchanges rather than exclusively inside a closed brokerage interface
2026/09/24
Tokenized Stock Trading Hits $20.9B: Why Uniswap Leads
Tokenized stock trading has reached a new liquidity milestone, generating approximately $20.9 billion in decentralized exchange volume over the past 30 days. Uniswap accounted for 60.1% of that activity, with Uniswap v4 representing 40.7% and v3 another 19.4%, equivalent to roughly $12.6 billion in combined trading volume. The figures show that tokenized equities are progressing beyond issuance and brokerage access toward an increasingly active onchain secondary market.
2026/09/28
RWA Perpetuals Hit $1.4T: Why Trading Is Exploding
RWA perpetuals are becoming one of the fastest-growing bridges between traditional markets and crypto-native trading. Recent industry analysis cited by MEXC indicates that onchain RWA perpetual activity in July 2026 reached an annualized trading run rate of approximately $1.4 trillion, reflecting rapid growth in perpetual contracts linked to equities, commodities, foreign exchange, indices and other offchain reference markets
2026/09/30
You May Also Like
HOT
Currently trending cryptocurrencies that are gaining significant market attention
Crypto Prices
The cryptocurrencies with the highest trading volume
Newly Added
Recently listed cryptocurrencies that are available for trading