When AI starts paying for itself

Written by: Clow, Plain Language Blockchain

An AI wrote a piece of code that requires data for verification.

It sent an HTTP request, and the server returned a number: 402.

Then, it paid 0.001 USD using USDC. Less than a second, the data was back.

This transaction involved no account, no password, no bank card, no KYC. The entire process involved no human participation.

This is no longer science fiction. By the end of 2025, the x402 protocol handled over 100 million such transactions; in the first 30 days of this year alone, another 15 million.

The “Payment Code” Sleeping for Thirty Years

In 1990, when the creators of the HTTP protocol drafted status codes, they specifically reserved a spot: 402, Payment Required.

The meaning was straightforward—“Payment needed to proceed.”

But this status code was never officially used. It just sat in the protocol documentation, dormant for thirty-four years.

The reason is simple: the early builders of the internet never imagined that one day machines would be responsible for paying bills. Credit cards, bank accounts, KYC verification—these payment infrastructures were designed for humans, and they completely fail in autonomous code execution.

AI Agents need to call APIs, purchase data, and acquire computing power at millisecond speeds. Traditional payment account registration and transaction fees are like a wall of death.

By 2025, three conditions are simultaneously met.

The total supply of stablecoins surpasses 300 billion USD, with Layer 2 solutions like Base driving single-transaction costs down to sub-cent levels; AI Agent ecosystems led by OpenAI and Anthropi begin large-scale commercialization; Coinbase engineers unearth the long-forgotten 402 status code and decide to activate it.

In May 2025, Coinbase, in partnership with Cloudflare, officially releases the x402 protocol. By September, they collaborate again to establish the x402 Foundation. A forgotten status code re-enters the center of the internet. Cloudflare manages about 20% of global web traffic—meaning x402 had infrastructure support from day one.

Machines, Learning to Pay for the First Time

The design of x402 is surprisingly simple.

An AI Agent initiates an HTTP request, the server responds with a 402 status code, along with payment requirements: how much, which chain, which token. The Agent signs the payment info with an EIP-712 encrypted signature, embeds it into the request headers, and resends. After verification, the server returns the resource.

All this takes less than a second—no account, no subscription, no API key.

This turns “payment” into a part of the internet. Like GET or POST, it’s just an HTTP action. Any service can add a middleware to charge machines.

Data proves this logic works. Within about seven months of protocol release, over 100 million transactions were processed. According to Cambrian Network’s Q1 2026 report, in the past 30 days, over 15 million transactions, with more than 400k buyers and over 80k sellers. The largest source of transactions is the AI Agent community of Virtuals Protocol, autonomously settling collaboration fees among Agents on the protocol.

On December 11, 2025, x402 V2 launched. This upgrade moved the protocol from “usable” to “user-friendly”: supporting multiple chains like Base, Solana, Avalanche; introducing a Session mechanism (wallets as identity credentials, no need for repeated on-chain interactions); integrating ACH bank transfers and credit card networks—connecting Web2 and Web3 payment systems for the first time within this protocol.

Google then integrated x402 into the Agent2Agent (A2A) protocol, releasing the Agentic Payments Protocol (AP2); machine payments are becoming a foundational infrastructure consensus for major tech companies.

Trust, the First Hurdle in the Agent Economy

While payment issues are solved, a more fundamental problem remains.

“Commerce can’t happen if people don’t trust each other.”

Davide Crapis, head of AI at the Ethereum Foundation and co-drafter of ERC-8004, directly pointed out the core obstacle of the Agent economy: when one AI Agent needs to hire another to complete a task, how does it know the other isn’t a scammer? Where are the transaction records? How is reputation transmitted?

ERC-8004 is Ethereum’s answer to this problem. Drafted in August 2025, officially launched on the Ethereum mainnet on January 29, 2026. It establishes three lightweight on-chain registries:

Identity Registry: Each Agent gets an on-chain ID based on an ERC-721 NFT, which is portable, transferable, and cross-chain searchable. AgentCard (JSON format) records capabilities, endpoints, and x402 payment support status.

Reputation Registry: On-chain archive of feedback signals between Agents—accuracy, timeliness, reliability scores. Only indexes are stored on-chain; data hashes point to off-chain storage, reducing gas costs.

Verification Registry: After task completion, the result data hash is submitted for verification, making “task completion” cryptographically provable.

The drafting team spans four major crypto ecosystems: Marco De Rossi of MetaMask, Davide Crapis of Ethereum Foundation, Jordan Ellis of Google, Erik Reppel of Coinbase. EigenLayer, ENS, The Graph, Taiko have all expressed support. Within less than a month after mainnet deployment, Ethereum registered over 24k Agents, totaling about 49k across all EVM chains.

A typical workflow looks like this: Agent A discovers service providers via ERC-8004 identity registry, filters by reputation registry to select high-scoring Agent B, completes payment with x402, and after the task, attaches reputation feedback—payment history becomes a trust anchor. This chain is what Cambrian Network calls the “Agent Economy Operating System”: Payment + Identity + Reputation, three layers in one.

How deep is this water?

The data looks promising, but a few things need clarification.

Tokens and protocols are two different things.

The x402 ecosystem token once exceeded a market cap of $9 billion on CoinGecko, with a daily trading volume over $230 million. But many “x402 concept tokens” are meme tokens, not substantively linked to the protocol itself. Buying x402-related tokens doesn’t mean buying protocol growth. The market has always been good at mixing narrative and reality, and this time is no exception.

Technical risks are still unresolved.

x402’s EIP-712 signature mechanism requires ongoing security audits. ERC-8004’s reputation registry faces Sybil attack threats—mass registration of fake identities, with current economic incentives still imperfect. Micro-payments (around $0.0001 per transaction) versus Layer 2 fees (still up to $0.05) create economic tension; very small transactions still get eaten up by fees.

The protocol war isn’t over.

x402, Google’s AP2, and a16z’s ACP coexist. If developers split among three standards, network effects weaken. Moreover, OpenAI and Anthropic can bypass on-chain protocols to build their own closed-loop payment systems—they have users, data, and scale advantages that x402 cannot ignore, creating competitive pressure.

Regulatory issues remain a blank space. Who is the actual transaction subject when an AI Agent initiates a payment? Where are the KYC/AML responsibility trigger points? No major jurisdiction has provided definitive answers.

Summary

Someone once wrote a phrase worth quoting here: “In 2023, inscriptions let humans embed value on-chain; in 2025, x402 enables machines to autonomously pay value on the network.”

If HTTP connected all computers into an information network, then the combination of x402 and ERC-8004 aims to connect hundreds of millions of Agents into an open service and data marketplace—no accounts, no approvals needed. One request, one payment, one result.

But whether the protocol can win amid fragmentation, whether trust mechanisms can truly mature, and whether the Agent economy can move from demo to real business—these remain open questions.

Before the narrative materializes, clarifying the “value of the protocol” versus the “tokens hyped around the protocol” is perhaps the most important thing every participant should understand.