PJM · Load
PJM metered hourly load
PJM's settlement-quality hourly load for 30 load areas and the RTO, from the distribution companies' own meters, filled in company by company over the days after — the RTO row is a running total until every company has reported.
pjm-load-meteredevery 3 h, a few days behind · 1h rows31 entitiesWhat is in it
- Updates
- every 3 h, a few days behind · 1h rows
- Entities
- 31 entities — AECO, DOM, PS…
- Source timezone
- US Eastern — every timestamp Dryos serves is UTC
- Coverage
- 2 September 2026 to now
- Rows held
- 10,110
- Primary key
- iso, load_area, interval_start_utc
What it measures
Every value, its unit, and what the source means by it.
- LoadMW
Metered energy for load over the hour — its average MW.
demand_mw
Columns
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 PJM's own UTC column.e.g. 2026-09-09T12:30:00Z |
| isorequired | string | Publishing ISO.e.g. PJM |
| load_arearequired | string | Load area as PJM names it — a distribution company's territory (`AECO`, `AEPAPT`) — or RTO, the total of those reported so far.e.g. AECO |
| zonerequired | string | The transmission zone the area sits in.e.g. AE |
| mkt_regionrequired | string | PJM's market region for the area (MIDATL, WEST, SOUTH; RTO for the total).e.g. MIDATL |
| demand_mwrequired | number | Metered net energy for load over the hour, MWh — the hour's average MW.e.g. 905.296 |
| is_verifiedrequired | boolean | PJM's flag that the distribution company's meter data is verified.e.g. true |
| source_published_at_utc | timestamp | When PJM 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-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
curl "https://api.dryos.ai/v1/datasets/pjm-load-metered/query?node=AECO&limit=12"The catalogue entry — every column, its type and the source
curl "https://api.dryos.ai/v1/datasets/pjm-load-metered"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.
claude mcp add --transport http dryos https://api.dryos.ai/mcpThen ask:
What has Load been at AECO 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.
- 2026-09-13
First collected, from PJM Data Miner 2.
PJM's hourly load, kept by PJM indefinitely. Reconciled against live responses on 2026-09-13.
How this stream is checked
- Pulled straight from PJM Data Miner 2 · hrl_load_metered — 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 every 3 h, a few days behind; 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
- PJM load by areaPJM
Real-time load every five minutes in each of PJM's 21 transmission zones, its three regions and the RTO total — telemetry, the number on PJM's own dashboard, not the metered load that settles.
every 5 min · 5m rows25 entitiespjm-system-load - PJM preliminary hourly loadPJM
PJM's preliminary hourly load for ten areas, integrated from telemetry the day after — between the five-minute reading and the metered settlement load.
every 3 h, a day behind · 1h rows10 entitiespjm-load-prelim - PJM five-minute load forecastPJM
PJM's load forecast for the next two hours in five-minute steps, for the zones, the three regions and the RTO, re-issued every five minutes and kept as vintages — so a forecast can be scored against what it said at the time.
every 5 min, two hours ahead · 5m rows25 entitiespjm-load-forecast-5min - PJM seven-day load forecastPJM
PJM's hourly load forecast for the next seven days, for the zones, the three regions and the RTO.
twice hourly, a week ahead · 1h rows25 entitiespjm-load-forecast-7day - PJM real-time LMPPJM
Unverified five-minute prices at PJM's 12 trading hubs, 22 transmission zones, 7 interfaces and every other aggregate pricing node, with the congestion and loss components, about four minutes after the interval starts.
every 5 min · 5m rows482 entitiespjm-realtime-lmp - PJM real-time hourly LMPPJM
PJM's own hourly integration of its unverified real-time prices at the 12 trading hubs, 22 transmission zones, 7 interfaces and every other aggregate, with the congestion and loss components, posted for the previous hour.
hourly, for the hour before · 1h rows482 entitiespjm-realtime-lmp-hourly