> For the complete documentation index, see [llms.txt](https://docs.awenetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.awenetwork.ai/infrastructure/overview/identity.md). # Identity ## ERC-8004 and AgentBeat **ERC-8004 gives agents an onchain identity. AgentBeat makes their activity visible.** Agents need a consistent way to identify themselves, advertise their services and establish trust with applications and other agents. ### ERC-8004 ERC-8004 is an Ethereum standard for discovering and evaluating agents across organizations without requiring pre-existing trust. It defines three onchain registries: * **Identity Registry** — Gives each agent an ERC-721-based identifier connected to a registration file containing its metadata and service endpoints. * **Reputation Registry** — Provides a standard interface for publishing and retrieving feedback about an agent. * **Validation Registry** — Records requests and responses from systems independently validating an agent’s work. ERC-8004 provides identity and trust signals. It does not handle payments; x402 provides the separate payment layer. ### AgentBeat AgentBeat is AWE’s analytics and information layer for ERC-8004 agents. It indexes agent registrations and surfaces standardized signals around activity, decentralization and verification. This helps builders and users distinguish between agents that are merely registered and agents demonstrating real activity. ### How they work together 1. An agent registers an ERC-8004 identity. 2. Its registration file describes its capabilities and service endpoints. 3. Reputation, validation and economic activity generate additional signals. 4. AgentBeat indexes those signals and makes them easier to inspect. ### Identity is the starting point Registration proves that an onchain identity exists. It does not guarantee that an agent is active, reliable or safe. AgentBeat adds observable context, but users and applications should still evaluate individual agents before trusting them with valuable actions. > ERC-8004 is currently marked as a Draft Standards Track proposal. Its specification and implementations may continue to evolve. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.awenetwork.ai/infrastructure/overview/identity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.