The open, connected registry of the U.S. power grid
Built and maintained by a community of users who know every corner of the grid, CommonGrid connects energy infrastructure data into a public, shareable model. Anyone can contribute what's missing and sharpen what's rough, and the data is free to use under an open license.
- Utilities
- Grid operators
- Power plants
- Transmission lines
- EV stations
Nine entry points, one connected graph.
Every utility links to its territory, every territory to its operator, every plant to its interconnection. Start anywhere.
All U.S. utilities — IOUs, co-ops, munis, and federal power agencies. Filtered by state, segment, and ISO.
The entities that coordinate dispatch, markets, and reliability across every interconnection.
Demand response, rebates, EV programs, VPP — queryable by asset type, segment, and territory.
Residential and commercial rate structures — TOU windows, demand charges, standby, net metering.
Solar, wind, nuclear, gas, hydro — EIA Form 860 normalized and connected to utilities and territories.
High-voltage infrastructure from 69 kV to 765 kV. Spatially queryable, attributed to owners.
Every public AC and DC station in the U.S. — networks, plug standards, and power levels.
Wholesale market nodes — trading hubs, load zones, SUBLAPs, and generation pricing across 7 ISOs/RTOs.
Step-up, step-down, and switching substations — voltage class, owner, and interconnected assets normalized from OpenStreetMap.
Have a great dataset that belongs in the connected graph? Let’s get it in here.
A living dataset, with every edit citable, attributed, and reversible.
CommonGrid is built like a wiki, with every change recorded with an author, a source, and a timestamp. Every record has a history, and no record is silently overwritten.
Public infrastructure deserves public data.
The grid is a shared good. The knowledge of how it’s structured should be, too — available to regulators, researchers, startups, utilities, and anyone building what comes next.
Fragmentation is the tax.
EIA forms, FERC filings, HIFLD shapefiles, state dockets, GIS exports — every serious grid question begins with three weeks of data plumbing. CommonGrid pays that cost once, for everyone.
People who work with this data.
Utility engineers, researchers, analysts at ISOs, and developers at energy startups. Contributors and a small elected moderation team. Texture funds the infrastructure; the project governs itself.
ODbL 1.0 — free, forever.
Use it commercially. Build products on it. Redistribute it. The only obligation is attribution and sharing improvements back. Same license as OpenStreetMap.
How an edit becomes part of the record.
Low-friction for small fixes, structured for big changes. Anyone can propose; trusted contributors are auto-approved on non-critical fields; approved edits are recorded in the changelog.
Propose
Hit Suggest edit on an entity page. Cite a source. Describe what changed and why.
Review
Moderators check citations and weigh conflicts. Trusted contributors skip review for non-critical fields. Contested changes trigger a discussion thread on the entity.
Approve & publish
Approved edits update the database immediately, making them available on the site and through the API. Each change also appears in the changelog.
Attribute
Every record carries its full edit history and citation trail. Researchers can cite a specific revision; auditors can see exactly who touched what.
REST API, vector tiles, weekly snapshot.
60 requests/hour unauthenticated. 5,000/hour with a free key. Geo endpoints serve MVT tiles. Full database dumps published weekly under ODbL.
# every utility in California curl https://commongrid.info/api/v1/utilities?state=CA # a specific power plant by slug curl https://commongrid.info/api/v1/power-plants/palo-verde # which utility serves this coordinate? curl https://commongrid.info/api/v1/territories/lookup?lat=30.2672&lng=-97.7431 # state of a record at a point in time curl https://commongrid.info/api/v1/utilities/austin-energy?at=2025-12-01
Every endpoint below is documented in our interactive REST API reference, generated from the same OpenAPI spec. See the developer overview for auth, rate limits, and keys.