# Indexing with Goldsky Goldsky is Web3’s realtime data platform, giving developers access to world-class data infrastructure to power their onchain applications. Seamlessly access the data you need with lightning-fast indexing, resilient subgraphs, and flexible data streaming pipelines. Spend less time on the complexities of infra maintenance and more time building incredible user experiences. ### Why Goldsky? * **Scalable Infrastructure**: Scalable and resilient infrastructure, handling data challenges as your application grows. * **Developer-Friendly Tools**: Easily integrate and iterate without being slowed down by complex data engineering. * **Enterprise Support:** The Goldsky team is available 24/7 to help if things go wrong. ### Goldsky Subgraphs **Subgraphs** let you efficiently access blockchain data relevant to your application. * **Fast Queries**: Optimized infrastructure means faster query responses and better performance. * **Flexible Integration**: Customize your queries and adapt indexing to suit your application's unique needs. * **Tagging & Organization**: Use tagging to organize your data, making it easier to manage and access. **Use Cases**: dApps, NFT marketplaces, gaming, DAOs – any scenario where you need reliable, real-time blockchain data. ### Getting Started For more details, check out the [Goldsky Documentation](https://docs.goldsky.com/chains/lumia/?utm_source=lumia\&utm_medium=docs). Start building smarter, faster, and focus on what really matters: delivering a great experience to your users. --- # Agent Instructions: 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: ``` GET https://docs.lumia.org/build/indexers/indexing-with-goldsky.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.