ERCOT · Ancillary

Ancillary service plan

How much of each service ERCOT plans to procure, per hour, seven days out — republished daily with every revision kept. Collected from ERCOT MIS (NP4-33).

ercot-dam-as-plandaily, 7-day plan · 1h rows5 entities
REGUP
269MW
2026-09-24 04:00 UTC
RRS
2,426MW
2026-09-24 04:00 UTC
ECRS
1,266MW
2026-09-24 04:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates daily, 7-day plan.

What is in it

Updates
daily, 7-day plan · 1h rows
Entities
5 entities — REGUP, RRS, ECRS…
Source timezone
US Central — every timestamp Dryos serves is UTC
Coverage
27 August 2026 to now
Rows held
18,480
Primary key
iso, as_type, interval_start_utc, source_published_at_utc

What it measures

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

  • Planned quantityMW

    Capacity ERCOT plans to procure for the product and hour.

    quantity_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
as_typerequiredstringAncillary service product, as ERCOT names it (REGUP, REGDN, RRS, ECRS, NSPIN, ...). The product list has grown over time and is passed through verbatim rather than mapped.e.g. ECRS
quantity_mwrequirednumberCapacity ERCOT plans to procure for this product and hour, MW.e.g. 1316
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-dam-as-plan/query?node=REGUP&limit=12"

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

shell
curl "https://api.dryos.ai/v1/datasets/ercot-dam-as-plan"

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 Planned quantity been at REGUP 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 MIS · NP4-33-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 daily, 7-day plan; 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