SPP · Pricing
SPP day-ahead LMP
Hourly day-ahead prices at every SPP settlement location — the trading hubs, load areas, resources, demand response and the interfaces with its neighbours — with the energy, congestion and loss components, posted for the whole of tomorrow each afternoon. The western market clears in the same run on its own energy price.
spp-dam-lmpdaily, afternoon CT · 1h rows1,612 entitiesWhat is in it
- Updates
- daily, afternoon CT · 1h rows
- Entities
- 1,612 entities — SPPNORTH_HUB, SPPSOUTH_HUB, SWPW_HUB…
- Source timezone
- US Central — every timestamp Dryos serves is UTC
- Coverage
- 14 September 2026 to now
- Rows held
- 193,440
- Primary key
- iso, market, node, interval_start_utc
- On the map
- 557 of 1,612 placed — EIA-860M plant coordinates, matched by the plant and unit in the name; hubs, interfaces and DC ties where SPP's own price map draws them
What it measures
Every value, its unit, and what the source means by it.
- Total LMP$/MWh
The hourly day-ahead price at the settlement location.
lmp_total - Congestion$/MWh
Marginal congestion component — the part that differs between locations.
lmp_congestion - Losses$/MWh
Marginal loss component.
lmp_loss - Energy$/MWh
Marginal energy component, published by SPP. The RTO's and the western market's differ each hour.
lmp_energy
Columns
Exactly what a request answers with, read from the API rather than written here.
| Column | Type | Description |
|---|---|---|
| interval_start_utcrequired | timestamp | Start of the settlement interval, UTC. Always UTC — the ISOs publish in local time with inconsistent DST handling.e.g. 2026-08-14T15:00:00Z |
| isorequired | string | Publishing ISO.e.g. ERCOT |
| marketrequired | string | Market the price cleared in: DAM (day-ahead), RTM (real-time, SCED), or RTPD for CAISO's fifteen-minute market.e.g. RTM |
| noderequired | string | Pricing node or settlement point identifier, as published by the ISO.e.g. HB_HOUSTON |
| node_type | string | Node classification. For ERCOT this is derived from the settlement point naming convention: HUB / LOAD_ZONE / DC_TIE / RESOURCE_NODE. For MISO it is the ISO's own pricing-node type: HUB (every aggregate, the eight trading hubs and the .AZ zones alike) / LOAD_ZONE / RESOURCE_NODE (a generator's node) / INTERFACE. For PJM it is the type on the row: HUB / LOAD_ZONE (a transmission zone) / INTERFACE / EHV / AGGREGATE for the aggregate streams, and RESOURCE_NODE (a generator's bus) / LOAD_BUS / EXTERNAL_BUS for the bus streams. For SPP it is read off SPP's own suffix on the Pnode behind the settlement location: HUB / LOAD_ZONE (a load area) / RESOURCE_NODE / DEMAND_RESPONSE / INTERFACE (a neighbouring operator). For CAISO it is the APnode type in CAISO's own reference: HUB (trading hubs) / LOAD_ZONE (every kind of load aggregation point) / RESOURCE_NODE / DEMAND_RESPONSE (a proxy or reliability demand resource, read off the resource id) / INTERFACE (intertie resources) / EIM_NODE (a Western EIM area's node — CAISO's EIMT, which holds the area's plants and its transfer points alike) / AGGREGATE (generation aggregation points, distributed-resource aggregations, flexible-ramp and imbalance-reserve zones). For NYISO it is LOAD_ZONE (the eleven zones) / INTERFACE (the four external proxy zones, the proxy buses of scheduled lines, and any generator NYISO files in an external zone) / DEMAND_RESPONSE (a demand-response provider) / RESOURCE_NODE (a bus in NYISO's generator reference, DER aggregations included) / LOAD_BUS (a bus NYISO prices beside the generators that no generator is registered to — transformer banks and load buses). For ISO-NE it is the location type ISO-NE publishes, a network node refined by the prefix on its name: HUB (the Internal Hub) / LOAD_ZONE (the eight) / INTERFACE (an external node) / DEMAND_RESPONSE (a demand-response aggregation zone) / HUB_NODE (one of the network nodes the Hub averages) / RESOURCE_NODE (a unit, UN., or a storage plant's asset-related demand, AR.) / LOAD_BUS (a load node, LD.).e.g. APND |
| lmp_totalrequired | number | Total locational marginal price, $/MWh.e.g. 41.83 |
| lmp_energy | number | Energy component, $/MWh.e.g. 39.12 |
| lmp_congestion | number | Congestion component, $/MWh. Signed so that total = energy + congestion + loss on every row: NYISO publishes it with the opposite sign, and it is stored negated.e.g. 2.94 |
| lmp_loss | number | Loss component, $/MWh.e.g. -0.23 |
| source_published_at_utc | timestamp | When the ISO published this interval, UTC. Lets a buyer distinguish 'we were slow' from 'the ISO was slow'. |
| collected_at_utcrequired | timestamp | When Dryos collected this row, UTC. Stamped by the platform, not the collector. Together with interval_start_utc this makes freshness auditable per row instead of only in aggregate.e.g. 2026-08-15T21:22:09Z |
Read it
Public, read-only, no key and no sign-up. Relative times stay relative, so a URL keeps working.
The newest rows
curl "https://api.dryos.ai/v1/datasets/spp-dam-lmp/query?node=SPPNORTH_HUB&limit=12"The catalogue entry — every column, its type and the source
curl "https://api.dryos.ai/v1/datasets/spp-dam-lmp"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.
claude mcp add --transport http dryos https://api.dryos.ai/mcpThen ask:
What has Total LMP been at SPPNORTH_HUB over the last 24 hours, and when did it peak?
Setup for every client is on the MCP server page.
Changes to this collector
A change in the collector is a change in the data. Anyone reading a step in a series is owed the day it moved under them.
- 2026-09-14
First collected, from SPP's marketplace portal.
The real-time price was SPP's only one here, and every other operator with a real-time price had a day-ahead one beside it. Reconciled against a live response on 2026-09-14: schema, nulls, primary key, value bands and row counts passed, every location typed, and the three components summed to the LMP on every row.
How this stream is checked
- Pulled straight from SPP Marketplace Portal · DA LMP by Settlement Location — 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, afternoon CT; the interval timestamp is the start of the interval, in UTC.
- SPP publishes on US Central prevailing time, with a UTC column on every row. Every timestamp Dryos serves is UTC.
Related streams
- SPP real-time LMPSPP
Real-time balancing market prices at every SPP settlement location — the trading hubs, load areas, resources, demand response and the interfaces with its neighbours — with the energy, congestion and loss components, every five minutes.
every 5 min · 5m rows1,612 entitiesspp-realtime-lmp - SPP real-time bus LMPSPP
Real-time balancing market prices at every SPP electrical bus — about 9,250 of them, the western market included — with the energy, congestion and loss components, every five minutes.
every 5 min · 5m rows9,252 entitiesspp-rt-lmp-bus - SPP day-ahead bus LMPSPP
Hourly day-ahead prices at every SPP electrical bus, the western market included, with the energy, congestion and loss components, posted for the whole of tomorrow each afternoon.
daily, afternoon CT · 1h rows9,252 entitiesspp-dam-lmp-bus - SPP real-time binding constraintsSPP
Every transmission constraint in SPP's real-time dispatch, five minutes at a time — binding, breached, or activated at a zero price — with the contingency it is monitored for, its limits and its shadow price.
every 5 min · 5m rows88 entitiesspp-rt-shadow-prices - SPP day-ahead binding constraintsSPP
Every transmission constraint that bound in SPP's day-ahead market, hour by hour, with the contingency it bound for and its shadow price, posted for the whole of tomorrow each afternoon.
daily, afternoon CT · 1h rows84 entitiesspp-dam-shadow-prices - MISO day-ahead LMPMISO
Hourly day-ahead ex-post prices for every MISO commercial pricing node — hubs, load zones, generator nodes and interfaces — with the energy, congestion and loss components, posted for the whole of tomorrow each afternoon.
daily, afternoon ET · 1h rows2,628 entitiesmiso-dam-lmp