LMP by Bus

Locational marginal prices for each electrical bus in ERCOT, produced by Security Constrained Economic Dispatch (SCED) roughly every five minutes.

Prices data ERCOT market

Query with the agent

Native record

event_time x bus_name

5-minute (SCED) publication cadence

Evidence

Observed market data

Published observations from the named source

Time basis

Point-in-time records

UTC · event_time

Overview

This is the finest public spatial view of observed ERCOT price variation and supports bus-level ranking, history, and basis analysis. A bus price or price spread alone does not identify a binding constraint, congestion component, or electrical relationship to another entity; those claims require direct component or attribution evidence.

Query contract

Preserve one canonical row per (event_time, bus_name) before aggregating.

Analysis rules

Group only after preserving the declared grain: event_time, bus_name.

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_lmp_by_bus/query

Schema7

Column

Type

event_timeDateTime64(6, 'UTC')

bus_nameLowCardinality(String)

lmpNullable(Float64)

dst_flagNullable(Bool)

emil_idNullable(String)

doc_idNullable(Int64)

ingested_atDateTime64(6, 'UTC')

Sample data

event_time	bus_name	lmp	dst_flag	emil_id	doc_id	ingested_at
2026-09-26 03:50:20.000000	_T2	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	_PR_E_1	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	_LD2	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	_LD1	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	_BI_138L	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	_BI_138J	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	_AZ_L_D	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	_AZ_E_1	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	_AK__AK_G1	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZPT4671	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZPT4670	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZPT4669	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZIONHILL	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZIER_LN1	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZIER_LD1	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZIER_ALL	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZEPHYR	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZEN_____345S	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZEN_____345Q	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZEN_____345O	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZEN_____345M	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZEN_____345I	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZEN_____345D	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZEN_____345C	∅	∅	∅	∅	2026-09-26 03:58:15.676463
2026-09-26 03:50:20.000000	ZEN_____345B	∅	∅	∅	∅	2026-09-26 03:58:15.676463

Coverage

Showing the last 218 days of a 3,556-day history (Jan 1, 2017 → Sep 26, 2026). This dataset holds 16.3B rows — too many to count day by day on every visit — so the calendar and the figures below cover the window from Feb 21, 2026.

100.0% complete0 gap days218 days with data

Show coverage history

Coverage: 100.0%Days with data: 218Gaps: 0

2026

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.
DAM Total Energy SoldERCOT · hourly (DAM)	This dataset reports the total energy sold in ERCOT's Day-Ahead Market, in megawatt-hours, for each delivery hour. 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.
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.