Answering "can this site take 120 MW" means reading a tariff PDF, an ISO queue spreadsheet, a transmission plan, and a state docket that disagree on what the utility is even called. Gridstate normalizes them into an API where every field cites its source document and page. Facts are bitemporal, so you can ask what a tariff said on a date and separately what we knew on a date. Capacity comes back as utility confirmed, published, indicative, or unknown. Most sites are unknown.
Hi PH,
Answering "can this site take 120 MW" currently means fifteen browser tabs: a utility tariff PDF, an ISO queue spreadsheet, a transmission plan, a state docket. They disagree on what the utility is even called, and the answer expires in a few weeks.
Gridstate turns that into an API where every field cites its source document and page. Facts are bitemporal, so you can ask what a tariff said on a date and separately what we knew on that date.
It won't output available megawatts. Capacity comes back as utility confirmed, published, indicative, or unknown, and most sites are unknown. Deriving a number from queue data would be easy and wrong: queues measure development interest, not load-serving capacity.
There's an MCP server over the same API. Happy to answer questions about coverage.