ERCOT · Pricing

Indicative LMPs (RTD look-ahead)

Where real-time prices are about to go: RTD's forward intervals for every settlement point, republished each run with every vintage kept. Collected from ERCOT MIS (NP6-970).

ercot-indicative-lmpevery 5 min, look-ahead · 5m rows1,118 entities
HB_NORTH
$26.57
2026-09-18 06:50 UTC
HB_HOUSTON
$26.57
2026-09-18 06:50 UTC
LZ_WEST
$26.57
2026-09-18 06:50 UTC
Read from the Dryos API and cached for an hour; the stream itself updates every 5 min, look-ahead.

What is in it

Updates
every 5 min, look-ahead · 5m rows
Entities
1,118 entities — HB_NORTH, HB_HOUSTON, LZ_WEST…
Source timezone
US Central — every timestamp Dryos serves is UTC
Coverage
29 August 2026 to now
Rows held
136,005,480
Primary key
iso, node, interval_start_utc, rtd_timestamp_utc
On the map
698 of 1,118 placed — EIA-860M plant coordinates, through ERCOT's unit mapping

What it measures

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

  • Indicative LMP$/MWh

    Forecast price for the forward interval.

    lmp

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
rtd_timestamp_utcrequiredtimestampThe RTD run this forecast came from, UTC — the vintage. Carried from the data itself, not the listing.e.g. 2026-08-29T14:15:03Z
interval_idrequiredintegerPosition of this interval in the run's look-ahead (1 = next).e.g. 1
noderequiredstringSettlement point identifier, as published by ERCOT.e.g. HB_HOUSTON
node_typerequiredstringERCOT's settlement point type code (RN, HU, LZ, ...).e.g. RN
lmprequirednumberIndicative locational marginal price, $/MWh.e.g. 14.87
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-indicative-lmp/query?node=HB_NORTH&limit=12"

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

shell
curl "https://api.dryos.ai/v1/datasets/ercot-indicative-lmp"

Hourly averages for the last day

shell
curl "https://api.dryos.ai/v1/datasets/ercot-indicative-lmp/query?node=HB_NORTH&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 Indicative LMP been at HB_NORTH 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 · NP6-970-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 every 5 min, look-ahead; 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