Your @ensdomains name can now be a verifiable AI agent identity.
Using ERC-8004, ENSIP-25, and ENSIP-26, an ENS name can advertise metadata, MCP endpoints, and agent capabilities that AI applications can discover and consume.
We built a simple interface to make this easy 👇
Using ERC-8004, ENSIP-25, and ENSIP-26, an ENS name can advertise metadata, MCP endpoints, and agent capabilities that AI applications can discover and consume.
We built a simple interface to make this easy 👇
Try it out:
ens8004.xyz
Full walkthrough:
thomasclowes.com/turning-ens-na…
Learn how to:
• Register an ERC-8004 agent
• Link it to an ENS name
• Publish ENSIP-25/26 metadata
• Expose MCP endpoints
• View the binding on OpenSea
🧵2/3
ens8004.xyz
Full walkthrough:
thomasclowes.com/turning-ens-na…
Learn how to:
• Register an ERC-8004 agent
• Link it to an ENS name
• Publish ENSIP-25/26 metadata
• Expose MCP endpoints
• View the binding on OpenSea
🧵2/3
ERC-8004 bindings are now visible on @OpenSea.
The relationship between an ENS name and its agent can be viewed directly on the OpenSea asset page.
Because the agent is bound to the ENS NFT, ownership and control transfer with the name.
🧵3/3
The relationship between an ENS name and its agent can be viewed directly on the OpenSea asset page.
Because the agent is bound to the ENS NFT, ownership and control transfer with the name.
🧵3/3
• • •
Missing some Tweet in this thread? You can try to
force a refresh
