{
 "url": "https://agenticweb.wiki/compare/erc-8004-vs-erc-8126/",
 "title": "ERC-8004 vs ERC-8126: differences & adoption",
 "description": "ERC-8004: Trustless Agents vs ERC-8126: AI Agent Verification: The map lists them as complementary: sites and agents commonly implement both.…",
 "markdown_url": "https://agenticweb.wiki/compare/erc-8004-vs-erc-8126/index.md",
 "markdown": "# ERC-8004: Trustless Agents vs ERC-8126: AI Agent Verification\n\nThe map lists them as complementary: sites and agents commonly implement both. ERC-8004: Trustless Agents is a prerequisite of ERC-8126: AI Agent Verification.\n\n[2 Identify](/category/identify/) [ERC-8004: Trustless Agents](/protocols/erc-8004/) · [2 Identify](/category/identify/) [ERC-8126: AI Agent Verification](/protocols/erc-8126/)\n\n|  | [ERC-8004: Trustless Agents](/protocols/erc-8004/) ERC-8004 | [ERC-8126: AI Agent Verification](/protocols/erc-8126/) ERC-8126 |\n| --- | --- | --- |\n| Lifecycle step | 2 Identify: Who is this agent? Who is this site? | 2 Identify: Who is this agent? Who is this site? |\n| Answers | Who is an agent, and what onchain identity, reputation and validation record does it carry? | How can an agent registered under ERC-8004 be put through standard security checks and carry a comparable risk score? |\n| Governed by | Ethereum EIP process; no formal steward until finalized | Ethereum EIP/ERC process (Ethereum Magicians discussion + ERCs repository); status Final |\n| Status (issuer's words) | Draft Standards Track ERC | Final Standards Track ERC (moved to Last Call 2026-05-12 and to Final 2026-06-02); requires ERC-8004, which is still Draft |\n| Version | Draft ERC, created 2025-08-13; Identity and Reputation Registries live on Ethereum mainnet since 2026-01-29 (2025-08-13) | Final, created 2026-01-15 (2026-06-02) |\n| Form / transport | on-chain registry | on-chain registry |\n| Found at | /.well-known/agent-registration.json | none — no well-known file; discovery is by contract address/ABI |\n| Implementation | multi-implementation — Forbes (2026-02-05) citing community trackers; community-maintained awesome-erc8004 deployment list | prototype |\n| Evidence | 4 verified, 1 reported | 3 verified |\n| Primary use case | Name and resolve agents | Prove an agent's identity |\n| Last verified | 2026-10-23 (current) | 2026-10-23 (current) |\n| Specification | [https://eips.ethereum.org/EIPS/eip-8004](https://eips.ethereum.org/EIPS/eip-8004) | [https://eips.ethereum.org/EIPS/eip-8126](https://eips.ethereum.org/EIPS/eip-8126) |\n\n## When to use which\n\n- Choose ERC-8004: Trustless Agents when your question is “Who is an agent, and what onchain identity, reputation and validation record does it carry?” and you accept its maturity: status \"Draft Standards Track ERC\", implementation multi-implementation (Forbes (2026-02-05) citing community trackers; community-maintained awesome-erc8004 deployment list).\n- Choose ERC-8126: AI Agent Verification when your question is “How can an agent registered under ERC-8004 be put through standard security checks and carry a comparable risk score?” and you accept its maturity: status \"Final Standards Track ERC (moved to Last Call 2026-05-12 and to Final 2026-06-02); requires ERC-8004, which is still Draft\", implementation prototype.\n\nGuidance is derived from the two records (question, status, implementation, prerequisites, pairings), not from opinion. Each record's page carries its numbered references.\n\n## Read the full articles\n\n- [ERC-8004: Trustless Agents](/protocols/erc-8004/): Who is an agent, and what onchain identity, reputation and validation record does it carry?\n- [ERC-8126: AI Agent Verification](/protocols/erc-8126/): How can an agent registered under ERC-8004 be put through standard security checks and carry a comparable risk score?\n\nAsk the MCP server to compare any two: the compare-protocols prompt, or get on both ids. [Connect](/connect/).\n\n[erc-8004.json](/data/protocols/erc-8004.json) · [erc-8126.json](/data/protocols/erc-8126.json) · [Markdown](/compare/erc-8004-vs-erc-8126/index.md)\n"
}