# ERC-8126: AI Agent Verification ERC-8126

[2 · Identify](/category/identify/)

| ERC-8126: AI Agent Verification |
| --- |
| Category | [Identify](/category/identify/) |
| Governed by | Ethereum EIP/ERC process (Ethereum Magicians discussion + ERCs repository); status Final |
| 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 |
| Phase | stable |
| Implementation | prototype |
| Adoption | unmeasured |
| Version | Final, created 2026-01-15 (2026-06-02) |
| Specification | [https://eips.ethereum.org/EIPS/eip-8126](https://eips.ethereum.org/EIPS/eip-8126) |
| Found at | none — no well-known file; discovery is by contract address/ABI |
| Last checked | 2026-10-20 |
| Freshness | current · checked 2026-10-20 |
| Solves | Prove an agent's identity, Audit what an agent did |

ERC-8126: AI Agent Verification is an agentic-web standard (on-chain registry) at step 2, Identify, governed by Ethereum EIP/ERC process (Ethereum Magicians discussion + ERCs repository); its own status is "Final Standards Track ERC (moved to Last Call 2026-05-12 and to Final 2026-06-02); requires ERC-8004, which is still Draft" (stable). It answers: How can an agent registered under ERC-8004 be put through standard security checks and carry a comparable risk score? Adoption is unmeasured, last verified 2026-10-20.

[Identify](/category/identify/) ERC-8126 is a Final Ethereum standard for checking AI agents that already hold an ERC-8004 identity [[1]](#ref-1). A verification provider runs up to five checks: the agent's token contract, media it produces (with C2PA guidance), its Solidity code (with OWASP guidance), its web endpoints, and its wallet history. It turns the results into zero-knowledge proofs and a single 0-100 risk score [[1]](#ref-1). Detailed results go only to the agent's wallet holder, and attestations can be posted to ERC-8004's Validation Registry so others can see that a check happened [[1]](#ref-1). An optional quantum-resistant encryption layer is also described [[1]](#ref-1).

## Overview
It is the first layer of a two-part stack by the same authors: ERC-8196 builds policy-bound agent wallets on top of it. The authors are Leigh Cronian (Cybercentry) and Chris Johnson (Virtuals) [[1]](#ref-1). It moved to Last Call on 2026-05-12 and to Final on 2026-06-02 [[2]](#ref-2).

The oddity: ERC-8126 is Final while the standard it requires, ERC-8004, is still a Draft that can change [[2]](#ref-2)[[3]](#ref-3). Its interfaces could therefore break if ERC-8004 changes before finalisation. The spec carries reference code, but no deployed verification provider was counted in this pass, so adoption is unmeasured.

## Discovery and probe

Agents are identified by their ERC-8004 Identity Registry token; verification attestations can be posted to ERC-8004's Validation Registry · none — no well-known file; discovery is by contract address/ABI

```
eth_call {contract_address}
parse:     Look up the agent in an ERC-8004 Validation Registry for ERC-8126 verification attestations; detailed results and the 0-100 risk score are readable only by the agent's wallet holder
on absent: No attestation means no ERC-8126 provider has posted one for this agent; it says nothing about whether the agent is safe.
```

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

## History
- 2026-10-20 — added from gap scout 2026-10-20; verified against eips.ethereum.org/EIPS/eip-8126, the ERCs repository file and commit history (Last Call 2026-05-12, Final 2026-06-02), and the ERC-8004 EIP page (Draft); dispute recorded: Final while its dependency ERC-8004 is Draft

## Instances

No instances recorded yet.

## See also

## References

- ERC-8126 defines a standard interface for verifying AI agents registered via ERC-8004, with five verification types (Ethereum Token, Media Content, Solidity Code, Web Application and Wallet Verification), zero-knowledge proofs generated by Private Data Verification, and a unified 0-100 risk score visible only to the agent's wallet holder; attestations can be posted to ERC-8004's Validation Registry. Status Final; requires 155, 191, 712, 721, 3009 and 8004; created 2026-01-15. — [https://eips.ethereum.org/EIPS/eip-8126](https://eips.ethereum.org/EIPS/eip-8126) (2026-06-02) VERIFIED
- The ERCs repository front matter for erc-8126.md reads status: Final with requires including 8004; its commit history shows the move to Last Call on 2026-05-12 and to Final on 2026-06-02. — [https://github.com/ethereum/ERCs/blob/master/ERCS/erc-8126.md](https://github.com/ethereum/ERCs/blob/master/ERCS/erc-8126.md) (2026-06-02) VERIFIED
- ERC-8004, which ERC-8126 requires, is still status Draft on its EIP page. — [https://eips.ethereum.org/EIPS/eip-8004](https://eips.ethereum.org/EIPS/eip-8004) (2025-08-13) VERIFIED

Disputed: ERC-8126 reached Final while it depends on ERC-8004, which is still a Draft. A Final standard is meant to be frozen, but the identity and validation registries it builds on can still change, so ERC-8126 implementations may need to follow ERC-8004 revisions.

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