Use public energy data
Search public energy records in one API and open the source behind each result.
Gridstate puts public data on power projects, plants, utilities, and grid activity in one API. Every key fact links back to its source.
Search records
Create a key and make your first request.
Connect an AI agent
Let Claude Code, Codex, Cursor, or VS Code search Gridstate.
Check a location
Find public records for a location.
Browse the API
See every endpoint and response field.
What do you want to do?
Open the source
See the file and exact row behind a value.
See what data is available
Check which places and data types Gridstate covers.
Look back in time
See what a source said on an earlier date.
What you can find
| Data | What it includes | What it does not prove |
|---|---|---|
| New projects | Queue records and reported transmission projects | Projects in a queue do not prove available power |
| Generation | EIA plants, generators, and monthly output | Published inventory may be revised |
| Grid activity | Regional demand, forecasts, power flows, and fuel mix | Past activity does not predict the future |
| Expected demand | Published demand and supply forecasts | Public plans do not prove that a site can connect |
| Utilities | Likely utilities for a location | Some locations can return more than one utility |
| Sources | Filings, source files, and record changes | You must still read the source for important decisions |
Gridstate cannot tell you how much power a site can receive
Public data helps you compare locations and find questions to ask. It cannot replace a utility study or approval. Missing answers stay unknown.
Use Gridstate with an AI agent
AI agents can find every documentation page through /llms.txt. Add .md to a documentation URL to get plain Markdown.
Use the hosted MCP server to let an agent search Gridstate directly.