ERCOT · Load

Actual system load

Metered demand by weather zone, hourly, with ERCOT's own system total as its own row. The denominator for scarcity. Collected from ERCOT MIS (NP6-345), reconciled against the source file.

ercot-actual-load-weather-zonehourly, posted next day · 1h rows9 entities
COAST
17,198MW
2026-09-17 04:00 UTC
NORTH_C
20,590MW
2026-09-17 04:00 UTC
TOTAL
69,398MW
2026-09-17 04:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates hourly, posted next day.

What is in it

Updates
hourly, posted next day · 1h rows
Entities
9 entities — COAST, NORTH_C, TOTAL…
Source timezone
US Central — every timestamp Dryos serves is UTC
Coverage
26 August 2026 to now
Rows held
4,752
Primary key
iso, zone, interval_start_utc

What it measures

Every value, its unit, and what the source means by it.

  • Actual loadMW

    Hourly average metered demand for the zone.

    load_mw

Columns

Exactly what a request answers with, read from the API rather than written here.

ColumnTypeDescription
interval_start_utcrequiredtimestampStart 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
isorequiredstringPublishing ISO.e.g. ERCOT
zonerequiredstringERCOT zone, in the actual-load report's spelling (COAST, EAST, FAR_WEST, NORTH, NORTH_C, SOUTH_C, SOUTHERN, WEST for weather zones; NORTH, SOUTH, WEST, HOUSTON for forecast zones). 'TOTAL' is the ERCOT system total as published, not a sum computed here.e.g. COAST
load_mwrequirednumberHourly average load, MW.e.g. 17115.5
source_published_at_utcrequiredtimestampWhen 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_utcrequiredtimestampWhen 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

shell
curl "https://api.dryos.ai/v1/datasets/ercot-actual-load-weather-zone/query?node=COAST&limit=12"

The catalogue entry — every column, its type and the source

shell
curl "https://api.dryos.ai/v1/datasets/ercot-actual-load-weather-zone"

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.

shell
claude mcp add --transport http dryos https://api.dryos.ai/mcp

Then ask:

What has Actual load been at COAST over the last 24 hours, and when did it peak?

Setup for every client is on the MCP server page.

How this stream is checked

  • Pulled straight from ERCOT MIS · NP6-345-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 hourly, posted next day; 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