ISO-NE · Pricing

ISO-NE day-ahead LMP

Hourly day-ahead prices at ISO New England's Internal Hub, its eight load zones, its ties with New York, Québec and New Brunswick, and every generator and load node, with the energy, congestion and loss components, posted for the whole of tomorrow each afternoon.

isone-dam-lmpdaily, early afternoon ET · 1h rows1,207 entities
.H.INTERNAL_HUB
$33.83
2026-11-23 04:00 UTC
.Z.NEMASSBOST
$33.82
2026-11-23 04:00 UTC
.Z.CONNECTICUT
$32.80
2026-11-23 04:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates daily, early afternoon ET.

What is in it

Updates
daily, early afternoon ET · 1h rows
Entities
1,207 entities — .H.INTERNAL_HUB, .Z.NEMASSBOST, .Z.CONNECTICUT…
Source timezone
US Eastern — every timestamp Dryos serves is UTC
Coverage
16 November 2026 to now
Rows held
202,776
Primary key
iso, market, node, interval_start_utc
On the map
1,137 of 1,207 placed — ISO-NE's own pricing-node table, which gives each node its substation's coordinate

What it measures

Every value, its unit, and what the source means by it.

  • Total LMP$/MWh

    The hourly day-ahead price at the 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, as ISO-NE publishes it. One number across New England each hour.

    lmp_energy

Columns

Exactly what a request answers with, read from the API rather than written here.

ColumnTypeDescription
interval_start_utcrequiredtimestampStart of the settlement interval, UTC. Always UTC — the ISOs publish in local time with inconsistent DST handling.e.g. 2026-08-14T15:00:00Z
isorequiredstringPublishing ISO.e.g. ERCOT
marketrequiredstringMarket the price cleared in: DAM (day-ahead), RTM (real-time, SCED), or RTPD for CAISO's fifteen-minute market.e.g. RTM
noderequiredstringPricing node or settlement point identifier, as published by the ISO.e.g. HB_HOUSTON
node_typestringNode 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_totalrequirednumberTotal locational marginal price, $/MWh.e.g. 41.83
lmp_energynumberEnergy component, $/MWh.e.g. 39.12
lmp_congestionnumberCongestion 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_lossnumberLoss component, $/MWh.e.g. -0.23
source_published_at_utctimestampWhen the ISO published this interval, UTC. Lets a buyer distinguish 'we were slow' from 'the ISO was slow'.
collected_at_utcrequiredtimestampWhen 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

shell
curl "https://api.dryos.ai/v1/datasets/isone-dam-lmp/query?node=.H.INTERNAL_HUB&limit=12"

The catalogue entry — every column, its type and the source

shell
curl "https://api.dryos.ai/v1/datasets/isone-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.

shell
claude mcp add --transport http dryos https://api.dryos.ai/mcp

Then ask:

What has Total LMP been at .H.INTERNAL_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.

  1. 2026-11-15

    First collected, from ISO Express.

    ISO-NE was the one operator with a real-time price here and no day-ahead one beside it, though its day-ahead file was already read daily for location names. Reconciled against the live file on 2026-11-15: market days 2026-11-15 and 11-16, every check passing; the hour-ending convention was checked against ISO-NE's hourly real-time file and the five-minute prices.

How this stream is checked

  • Pulled straight from ISO Express · Day-Ahead Energy Market Hourly LMP Report — 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, early afternoon ET; the interval timestamp is the start of the interval, in UTC.
  • ISO-NE stamps its files in Eastern prevailing time with no zone column. Every timestamp Dryos serves is UTC.

Related streams