PJM · Pricing
PJM real-time LMP
Unverified five-minute prices at PJM's 12 trading hubs, 22 transmission zones, 7 interfaces and every other aggregate pricing node, with the congestion and loss components, about four minutes after the interval starts. Unverified is PJM's word: the verified copy posts the next business day and 28 of 14,449 nodes differed on the interval checked, most by rounding.
pjm-realtime-lmpevery 5 min · 5m rows482 entitiesWhat is in it
- Updates
- every 5 min · 5m rows
- Entities
- 482 entities — WESTERN HUB, PJM-RTO, COMED…
- Source timezone
- US Eastern — every timestamp Dryos serves is UTC
- Coverage
- 10 September 2026 to now
- Rows held
- 1,122,066
- 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 five-minute unverified 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 — the same number at every node in an interval. Derived as LMP minus congestion minus losses, PJM's own identity; the feed omits it.
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/pjm-realtime-lmp/query?node=WESTERN%20HUB&limit=12"The catalogue entry — every column, its type and the source
curl "https://api.dryos.ai/v1/datasets/pjm-realtime-lmp"Hourly averages for the last day
curl "https://api.dryos.ai/v1/datasets/pjm-realtime-lmp/query?node=WESTERN%20HUB&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 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.
- 2026-09-09
First collected, from PJM Data Miner 2.
Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.
How this stream is checked
- Pulled straight from PJM Data Miner 2 · rt_unverified_fivemin_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 every 5 min; 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
- PJM real-time hourly LMPPJM
PJM's own hourly integration of its unverified real-time prices at the 12 trading hubs, 22 transmission zones, 7 interfaces and every other aggregate, with the congestion and loss components, posted for the previous hour.
hourly, for the hour before · 1h rows482 entitiespjm-realtime-lmp-hourly - PJM real-time LMPs by busPJM
Unverified five-minute prices at every one of PJM's 13,967 electrical buses — generator, load and external — with the congestion and loss components.
every 5 min · 5m rows13,967 entitiespjm-rt-lmp-bus - PJM day-ahead LMPPJM
Hourly day-ahead prices at PJM's 482 aggregate pricing nodes — hubs, zones, interfaces, EHV and residual aggregates — with the energy, congestion and loss components as PJM publishes them, posted for the whole of tomorrow between 12:00 and 13:30 Eastern.
daily, ~12:30 ET · 1h rows482 entitiespjm-dam-lmp - PJM day-ahead LMPs by busPJM
Hourly day-ahead prices at every one of PJM's 13,967 electrical buses, with the energy, congestion and loss components as PJM publishes them.
daily, ~12:30 ET · 1h rows13,967 entitiespjm-dam-lmp-bus - PJM binding constraintsPJM
Every transmission constraint the real-time dispatch was up against, five minutes at a time, with the contingency it bound for and its shadow price (negative, in PJM's convention).
every 5 min, when bound · 5m rows60 entitiespjm-binding-constraints - PJM real-time constraint marginal valuesPJM
PJM's settled record of every transmission constraint that bound in the real-time market, five minutes at a time, with its contingency, shadow price (negative, in PJM's convention), penalty factor and limit control percentage.
every 5 min, posted ~3 days late · 5m rows60 entitiespjm-rt-marginal-value