SPP · Generation

SPP wind and solar curtailments

Name: SPP wind and solar curtailments
Creator: Dryos

Wind and solar curtailed every five minutes in SPP's RTO and RTO West — by redispatch, manually by the operator, and for energy — a day behind.

spp-curtailmentsdaily, a day behind · 5m rows2 entities

SPP

0.00MW

2026-09-17 04:55 UTC

SWPW

0.00MW

2026-09-17 04:55 UTC

Read from the Dryos API and cached for an hour; the stream itself updates daily, a day behind.

What is in it

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

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

Column	Type	Description
interval_start_utcrequired	timestamp	Start of the interval, UTC. SPP stamps the interval's end.e.g. 2026-09-13T05:00:00Z
isorequired	string	Publishing ISO.e.g. SPP
zonerequired	string	Balancing authority: SPP for the RTO, SWPW for RTO West.e.g. SPP
wind_redispatch_mw	number	Wind curtailed by redispatch in the interval, MW.e.g. 0.0
wind_manual_mw	number	Wind curtailed manually by the operator, MW.e.g. 0.0
wind_for_energy_mw	number	Wind curtailed for energy (SPP's CurtailedForEnergy), MW.e.g. 0.0
solar_redispatch_mw	number	Solar curtailed by redispatch in the interval, MW.e.g. 0.0
solar_manual_mw	number	Solar curtailed manually by the operator, MW.e.g. 0.0
solar_for_energy_mw	number	Solar curtailed for energy (SPP's CurtailedForEnergy), MW.e.g. 0.0
source_published_at_utc	timestamp	When SPP published the row.
collected_at_utcrequired	timestamp	When Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-09-14T22:20:00Z

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/spp-curtailments/query?node=SPP&limit=12"

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

shell

curl "https://api.dryos.ai/v1/datasets/spp-curtailments"

Hourly averages for the last day

shell

curl "https://api.dryos.ai/v1/datasets/spp-curtailments/query?node=SPP&start=-24h&interval=1h&agg=avg"

Full parameters — bucketing, aggregation, filters and search — are on the API reference.

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 Wind · redispatch been at SPP over the last 24 hours, and when did it peak?

Setup for every client is on the MCP server page.

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.

2026-09-17
Intervals SPP files under no balancing authority are dropped rather than stored as zero curtailment. Ten of them are missing from 2026-09-15, 21:10 to 21:55 Central.
SPP writes the row anyway when an authority reports nothing for an interval — its two stamps and every other cell empty, the authority included. The authority is in the primary key, so the row could not be stored, and stored it would have claimed no curtailment in those intervals, which SPP did not say. The six value columns came back 0.88% null against a zero budget and the collector refused every batch for three days.
2026-09-14
First collected, from SPP's marketplace portal.
Curtailment is the story of SPP's wind, and it was not here. Reconciled against the live files on 2026-09-14: schema, nulls, primary key, value bands and row counts passed.

Pulled straight from SPP Marketplace Portal · VER Curtailments — 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, a day behind; the interval timestamp is the start of the interval, in UTC.
SPP publishes on US Central prevailing time, with a UTC column on every row. Every timestamp Dryos serves is UTC.