--- type: Agentic Web Standard title: "ERC-8226 Regulated Agent Mandate" description: "What scoped, time-bounded, and financially capped authority may an on-chain agent exercise on a regulated asset holder's behalf?" resource: "https://eips.ethereum.org/EIPS/eip-8226" tags: ["permit", "onchain-registry", "community", "delegate-user-authority", "agent-checkout", "audit-agent-actions"] status: draft generated: { by: agenticweb-builder/1.0, at: 2026-10-30T00:00:00Z } verified: { by: process:agenticweb-engine, at: 2026-10-29T00:00:00Z } stale_after: 2026-11-28T00:00:00Z sources: - id: ref-1 resource: "https://eips.ethereum.org/EIPS/eip-8226" title: "The canonical spec text (abstract, motivation, IAgentMandate/IComplianceProvider interfaces, reference implementation) is published on eips.ethereum.org, status Draft, created 2026-04-12." last_modified: 2026-04-12T00:00:00Z - id: ref-2 resource: "https://github.com/ethereum/ERCs/pull/1844" title: "The EIP's discussion thread and originating pull request on the ethereum/ERCs repo record the proposal's provenance and author affiliation with Brickken." last_modified: 2026-05-12T00:00:00Z --- # ERC-8226 Regulated Agent Mandate ERC-8226 Regulated Agent Mandate is an agentic-web standard (on-chain registry) at step 3, Permit, governed by Ethereum ERC process; its status is "Draft, Standards Track: ERC". It answers: "What scoped, time-bounded, and financially capped authority may an on-chain agent exercise on a regulated asset holder's behalf?" Replacing or extending Power of attorney, implementation status is prototype, last verified 2026-10-29. # Overview ERC-8226, also called the Regulated Agent Mandate Standard (RAMS), is a Draft Ethereum Request for Comments that defines a compliance-delegation layer for AI agents acting on tokenized regulated assets such as securities or fund units [^ref-1]. It answers the permit question for on-chain agents: what scoped, time-bounded, financially capped authority has a KYC-cleared principal granted an agent, and how does a regulated token contract check that authority before letting the agent's call through. The spec defines two Solidity interfaces: `IAgentMandate`, a registry keyed by (agent, principal) pairs that exposes `canExecute` for pre-flight checks and `recordExecution` for logging use, and `IComplianceProvider`, which lets a token-compliance framework plug in. Mandates cap a transferred quantity (token amount for ERC-20/ERC-1155, count for ERC-721) per asset address, can be time-limited, and can be frozen (halted but not revoked) by an authorized enforcer while only the principal can revoke outright. RAMS is explicitly agnostic to the agent-identity standard used (it names ERC-8004 as a compatible example), the token standard (ERC-20/721/1155), and the regulated-token compliance framework (it names ERC-7943 and ERC-3643) [^ref-1]. It does not itself provide agent identity, KYC verification, or token-transfer-eligibility logic; those are left to the named companion standards. It does not define an off-chain permission surface (no well-known file or HTTP header) — the entire mechanism is on-chain, discoverable only by probing whether a given regulated-token deployment has wired an IAgentMandate-conformant registry into its transfer checks. As of this verification (2026-09-06) the proposal is Draft status, created 2026-04-12 by four authors affiliated with Brickken, a tokenized real-world-asset platform, with an open Ethereum Magicians discussion thread and a merged pull request into the community ethereum/ERCs repository dated 2026-05-12 [^ref-1][^ref-2]. A reference implementation and test suite (IAgentMandate registry, IComplianceProvider, an optional IAgentExecutor forwarding interface, a RamsGated base contract, and an ERC-7943 asset that inherits it) ship alongside the spec text, but this is the proposers' own reference code, not an independent production deployment [^ref-1]. What is unresolved: no independent implementer, regulated-asset platform, or agent-identity project has been found describing production use of RAMS; adoption is unmeasured. It is unclear whether RAMS will progress through EIP editor review toward Final status, whether it will compete with or be folded into ERC-8004's agent-identity ecosystem, and whether real KYC/regulatory infrastructure will treat an on-chain mandate as legally sufficient without off-chain paperwork. # Examples ```http ETH_CALL {contract}.canExecute(agent, principal, asset, action, amount) via eth_call against IAgentMandate # parse: Call reverts with false/error if no active mandate exists; a successful bool return with mandate data proves an IAgentMandate registry is deployed at {contract} # on absent: No IAgentMandate registry is deployed at the address; the asset contract carries no RAMS-conformant delegation layer ``` # Knowledge Graph * **Lifecycle Step**: [3 Permit](/category/permit/index.md) * **Builds on**: [ERC-8004: Trustless Agents](/okf/protocols/erc-8004.md) * **Pairs with**: [ERC-8004: Trustless Agents](/okf/protocols/erc-8004.md), [ERC-8183: Agentic Commerce](/okf/protocols/erc-8183.md), [Agent Payments Protocol (AP2)](/okf/protocols/ap2.md) * **Related terms**: [Agentic EoR (Employer / Entity of Record)](/okf/terms/agentic-eor.md) * **Compared in**: [ERC-8226 Regulated Agent Mandate vs ERC-8196: AI Agent Authenticated Wallet](/compare/erc-8226-vs-erc-8196/index.md) [^ref-1]: The canonical spec text (abstract, motivation, IAgentMandate/IComplianceProvider interfaces, reference implementation) is published on eips.ethereum.org, status Draft, created 2026-04-12. (https://eips.ethereum.org/EIPS/eip-8226) [^ref-2]: The EIP's discussion thread and originating pull request on the ethereum/ERCs repo record the proposal's provenance and author affiliation with Brickken. (https://github.com/ethereum/ERCs/pull/1844)