ERCOT · Pricing

DAM settlement point prices

Name: DAM settlement point prices
Creator: Dryos

Day-ahead hourly settlement point prices for every settlement point, posted once after the DAM run. Collected from ERCOT MIS (NP4-190).

ercot-dam-sppdaily, ~12:35 CT · 1h rows1,118 entities

HB_NORTH

$32.00

2026-09-19 04:00 UTC

HB_HOUSTON

$32.09

2026-09-19 04:00 UTC

LZ_WEST

$33.42

2026-09-19 04:00 UTC

Read from the Dryos API and cached for an hour; the stream itself updates daily, ~12:35 CT.

What is in it

Updates: daily, ~12:35 CT · 1h rows
Entities: 1,118 entities — HB_NORTH, HB_HOUSTON, LZ_WEST…
Source: ERCOT MIS · NP4-190-CD
Source timezone: US Central — every timestamp Dryos serves is UTC
Coverage: 28 August 2026 to now
Rows held: 592,224
Primary key: iso, market, node, interval_start_utc
On the map: 698 of 1,118 placed — EIA-860M plant coordinates, through ERCOT's unit mapping

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
marketrequired	string	Market the price settled in: RTM15 (real-time 15-minute) or DAM.e.g. RTM15
noderequired	string	Settlement point identifier, as published by ERCOT.e.g. HB_HOUSTON
node_typerequired	string	ERCOT's settlement point type code where the report carries one (RN, HU, LZ, LZEW, ...); derived from the naming convention (HUB / LOAD_ZONE / DC_TIE / RESOURCE_NODE) where it does not.e.g. HU
spprequired	number	Settlement point price, $/MWh.e.g. 41.83
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-dam-spp/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-dam-spp"

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 Cleared price been at HB_NORTH 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-190-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, ~12:35 CT; 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.