agents.dinamic.eth

On-chain agent identities bound to NFT collections —
trustlessly registered, ENS-discoverable, zero custody.

Ready to register your agent?

Hold an NFT from an onboarded collection — bridge it in under a minute.

agents
.dinamic.eth

NFT holders bridge their collection into a trustless on-chain agent identity. Each agent is an ERC-721 NFT with a portable registration file, verifiable services, and a bidirectional ENS link via ENSIP-25.

Bridge Your NFT

Manage Your Agent Use Your Agent ERC-8004 spec

ERC-8004

ENSIP-25

ERC-7930

Non-custodial

EIP-712 verified

Trustless Agent Registry

Agents indexed from gateway

gateway.ensub.org

Registered

—

Active

—

Registered Agents

Nameagents.dinamic.ethpolls every 10s

How it works

Bridge your NFT

Hold an NFT from an onboarded collection. Call registerWithSource — no lock, no transfer. Ownership is checked live at mint time.

Agent identity NFT

Minting issues an ERC-721 agent identity on-chain. The token URI resolves to a portable registration file declaring your agent's services and endpoints.

ENS verified via ENSIP-25

Link your agent to any ENS name with a single setText call. The key encodes your registry as an ERC-7930 interoperable address — trustless, bidirectional.

Non-custodial

The factory is Ownable2Step. Agent wallets use EIP-712 signatures with IERC1271 smart wallet support. Your keys, your agent.

Under the hood

ERC-8004ERC-721

Trustless Agent Registry

One AgentIdentityRegistryFactory deploys a per-collection registry. Each registry is an ERC-721 contract — agent identities are owned, transferable NFTs. The token URI resolves to an ERC-8004 registration JSON declaring the agent's name, description, services (MCP, A2A), and its source NFT link. Services are agnostic to the underlying AI stack — any endpoint can be declared.

factory.deployRegistry(collection, cfg)
registry.registerWithSource(tokenId)
tokenURI → ERC-8004 registration JSON

ENSIP-25ERC-7930

Bidirectional ENS ↔ Agent linking

ENSIP-25 defines a text record convention that links an ENS name to an on-chain agent identity. The key encodes the registry address as an ERC-7930 interoperable binary address — chain type, chain ID, and EVM address packed into a single compact hex string. Any ENS resolver that reads text records can verify the link without trusting a third party. The gateway at agents.dinamic.eth serves this page as the canonical landing for the registry.

key: agent-registration[<ERC-7930>][<agentId>]
value: <ens-name>
setText(node, key, value)

Supported service types

Model Context Protocol

Anthropic's open protocol for connecting AI models to external tools and data sources. Agents that expose MCP endpoints can be plugged into Claude, Cursor, and any MCP-compatible host.

Agent-to-Agent

Google's Agent-to-Agent protocol for structured inter-agent communication. Enables autonomous multi-agent workflows without a human in the loop at each step.

ENS Name

A linked ENS name for the agent — human-readable, CCIP-Read resolvable. Set via ENSIP-25 text record. Allows agents to be discovered by name, not just registry address.