PJM · Generation

PJM wind and solar by area, hourly

PJM Settlements' hourly wind and solar generation for each region and the RTO, kept indefinitely and revised for ninety days — the settled record behind the real-time readings.

pjm-wind-solar-hourlydaily, revised for 90 days · 1h rows6 entities
RTO
0.00MW
2026-11-22 16:00 UTC
WEST
0.00MW
2026-11-22 16:00 UTC
MIDATL
0.00MW
2026-11-22 16:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates daily, revised for 90 days.

What is in it

Updates
daily, revised for 90 days · 1h rows
Entities
6 entities — RTO, WEST, MIDATL…
Source timezone
US Eastern — every timestamp Dryos serves is UTC
Coverage
18 August 2026 to now
Rows held
13,680
Primary key
iso, zone, interval_start_utc

What it measures

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

  • WindMW

    Settled wind generation over the hour.

    wind_mw
  • SolarMW

    Settled utility-scale solar generation over the hour.

    solar_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: `MIDATL`, `WEST`, `SOUTH`, `OTHER` (external units and units PJM cannot place), `RFC` (MIDATL plus WEST) and `RTO` (the regions less OTHER).e.g. RTO
wind_mwnumberWind generation over the hour, MW, from PJM Settlements.e.g. 3908.35
solar_mwnumberSolar generation over the hour, MW, from PJM Settlements. Utility scale; behind-the-meter solar is not in it.e.g. 11066.04
source_published_at_utctimestampWhen PJM published the row, UTC.
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-wind-solar-hourly/query?node=RTO&limit=12"

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

shell
curl "https://api.dryos.ai/v1/datasets/pjm-wind-solar-hourly"

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 Wind 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 · wind_gen, solar_gen — 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, revised for 90 days; 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