ERCOT · Generation

Wind: actual and forecast

Hourly averaged actual wind generation and ERCOT's own forecasts, system-wide and by load zone, refreshed hourly. Collected from ERCOT MIS (NP4-732).

ercot-wind-hourlyhourly, rolling week · 1h rows4 entities

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. Always UTC — ERCOT publishes wall-clock Central with a repeated-hour flag, which is resolved on ingest.e.g. 2026-08-29T14:15:00Z
isorequired	string	Publishing ISO.e.g. ERCOT
fuelrequired	string	WIND or SOLAR.e.g. WIND
regionrequired	string	SYSTEM, or the report's region: load zones (LZ_WEST, ...) for the zonal wind report, geographic regions (PANHANDLE, CENTER_WEST, ...) for the geographic ones.e.g. SYSTEM
gen_mw	number	Hourly averaged actual generation, MW.e.g. 3710.55
cop_hsl_mw	number	COP high sustained limit for online resources, MW — what operators told ERCOT they could produce.e.g. 2360.3
forecast_stf_mw	number	ERCOT's short-term forecast (STWPF for wind, STPPF for solar), MW.e.g. 3812.6
forecast_pp_mw	number	ERCOT's production potential forecast (WGRPP for wind, PVGRPP for solar), MW.e.g. 3106.1
hsl_mw	number	Actual system-wide HSL, MW.e.g. 10994.2
source_published_at_utcrequired	timestamp	When ERCOT posted the document this row came from, UTC. For reports republished on a rolling window this is the vintage: the same interval appears once per publication, and the newest is the current view.e.g. 2026-08-29T14:17:01Z
collected_at_utcrequired	timestamp	When Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-08-29T14:18:02Z

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/ercot-wind-hourly/query?node=LZ_WEST&limit=12"

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

shell

curl "https://api.dryos.ai/v1/datasets/ercot-wind-hourly"

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

Setup for every client is on the MCP server page.

Pulled straight from ERCOT MIS · NP4-732-CD — 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, rolling week; the interval timestamp is the start of the interval, in UTC.
ERCOT settles and publishes on US Central time. Every timestamp Dryos serves is UTC.