{
 "url": "https://agenticweb.wiki/compare/erc-8183-vs-x402/",
 "title": "ERC-8183: Agentic Commerce vs x402",
 "description": "ERC-8183: Agentic Commerce vs x402: The map lists them as complementary: sites and agents commonly implement both. Side-by-side step, governance, status…",
 "markdown_url": "https://agenticweb.wiki/compare/erc-8183-vs-x402/index.md",
 "markdown": "# ERC-8183: Agentic Commerce vs x402\n\nThe map lists them as complementary: sites and agents commonly implement both.\n\n[7 Pay](/category/pay/) [ERC-8183: Agentic Commerce](/protocols/erc-8183/) · [7 Pay](/category/pay/) [x402](/protocols/x402/)\n\n|  | [ERC-8183: Agentic Commerce](/protocols/erc-8183/) ERC-8183 | [x402](/protocols/x402/) |\n| --- | --- | --- |\n| Lifecycle step | 7 Pay: Settle the bill | 7 Pay: Settle the bill |\n| Answers | How can two agents (a client and a provider) settle a job on-chain, with funds held in escrow and released only once an evaluator attests the work was done? | How can an HTTP client pay per-request or per-resource, in stablecoins, without accounts, API keys, or signup? |\n| Governed by | Ethereum EIP/ERC process (Ethereum Magicians discussion + EIPs repository); status Draft, an ERC Standards Track proposal, not yet Final | x402 Foundation, a Series of LF Projects, LLC (Linux Foundation); operational launch announced 2026-07-14; Executive Director Michael Hursta from 2026-10-01; 50+ members |\n| Status (issuer's words) | Draft ERC — 'This specification defines the Agentic Commerce Protocol: a job with escrowed budget...' | Open, neutral standard for internet-native payments |\n| Version | Draft, created 2026-02-25 (2026-02-25) | x402 protocol specification v2, transports-v2/http.md |\n| Form / transport | on-chain registry | HTTP header |\n| Found at | none — no well-known file; discovery is by contract address/ABI | none — signalled per-request via the 402 status code, not a fixed well-known path |\n| Implementation | prototype | multi-implementation — x402 Foundation (x402.org live dashboard) |\n| Evidence | 1 verified, 1 reported | 5 verified |\n| Primary use case | Accept payments from agents | Accept payments from agents |\n| Last verified | 2026-10-23 (current) | 2026-10-23 (current) |\n| Specification | [https://eips.ethereum.org/EIPS/eip-8183](https://eips.ethereum.org/EIPS/eip-8183) | [https://github.com/x402-foundation/x402/blob/main/specs/transports-v2/http.md](https://github.com/x402-foundation/x402/blob/main/specs/transports-v2/http.md) |\n\n## When to use which\n\n- Choose ERC-8183: Agentic Commerce when your question is “How can two agents (a client and a provider) settle a job on-chain, with funds held in escrow and released only once an evaluator attests the work was done?” and you accept its maturity: status \"Draft ERC — 'This specification defines the Agentic Commerce Protocol: a job with escrowed budget...'\", implementation prototype.\n- Choose x402 when your question is “How can an HTTP client pay per-request or per-resource, in stablecoins, without accounts, API keys, or signup?” and you accept its maturity: status \"Open, neutral standard for internet-native payments\", implementation multi-implementation (x402 Foundation (x402.org live dashboard)).\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-8183: Agentic Commerce](/protocols/erc-8183/): How can two agents (a client and a provider) settle a job on-chain, with funds held in escrow and released only once an evaluator attests the work was done?\n- [x402](/protocols/x402/): How can an HTTP client pay per-request or per-resource, in stablecoins, without accounts, API keys, or signup?\n\nAsk the MCP server to compare any two: the compare-protocols prompt, or get on both ids. [Connect](/connect/).\n\n[erc-8183.json](/data/protocols/erc-8183.json) · [x402.json](/data/protocols/x402.json) · [Markdown](/compare/erc-8183-vs-x402/index.md)\n"
}