Query normalized LMP, fuel mix, and load data across multiple US ISOs/RTOs through the GridStatus.io API
domain: api.gridstatus.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an account and get an API key from GridStatus.io account settings.
Authenticate via an x-api-key header or api_key query parameter on requests to api.gridstatus.io/v1/.
Call /v1/datasets to discover and query normalized datasets spanning CAISO, ERCOT, PJM, MISO, SPP, NYISO, ISO-NE, and AESO in one consistent schema.
Check /v1/api_usage to see your plan's row/request limits and current usage before running large historical pulls.
Use the official gridstatusio Python client as a wrapper instead of raw HTTP calls if preferred.
Known gotchas
Metering is row-based, not just request-based — the free tier is on the order of 500,000 rows/month, and wide historical LMP pulls burn through that fast.
Don't confuse the hosted, maintained api.gridstatus.io product with the separate open-source gridstatus Python library, which scrapes ISOs directly and is more fragile to upstream site changes.
Exact per-second/minute rate limits are plan-specific and only visible via your own /v1/api_usage response, not published statically.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?