Machine-readable endpoints

There is no ZoningLabs API, no key, no rate limit and no uptime commitment. This page previously described all four. What does exist are the static files the site's own maps fetch.

What the site serves

Every map on this site fetches a prerendered file. Those files are public, and nothing stops you fetching them too — but they are build artefacts, their shapes follow whatever the pages need, and they can change without notice.

Live operator status: /live/{iso}/status.json — one of ercot, pjm, miso, spp, caiso, nyiso, isone, ieso
Power plants, GeoJSON: /power-plants/data/{operating|planned}/{fuel}/{state|us}
Data centres, GeoJSON: /data-centers/data/{state|us}
Nodal prices by market: /grid/map/nodal/data/{iso}
National plant layer: /grid/map/power-plants/data
Balancing authority polygons: /grid/map/balancing-authorities/data
Blog feed: /blog/feed.xml

Go to the sources instead

For anything you intend to build on, the upstream sources are better than these files: they are documented, versioned and maintained by the bodies that produce them. Each page on this site links to the ones it used.

If you need a real feed

Tell us what you are building and which dataset you need. If there is a case for a supported endpoint with a stable shape, that is worth doing properly rather than by scraping a build artefact.