# ENS Organizational Registry

> ENS-based organizational identity and metadata registry protocol

## Docs

- [AI Agents](/use-cases/agents): AI agents are proliferating rapidly, but they lack a universal identity layer. Standards like [ERC-8004](https://eips.ethereum.org/EIPS/eip-8004) have emerged to address this — giving agents an on-chain anchor and a standardised way to publish capability metadata. However, ERC-8004 requires agents to register with a smart contract, which pushes the discoverability issue from the agent onto the smart contract. Many different registries could exist, which results in continued fragmentation where users who want to discover an agent have no single source of truth.
- [Delegate Statements](/use-cases/delegate-statements): Delegates in a DAO governance system often publish a statement — a
summary of their philosophy and why others should delegate voting power
to them. Because many delegates participate in multiple DAOs, their
statement often varies from one community to the next.
- [Forum Username Linking](/use-cases/forum-username-linking): Governance platforms need to connect on-chain wallets to the forum identities of the people behind them. Right now, every service that needs this mapping — Karma, Tally, Curia, Agora, Snapshot — solves it independently.
- [Regulatory Compliance](/use-cases/regulatory-compliance): As DAOs adopt legal wrappers — such as Wyoming's Decentralised Unincorporated Nonprofit Association (DUNA) — they take on regulatory obligations that exist in tension with how on-chain organisations typically operate. A DUNA, for example, may need to publish its registered agent, principal office address, officers, and registration numbers. Other jurisdictions impose similar disclosure requirements on foundations, cooperatives, and other DAO-adjacent legal structures.
- [Treasury & Contract Discovery](/use-cases/treasury-and-contracts): On-chain organisations and DAOs typically operate across multiple treasury addresses, governance contracts, token contracts, and protocol deployments. But there is no authoritative place where an organisation publishes the full list of addresses it controls. Tracking down this information usually involves searching through forums posts or github repositories.
- [getMetadata](/sdk/get-metadata): Gets metadata for specified ENS name.
- [Agent](/schemas/agent): AI agent identity metadata aligned with ERC-8004 registration format.
- [Application](/schemas/application): An application, service, or dApp within the organization.
- [Contract](/schemas/contract): Smart contract metadata profile following Enscribe smart contract metadata format.
- [Delegate](/schemas/delegate): A delegate.
- [Globals](/schemas/globals): A collection of globally applicable ENS record schemas.
- [Grant](/schemas/grant): A grant issued by an organization.
- [Group](/schemas/group): This node describes a group of individuals or entities with a shared purpose or responsibility.
- [Organization](/schemas/org): A legal or organizational entity.
- [Person](/schemas/person): A person.
- [Treasury](/schemas/treasury): Funds and assets managed by a collective of individuals or entities.
- [Wallet](/schemas/wallet): A wallet for holding or managing assets.
- [ENSIP-X: Node Classification Metadata](/overview/ensip-xx): This ENSIP proposes a standard method for using text records to declare the role of an ENS name/subname (node). Two types of standardized text records are introduced, which provide for labeling the role of node against a larger organizational structure, and for defining the structure of additional, context-dependent attributes that may be appended to that node.
- [Resources](/overview/resources): View the [draft ENSIP](https://github.com/ensdomains/ensips/pull/64) to provide feedback
- [Schemas](/overview/schemas): The node classification metadata spec dictates how JSON schemas can be appended to an ENS name (or subname) to expose which additional metadata attributes are expected to be provided for that node. It is expected that a popular, standardized set of schemas will become widely used, which will improve cross-compatibility across the industry, however anyone is free to create additional JSON schemas to facilitate attaching whatever metadata serves their purpose best.