NYISO · Load

NYISO load forecast

NYISO's hourly load forecast six days ahead for each of its eleven zones and the state, issued each morning — every issue kept.

nyiso-load-forecast-6daydaily, morning ET · 1h rows12 entities
N.Y.C.
4,671MW
2026-09-24 03:00 UTC
LONGIL
1,800MW
2026-09-24 03:00 UTC
NYISO
14,300MW
2026-09-24 03:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates daily, morning ET.

What is in it

Updates
daily, morning ET · 1h rows
Entities
12 entities — N.Y.C., LONGIL, NYISO…
Source timezone
US Eastern — every timestamp Dryos serves is UTC
Coverage
14 September 2026 to now
Rows held
12,096
Primary key
iso, zone, interval_start_utc, source_published_at_utc

What it measures

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

  • Load forecastMW

    NYISO's forecast of the zone's load for the hour.

    load_forecast_mw

Columns

Exactly what a request answers with, read from the API rather than written here.

ColumnTypeDescription
interval_start_utcrequiredtimestampStart of the forecast hour, UTC.e.g. 2026-09-15T04:00:00Z
isorequiredstringPublishing ISO.e.g. NYISO
zonerequiredstringLoad zone as NYISO names it: CAPITL, CENTRL, DUNWOD, GENESE, HUD VL, LONGIL, MHK VL, MILLWD, N.Y.C., NORTH, WEST — and, in the forecast, NYISO, their sum.e.g. N.Y.C.
load_forecast_mwnumberNYISO's forecast of the zone's load for the hour, MW.e.g. 6239
source_published_at_utcrequiredtimestampThe issue this forecast is from — the file's Last-Modified, UTC; a file is written once. Every issue is kept, so an hour carries a row per issue.e.g. 2026-09-14T11:30:06Z
collected_at_utcrequiredtimestampWhen Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-09-14T22:35:00Z

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/nyiso-load-forecast-6day/query?node=N.Y.C.&limit=12"

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

shell
curl "https://api.dryos.ai/v1/datasets/nyiso-load-forecast-6day"

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 Load forecast been at N.Y.C. 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-14

    First collected, from NYISO's MIS.

    Every other operator's load forecast was here and NYISO's was not. Reconciled against the live files on 2026-09-14: every check passed.

How this stream is checked

  • Pulled straight from NYISO MIS · ISO Load Forecast — 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, morning ET; the interval timestamp is the start of the interval, in UTC.
  • NYISO stamps its files in Eastern prevailing time with no zone column. Every timestamp Dryos serves is UTC.

Related streams