PJM · Grid

PJM operations summary, projected area peak

PJM's morning projection for each zone at the day's RTO peak: load forecast, scheduled capacity and unscheduled steam — kept as vintages.

pjm-ops-peak-areadaily, each morning · 1d rows11 entities
AEP
17,107MW
2026-11-22 23:00 UTC
COMED
10,252MW
2026-11-22 23:00 UTC
DOM
16,292MW
2026-11-22 23:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates daily, each morning.

What is in it

Updates
daily, each morning · 1d rows
Entities
11 entities — AEP, COMED, DOM…
Source timezone
US Eastern — every timestamp Dryos serves is UTC
Coverage
10 November 2026 to now
Rows held
187
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.

  • Peak load forecastMW

    Load forecast for the area at the RTO's projected peak.

    load_forecast_mw
  • Scheduled capacityMW

    Generation scheduled in the area for the peak.

    internal_scheduled_capacity_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
zonerequiredstringPJM's area as the summary names it: a region or a transmission zone.e.g. AEP
load_forecast_mwnumberLoad forecast for the area at the RTO's projected peak, MW.e.g. 21674
internal_scheduled_capacity_mwnumberGeneration scheduled in the area for the peak, MW.e.g. 28147
unscheduled_steam_capacity_mwnumberSteam capacity in the area available but not scheduled, MW.e.g. 1218
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-ops-peak-area/query?node=AEP&limit=12"

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

shell
curl "https://api.dryos.ai/v1/datasets/pjm-ops-peak-area"

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 Peak load forecast been at AEP 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.

    PJM's morning Operations Summary, kept by PJM indefinitely. Reconciled against live responses on 2026-11-15.

How this stream is checked

  • Pulled straight from PJM Data Miner 2 · ops_sum_frcst_peak_area — 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, each morning; 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