ERCOT · Load
System-wide demand
System-wide actual demand at 15-minute resolution — the one-line answer to how much Texas is using. Collected from ERCOT MIS (NP6-235).
ercot-system-demand15-min, posted hourly · 15m rows1 entityWhat is in it
- Updates
- 15-min, posted hourly · 15m rows
- Entities
- 1 entity
- Source
- ERCOT MIS · NP6-235-CD
- Source timezone
- US Central — every timestamp Dryos serves is UTC
- Coverage
- 29 August 2026 to now
- Rows held
- 1,868
- Primary key
- iso, interval_start_utc
What it measures
Every value, its unit, and what the source means by it.
- DemandMW
System-wide 15-minute average demand.
demand_mw
Columns
Exactly what a request answers with, read from the API rather than written here.
| Column | Type | Description |
|---|---|---|
| interval_start_utcrequired | timestamp | Start of the interval, UTC. Always UTC — ERCOT publishes wall-clock Central with a repeated-hour flag, which is resolved on ingest.e.g. 2026-08-29T14:15:00Z |
| isorequired | string | Publishing ISO.e.g. ERCOT |
| demand_mwrequired | number | System-wide demand, 15-minute average, MW.e.g. 56823.7 |
| source_published_at_utcrequired | timestamp | When ERCOT posted the document this row came from, UTC. For reports republished on a rolling window this is the vintage: the same interval appears once per publication, and the newest is the current view.e.g. 2026-08-29T14:17:01Z |
| collected_at_utcrequired | timestamp | When Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-08-29T14:18:02Z |
Read it
Public, read-only, no key and no sign-up. Relative times stay relative, so a URL keeps working.
The newest rows
curl "https://api.dryos.ai/v1/datasets/ercot-system-demand/query?limit=12"The catalogue entry — every column, its type and the source
curl "https://api.dryos.ai/v1/datasets/ercot-system-demand"Full parameters — bucketing, aggregation, filters and search — are on the API reference.
Ask an agent
The same stream through the Model Context Protocol, so Claude, ChatGPT, Cursor or any MCP client can query it directly.
claude mcp add --transport http dryos https://api.dryos.ai/mcpThen ask:
Show me Demand on System-wide demand over the last 24 hours.
Setup for every client is on the MCP server page.
How this stream is checked
- Pulled straight from ERCOT MIS · NP6-235-CD — no reseller in between — and compared against that file before it is served.
- Null means the source did not report it — never zero.
- A reading lands 15-min, posted hourly; the interval timestamp is the start of the interval, in UTC.
- ERCOT settles and publishes on US Central time. Every timestamp Dryos serves is UTC.
Related streams
- Actual system loadERCOT
Metered demand by weather zone, hourly, with ERCOT's own system total as its own row.
hourly, posted next day · 1h rows9 entitiesercot-actual-load-weather-zone - Seven-day load forecastERCOT
ERCOT's own load forecast by weather zone, refreshed every hour, seven days out.
hourly, 7 days ahead · 1h rows9 entitiesercot-load-forecast-weather-zone - Actual load by forecast zoneERCOT
Metered demand by the four forecast zones plus the system total, hourly.
hourly, posted next day · 1h rows5 entitiesercot-actual-load-forecast-zone - Seven-day forecast by forecast zoneERCOT
ERCOT's hourly-refreshed load forecast for the four forecast zones and the system, seven days out — every revision kept.
hourly, 7 days ahead · 1h rows5 entitiesercot-load-forecast-forecast-zone - Supply and demandERCOT
The grid-conditions headline: 5-minute demand against available committed capacity, from ERCOT's own dashboard feed — which retains two days, so the history exists because the collector keeps running.
every 5 min · 5m rows1 entityercot-supply-demand - ERCOT real-time LMPERCOT
Locational marginal prices from the latest SCED run, every ERCOT settlement point.
every 5 min · 5m rows1,118 entitiesercot-realtime-lmp