kardashev vs gridstatus
This comparison is Python-specific - gridstatus has no JavaScript/TypeScript equivalent, so there’s nothing to compare kardashev against here. The JS client covers the same hosted API as the Python Client.
| kardashev | gridstatus | |
|---|---|---|
| API key required | No for hosted Client; ISO-NE LMP needs a free ISO account; direct PJM hourly LMP is currently broken (use hosted API) | No (direct ISO access); hosted gridstatusio client requires a key |
| License | MIT | BSD-3-Clause |
| US ISO coverage | 7 (CAISO, ERCOT, MISO, NYISO, ISONE, SPP, PJM) | 7 US ISOs + IESO, AESO (Canada), plus EIA |
| Hosted normalized API | Yes, free, no key (Client) | Yes, paid tiers (gridstatusio) |
| Direct ISO scrapers | Yes, for 6 of 7 ISOs | Yes, for all covered ISOs |
| Datasets | 25+ | 450+ |
| Maturity | Early (2026) | 3+ years, funded, staffed |
Use gridstatus when
- You need Canadian ISOs (IESO, AESO) or direct EIA access
- You need the widest dataset catalog (450+ datasets)
- You want a project with years of production use and a large contributor base
Use kardashev when
- You want a free hosted API with no key for the 7 major US ISOs
- You want direct, no-key scrapers for the same set of ISOs
- You’re building a dashboard, research script, or agent workflow against LMP, load, fuel mix, carbon intensity, curtailment, or interconnection queue data and don’t need Canadian coverage
See Data Sources for exact provenance and refresh cadence, and Supported ISOs for the per-ISO coverage matrix.
Last updated on