$\"x402$

The x402 protocol is an open payment standard that uses the HTTP 402 status code to enable AI agents and software to make instant stablecoin payments onchain. Developed by Coinbase and backed by the x402 Foundation, it turns any API endpoint into a paywall that machines can navigate without human intervention, credit cards, or subscription accounts.

When an AI agent requests a resource that costs money, the server replies with an HTTP 402 Payment Required response. The agent reads the payment instructions, signs a stablecoin transaction, attaches the proof, and retries the request. The server verifies the payment and returns the data. The entire cycle takes seconds, requires no login, and settles onchain.

This guide covers what x402 is, how it works at the protocol level, which blockchains and stablecoins it supports, who is building with it, and how it fits alongside related standards like Google's Agent2Agent (A2A) and Agent Payments Protocol (AP2).

Why x402 Exists

HTTP 402 Payment Required has been a reserved status code since the early 1990s. The original HTTP specification set it aside for future use in digital payments, but no standard ever materialized. Credit cards, OAuth tokens, and API keys filled the gap instead.

Those mechanisms work for humans but break down for autonomous software. An AI agent cannot sign up for a SaaS account, enter credit card details, or negotiate an enterprise contract. It needs a payment method that is native to the web's request-response model, settles in seconds, and requires no pre-existing relationship between buyer and seller.

The x402 protocol solves this by embedding stablecoin payments directly into HTTP. Any server can require payment for a resource, and any client, whether human-operated or fully autonomous, can pay for it with a single additional header. There are no subscriptions, no prepayments, and no lock-in.

How the x402 Protocol Works

The x402 payment flow operates through a simple request-response cycle between three parties: the client (the AI agent or application making the request), the resource server (the API or service requiring payment), and the facilitator (an onchain verification and settlement service).

Step-by-Step Payment Flow

Request: The client sends a standard HTTP request to the resource server.
402 Response: If payment is required, the server responds with HTTP 402 and includes payment instructions in a structured header. These instructions specify the price, accepted tokens, recipient address, and the network to settle on.
Payment Construction: The client reads the payment instructions and constructs a signed payment payload. For EIP-3009 tokens like USDC, this uses a gasless authorization signature. For other ERC-20 tokens, it uses Permit2.
Retry with Payment: The client retries the original request with the signed payment attached in a header.
Verification and Settlement: The resource server forwards the payment to a facilitator, which verifies the signature, checks the client's balance, and settles the payment onchain. Once confirmed, the server delivers the requested resource.

The facilitator is a critical piece of the architecture. It abstracts away onchain complexity so that resource servers do not need to run blockchain nodes or manage wallets. Coinbase and other providers operate public facilitators that handle verification and settlement for free on supported networks.

The Facilitator's Role

A facilitator is a trusted intermediary that sits between the resource server and the blockchain. When a resource server receives a payment header, it sends the payload to the facilitator for verification. The facilitator checks that the signature is valid, the payer has sufficient balance, and no replay attack is occurring. If everything checks out, it submits the transaction onchain and confirms settlement to the resource server.

Public facilitators from Coinbase (via CDP) are available for Base, Solana, and Stellar at no cost. Third-party facilitators can also be deployed for custom settlement logic, alternative chains, or specialized compliance requirements. This open facilitator model means x402 is not locked to a single chain or token. It supports any ERC-20 via Permit2 and works natively with USDC and EURC via EIP-3009 for gasless transfers.

Supported Blockchains and Tokens

The x402 protocol is chain-agnostic by design. Its payment header format does not assume a specific blockchain; it describes the network, token, amount, and recipient, and leaves settlement to the facilitator. As of early 2026, x402 is live on multiple networks:

Network	Token Support	Facilitator	Finality
Base	USDC, EURC, ERC-20s	Coinbase CDP (free)	~2 seconds
Solana	USDC, SPL tokens	Coinbase CDP (free)	~400ms
Stellar	USDC, Stellar assets	OpenZeppelin Relayer	~5 seconds
Arbitrum	USDC, ERC-20s	Third-party	~1 second
Polygon	USDC, ERC-20s	Coinbase CDP	~2 seconds
Ethereum L1	USDC, ERC-20s	Third-party	~12 seconds

Base and Solana are the most commonly used networks for x402 payments due to low fees and fast finality. Most x402 transactions settle in stablecoins, primarily USDC, which is the dominant settlement token across the protocol. For applications that need to route payments across chains, cross-chain intent protocols and intent-based solvers can abstract away the chain selection entirely.

The x402 Foundation and Ecosystem

Coinbase and Cloudflare launched the x402 Foundation in 2025 to establish x402 as the universal standard for internet-native payments. The foundation oversees protocol governance, ecosystem growth, and interoperability across implementations.

Foundation membership has expanded rapidly. Core members now include Google, Visa, AWS, Circle, Anthropic, and Vercel alongside the founding partners. The breadth of this coalition, spanning cloud infrastructure, payments, AI, and crypto, signals that x402 is being positioned as foundational plumbing for the agentic economy rather than a crypto-only standard.

Who Is Building with x402

The ecosystem spans several categories of builders and integrations:

Infrastructure providers: Cloudflare integrated x402 into its Workers platform and is piloting a pay-per-crawl product. Vercel supports x402 middleware for serverless functions. Zuplo offers x402 paywalls for API gateway customers.
AI agent frameworks: MCP (Model Context Protocol) servers are adding x402 support so that AI models can pay for tool calls and data access autonomously. Developers are building x402-enabled MCP servers that let agents purchase compute, data, and API access without pre-provisioned keys.
Identity and verification: World (formerly Worldcoin) has integrated agent-identity tooling with x402, attaching cryptographic proof of human identity to AI agent transactions for stablecoin micropayments.
Payment aggregators: Kobaru provides a transparent proxy layer that lets vendors add x402 paywalls to existing APIs without modifying backend code. Agently operates a routing and settlement layer for agent-to-agent commerce.
Financial institutions: Visa added x402 support through its Trusted Agent Protocol (TAP), and Stripe integrated x402 through its Agent Commerce Protocol (ACP), connecting the protocol to traditional payment rails.

On Solana, the protocol has seen meaningful adoption since the chain integration shipped in mid-2025. Across all networks, adoption is accelerating as more APIs add x402 paywalls and more AI agents gain wallet capabilities.

Key Use Cases for x402

x402 is purpose-built for scenarios where one piece of software needs to pay another piece of software. The most active use cases include:

AI agent API access: An agent that needs weather data, financial quotes, or geolocation services can pay per request instead of managing API keys and subscription tiers.
Machine-to-machine micropayments: IoT devices, automated trading bots, and backend services can settle sub-cent payments for data feeds, compute cycles, or storage access.
Content paywalls: Websites can charge per article, per data export, or per search query. The x402 header makes the cost transparent and the payment automatic.
MCP tool monetization: Developers building MCP servers can monetize tool access. An AI model calling a translation tool, a database query tool, or an image generation tool can pay the provider directly per invocation.
Data marketplace access: Agents that need training data, market research, or proprietary datasets can purchase access in real time without negotiating contracts.

The common thread is removing friction from machine-to-machine payments. Where traditional payment infrastructure requires accounts, credentials, and human approval, x402 requires only a wallet with a stablecoin balance and the ability to sign a transaction. This aligns with the growing use of stablecoin payments for programmatic settlement across crypto and traditional finance.

x402 vs. Agent2Agent (A2A) vs. Agent Payments Protocol (AP2)

Three protocols are shaping the AI agent economy, and they serve different functions. Understanding where each fits prevents confusion between communication, payment, and authorization layers.

	x402	A2A (Agent2Agent)	AP2 (Agent Payments)
Purpose	Onchain payment settlement	Agent-to-agent communication	Payment authorization framework
Created by	Coinbase	Google	Google
Layer	Payment execution (HTTP)	Communication (agent interop)	Authorization and governance
Settlement	Stablecoins onchain	N/A (not a payment protocol)	Supports fiat + crypto via extensions
Launched	May 2025	April 2025	2026
Relationship	Can integrate with A2A and AP2	Can use x402 for payments	Uses x402 as crypto payment rail

A2A is a communication protocol. It allows agents built on different frameworks to discover each other, exchange messages, and coordinate tasks. It does not handle payments.

AP2 is a payment authorization framework. It defines how agents identify themselves, what credentials they carry, and how payment requests are approved across platforms. It supports both fiat and crypto rails.

x402 is a payment execution protocol. It handles the actual movement of money onchain. When an AI agent needs to pay for something, x402 is the mechanism that transfers stablecoins from buyer to seller.

These three protocols are complementary. Google launched an official A2A x402 extension that lets agents using A2A for communication settle payments via x402. AP2 uses x402 as its stablecoin payment rail. In practice, a fully autonomous AI agent might use A2A to find a service, AP2 to authorize the transaction, and x402 to settle the payment.

x402 and Onchain Standards

x402 operates at the HTTP layer, but it depends on onchain token standards for settlement. The protocol uses EIP-3009 (transferWithAuthorization) for gasless USDC transfers and Permit2 for other ERC-20 tokens. Emerging standards like ERC-8004 are also relevant, as they define trustless payment channels that could further reduce settlement latency for high-frequency x402 transactions.

The interaction between HTTP-level payment negotiation (x402) and onchain settlement standards (EIP-3009, Permit2, ERC-8004) is what makes the protocol efficient. The agent never submits a raw blockchain transaction. Instead, it signs an authorization that the facilitator executes, keeping the agent's interaction at the HTTP level while settlement happens onchain in the background.

Getting Started with x402

For developers who want to accept x402 payments, the integration is lightweight:

Add x402 middleware to your server. SDKs are available for Node.js, Python, and Go. The middleware intercepts requests, checks payment status, and returns 402 responses with payment instructions for unpaid requests.
Configure pricing. Set per-endpoint or per-resource pricing in the stablecoin of your choice. Most implementations use USDC on Base for lowest fees.
Point to a facilitator. Use Coinbase's free public facilitator or deploy your own. The facilitator handles all onchain verification and settlement.
Test and deploy. The x402 GitHub repository includes sample applications, integration tests, and testnet configurations.

For AI agents and clients, x402 support means equipping the agent with a wallet (or access to a wallet service) and adding logic to handle 402 responses. Most agent frameworks are adding this as a built-in capability.

Frequently Asked Questions

What is the x402 protocol?

The x402 protocol is an open payment standard that uses the HTTP 402 status code to enable instant stablecoin payments over the web. When a server requires payment for a resource, it responds with a 402 status code and payment instructions. The client signs a stablecoin transaction and retries the request with the payment attached. A facilitator verifies and settles the payment onchain.

Is x402 the same as Agent2Agent (A2A)?

No. x402 and A2A are separate protocols that serve different functions. x402 is a payment execution protocol that moves stablecoins onchain. A2A is Google's agent communication protocol that lets agents discover and coordinate with each other. They are complementary: Google launched an A2A x402 extension so agents can use A2A for communication and x402 for payment settlement.

What stablecoins does x402 support?

x402 supports USDC and EURC natively via EIP-3009 for gasless authorization. It also supports any ERC-20 token through Permit2 and SPL tokens on Solana. USDC is the most widely used settlement token across the x402 ecosystem.

Which blockchains support x402?

x402 is live on Base, Solana, Stellar, Arbitrum, Polygon, and Ethereum mainnet. Base and Solana are the most active networks, with free public facilitators from Coinbase. The protocol is chain-agnostic, and new networks can be added by deploying a facilitator.

Who created x402?

Coinbase created and open-sourced the x402 protocol in May 2025. The x402 Foundation, launched by Coinbase and Cloudflare in 2025, now governs the protocol. Foundation members include Google, Visa, AWS, Circle, Anthropic, and Vercel.

How much does it cost to use x402?

The protocol itself is free and open source. Coinbase operates free public facilitators on Base, Solana, and other supported networks. The only costs are the underlying blockchain gas fees, which on L2 networks like Base are typically fractions of a cent per transaction. There are no subscription fees, platform fees, or percentage-based charges.

Can x402 handle micropayments?

Yes. x402 is specifically designed for high-frequency, low-value transactions. On Base and Solana, gas fees are low enough to make sub-cent payments economically viable. This makes x402 well-suited for per-request API pricing, pay-per-query data access, and other machine-to-machine micropayment use cases.

How does x402 relate to MCP (Model Context Protocol)?

MCP defines how AI models interact with external tools and data sources. x402 provides the payment layer that lets those tools charge for access. Developers are building MCP servers with x402 paywalls, enabling AI models to pay for tool invocations, data retrieval, and compute resources autonomously.

The Bottom Line

The x402 protocol fills a gap that has existed since the web's inception: a native way for software to pay for resources over HTTP. By embedding stablecoin payments into the request-response cycle, x402 gives AI agents, automated services, and MCP tool providers a frictionless way to transact. With backing from the x402 Foundation and integration into Google's agent protocols, x402 is becoming the default payment rail for the machine economy.

As AI agents become more autonomous and the demand for machine-to-machine payments grows, x402 provides the infrastructure to make those payments instant, programmable, and settled onchain.

x402 is an open HTTP 402 payment protocol that lets servers charge AI agents and machines for API calls using stablecoins. Coinbase released x402 in May 2025. Servers return HTTP 402 with payment requirements; clients pay in USDC on Base; facilitators verify and settle onchain.

What Is x402?

x402 is an open HTTP payment protocol that uses the 402 Payment Required status code to negotiate and settle stablecoin transfers between a client and a server. The status code itself was reserved in the original HTTP/1.0 specification in 1991 but never standardized for any specific payment system; for thirty-five years it sat in the spec as a placeholder. x402 fills that placeholder with a concrete schema: a JSON envelope in the response header for what payment is required, and a signed payload in the request header for the response.

The protocol is permissionless and chain-agnostic by design. Any server can return 402, any client can satisfy it, and the underlying token transfer happens onchain rather than through a card network. Coinbase published the first reference implementation under Apache 2.0 with TypeScript, Python, and Go SDKs at GitHub, alongside framework adapters for Express, Fastify, Next.js, and Axios. The reference repo currently records 28 releases. The official spec lives under the x402 Foundation at x402.org.

Governance moved to the x402 Foundation in two steps. Coinbase and Cloudflare announced the foundation on September 23, 2025. The Linux Foundation formalized it on April 2, 2026 at the MCP Dev Summit North America. The launch member list spans 22 organizations including Adyen, AWS, American Express, Base, Circle, Fiserv Merchant Solutions, Google, KakaoPay, Mastercard, Microsoft, Polygon Labs, PPRO, Shopify, Solana Foundation, Stripe, thirdweb, and Visa. The foundation owns the spec, runs working groups, and maintains the canonical reference implementations. Coinbase contributed the protocol but does not control its evolution.

The scale numbers point to a real workload, not a demo. Coinbase reported 69,000 active agents, 165 million transactions, and approximately $50 million in cumulative volume on x402 by late April 2026, the week it launched the Agent.market directory of x402-paywalled services. The implied average value per call sits near $0.30, calibrated for sub-cent and small-cents API metering rather than retail purchases. The transaction count alone exceeds the daily volume of most consumer-facing payment processors at the same ticket size, an early read on how dense agent traffic gets when the friction of accounts and API keys disappears.

How does x402 actually work?

Every x402 transaction follows a four-step request-response cycle: the client pings the endpoint, the server returns 402 with payment terms, the client signs a token transfer authorization, and the client retries the request with the signed payload in a header. A facilitator confirms onchain settlement, then the server returns the resource alongside an optional receipt header.

$\"How$

Every x402 transaction follows a four-step request-response cycle. The client makes a normal HTTP request. The server returns 402 with payment terms. The client constructs and signs a payment payload. The client retries the request with the signed payload in a header, and the server returns the resource after a facilitator confirms settlement. The protocol uses two named headers: PAYMENT-REQUIRED on the response side and PAYMENT-SIGNATURE on the request side, with an optional PAYMENT-RESPONSE for settlement confirmation.

Step 1: client request

The client issues a normal HTTP request to a paywalled resource. No special headers, no authentication, no payment information. From the client's perspective this is the same request it would make against an unauthenticated endpoint.

Step 2: server returns 402 with payment terms

The server responds with HTTP status 402 Payment Required. The body and the PAYMENT-REQUIRED header carry a JSON envelope describing what the client needs to pay. The fields are minimal but specific: a payment scheme (the protocol uses exact for fixed-amount transfers, with experimental support for upto consumption-based pricing), a network identifier in CAIP-2 format such as eip155:8453 for Base, the asset contract address (typically the USDC contract on the named network), the recipient address, the maximum amount, an expiry timestamp, and an optional facilitator endpoint URL.

The CAIP-2 namespace matters because it is what makes x402 chain-agnostic. eip155:1 is Ethereum mainnet. eip155:8453 is Base. solana:mainnet is Solana. The same protocol envelope describes a payment regardless of the underlying chain, which lets clients route to whichever network has the cheapest gas and the right token. The Coinbase facilitator currently supports Base, Polygon, Arbitrum, and World as EVM networks, plus Solana for SVM. Stellar shipped a production-ready x402 facilitator (Built on Stellar / OpenZeppelin Relayer) in March 2026, joining the EVM and SVM tracks already in the CDP facilitator.

Step 3: client signs a payment authorization

The client reads the PAYMENT-REQUIRED envelope and constructs a signed transfer authorization. x402 supports two signing paths depending on the token. The EIP-3009 path handles USDC and EURC, both of which implement the transferWithAuthorization entry point natively. The Permit2 path handles every other ERC-20.

EIP-3009 was proposed by Peter Jihoon Kim, Kevin Britz, and David Knott on September 28, 2020. The core function takes seven fields: from, to, value, validAfter, validBefore, nonce, and a signature over the EIP-712 typed-data hash. The nonce is a random 32-byte value rather than a sequential counter, which is what lets a wallet construct several authorizations in parallel without collision. Circle's USDC contract has implemented EIP-3009 since the v2 upgrade, which is why it is the smoothest path for x402 transfers; the facilitator submits the signed authorization and the recipient's balance updates without a prior approval transaction.

Permit2, originally shipped by Uniswap in 2022, sits in front of any ERC-20. The client signs a Permit2 message with a deadline and a token-spend allowance scoped to the Permit2 contract. The facilitator submits a single transaction to Permit2, which pulls the ERC-20 from the client's address and forwards it to the recipient. Permit2 charges one approval ever (to itself) per token; subsequent payments require only an off-chain signature.

Solana follows a different mechanism because it has neither ERC-20 nor EIP-712. The x402 Solana implementation uses a partial transaction signed by the client. The client constructs a Solana SPL token transfer, signs the message, and sends the partial transaction to the facilitator. The facilitator co-signs as fee payer and submits to a validator. Functionally the result is the same: the client never holds SOL for gas, and the recipient receives SPL USDC.

Step 4: client retries; facilitator settles

The client makes the same request again. This time it includes the signed payload in the PAYMENT-SIGNATURE header, encoded as base64. The server has two options for verification. It can pass the signed payload to a facilitator over a separate API call, in which case the facilitator validates the signature, simulates the onchain call, broadcasts the transaction, waits for confirmation, and returns success. Or the server can run the verification itself by holding its own RPC keys and calling the token contract directly. Most production deployments use a facilitator because the operational footprint of running RPC infrastructure across four chains is non-trivial.

Once settlement confirms, the server returns 200 with the resource and an optional PAYMENT-RESPONSE header carrying the transaction hash and any settlement metadata. The client now has both the data it requested and a verifiable receipt of payment. Total round-trip latency is dominated by the chain confirmation rather than the HTTP layer; on Base, where blocks land every two seconds, an end-to-end x402 call typically completes inside three or four seconds. Allium's x402 explainer documents the same flow and notes that facilitators handle gas, retries, and chain routing on behalf of both ends.

The whole exchange composes with anything that already speaks HTTP. An agent calling a paywalled REST endpoint adds one header and handles one extra status code. A model gateway proxies x402 calls without inspecting them. The Cloudflare Agents SDK ships native middleware that intercepts 402 responses, fetches the appropriate signature from a configured wallet, and retries automatically, which means in many client codepaths the protocol is invisible above a single SDK call.

The x402 Stack: Facilitators, Foundation, and Supported Chains

The x402 stack splits across three operational layers: a facilitator that handles signature verification and onchain submission, a foundation that owns the protocol specification, and a chain layer that holds the stablecoin balances. Each layer is swappable, and merchants can run their own facilitators or bypass them entirely with self-managed RPC infrastructure.

x402 is a thin protocol that delegates most heavy lifting to three external pieces: the facilitator that handles chain submission, the foundation that owns the spec, and the chain itself that holds the stablecoin balances. Each layer has a specific shape worth understanding before integrating.

The facilitator is the operational layer. It accepts a signed payload, verifies the signature, simulates the token transfer, broadcasts the transaction, and reports back to the server. Coinbase runs the most-used implementation, the CDP Facilitator, which is free for the first 1,000 transactions per month and charges $0.001 per transaction beyond that according to the CDP docs. Cloudflare ships a facilitator inside its Agents SDK with a deferred-payment scheme that batches sub-cent payments and settles on a separate cadence, useful for very high-frequency calls. Anyone can run a facilitator. The protocol does not require a specific operator, and merchants with their own RPC infrastructure can bypass facilitators entirely.

The x402 Foundation is the standards layer. Sitting under the Linux Foundation, it owns the protocol specification, runs working groups, and maintains the reference implementations. The 22-organization launch list spans payment networks (Visa, Mastercard, American Express, PayPal-affiliated PPRO, Adyen, Stripe, Fiserv), cloud and infra (AWS, Cloudflare, Microsoft, Google, thirdweb), stablecoin issuers and chains (Circle, Base, Polygon Labs, Solana Foundation), and shopping surfaces (Shopify). The breadth matters: x402 is not a stablecoin-only protocol or a Coinbase-only protocol. It is positioned to settle in fiat eventually through the card-network members, even though every production deployment in April 2026 uses stablecoins.

The chain layer is where the stablecoin actually moves. Base is the default in most x402 docs because Coinbase is the issuer of the chain and the protocol's incubator. Polygon, Arbitrum, and World cover the rest of the EVM footprint inside the CDP facilitator. Solana lives in its own track with SPL USDC and the partial-transaction signing path described above. Stellar has its own production facilitator (run by OpenZeppelin's Relayer service) that went live in March 2026. Stablecoins that travel x402 today are USDC and EURC on EVM (via EIP-3009), and SPL USDC on Solana. CoinGecko's x402 endpoint notes that Base and Solana are the two settlement networks accepted at the time of the integration.

Each chain has its own gas economics, and that is where the protocol bumps into reality. Base settles in roughly two-second blocks for fractions of a cent in gas. Solana settles in about half a second for similar fees. Arbitrum and Polygon are slower than Base but faster than Ethereum mainnet. Ethereum L1 is technically supported but functionally too expensive for the sub-dollar payments x402 is designed for. Routing decisions inside agent stacks usually default to Base for EVM and Solana for high-throughput cases, with the rest reserved for specific chain-local services.

Real x402 Deployments

Five named x402 deployments were running in production by April 2026: Coinbase Agent.market, Stripe Machine Payments, CoinGecko paid endpoints, Circle Wallets reference workflow, and the Cloudflare Agents SDK. Together they account for the bulk of the 165 million transactions and roughly $50 million in cumulative protocol volume reported at the Foundation launch.

x402 left the demo phase by the end of Q1 2026. Five named deployments are running in production today and are worth examining as a sanity check on the protocol's actual usage.

Coinbase Agent.market. Coinbase launched Agent.market in April 2026 as a directory of x402-paywalled services aimed at autonomous agents. The marketplace organizes endpoints into seven categories, reasoning, data, media, search, social, infrastructure, and trading. Each listing carries pricing, an example call, and a payment endpoint. The 165 million transactions and roughly $50 million in cumulative volume cited at launch are the protocol-wide totals across all x402 services as of mid-April 2026, not the marketplace alone, but Agent.market consolidates discovery in a way that pushed adoption sharply that month.

Stripe Machine Payments. Stripe shipped x402 support on February 10, 2026 in a preview product called Machine Payments, announced by product manager Jeff Weinstein. The launch supports USDC on Base. Stripe also released an open-source CLI named purl, plus Python and Node sample code for both the client and server sides. Stripe positions Machine Payments as a developer-facing extension of its broader Agentic Commerce Suite, which targets agent-initiated card payments and stablecoin payments inside the same Stripe account. The Block's coverage of the launch confirms the Feb 10 date and the USDC-on-Base launch pair.

CoinGecko x402 endpoints. CoinGecko activated x402 across a set of high-leverage market-data endpoints (token prices, DEX liquidity, trending activity) on the same window as the Stripe launch. Pricing is a flat $0.01 USDC per request, with payment accepted on Base or Solana. The integration eliminates the API-key onboarding that previously required a CoinGecko account and a paid subscription tier. An agent that needs a single price quote pays a cent and gets the data; an agent that polls heavily pays in proportion. Coinbase's launch page for the integration documents both the pricing and the supported networks.

Circle Wallets + USDC. Circle published a reference workflow for autonomous agents using Circle Wallets, USDC, and x402. The flow combines Circle's MPC-based developer wallets with the EIP-3009 transferWithAuthorization path. An agent provisions a Circle wallet through the API, funds it with USDC (testnet via faucet), encounters an x402 paywall, calls the Circle Signing API to produce the EIP-712 signature, and posts the result via PAYMENT-SIGNATURE. The reference example pays $0.01 USDC for wallet risk-profile data. Circle's blog frames the integration as the canonical pattern for agent payment infrastructure where the agent never holds raw private keys.

Cloudflare Agents SDK. Cloudflare integrated x402 into its Agents SDK and MCP servers on September 23, 2025, the same day the foundation was announced. The integration includes a deferred-payment scheme designed for sub-cent transactions where per-call settlement costs more than the call. Clients post a credential, servers record consumption, and settlement happens on a separate cadence. The Cloudflare implementation also ships an x402 Playground for developers testing the flow without onboarding a wallet first.

Around these five anchors sit dozens of smaller integrations. Allium offers x402-paywalled onchain data through its Allium for Agents product. StraitsX added native x402 support for XSGD and XUSD on Solana in December 2025. The reference SDKs accumulate community frameworks (FastAPI, Hono, Cloudflare Workers) outside the official adapter set. The 165 million transaction count is the number that integrates all of these.

Tradeoffs and Limits

x402 trades dispute rights, sub-millisecond latency, and gas-free settlement for chain-native finality and accountless payments. Transactions are non-reversible, end-to-end latency is bound by chain confirmation, and microtransactions below a cent run into gas economics that motivate deferred-payment schemes. Custody also shifts to the agent, requiring MPC wallets or session keys.

x402 solves a specific class of problem and creates new tradeoffs that traditional payment rails do not have. Three are worth flagging in any production-deployment evaluation.

The first is microtransaction economics. x402 is competitive at $0.30 per call because the gas to settle a USDC transfer on Base is well under a cent. At $0.0001 per call, the gas itself becomes a meaningful portion of the spend, which is what motivates Cloudflare's deferred payment scheme and the experimental upto consumption-metered scheme in the reference repo. Most current deployments price in single-digit cents per call (CoinGecko at $0.01, Circle's reference at $0.01), which sits in the comfort zone where standard exact mode is profitable for both ends.

The second is settlement finality and chargeback semantics. x402 transactions are non-reversible by design. Once the facilitator confirms onchain settlement, there is no chargeback path, no dispute window, no merchant pull-back. This is intentional, agents and APIs do not have the human-dispute infrastructure that justifies card-network reversal, but it is a sharp departure from how Stripe and Visa handle agent payments on their card-rail products. Mastercard's Agentic Tokens and OpenAI's Shared Payment Tokens both keep dispute rights in place. x402 does not. Production deployments should treat the payment as final the moment 200 returns and architect refunds at the application layer if they need them.

The third is custody. x402 requires the client to hold a wallet that can sign transfers. For an agent acting on behalf of a human user, that means either the user's wallet (with delegated signing), an MPC-backed agent wallet (Circle Wallets, Coinbase Smart Wallet), or a session-scoped key issued by the agent platform. Each option has its own operational profile. Bare private keys held by an autonomous process are the worst version of this; MPC-backed wallets with policy controls (per-call spend limits, per-day caps, per-merchant allowlists) are the production pattern most large integrators are settling on. The stablecoin developer tools ecosystem now includes wallet-as-a-service offerings explicitly marketed for agent payments.

Latency rounds out the limits. The HTTP layer adds a single round trip on top of the chain-confirmation time. On Base that means roughly three to four seconds end to end. On Solana, closer to one to two. Compared with a card-network call (typically 200–800 ms for Visa or Mastercard authorization), x402 is one to two orders of magnitude slower per call. For sub-second agent-to-agent calls inside a single hot loop, that latency floor matters. Many deployments mitigate it by using deferred payment for high-frequency paths and reserving exact-mode x402 for the discrete, paid actions where settlement confirmation is the goal.

x402 vs Adjacent Agentic Commerce Protocols

x402 sits at the machine-to-machine API payment layer and does not compete with adjacent agentic protocols. ACP and UCP handle agent-to-merchant retail checkout, AP2 and TAP handle authorization attestation, and MCP handles tool discovery. Most production agent stacks use x402 alongside these protocols rather than choosing between them.

x402 is one piece of the broader agentic commerce stack. It does not compete head-on with the other agent-payment protocols; it sits at a different layer. A short comparison clarifies where x402 stops and other protocols begin.

OpenAI's Agentic Commerce Protocol (ACP) and Google's Universal Commerce Protocol (UCP) handle agent-to-merchant checkout for retail purchases. They issue scoped ephemeral tokens (Stripe Shared Payment Tokens for ACP) that route through traditional card networks. ACP and UCP and x402 are complementary: a shopping agent might use ACP to buy a sweater on Etsy and x402 to pay for the price-comparison API it consulted on the way.

Google's Agent Payments Protocol (AP2) and Visa's Trusted Agent Protocol (TAP, launched October 14, 2025) sit on the authorization side. AP2 attaches a cryptographic mandate to a payment confirming a user delegated the action; TAP signs the agent's identity into HTTP request headers. Both are designed to make the merchant comfortable that the agent is real and the user authorized the call. x402 does not solve agent-identity attestation. It solves payment movement, given that authorization has already happened upstream.

Anthropic's Model Context Protocol (MCP), open-sourced in November 2024 and donated to the Linux Foundation's Agentic AI Foundation in December 2025, is the data layer below all of these. MCP servers expose tools (search a catalog, read a database, call an API). x402 is the natural payment companion: an MCP server can return 402 to monetize its tools without changing the JSON-RPC schema, and the Cloudflare integration ships exactly that pattern. The two protocols compose in a way that doesn't require either side to know about the other.

For most agent-payment systems in production, the protocol stack is layered: MCP for tool discovery, x402 for machine-to-machine API payments, ACP or UCP for retail checkout, AP2 or TAP for the authorization signature. Stablecoin agent payments as a category currently route through x402 for the vast majority of sub-dollar settlements, and through MPP or ACP for higher-value flows.

Sources and methodology. Protocol specifications verified against the x402 reference repository and Coinbase x402 documentation. Active-agent and transaction figures from Cryptonews' April 2026 reporting. Stablecoin supplies pulled from DeFiLlama on April 30, 2026. Figures refresh quarterly.

Eco's Role

x402 specifies the protocol; it does not specify which chain the dollars sit on. When an agent paying USDC on Base needs to pay a recipient whose treasury lives on Solana, Arbitrum, or Tron, x402 gets the agent to the payment endpoint but does not bridge the funds. Eco operates as the cross-chain stablecoin orchestration layer that fills that gap, abstracting routing, solver selection, and finality across 15 chains. An agent integrated against Eco can pay an x402 endpoint anywhere without holding a separate wallet or liquidity pool per chain; the orchestration network handles where the dollars settle. Agentic payments systems running x402 at scale typically pair the protocol with this orchestration layer because settlement chain selection becomes its own engineering surface once the agent footprint moves past one network. Cross-chain messaging is the third leg of the same stack, handling the under-the-hood transport that lets routes settle across chains in seconds rather than minutes.

Coinbase Lets AI Agents Pay Businesses in USDC as Machine Commerce Expands

Coinbase is rolling out support for payments initiated by artificial intelligence (AI) agents through Coinbase Business. Merchants can accept USDC from autonomous software using x402, an open payment standard developed by Coinbase for machine-to-machine transactions.

The feature uses the same Coinbase Business account that companies already use to receive payments from people. Businesses can manage, reconcile, and convert agent payments without creating a separate checkout flow.

“A business owner can now sell their stuff to agents online,” Siddharth Coelho-Prabhu, head of Coinbase Business, said, as businesses can now manage, reconcile, and cash out agent payments, all in one account.

Stablecoins Move Into Autonomous Commerce

Coinbase views agent payments as one of its highest-conviction growth areas.

Coelho-Prabhu said the company began investing in the idea several years ago after concluding that AI agents would become a major force on the internet. Coinbase said agent traffic recently surpassed human traffic on its Base documentation pages.

The company is positioning USDC as the settlement layer for that activity. Agents can create wallets, receive funds, and pay merchants across Base and other supported networks.

Brian Armstrong, co-founder and CEO of Coinbase, tweeted, “The agentic economy is going to be huge; it needs new financial rails, and we’re building them.”

$\"Coinbase$

Source: Brian Armstrong on X

Coinbase Business launched in June 2025 and has signed up about 5,000 customers. The unit has processed roughly $1 billion in combined payments and trading volume, according to the company.

Businesses using the service can earn 3.35% in rewards on eligible idle USDC balances. Coinbase also says USDC payments do not carry traditional card chargeback risk, though foreign exchange and other charges may apply.

Early use cases are concentrated in digital services. AI agents are already purchasing access to application programming interfaces, cloud storage, domain names, and other online tools.

New Tools Put Agents Closer to Markets

Coinbase is also adding real-time trading features to Coinbase for Agents, its interface for connecting AI systems to customer accounts.

The new tools allow agents to monitor open orders, inspect market depth and follow live price and volume data. Users can also set conditions in natural language, such as selling bitcoin below a certain price or cancelling an order after a fixed period.

Coinbase said those actions remain subject to limits set by the user.

For developers, the exchange introduced an x402 software development kit that can add agent payments to an API, web service or AI server with minimal code. Its managed wallet tools also let developers apply spending controls.

Coinbase’s broader bet is that the next internet economy will serve two types of customers: people and software acting on their behalf.

x402 Protocol Explained: How AI Agents Pay Onchain

Why x402 Exists

How the x402 Protocol Works

Step-by-Step Payment Flow

The Facilitator's Role

Supported Blockchains and Tokens

The x402 Foundation and Ecosystem

Who Is Building with x402

Key Use Cases for x402

x402 vs. Agent2Agent (A2A) vs. Agent Payments Protocol (AP2)

x402 and Onchain Standards

Getting Started with x402

Frequently Asked Questions

What is the x402 protocol?

Is x402 the same as Agent2Agent (A2A)?

What stablecoins does x402 support?

Who created x402?

How much does it cost to use x402?

Can x402 handle micropayments?

How does x402 relate to MCP (Model Context Protocol)?

The Bottom Line

x402 Protocol Explained

What Is x402?

How does x402 actually work?

Step 1: client request

Step 2: server returns 402 with payment terms

Step 3: client signs a payment authorization

Step 4: client retries; facilitator settles

The x402 Stack: Facilitators, Foundation, and Supported Chains

Real x402 Deployments

Tradeoffs and Limits

x402 vs Adjacent Agentic Commerce Protocols

Eco's Role

Coinbase Rolls Out AI Agents Payment for Businesses in USDC, Calls it a 'High-Conviction Bet'

Key Takeaways

Coinbase Lets AI Agents Pay Businesses in USDC as Machine Commerce Expands

Stablecoins Move Into Autonomous Commerce

New Tools Put Agents Closer to Markets

9 Wall Street and Crypto Giants Unite to Protect Bitcoin With $15 Million Initiative

9 Wall Street and Crypto Giants Unite to Protect Bitcoin With $15 Million Initiative

9 Wall Street and Crypto Giants Unite to Protect Bitcoin With $15 Million Initiative

Tags in this story

LATEST PODCASTS

Gauntlet CEO Tarun Chitra on DeFi Risk, RWAs, Japan & Crypto’s AI Moment

Real Finance CEO on RWAs, Tokenization & the Future of Onchain Finance

Taiwan's First Bitcoin-Holding Lawmaker Wants a National BTC Reserve

Charles Guillemet, Ledger CTO — AI Agents, Self-Custody & Wallet Security

Europe's Digital Euro Trap, Robinhood's Rise, and Crypto's Bottoming Process

PRESS RELEASES

Antony Mlelwa Champions Responsible Crypto Adoption Across Africa

TRON Reaches $90B+ USDT on the Network, $887M+ in Crypto Card Volume in Q2, CoinDesk Data and CryptoQuant

BloFin Wallet Unifies Visa Payments and Perpetual Trading for the Next Era of Finance

Flyfi Turns Crypto Into Hotel Keys for Token2049, Devcon 8 and Conference Season

TRON Included in S&P Pantera Digital Asset Index as Institutional Benchmarking Expands to Blockchain Networks

LATEST NEWS

Bitcoin's 15th Difficulty Reset Exposes a Mining Industry Under Pressure

‘We’re Gonna Need Another Color’: Michael Saylor Fuels Speculation Over Strategy’s Next Bitcoin Move

Bitcoin Enters Volatility Trap as Fed Decision, CLARITY Act and Fork Drama Converge

Despite Tradfi Headwinds, Bottom Signs Abound – Week in Review

Argentina Opens the Door to USD Wages as Central Bank Approves Dollar Salary Accounts

LATEST NEWS

Bitcoin's 15th Difficulty Reset Exposes a Mining Industry Under Pressure

‘We’re Gonna Need Another Color’: Michael Saylor Fuels Speculation Over Strategy’s Next Bitcoin Move

Bitcoin Enters Volatility Trap as Fed Decision, CLARITY Act and Fork Drama Converge

Despite Tradfi Headwinds, Bottom Signs Abound – Week in Review

Argentina Opens the Door to USD Wages as Central Bank Approves Dollar Salary Accounts

Related articles

Keyrock Report: 76% of AI Agent Transactions Fall Below Visa's $0.30 Fee Floor

Linux Foundation and Coinbase Launch x402 Foundation for AI Agents

Coinbase Launches Purpose-Built Wallets for Autonomous AI Agent Commerce

Coinbase CEO Brian Armstrong: Hash Power Doesn't Determine Bitcoin's Price

'The Only Way': Coinbase CEO Brian Armstrong Champions Self-Custody to Reach 1 Billion Users

Americans Have Been Paying Less for Bitcoin Than the Rest of the World for 50 Straight Days

Coinbase Lets AI Agents Make Crypto Payments and Trades

MOST VIEWED\n\n

PRICE PREDICTIONS\n\n

CRYPTO 101\n