CAISO · Load

CAISO seven-day load forecast

CAISO's hourly load forecast for the next seven days, by area, kept as snapshots stamped when Dryos first saw each value.

caiso-load-forecast-7daychecked every 15 min, a week ahead · 1h rows36 entities
CA ISO-TAC
28,389MW
2026-09-25 06:00 UTC
PGE-TAC
11,836MW
2026-09-25 06:00 UTC
SCE-TAC
13,487MW
2026-09-25 06:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates checked every 15 min, a week ahead.

What is in it

Updates
checked every 15 min, a week ahead · 1h rows
Entities
36 entities — CA ISO-TAC, PGE-TAC, SCE-TAC…
Source timezone
US Pacific — every timestamp Dryos serves is UTC
Coverage
14 September 2026 to now
Rows held
161,568
Primary key
iso, zone, interval_start_utc, source_published_at_utc

What it measures

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

  • ForecastMW

    Forecast load for the area and hour, as of this snapshot.

    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, read from OASIS's GMT column.e.g. 2026-09-14T20:00:00Z
isorequiredstringPublishing ISO.e.g. CAISO
zonerequiredstringLoad 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_mwrequirednumberLoad for the area, MW.e.g. 9086.18
source_published_at_utcrequiredtimestampWhen Dryos first saw this value, UTC — the vintage. OASIS overwrites a forecast in place and stamps no issue time, so this is Dryos's first sight, to within fifteen minutes, never CAISO's issue time. One interval carries a row per value it has held.e.g. 2026-09-14T17:37:00Z
collected_at_utcrequiredtimestampWhen Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-09-14T17:37:12Z

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/caiso-load-forecast-7day/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-forecast-7day"

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 Forecast 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.

Changes to this collector

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.

  1. 2026-09-14

    First collected, from CAISO OASIS.

    OASIS overwrites these forecasts in place with no issue time, so they are kept as snapshots stamped with Dryos's first sight of each value.

How this stream is checked

  • Pulled straight from CAISO OASIS · SLD_FCST (7DA) — 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 checked every 15 min, a week ahead; 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.

Related streams