> For the complete documentation index, see [llms.txt](https://docs.scrt.network/secret-network-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scrt.network/secret-network-documentation/secretvm-confidential-virtual-machines/agentic-support/eip-8004-support/what-erc-8004-stores.md). # What ERC-8004 stores ERC-8004 uses an identity registry based on ERC-721, where each agent is represented by a unique agentId. The registry points to an agent registration file via agentURI, and that registration file contains fields such as name, description, image, services, x402Support, registrations, and supportedTrust. In SecretVM, the registration flow maps naturally to this structure: * Agent name → name * Image URL → image * Description → description * Services → services * x402 support → x402Support * Supported trust models → supportedTrust ERC-8004 allows agents to advertise arbitrary service endpoints, and the supportedTrust field is optional. If present, it communicates which trust assumptions or validation models the agent supports. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.scrt.network/secret-network-documentation/secretvm-confidential-virtual-machines/agentic-support/eip-8004-support/what-erc-8004-stores.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.