SPP · Load

SPP hourly load by control zone

Name: SPP hourly load by control zone
Creator: Dryos

Hourly load in each of SPP's 20 control zones across the RTO and RTO West, split as SPP files it into CF and NC load, about two days behind.

spp-load-hourlydaily, two days behind · 1h rows20 entities

CSWS

6,982MW

2026-09-17 04:00 UTC

OKGE

5,314MW

2026-09-17 04:00 UTC

WACM

2,447MW

2026-09-17 04:00 UTC

Read from the Dryos API and cached for an hour; the stream itself updates daily, two days behind.

What is in it

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

LoadMW
The zone's load for the hour, CF and NC together.
load_mw
CF loadMW
Load filed under SPP's Forecast Area Type CF.
load_cf_mw
NC loadMW
Load filed under SPP's Forecast Area Type NC; seven zones have it.
load_nc_mw

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. SPP stamps the interval's end.e.g. 2026-09-13T05:00:00Z
isorequired	string	Publishing ISO.e.g. SPP
zonerequired	string	Control zone as SPP names it (CSWS, EDE, … in the RTO; PRPA, WACM, WAUW in RTO West).e.g. SPP
baarequired	string	Balancing authority: SPP for the RTO, SWPW for RTO West.e.g. SPP
load_mw	number	Load in the zone for the hour, MW: the CF and NC rows summed.e.g. 0.0
load_cf_mw	number	The zone's load filed under Forecast Area Type CF, MW.e.g. 0.0
load_nc_mw	number	The zone's load filed under Forecast Area Type NC, MW — seven zones have one.e.g. 0.0
source_published_at_utc	timestamp	When SPP published the row.
collected_at_utcrequired	timestamp	When Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-09-14T22:20:00Z

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/spp-load-hourly/query?node=CSWS&limit=12"

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

shell

curl "https://api.dryos.ai/v1/datasets/spp-load-hourly"

Full parameters — bucketing, aggregation, filters and search — are on the API reference.

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 Load been at CSWS over the last 24 hours, and when did it peak?

Setup for every client is on the MCP server page.

A change in the collector is a change in the data. Anyone reading a step in a series is owed the day it moved under them.

2026-09-14
First collected, from SPP's marketplace portal.
SPP's load by zone was not here. Reconciled against the live files on 2026-09-14: schema, nulls, primary key, value bands and row counts passed.

Pulled straight from SPP Marketplace Portal · Hourly Load — 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 daily, two days behind; the interval timestamp is the start of the interval, in UTC.
SPP publishes on US Central prevailing time, with a UTC column on every row. Every timestamp Dryos serves is UTC.