CAISO · Load

CAISO hourly actual load

Name: CAISO hourly actual load
Creator: Dryos

Hourly integrated actual load for each CAISO area and every Western EIM balancing authority — what the forecasts are scored against.

caiso-load-actual-hourlyhourly, ~1 h after the hour · 1h rows37 entities

CA ISO-TAC

30,638MW

2026-09-18 03:00 UTC

PGE-TAC

13,123MW

2026-09-18 03:00 UTC

SCE-TAC

14,153MW

2026-09-18 03:00 UTC

Read from the Dryos API and cached for an hour; the stream itself updates hourly, ~1 h after the hour.

What is in it

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

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, read from OASIS's GMT column.e.g. 2026-09-14T20:00:00Z
isorequired	string	Publishing ISO.e.g. CAISO
zonerequired	string	Load area as CAISO names it (TAC_AREA_NAME): CAISO's own areas PGE-TAC, SCE-TAC, SDGE-TAC, VEA-TAC and MWD-TAC; CA ISO-TAC, which is their sum; and each Western EIM balancing authority (PACE, BPAT, AZPS…).e.g. PGE-TAC
load_mwrequired	number	Load for the area, MW.e.g. 9086.18
source_published_at_utc	timestamp	When CAISO published the row, UTC.
collected_at_utcrequired	timestamp	When Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-09-14T17:37:12Z

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/caiso-load-actual-hourly/query?node=CA%20ISO-TAC&limit=12"

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

shell

curl "https://api.dryos.ai/v1/datasets/caiso-load-actual-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 Actual been at CA ISO-TAC 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 CAISO OASIS.
Load by area at every grain CAISO publishes it.

Pulled straight from CAISO OASIS · SLD_FCST (ACTUAL) — 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, ~1 h after the hour; the interval timestamp is the start of the interval, in UTC.
CAISO's market clock is US Pacific; OASIS answers in UTC. Every timestamp Dryos serves is UTC.