LMP by Settlement Point

Locational marginal prices from ERCOT's real-time market, published every five minutes by Security Constrained Economic Dispatch (SCED) for resource nodes, load zones, and trading hubs.

Prices data ERCOT market

Query with the agent Open on map

Native record

settlement point x SCED interval

5-minute (SCED) publication cadence

Evidence

Observed market data

Published observations from the named source

In Ask the Grid

Price nodes on the ERCOT map

Values for the live grid surface

Overview

This table supports observed price levels, rankings, volatility, and basis between settlement points. Total-LMP differences do not identify a congestion component, binding facility, shift factor, or physical topology relationship, so they cannot establish why two points separated without matched attribution data. The official source is ERCOT report NP6-788-CD (Settlement Point Prices at Resource Nodes, Hubs and Load Zones).

Query contract

Read ercot.lmp_by_settlement_point with FINAL before returning or aggregating settlement-point intervals; repeated ingestion revisions otherwise multiply observations.

Analysis rules

For a complete multi-interval bucket, resolve the latest closed bucket from distinct event timestamps, then rank or aggregate settlement points inside that exact bucket.
When ranking settlement points over a bucket containing multiple SCED observations, aggregate LMP per settlement point first; use average LMP unless the user explicitly asks for an interval maximum or minimum.

Related analysis

price history beyond the current snapshot and energy/congestion decomposition without a manual system-lambda join · Use ercot_prices_rt, not this table, for anything beyond the current price — it pre-joins ercot_sced_system_lambda and collapses this table's rolling-poll duplicates, at the cost of trailing live SCED by roughly one refresh cycle (5-15 minutes).
real-time congestion component and point price decomposition · same five-minute SCED interval

Interpretation

LMP separation is an effect, not proof of a specific binding constraint.
Settlement-point labels are identifiers. Do not infer resource technology, storage status, location, or ownership from a label or suffix.

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

Schema7

Column

Type

event_timeDateTime64(6, 'UTC')

settlement_pointLowCardinality(String)

lmpNullable(Float64)

dst_flagNullable(Bool)

emil_idNullable(String)

doc_idNullable(Int64)

ingested_atDateTime64(6, 'UTC')

Sample data

event_time	settlement_point	lmp	dst_flag	emil_id	doc_id	ingested_at
2026-09-26 05:35:17.000000	ZIER_SLR_ALL	34.59	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	Z5_DGR1_RN	30.41	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	Z0_DGR2_RN	30.4	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	Z0_DGR1_RN	30.4	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	YNG_WND_ALL	14.04	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	YCAT_WND_RN	24.72	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	YAPN_SLR_RN	26.82	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	X443ESRN	30.57	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	X1_DGR_RN	30.51	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	W_PECO_UNIT1	51.82	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	W_HRL_ESR_RN	29.85	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WZRD_ESS_RN	27.51	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WR_RN	27.92	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WRSBES_BESS1	51.84	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WOV_BESS_RN	53.59	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WOODWRD2_RN	50.11	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WOODWRD1_RN	50.11	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WND_WHITNEY	20.68	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WNDTS2_UNIT1	26.43	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WL_RANCH_RN	44.14	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WLTC_ESR_RN	29.7	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WIR_WIRTZ_G2	30.56	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WIR_WIRTZ_G1	30.56	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WIPOPA_3_4	28.85	false	∅	∅	2026-09-26 05:40:18.029772
2026-09-26 05:35:17.000000	WIPOPA_1_2	28.85	false	∅	∅	2026-09-26 05:40:18.029772

Coverage

Showing the last 3,727 days of a 4,532-day history (May 1, 2014 → Sep 26, 2026). This dataset holds 1.22B rows — too many to count day by day on every visit — so the calendar and the figures below cover the window from Jul 14, 2016.

100.0% complete0 gap days3,727 days with data

Show coverage history

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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

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.