> 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/developers/guides.md). # Guides - [Best Practices](https://docs.gridstatus.io/developers/guides/best-practices.md): Optimize your Grid Status API usage for performance, reliability, and cost-effectiveness. - [Error Handling](https://docs.gridstatus.io/developers/guides/error-handling.md): Understanding API error responses and how to handle them effectively in your applications. - [Utility Endpoints](https://docs.gridstatus.io/developers/guides/utility-endpoints.md): Additional endpoints for metadata, monitoring, and discovery. - [Breaking Changes](https://docs.gridstatus.io/developers/guides/breaking-changes.md): What constitutes a breaking change to the Grid Status API, how we notify affected customers, and what to do when one affects you. - [Recipes](https://docs.gridstatus.io/developers/guides/recipes.md): Complete, copy-paste-ready examples for common energy market analysis tasks using the Grid Status API. - [Setup](https://docs.gridstatus.io/developers/guides/recipes/setup.md): Setup instructions for all recipe examples - [Pull data for a single node](https://docs.gridstatus.io/developers/guides/recipes/pull-data-for-single-node.md): Fetch day-ahead hourly settlement point prices for a specific ERCOT node - [Get Latest Forecast as of Bid Close](https://docs.gridstatus.io/developers/guides/recipes/ercot-day-ahead-load-forecast-cutoff.md): Get the latest ERCOT load forecast available as of day-ahead bid close - [Backfill and Incrementally Sync a Dataset](https://docs.gridstatus.io/developers/guides/recipes/backfill-and-incremental-sync.md): Backfill a dataset once, then keep it current with high-watermark incremental syncs - [Trading Hub Price Analysis](https://docs.gridstatus.io/developers/guides/recipes/trading-hub-price-analysis.md): Compare prices across trading hubs to identify arbitrage opportunities and congestion patterns - [Data Freshness Monitoring](https://docs.gridstatus.io/developers/guides/recipes/data-freshness-monitoring.md): Monitor data pipeline health and alert on stale data - [Quota-Aware Batch Processing](https://docs.gridstatus.io/developers/guides/recipes/quota-aware-batch-processing.md): Process large date ranges while respecting API quotas --- # 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://docs.gridstatus.io/developers/guides.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.