PJM · Generation

PJM five-minute wind and solar forecast

PJM's wind and solar forecasts for the next six hours in five-minute steps — solar utility-scale and behind-the-meter separately — re-issued every ten minutes. Every issue is a vintage. PJM keeps them thirty days.

pjm-wind-solar-forecast-5minevery 10 min, six hours ahead · 5m rows3 entities
WIND
1,686MWh
2026-09-18 10:50 UTC
SOLAR
18.3MWh
2026-09-18 10:55 UTC
SOLAR_BTM
16.7MWh
2026-09-18 10:55 UTC
Read from the Dryos API and cached for an hour; the stream itself updates every 10 min, six hours ahead.

What is in it

Updates
every 10 min, six hours ahead · 5m rows
Entities
3 entities — WIND, SOLAR, SOLAR_BTM…
Source timezone
US Eastern — every timestamp Dryos serves is UTC
Coverage
13 September 2026 to now
Rows held
137,168
Primary key
iso, resource, interval_start_utc, source_published_at_utc

What it measures

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

  • ForecastMW

    PJM's forecast for the five-minute interval, 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
resourcerequiredstringWIND, SOLAR (metered utility-scale) or SOLAR_BTM (behind-the-meter, which PJM forecasts separately because it shows up as reduced load).e.g. WIND
forecast_mwrequirednumberPJM's forecast for the five-minute interval, as of this vintage, average MW. PJM's column says MWh; read that way the values would be twelve times the fleet, so they are power, not energy.e.g. 3756.14
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-wind-solar-forecast-5min/query?node=WIND&limit=12"

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

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

Hourly averages for the last day

shell
curl "https://api.dryos.ai/v1/datasets/pjm-wind-solar-forecast-5min/query?node=WIND&start=-24h&interval=1h&agg=avg"

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 WIND 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-09-13

    First collected, from PJM Data Miner 2.

    Taken first of PJM's uncollected feeds because PJM keeps it thirty days. Reconciled against live responses on 2026-09-13.

How this stream is checked

  • Pulled straight from PJM Data Miner 2 · five-minute wind and solar power forecasts — 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 10 min, six hours ahead; 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