> For the complete documentation index, see [llms.txt](https://docs.pharos.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.xyz/tooling-and-infrastructure/indexing.md). # Indexer ## Overview Indexing allows developers to efficiently query and access on-chain data without directly relying on raw RPC calls. Instead of scanning the blockchain for every request, indexing services process and organize data in a way that makes it easier to retrieve, filter, and use within applications. ## What You Can Do with Indexers * Query smart contract data efficiently * Track events and historical activity * Build dashboards and analytics * Power frontend applications with structured data * Monitor protocol and application-level metrics ## Why It Matters While RPC endpoints are useful for direct interaction with the network, they are not optimized for complex queries or large-scale data retrieval. Indexing services solve this by providing faster and more flexible access to blockchain data, making them essential for building scalable applications. ## Available Indexing Providers Pharos supports indexing solutions that help developers access and structure on-chain data efficiently. Refer to the provider below for setup and integration details: * Goldsky --- # 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.pharos.xyz/tooling-and-infrastructure/indexing.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.