# ERC-8226 Regulated Agent Mandate ERC-8226

[3 · Permit](/category/permit/)

| ERC-8226 Regulated Agent Mandate |
| --- |
| Category | [Permit](/category/permit/) |
| Governed by | Ethereum ERC process (Ethereum Magicians discussion thread + ethereum/ERCs GitHub repo); not yet adopted by an EIP editor as Final |
| Status | Draft, Standards Track: ERC (marked ⚠️ Draft on eips.ethereum.org) |
| Phase | draft |
| Implementation | prototype |
| Adoption | unmeasured |
| Version | Draft, created 2026-04-12 (2026-04-12) |
| Specification | [https://eips.ethereum.org/EIPS/eip-8226](https://eips.ethereum.org/EIPS/eip-8226) |
| Found at | EVM contract interface detection (ERC-165 supportsInterface for IAgentMandate) |
| Last checked | 2026-09-06 |

[Permit](/category/permit/) 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 [[1]](#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.

## Overview
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) [[1]](#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 [[1]](#ref-1)[[2]](#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 [[1]](#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.

## Discovery and probe

EVM contract interface detection (ERC-165 supportsInterface for IAgentMandate)

```
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
```

Not probed live: not-http. An Ethereum contract; observable via eth_call, not HTTP.

## History
- 2026-09-05 — seeded from Exa Agent research run
- 2026-09-06 — verified against eips.ethereum.org/EIPS/eip-8226 and github.com/ethereum/ERCs/pull/1844

## Instances

- [Ethereum ERC-8226 authors (Brickken)](https://ethereum-magicians.org/t/erc-8226-regulated-agent-mandate/28208) · Observed 2026-08-17 · business
- [RAMS reference implementation and test suite (IAgentMandate, IComplianceProvider, RamsGated)](https://eips.ethereum.org/EIPS/eip-8226) · Observed 2026-04-12 · service

Every instance with its source is listed on the [instances page](/instances/).

## See also

## References

- 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](https://eips.ethereum.org/EIPS/eip-8226) (2026-04-12) VERIFIED
- 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](https://github.com/ethereum/ERCs/pull/1844) (2026-05-12) REPORTED

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