SASAME S.R.L. — research
x402 revives HTTP's old 402 status code to let AI agents pay per API call in stablecoins. The rails exist and work technically, but real agent-to-agent commerce is still early and mostly experimental.
x402 answers a narrow but real gap in the agent economy: HTTP never had a native way to say 'this costs money, here's how to pay,' so API access has always relied on human-managed accounts, API keys, and invoices. By reviving the HTTP 402 status code, x402 lets a server tell a requesting client exactly what payment is required, and lets the client — often an autonomous agent rather than a human — attach a stablecoin payment and retry the request in the same protocol flow. This makes fine-grained, pay-per-call access technically straightforward for the first time, which matters for AI agents that need to call many small external tools without a human setting up a merchant account for each one.
The mechanics are already usable: agent wallets funded with a stablecoin such as USDC on a low-fee network like Base, 'facilitator' services that verify and settle payments, and MCP servers or plain HTTP APIs that gate tool calls behind an x402 check. This is compatible with, not a replacement for, broader agentic-commerce frameworks such as Google's Agent Payments Protocol (AP2), which can treat x402 as one settlement option among several. Smaller studios building agent tooling — including SASAME S.R.L., a Romanian software/AI shop working on MCP servers, Claude-based agents, RAG pipelines and automation — track protocols like this as part of normal due diligence on where agent-native infrastructure is heading.
Whether this adds up to AIs genuinely paying other AIs at scale in 2026 is a separate, harder question from whether the plumbing works. The protocol layer is real and functioning; the demand layer is much less settled. Public listings of x402-payable endpoints exist, but distinguishing broad-based, organic agent-to-agent commerce from a smaller set of operators publishing many similar low-cost API wrappers, or from test and promotional traffic, requires independent verification rather than taking aggregate listing or transaction counts at face value.
For developers evaluating x402 today, the practical takeaway is to treat it as a working, low-friction payment rail for machine clients rather than a mature market. It removes real friction (no signup flow, no stored card, granular per-call pricing) and is being built with interoperability in mind, but adopters should plan for irreversible settlement, wallet/gas management, and unresolved questions around spending limits and liability before wiring it into anything that isn't tightly bounded.
What is x402?
x402 is an open payment protocol, introduced by Coinbase, that reuses the long-dormant HTTP 402 'Payment Required' status code. A server can respond to a request with a 402 and machine-readable payment instructions; the client (often an AI agent) attaches a stablecoin payment and retries, completing the transaction without a pre-registered account or manual checkout.
Can an AI agent actually pay another AI agent today?
Technically yes: an agent with a crypto wallet holding a stablecoin like USDC on a network such as Base can complete an x402 payment to another service or agent programmatically. In practice, most current activity involves agents paying for API access or tool calls rather than agent-to-agent payments in a fully autonomous, closed loop.
Does x402 require a blockchain?
Yes, settlement happens on-chain, typically using stablecoins on low-fee networks (Base, an Ethereum layer-2, is the most commonly referenced one). This gives near-instant, irreversible settlement without card-network intermediaries, but it also means no chargebacks and it requires the paying agent to hold funded wallet infrastructure.
How does x402 relate to MCP and to Google's Agent Payments Protocol (AP2)?
MCP (Model Context Protocol) servers can expose 'paid tools' by pairing an x402 payment-check middleware in front of a tool call, so an MCP client agent pays per invocation. AP2 is a separate, broader authorization/intent framework for agentic commerce that can incorporate x402 as one of its settlement mechanisms rather than competing with it directly.
Is agent-to-agent payment volume on x402 mostly real demand?
As of 2026 it's hard to tell. Public marketplaces listing x402-enabled endpoints show real technical uptake, but distinguishing genuine, diverse buyer demand from test transactions, promotional listings, or a small number of operators publishing many similar low-value endpoints requires independent verification rather than taking listing counts at face value.