ERCOT · Generation

Fuel mix

Output by fuel type across the interconnect, every five minutes. What is actually setting the price. Collected from ERCOT's dashboard feed, which retains two days — the history exists because this collector keeps running.

ercot-fuel-mixevery 5 min · 5m rows8 entities
NATURAL_GAS
34,565MW
2026-09-18 04:55 UTC
WIND
16,014MW
2026-09-18 04:55 UTC
SOLAR
0.10MW
2026-09-18 04:55 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
8 entities — NATURAL_GAS, WIND, SOLAR…
Source timezone
US Central — every timestamp Dryos serves is UTC
Coverage
28 August 2026 to now
Rows held
48,160
Primary key
iso, fuel, interval_start_utc

What it measures

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

  • OutputMW

    Generation for the fuel type over the interval. Storage runs negative while charging.

    gen_mw

Columns

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

ColumnTypeDescription
interval_start_utcrequiredtimestampStart 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
isorequiredstringPublishing ISO.e.g. ERCOT
fuelrequiredstringFuel type token: NATURAL_GAS, WIND, SOLAR, NUCLEAR, COAL_LIGNITE, HYDRO, POWER_STORAGE, OTHER. Storage runs negative while charging.e.g. NATURAL_GAS
gen_mwrequirednumberGeneration from this fuel over the 5-minute interval, MW.e.g. 44687.6
source_published_at_utcrequiredtimestampWhen 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_utcrequiredtimestampWhen Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-08-29T14:18: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/ercot-fuel-mix/query?node=NATURAL_GAS&limit=12"

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

shell
curl "https://api.dryos.ai/v1/datasets/ercot-fuel-mix"

Hourly averages for the last day

shell
curl "https://api.dryos.ai/v1/datasets/ercot-fuel-mix/query?node=NATURAL_GAS&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 Output been at NATURAL_GAS 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 ERCOT Dashboards · fuel-mix.json — 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.
  • ERCOT settles and publishes on US Central time. Every timestamp Dryos serves is UTC.

Related streams