> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/explorers/guardian-indexer.md). # Guardian Indexer A developer tool to search and explore Guardian policies, credentials, accounts, schemas, tokens, and on-chain records. A comprehensive search and exploration tool for all data recorded through Guardian — every policy, credential, account, schema, token, and on-chain document, searchable in a single interface. The indexer can be run by setting up a development environment. *** ### Who it's for * Developers — inspect policy structures, schemas, and credential documents during development * Registry operators — monitor activity across a Standard Registry and all associated policies * Technical auditors — trace relationships between documents and verify credential chains * VVBs — locate and review policy records, verification documents, and token activity * Researchers — query across the full history of Guardian's on-chain output *** ### Features * Global search across the entire dataset: policy IDs, schema names, VC content, schema properties, and more * Per-section keyword search with AND logic across Accounts, Methodologies, Documents, and Others * Standard Registry detail pages with full activity summaries linking through to all associated records * Policy detail pages covering activity, schemas, tokens, and roles * Schema pages with a field tree diagram and list of all credentials issued against each schema * VC and VP detail pages with document content, full history, and a relationship map * NFT transaction history and topic content listings * Policy comparison view — inspect structural differences between two policy versions * Priority loading queue — push any document, topic, or policy ahead of the standard sync schedule *** ### Source code The Indexer spans several folders in the Guardian monorepo: Relevant directories include `indexer-frontend/`, `indexer-service/`, `indexer-api-gateway/`, `indexer-common/`, `indexer-interfaces/`, `indexer-worker-service/`, `indexer-web-proxy/`. The `docker-compose-indexer.yml` file in the repository root is the starting point for running the stack locally. --- # 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://guardian.hedera.com/docs/develop/explorers/guardian-indexer.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.