PJM · Generation

PJM wind and solar forecast

PJM's hourly wind forecast for the next 46 hours, re-issued every ten minutes, and its hourly solar forecast for the next four days — utility-scale and behind-the-meter separately — re-issued hourly. Every issue is a vintage.

pjm-wind-solar-forecastevery 10 min, two days ahead · 1h rows3 entities
WIND
2,846MWh
2026-09-20 03:00 UTC
SOLAR
0.00MWh
2026-09-20 03:00 UTC
SOLAR_BTM
0.00MWh
2026-09-20 03:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates every 10 min, two days ahead.

What is in it

Updates
every 10 min, two days ahead · 1h rows
Entities
3 entities — WIND, SOLAR, SOLAR_BTM…
Source timezone
US Eastern — every timestamp Dryos serves is UTC
Coverage
10 September 2026 to now
Rows held
62,904
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 hour, 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 hour, as of this vintage. PJM publishes it as MWh over the hour, which is the same number as average MW.e.g. 1765.97
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/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"

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

    First collected, from PJM Data Miner 2.

    Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

How this stream is checked

  • Pulled straight from PJM Data Miner 2 · hourly 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, two days 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