PJM · Grid

PJM operations summary, actuals

Yesterday hour by hour for PJM's zones and the Mid-Atlantic, from the morning Operations Summary: the load each area saw and its dispatch rate.

pjm-ops-actualsdaily, the day before · 1h rows13 entities
AEP
15,480MW
2026-11-22 04:00 UTC
Dom
14,584MW
2026-11-22 04:00 UTC
ComEd
9,154MW
2026-11-22 04:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates daily, the day before.

What is in it

Updates
daily, the day before · 1h rows
Entities
13 entities — AEP, Dom, ComEd…
Source timezone
US Eastern — every timestamp Dryos serves is UTC
Coverage
13 November 2026 to now
Rows held
2,379
Primary key
iso, zone, interval_start_utc

What it measures

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

  • LoadMW

    Load the area saw over the hour.

    actual_load_mw
  • Dispatch rate$/MWh

    PJM's dispatch rate in the area for the hour.

    dispatch_rate

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 transmission zone (`AEP`, `ComEd`, `Dom`, ...), `MidAtl`, or one of the three areas that carry only a dispatch rate (`MidAtl - East`, `MidAtl - West`, `OVEC`). There is no RTO row.e.g. AEP
actual_load_mwnumberThe load PJM saw in the area over the hour, MW.e.g. 16337.54
dispatch_ratenumberPJM's dispatch rate in the area for the hour, $/MWh.e.g. 25.79
source_published_at_utcrequiredtimestampWhen PJM wrote the refresh this row came from, UTC (`generated_at_ept`). A later refresh the same morning restates the day.e.g. 2026-11-15T13:03:19Z
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-actuals/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-actuals"

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 Load 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_prev_period — 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, the day before; 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