ERC-8004 Explained: The Onchain Agent Identity Standard from Ethereum Foundation, Google, and Coinbase

Ethereum Stakes a Claim on Agent Identity

The trust layer for AI agents has several answers competing: card networks (Visa, Mastercard), protocol standards (AP2), and web access layer (Web Bot Auth). There's another answer coming from the Web3 side — ERC-8004. Published in late 2025 as a joint proposal by the Ethereum Foundation, Google, and Coinbase, ERC-8004 manages agent identity on-chain.

This article walks through ERC-8004's structure, how it differs from existing trust layers, and what ecommerce operators should know. For the bigger picture, see MCP vs A2A vs AP2 vs UCP vs ACP.

What ERC-8004 Is

ERCs (Ethereum Requests for Comments) are the spec family for smart contracts and standardized mechanisms on Ethereum — ERC-20 (tokens) and ERC-721 (NFTs) are familiar examples. ERC-8004 adds "AI agent identity standard" to that lineage.

The proposers are three parties: the Ethereum Foundation, Google, and Coinbase. That's notable on its own — this isn't just an ecosystem proposal. It signals that big tech and non-card payment players are taking this seriously. Google pushing it in parallel with AP2 implicitly says "agent economy infrastructure shouldn't be left to card networks alone."

Three Registries — Identity, Reputation, Validation

ERC-8004 is structured as three registry contracts.

Identity Registry uniquely identifies agents. When an agent is created it's registered here, along with provider info, cryptographic keys, and metadata. The issued identifier functions like an NFT, with transfer and handoff tracked on-chain.

Reputation Registry records past agent behavior. When an agent transacts with another agent or service, the outcome (success, failure, score) is written to this registry. Over time each agent builds up a "credit history," and new counterparties can reference it.

Validation Registry stores third-party verifications of agent capabilities and compliance. A KYC-type validator certifies "this agent meets certain requirements," and the certification is written on-chain. This is where compliance layers like Skyfire's KYA connect.

These three layers together answer the three fundamental questions of the agent economy: "who is this?", "what have they done?", and "what are they certified for?"

Relationship With Skyfire, AP2, and On-Chain Payments

ERC-8004 isn't self-contained — it's designed to work alongside neighboring ecosystems. The clearest connection is with Skyfire KYAPay, where Skyfire KYA IDs are recorded as attributes in the ERC-8004 Identity Registry. That lets agents' KYA status be verified outside Skyfire's own network.

Integration with Google's AP2 works by embedding an "ERC-8004 Identity ID" in the AP2 Agent Card. When an AP2-compatible agent transacts, counterparties can look up Reputation history on ERC-8004 through the Agent Card. This is the first implementation of decentralized agent credit information that doesn't depend on a centralized trust model.

In the Coinbase-centric crypto ecosystem, implementations combine ERC-8004 with on-chain settlement and DeFi integration. When an AI agent uses an on-chain lending protocol, for example, counterparties can verify via ERC-8004 that "this agent has no prior defaults."

The Fundamental Difference From Visa and Mastercard

ERC-8004's defining feature is that there's no central administrator. Visa TAP ultimately has Visa holding the keys; Mastercard Agent Pay routes through Mastercard's network at some point. ERC-8004 puts agent identity and reputation on smart contracts, and no single company owns them.

This creates both advantages and drawbacks. The advantage: no one can easily exclude agents from the system, and it's resistant to censorship by states or corporations. The drawback: when something goes wrong, it's unclear who to complain to, and user protection doesn't map cleanly onto existing financial regulation.

The practical result is that ERC-8004 will likely gain traction first in areas less bound by legacy financial regulation — crypto economies, AI-to-AI transactions, open-source ecosystems. For mainstream ecommerce, Visa TAP and Mastercard Agent Pay will stay dominant for the foreseeable future.

What to Watch as an Ecommerce Operator

In April 2026, the need for ecommerce operators to directly implement ERC-8004 is low. But two things are worth tracking.

First, merchants handling crypto payments or NFT sales will likely find ERC-8004-based trust systems become part of the customer experience. "When an agent buys an NFT, require ERC-8004 certification" is a sensible policy.

Second, long-term optionality as a trust foundation. If full dependency on the centralized Visa/Mastercard model becomes a risk down the road, having a decentralized alternative like ERC-8004 in existence provides negotiating leverage and strategic choice. There's no need to rush implementation, but awareness of its existence and trajectory is worth the investment.

Conclusion — The Trust Layer From the Web3 Side

ERC-8004 is a "decentralized answer" to the agent economy's trust foundation. If Visa TAP and Mastercard Agent Pay are the hand reaching out from legacy finance, ERC-8004 is the hand reaching out from Web3. It's still early in 2026, but the Ethereum Foundation + Google + Coinbase combo is real weight behind it.

The agent economy's trust layer is becoming a three-way world: centralized (card networks), semi-centralized (protocol standards like AP2), and decentralized (ERC-8004). The key move for ecommerce operators isn't to pick one — it's to track maturity across all three so you can pick the right trust model per transaction type as the options mature.