The Ledger
ENS Forum Post Outlines Shared Schema for Agent Cards
A Nov. 5 ENS forum post labels a proposed schema for agent cards ENSIP-27 and describes how it would follow ENSIP-26’s agent-discovery records. The post lists required and optional JSON fields, points to a gateway reference implementation and sets out open questions about paths, identity and input provenance.

A Nov. 5 ENS forum post labels a proposed agent-card schema ENSIP-27 and links to pull request 75 in the ENSIP repository. The post says ENSIP-26 intentionally left the format of the document at the discovered endpoint open for a future ENSIP, and presents the schema proposal as that follow-up. It says a shared schema would let clients parse agent cards interoperably instead of relying on formats invented by every gateway.
Source discuss.ens.domains
“Without a shared schema, every gateway invents its own format and clients can’t parse agent cards interoperably.”
Gob Ross - Merlini (@TMerlini)
The proposal completes a discovery chain from an ENS name to an agent card
The post describes ENSIP-26 as standardising how to find an agent via ENS text records. It identifies agent-endpoint[mcp] and agent-endpoint[a2a] as the records used to locate an agent, while leaving the format of the document at the discovered endpoint open. The proposed schema defines that document as a JSON resource at /.well-known/agent.json.
The discovery chain in the post starts with an ENS name, then uses the agent-endpoint[mcp] text record to reach /.well-known/agent.json, followed by the MCP endpoint, capabilities and on-chain identity. The post also proposes agent-endpoint[ens-acs] as a dedicated protocol value in ENSIP-26. Clients that want to fetch the card directly could do so without going through the MCP endpoint first.
The proposed schema lists required and optional fields
The post lists eight required fields: schema_version, name, url, provider, version, capabilities, authentication and skills. It identifies url as the MCP endpoint and also names several optional fields.
The optional erc8004 field provides an on-chain identity anchor containing a registry and agent ID. trustScope provides A2A depth limiting through transitive, maxDepth and capabilities. The post describes sanitizationSpec as an IPFS URI for an input sanitization pipeline and inputSources as a declared input origin scope.
The post points to a gateway implementation and leaves three questions open
The post points to a reference implementation at https://gateway.ensub.org/agent/0xe61f5a6783ae09949b9a1b6821b68f89c0d7bb2d/5/.well-known/agent.json. It says three ERC-8004 collection registries are running on Ethereum mainnet and that the gateway serves agent cards offchain via CCIP-Read for *.dinamic.eth subnames.
The post asks whether /.well-known/agent.json should be the only valid path or whether agent-endpoint[ens-acs] should allow any URL. Multi-agent gateways may want per-agent paths rather than root-level cards. It also asks whether erc8004 should be required, and whether sanitizationSpec is too implementation-specific for a general schema or input provenance belongs at the agent-card level. The post says related PR #76 contributes erc8004 to ENSIP-26’s agent-context and registers agent-endpoint[ens-acs] as the protocol value pointing to the card.
Sources
- Original source ENS Discussion Forum discuss.ens.domains
Related stories
- ENS forum post proposes NSEC proofs to release TLDs permissionlessly
- ENS DAO Puts Governor Nexus Upgrade to a Vote After Reversing Audit Poll
- ENS Launches ENSv2 on Ethereum Mainnet
- Phase launches mainnet with $45M backing for AI-agent connectivity
- ERC-8454 Draft Adds a Bar Against Double-Counting Agent Claims