> For the complete documentation index, see [llms.txt](https://docs.gridstatus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridstatus.io/getting-started/readme.md). # Welcome Monitor, analyze, and export data about power markets. Grid Status has all the tools you need to stay on top of what's happening on the grid.
Our mission is to provide accessible, actionable energy data to accelerate the energy transition. The documentation here will give you everything you need to know to be successful with our platform. For additional support or questions, please [Contact Us](https://www.gridstatus.io/contact). ### Other Resources
Grid Status WebsiteOpen and use our productScreenshot 2025-01-21 at 11.08.15 AM.pnghttps://www.gridstatus.io/
Python Client LibraryPython client for accessing the GridStatus.io Hosted API.API Cover Image.pnghttps://github.com/gridstatus/gridstatusio
Grid Status ExportsBlog where we share our thoughts and analysis on the ever-evolving electrical grid.Screenshot 2025-01-17 at 1.16.16 PM.pnghttps://blog.gridstatus.io/
--- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.gridstatus.io/getting-started/readme.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 `build a script that syncs our docs to a CMS` 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.