MISO · Generation

MISO wind and solar

Hourly wind and solar output against MISO's own forecast for today and tomorrow, republished every hour and kept as vintages — so a forecast can be scored against what it said at the time, not only what it says now.

miso-wind-solarhourly, two days ahead · 1h rows2 entities
WIND
12,588MW
2026-09-19 04:00 UTC
SOLAR
0.00MW
2026-09-19 04:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates hourly, two days ahead.

What is in it

Updates
hourly, two days ahead · 1h rows
Entities
2 entities — WIND, SOLAR…
Source timezone
Eastern Standard Time all year, never EDT — every timestamp Dryos serves is UTC
Coverage
6 September 2026 to now
Rows held
25,152
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.

  • ActualMW

    Metered output for the hour. Empty for hours that have not happened; slightly negative for solar at night, which is the plants' own load.

    actual_mw
  • ForecastMW

    MISO'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. MISO publishes wall-clock Eastern Standard Time year-round with no offset and labels intervals by their end; both are resolved on ingest.e.g. 2026-09-06T14:05:00Z
isorequiredstringPublishing ISO.e.g. MISO
resourcerequiredstringWIND or SOLAR.e.g. WIND
forecast_mwrequirednumberMISO's forecast for the hour, MW, as of this vintage.e.g. 7994
actual_mwnumberMetered output for the hour, MW. Solar runs slightly negative at night, which is the plants' own station load.e.g. 5052.23
source_published_at_utctimestampMISO's own 'as of' stamp on the snapshot this row came from — the display's RefId — in UTC. The vintage of the reading, not when Dryos fetched it.e.g. 2026-09-06T14:20:00Z
collected_at_utcrequiredtimestampWhen Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-09-06T14:24:02Z

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/miso-wind-solar/query?node=WIND&limit=12"

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

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

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 Actual been at WIND over the last 24 hours, and when did it peak?

Setup for every client is on the MCP server page.

How this stream is checked

  • Pulled straight from MISO Public API · WindSolar — 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 hourly, two days ahead; the interval timestamp is the start of the interval, in UTC.
  • MISO runs on Eastern Standard Time all year and never observes daylight saving. Every timestamp Dryos serves is UTC.

Related streams