MISO · Pricing
MISO real-time LMP
Preliminary ex-post prices for every MISO commercial pricing node — hubs, load zones, generator nodes and interfaces — with the congestion and loss components, every five minutes. Collected from MISO's public real-time feed and checked against the Data Exchange copy of the same day.
miso-realtime-lmpevery 5 min · 5m rows2,628 entitiesWhat is in it
- Updates
- every 5 min · 5m rows
- Entities
- 2,628 entities — INDIANA.HUB, ILLINOIS.HUB, MICHIGAN.HUB…
- Source timezone
- Eastern Standard Time all year, never EDT — every timestamp Dryos serves is UTC
- Coverage
- 6 September 2026 to now
- Rows held
- 8,856,360
- Primary key
- iso, market, node, interval_start_utc
- On the map
- 731 of 2,628 placed — EIA-860M plant coordinates, matched by the name in the node; hubs and 260 generators where MISO's own map draws them
What it measures
Every value, its unit, and what the source means by it.
- Total LMP$/MWh
The five-minute preliminary ex-post price at the node.
lmp_total - Congestion$/MWh
Marginal congestion component — the part that differs between nodes.
lmp_congestion - Losses$/MWh
Marginal loss component.
lmp_loss - Energy$/MWh
System marginal energy cost — the same number at every node in an interval. Derived as LMP minus congestion minus losses, MISO's own identity.
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/miso-realtime-lmp/query?node=INDIANA.HUB&limit=12"The catalogue entry — every column, its type and the source
curl "https://api.dryos.ai/v1/datasets/miso-realtime-lmp"Hourly averages for the last day
curl "https://api.dryos.ai/v1/datasets/miso-realtime-lmp/query?node=INDIANA.HUB&start=-24h&interval=1h&agg=avg"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 INDIANA.HUB over the last 24 hours, and when did it peak?
Setup for every client is on the MCP server page.
How this stream is checked
- Pulled straight from MISO Public API · Real-Time Five Minute ExPost — 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 every 5 min; the interval timestamp is the start of the interval, in UTC.
- MISO runs on Eastern Standard Time all year and never observes daylight saving. Every timestamp Dryos serves is UTC.
Related streams
- 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 - MISO ex-ante hub LMPMISO
The forward-looking price at MISO's eight trading hubs and the SPP seam: what the next dispatch is about to clear at, published just before each interval.
every 5 min · 5m rows9 entitiesmiso-exante-lmp - ERCOT real-time LMPERCOT
Locational marginal prices from the latest SCED run, every ERCOT settlement point.
every 5 min · 5m rows1,118 entitiesercot-realtime-lmp - 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 - CAISO real-time LMPCAISO
Real-time dispatch prices at every CAISO aggregated pricing node — the NP15, SP15 and ZP26 trading hubs, the utilities' load aggregation points, resources, and the pricing points of every Western Energy Imbalance Market area — with the energy, congestion, loss and greenhouse-gas components, every five minutes.
every 5 min · 5m rows2,711 entitiescaiso-realtime-lmp - NYISO real-time LMPNYISO
Real-time dispatch prices at NYISO's eleven load zones — New York City, Long Island and the rest, lettered A to K — its proxies with Quebec, New England, Ontario and PJM, and every generator bus, with the energy, congestion and loss components, every five minutes.
every 5 min · 5m rows763 entitiesnyiso-realtime-lmp