I have been thinking further about how ENS names become agents, and concluded that the pattern utilized by ENS8004.xyz (see Turning ENS Names into Discoverable AI Agents) should be the canonical methodology.
All the relevant information for surfacing that an ENS name is an agent is available on-chain. That said, in the interest of making integration of an ENS names’ status as an agent as simple as possible I have added support for it to the ENSWhois.com API.
Integration guidance is outlined here: Integrating ENS Agents | ENSWhois Docs
A single API call to the /domain/:name/agent endpoint will indicate its registration status.
This API is consumed by the ENSWhois product itself to produce new tooling such as the ENS Agents Directory: ENS Agents Directory | ENSWhois.com
A complete agent setup would include the registration of the ENS name in the Adapter8004 adapter contract AND specification of appropriate ENSIP-26 records AND specification of the ENSIP-25 agent-registration text record.
The directory allows you to filter agents based on the specification of these values.
Additionally ENS names that are agents will display a notification indicating this on the individual domain page.
Feedback welcomed.