ERC-8004 Identity

​

Overview

​

Supported Networks

​

The app/erc-8004.ts File

import type { ERC8004Registration } from "aixyz/erc-8004";

const metadata: ERC8004Registration = {
  registrations: [],
  supportedTrust: ["reputation"],
};

export default metadata;

• GET /_aixyz/erc-8004.json

​

Register an Agent

aixyz erc-8004 register --chain sepolia --broadcast

1. Creates app/erc-8004.ts if it doesn’t exist — prompts you to select supported trust mechanisms
2. Asks for your agent’s deployment URL (e.g., https://my-agent.vercel.app)
3. Derives the on-chain URI as <url>/_aixyz/erc-8004.json and asks you to confirm
4. Selects chain and wallet, then signs and broadcasts the transaction
5. Writes the registration back into the registrations array in app/erc-8004.ts

const metadata: ERC8004Registration = {
  registrations: [{ agentId: 42, agentRegistry: "eip155:84532:0x8004A818BFB912233c491871b3d84c89A494BD9e" }],
  supportedTrust: ["reputation"],
};

​

Update Agent URI

aixyz erc-8004 update --url "https://new-domain.example.com" --broadcast

• If there’s one registration, it confirms and proceeds
• If there are multiple, it prompts you to select which one to update

​

Programmatic Usage

import { IdentityRegistryAbi, getIdentityRegistryAddress } from "@aixyz/erc-8004";

• Contract ABIs — TypeScript-typed ABIs for use with viem, ethers, or wagmi
• Deployed addresses — Known contract addresses across supported networks
• Zod schemas — Validation schemas for registration data and agent URIs

​

Integration with aixyz

• A2A — The agent card can reference an on-chain identity for verification
• x402 — Payment gating tied to verified on-chain agent identities
• MCP — Tool discovery backed by verifiable identity