# ENS Metadata

> ENS-based identity and metadata protocol

## Docs

- [SDK](/sdk/documentation): Find documentation [on Github](https://github.com/0xLighthouse/ens-metadata/tree/main/packages/sdk).
- [Agent](/schemas/agent): An AI agent with ERC-8004 metadata.
- [Application](/schemas/application): A software application, service, or website.
- [Contract](/schemas/contract): An on-chain smart contract found at this node's resolved address.
- [Delegate](/schemas/delegate): A voter who has been delegated voting power.
- [Globals](/schemas/globals): A collection of globally applicable ENS record schemas.
- [Grant](/schemas/grant): A grant issued by an organization.
- [Group](/schemas/group): 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.
- [Resources](/overview/resources): View the [draft ENSIP](https://github.com/ensdomains/ensips/pull/64) to provide feedback
- [How schemas work](/overview/schemas): ENS metadata is built on three layers: a class label, a schema definition, and the attributes themselves. Together they let any ENS node declare what it represents and carry structured, machine-readable metadata about it.
- [Setting up metadata for your AI agent](/guides/agents): This guide explains how to publish your AI agent's identity and capabilities as ENS metadata, turning an ENS name into a permissionless, registry-free discovery point for your agent. It complements [ERC-8004](https://eips.ethereum.org/EIPS/eip-8004), and the on-chain records described here can stand alone or point at an existing ERC-8004 registration file via `agent-uri`.
- [Attesting social attributes with ENS](/guides/attestations): This guide explains how to attach a compact, verifiable attestation to an ENS name. Supported platforms today are:
- [Filling out your delegate information](/guides/delegate-statements): This guide explains how to publish your delegate information as ENS
metadata, turning your ENS name into a single source of truth for your online delegate identity.
- [Representing your organization with ENS metadata](/guides/organizations): This guide explains how to use a single ENS name as the canonical, on-chain index of everything an organization controls, including legal entities, officers, treasuries, smart contracts, and internal working groups. The end result is a tree of subnames under your organization's root ENS name, where each subname resolves to a real on-chain address and carries structured metadata describing its role.
- [Using parameterized key names](/guides/parameterized-keys): ENS text records are simple key-value pairs. Parameterized key names extend this model to support dictionaries and ordered lists, without requiring any changes to the underlying resolver. A parameter is appended to a key name in square brackets:
- [CLI](/cli/documentation): Find documentation [on Github](https://github.com/0xLighthouse/ens-metadata/tree/main/packages/cli).