Free to look.
Talk to us to use it.
The data layer for US energy projects: everything that decides whether one gets built, on every project, traced to where it came from.
We are working with a small number of design partners to settle which data actually changes a decision. What we ingest next is coming out of those conversations, so access comes with one: tell us the call you are trying to make and we will tell you whether the record supports it yet.
A price list would fix the product before that question is answered. This way round, you get depth aimed at your work rather than ours.
We also carry projects that exist only via an aggregator. They are labelled as such, and they are excluded from the coverage table below.
What is actually in a record
What we are building: everything that decides whether a project gets built. Queue position and study milestones, the executed agreement and what the network upgrades cost, the air and water permits, site control, and eventually the local politics that kill projects long before the grid does. Today the record is deepest on the queue and the studies, and thinnest on the rest. The table below is exactly how deep, per market, with nothing rounded up.
A queue scraper gives you name, capacity and status. Every project here also
carries a construction stage, and beside it the method used to derive
that stage and a confidence score. Often the method is simply the
ISO's own status field, and the record says so rather than dressing it up as
analysis. Filter on min_confidence and keep only what you trust.
Coverage below is live. A thin column is not one thing.
Sometimes the market does not publish that field at all: PJM's serial file has
no developer column, so nobody has it. Sometimes it is published and we have
not wired it yet. n/a means the first. A percentage means the
second, and that is how much we hold.
What you can filter on
Twenty-two parameters on /projects, all available on the free key: