MISO · Grid

MISO scheduled interchange

Scheduled interchange with each neighbouring balancing authority every five minutes — PJM, SPP, TVA, AECI, Ontario, Manitoba and the rest — plus the MISO total. Negative is a net import.

miso-scheduled-interchangeevery 5 min · 5m rows10 entities
PJM
-950MW
2026-09-18 04:50 UTC
SWPP
-380MW
2026-09-18 04:50 UTC
TVA
48.0MW
2026-09-18 04:50 UTC
Read from the Dryos API and cached for an hour; the stream itself updates every 5 min.

What is in it

Updates
every 5 min · 5m rows
Entities
10 entities — PJM, SWPP, TVA…
Source timezone
Eastern Standard Time all year, never EDT — every timestamp Dryos serves is UTC
Coverage
5 September 2026 to now
Rows held
37,220
Primary key
iso, counterparty, interval_start_utc

What it measures

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

  • ScheduledMW

    Net scheduled interchange with the counterparty; negative is an import.

    nsi_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
counterpartyrequiredstringBalancing authority the schedule is with, as MISO labels it (PJM, SWPP, TVA, AECI, ...). MISO is the total across all of them.e.g. PJM
nsi_mwrequirednumberNet scheduled interchange, MW. Negative is a net import into MISO.e.g. -2080
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-scheduled-interchange/query?node=PJM&limit=12"

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

shell
curl "https://api.dryos.ai/v1/datasets/miso-scheduled-interchange"

Hourly averages for the last day

shell
curl "https://api.dryos.ai/v1/datasets/miso-scheduled-interchange/query?node=PJM&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 Scheduled been at PJM 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 · Interchange/GetNsi/FiveMinute — 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 5 min; 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