# ERC-8226 Regulated Agent Mandate vs ERC-8196: AI Agent Authenticated Wallet

They sit at the same step and overlap in purpose; the fields above are the basis for choosing.

[3 Permit](/category/permit/) [ERC-8226 Regulated Agent Mandate](/protocols/erc-8226/) · [3 Permit](/category/permit/) [ERC-8196: AI Agent Authenticated Wallet](/protocols/erc-8196/)

|  | [ERC-8226 Regulated Agent Mandate](/protocols/erc-8226/) ERC-8226 | [ERC-8196: AI Agent Authenticated Wallet](/protocols/erc-8196/) ERC-8196 |
| --- | --- | --- |
| Lifecycle step | 3 Permit: What may the agent do here? | 3 Permit: What may the agent do here? |
| Answers | What scoped, time-bounded, and financially capped authority may an on-chain agent exercise on a regulated asset holder's behalf? | How can an asset owner let an AI agent transact from a wallet only within a policy the owner set, with proof and an audit trail for every action? |
| Governed by | Ethereum ERC process (Ethereum Magicians discussion thread + ethereum/ERCs GitHub repo); not yet adopted by an EIP editor as Final | Ethereum EIP/ERC process (Ethereum Magicians discussion + ERCs repository); status Final |
| Status (issuer's words) | Draft, Standards Track: ERC (marked ⚠️ Draft on eips.ethereum.org) | Final Standards Track ERC (Final 2026-07-21); requires ERC-4337 and ERC-8126 |
| Version | Draft, created 2026-04-12 (2026-04-12) | Final, created 2026-03-14 (2026-07-21) |
| Form / transport | on-chain registry | on-chain registry |
| Found at | EVM contract interface detection (ERC-165 supportsInterface for IAgentMandate) | none — no well-known file; discovery is by contract address/ABI |
| Implementation | prototype | none found |
| Evidence | 1 verified, 1 reported | 2 verified |
| Primary use case | Delegate a user's authority to an agent | Delegate a user's authority to an agent |
| Last verified | 2026-10-23 (current) | 2026-10-23 (current) |
| Specification | [https://eips.ethereum.org/EIPS/eip-8226](https://eips.ethereum.org/EIPS/eip-8226) | [https://eips.ethereum.org/EIPS/eip-8196](https://eips.ethereum.org/EIPS/eip-8196) |

## When to use which

- Choose ERC-8226 Regulated Agent Mandate when your question is “What scoped, time-bounded, and financially capped authority may an on-chain agent exercise on a regulated asset holder's behalf?” and you accept its maturity: status "Draft, Standards Track: ERC (marked ⚠️ Draft on eips.ethereum.org)", implementation prototype.
- Choose ERC-8196: AI Agent Authenticated Wallet when your question is “How can an asset owner let an AI agent transact from a wallet only within a policy the owner set, with proof and an audit trail for every action?” and you accept its maturity: status "Final Standards Track ERC (Final 2026-07-21); requires ERC-4337 and ERC-8126", implementation none found.

Guidance is derived from the two records (question, status, implementation, prerequisites, pairings), not from opinion. Each record's page carries its numbered references.

## Read the full articles

- [ERC-8226 Regulated Agent Mandate](/protocols/erc-8226/): What scoped, time-bounded, and financially capped authority may an on-chain agent exercise on a regulated asset holder's behalf?
- [ERC-8196: AI Agent Authenticated Wallet](/protocols/erc-8196/): How can an asset owner let an AI agent transact from a wallet only within a policy the owner set, with proof and an audit trail for every action?

Ask the MCP server to compare any two: the compare-protocols prompt, or get on both ids. [Connect](/connect/).

[erc-8226.json](/data/protocols/erc-8226.json) · [erc-8196.json](/data/protocols/erc-8196.json) · [Markdown](/compare/erc-8226-vs-erc-8196/index.md)