API & data downloads
Everything on the map is available as JSON or CSV, free, without a key. Please cache responses and keep requests modest. The data combines several licenses: OpenStreetMap data is © OpenStreetMap contributors under the ODbL (derived databases must stay ODbL), and Epoch AI data is CC BY 4.0. Credit “Datacenter Source” and the underlying sources; see Sources & methodology.
On the map, Download CSV exports exactly the facilities your current filters show.
GET/api/facilities
Facility summaries (the rows the map shows), sorted by largest capacity. Add format=csv for a spreadsheet. Filters, combinable:
| q | Free text: name, company, city |
| status | operating, expanding, under_construction, planned, cancelled, unknown (comma-separated) |
| type | hyperscale, ai_campus, colocation, enterprise, government, crypto_hpc, unknown |
| state | Two-letter codes, e.g. VA,TX |
| org | Company ids (operator, owner, tenant or end user), from /companies/<id> |
| minMw | Minimum current-or-planned MW |
| hasPower | 1 = only facilities with a power figure |
| iso | PJM, ERCOT, MISO, SPP, CAISO, NYISO, ISO-NE… |
| utility | Utility company ids |
| verify | verified_operating, grid_backed, under_construction, in_development, announced_only, unverified |
| ttp | Time to power: energized, lt1, 1to2, 2to4, gt4, unknown |
| stage | pre_grid, grid_study, grid_signed, construction, operating |
| queue | 1 = has an interconnection-queue record |
| onsite | 1 = has documented on-site / dedicated generation |
/api/facilities?state=TX&stage=construction,grid_study&format=csv
GET/api/facilities/{id-or-slug}
The full record: every claim with its source, confidence, method and date; resolved fields with disagreeing values; parties; timeline and phases; parcels and valuations; interconnection records; the verification ladder; power reality; grid path; and the time-to-power window with its drivers and assumptions. sources lists every cited source.
/api/facilities/epoch-meta-hyperion
GET/feed.xml
Atom feed of sourced changes (capacity, status, permits, grid requests, construction milestones). Scope it with facility, state or org. Browse the same data at /changes.
/feed.xml?state=VA
GET/api/routing
Probabilistic estimate of which cloud regions and facilities could process an AI API request from a location. It is an estimate from documented routing scope, latency and capacity — never a claim about where a specific request went.
/api/routing?lat=40.71&lon=-74.0&service=claude-api
Bulk files
- /data/facilities.geojson — all facility summaries as GeoJSON points
- /data/footprints.geojson — building, site and parcel outlines
- /data/grid.geojson — OSM substations and transmission lines near tracked sites