PJM · Pricing

PJM verified real-time hourly LMP

PJM's verified hourly real-time prices at its 484 hubs, zones, interfaces, EHV and residual aggregates, with the energy, congestion and loss components as PJM publishes them. Posted the next business day and kept indefinitely, where the unverified hourly prices are kept thirty days.

pjm-realtime-lmp-hourly-verifieddaily on business days, the day before · 1h rows484 entities
WESTERN HUB
$33.56
2026-11-20 04:00 UTC
PJM-RTO
$30.22
2026-11-20 04:00 UTC
COMED
$19.27
2026-11-20 04:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates daily on business days, the day before.

What is in it

Updates
daily on business days, the day before · 1h rows
Entities
484 entities — WESTERN HUB, PJM-RTO, COMED…
Source timezone
US Eastern — every timestamp Dryos serves is UTC
Coverage
9 November 2026 to now
Rows held
123,420
Primary key
iso, market, node, interval_start_utc

What it measures

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

  • Total LMP$/MWh

    The verified hourly real-time 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 energy price as PJM publishes it, to the cent.

    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/pjm-realtime-lmp-hourly-verified/query?node=WESTERN%20HUB&limit=12"

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

shell
curl "https://api.dryos.ai/v1/datasets/pjm-realtime-lmp-hourly-verified"

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 WESTERN 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 PJM Data Miner 2.

    The verified copy of the real-time hourly prices, kept by PJM indefinitely where the unverified feed keeps thirty days. Reconciled against a live response on 2026-11-15.

How this stream is checked

  • Pulled straight from PJM Data Miner 2 · rt_hrl_lmps — 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 on business days, the day before; the interval timestamp is the start of the interval, in UTC.
  • PJM's Eastern Prevailing Time observes daylight saving; its rows carry UTC as well. Every timestamp Dryos serves is UTC.

Related streams