PJM · Load

PJM load forecast history

Every load forecast PJM issued, kept by the moment it was made, for each forecast area to the end of the next day — PJM's own archive of what it expected, to hold against what came.

pjm-load-forecast-historydaily, every forecast issued · 1h rows11 entities
RTO
80,555MW
2026-11-23 04:00 UTC
AEP
15,247MW
2026-11-23 04:00 UTC
DOM
14,501MW
2026-11-23 04:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates daily, every forecast issued.

What is in it

Updates
daily, every forecast issued · 1h rows
Entities
11 entities — RTO, AEP, DOM…
Source timezone
US Eastern — every timestamp Dryos serves is UTC
Coverage
13 November 2026 to now
Rows held
17,336
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 hour, as of this vintage.

    forecast_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 PJM's own UTC column.e.g. 2026-09-09T12:30:00Z
isorequiredstringPublishing ISO.e.g. PJM
zonerequiredstringForecast area as PJM names it: a transmission zone, a region or `RTO_COMBINED`.e.g. RTO_COMBINED
forecast_mwrequirednumberForecast load for the hour, MW.e.g. 88140
source_published_at_utcrequiredtimestampWhen PJM evaluated this forecast, UTC — the vintage. Every publication is kept, so one interval carries a row per vintage that covered it.e.g. 2026-09-10T02:15:00Z
collected_at_utcrequiredtimestampWhen Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-09-09T12:35: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/pjm-load-forecast-history/query?node=RTO&limit=12"

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

shell
curl "https://api.dryos.ai/v1/datasets/pjm-load-forecast-history"

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 RTO 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-11-15

    First collected, from PJM Data Miner 2.

    Kept by PJM indefinitely. Reconciled against live responses on 2026-11-15.

How this stream is checked

  • Pulled straight from PJM Data Miner 2 · load_frcstd_hist — 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, every forecast issued; the interval timestamp is the start of the interval, in UTC.
  • PJM's Eastern Prevailing Time observes daylight saving; its rows carry UTC as well. Every timestamp Dryos serves is UTC.

Related streams