DAM Total Energy Sold

This dataset reports the total energy sold in ERCOT's Day-Ahead Market, in megawatt-hours, for each delivery hour.

Prices data ERCOT market

Query with the agent

Native record

event_time

hourly (DAM) publication cadence

Evidence

Cleared day-ahead market

A market outcome, not a physical observation

Time basis

Point-in-time records

UTC · event_time

Overview

It represents the system-wide quantity of energy that cleared the day-ahead auction, where buyers and sellers commit to next-day positions before real-time operations. The hourly shape across a day shows how much of expected Texas demand is locked in financially a day ahead, and tracking it over time reveals shifts in day-ahead market participation and how forward commitments line up against eventual real-time conditions. The figures come from ERCOT report NP4-193-CD.

Query contract

Preserve one canonical row per (event_time) before aggregating.

Analysis rules

Group only after preserving the declared grain: event_time.

Access

Query from your own tools

Use the guarded HTTP endpoint directly, or connect an MCP client and load the dataset contract with describe_data before calling query_data.

ERCOT MCP API reference

HTTP endpoint

POST /api/v1/datasets/ercot_dam_total_energy_sold/query

Schema6

Column

Type

event_timeDateTime64(6, 'UTC')

total_energy_sold_mwhNullable(Float64)

dst_flagNullable(Bool)

emil_idNullable(String)

doc_idNullable(Int64)

ingested_atDateTime64(6, 'UTC')

Sample data

event_time	total_energy_sold_mwh	dst_flag	emil_id	doc_id	ingested_at
2026-09-26 05:00:00.000000	39979.9	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-26 04:00:00.000000	43352.9	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-26 03:00:00.000000	45645.8	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-26 02:00:00.000000	47018.2	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-26 01:00:00.000000	49710.1	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-26 00:00:00.000000	50571.6	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 23:00:00.000000	50070.6	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 22:00:00.000000	49272.5	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 21:00:00.000000	48513.8	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 20:00:00.000000	48012.7	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 19:00:00.000000	46558.6	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 18:00:00.000000	44328.4	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 17:00:00.000000	42161.3	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 16:00:00.000000	42207.2	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 15:00:00.000000	41255.5	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 14:00:00.000000	38989.1	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 13:00:00.000000	40338.6	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 12:00:00.000000	40240.3	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 11:00:00.000000	37723.4	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 10:00:00.000000	37177.3	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 09:00:00.000000	37411.2	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 08:00:00.000000	37822.4	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 07:00:00.000000	37793.3	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 06:00:00.000000	39054.3	false	∅	∅	2026-09-25 05:31:19.249118
2026-09-25 05:00:00.000000	41266.7	false	∅	∅	2026-09-25 05:31:19.249118

Coverage

100.0% complete0 gap days3,555 days with data

Show coverage history

Coverage: 100.0%Days with data: 3,555Gaps: 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

gaplessmore

Related prices data

Related prices data
Dataset	Description
DAM Settlement Point PricesERCOT · hourly (DAM)	Hourly settlement point prices cleared in the ERCOT Day-Ahead Market, covering every settlement point in Texas (load zones, hubs, and resource nodes). These are the prices at which energy is bought and sold a day in advance of delivery, set the afternoon before each operating day. They are the day-ahead counterpart to real-time locational prices, and the gap between the two reflects how the market expected conditions to differ from how they actually unfolded. Traders use them to position and hedge, generators and loads use them to plan commitments, and researchers use them to study how congestion and scarcity show up across the grid.
DAM System LambdaERCOT · hourly (DAM)	ERCOT's hourly day-ahead system lambda, the system-wide marginal energy component in the cleared Day-Ahead Market. For the same delivery hour and settlement point, day-ahead SPP minus DAM system lambda is the point's cleared day-ahead congestion component. Paired with SCED system lambda and real-time LMP, it supports day-ahead-versus-real-time congestion basis by point. It does not identify a binding constraint's effect on a point without direct attribution evidence.
ERCOT Day-Ahead PricesERCOT · hourly (DAM)	ERCOT day-ahead locational marginal prices, one row per interval and location. 66.7M rows, 2017-01 to the next delivery day. Carries price_usd_mwh plus energy_usd_mwh and congestion_usd_mwh, with energy taken from ERCOT's DAM system lambda. No loss component: ERCOT does not publish one. Locations are node, zone, hub, interface; location_id joins atg.ercot_locations for the readable name, and kind is carried inline so a hub-only or zone-only question needs no join at all. Every market's day-ahead price table in this catalog has these same column names, so a cross-market price comparison is a UNION rather than a per-ISO rewrite. Revisions are already collapsed — read it plainly.
ERCOT Real-Time PricesERCOT · 5-minute (SCED)	ERCOT real-time locational marginal prices, one row per interval and location. 979.1M rows, 2014-05 to now. Carries price_usd_mwh plus energy_usd_mwh and congestion_usd_mwh. ERCOT publishes no marginal-loss component and this table has no loss column: energy is ERCOT's own SCED system lambda and congestion is price minus lambda, an exact identity rather than an estimate. Locations are node (resource nodes), zone (load zones), hub, interface (the four DC ties); location_id joins atg.ercot_locations for the readable name, and kind is carried inline so a hub-only or zone-only question needs no join at all. Every market's real-time price table in this catalog has these same column names, so a cross-market price comparison is a UNION rather than a per-ISO rewrite. Revisions are already collapsed — read it plainly.