PJM · Pricing
PJM IT SCED interface prices
What PJM's intermediate-term dispatch expects the next four five-minute intervals to cost at its ties with New York and MISO, re-run every few minutes and kept case by case — the forward-looking price at the seams, MISO's ex-ante counterpart.
pjm-itsced-lmpevery 5 min, four intervals ahead · 5m rows5 entitiesWhat is in it
- Updates
- every 5 min, four intervals ahead · 5m rows
- Entities
- 5 entities — NYIS, MISO, NEPTUNE…
- Source timezone
- US Eastern — every timestamp Dryos serves is UTC
- Coverage
- 8 September 2026 to now
- Rows held
- 45,020
- Primary key
- iso, node, interval_start_utc, source_published_at_utc
What it measures
Every value, its unit, and what the source means by it.
- IT SCED LMP$/MWh
The price the case expects at the interface for the interval.
lmp_total - Congestion$/MWh
Marginal congestion component.
lmp_congestion - Losses$/MWh
Marginal loss component.
lmp_loss
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 five-minute interval being priced ahead of time, UTC.e.g. 2026-09-10T02:45:00Z |
| isorequired | string | Publishing ISO.e.g. PJM |
| noderequired | string | The tie or interface as PJM names it: NYIS, MISO, HUDSONTP, LINDENVFT, NEPTUNE.e.g. NYIS |
| node_typerequired | string | INTERFACE, for every row.e.g. INTERFACE |
| lmp_totalrequired | number | The IT SCED price at the interface for the interval, $/MWh, as of this case.e.g. 24.83 |
| lmp_energyrequired | number | Energy component, $/MWh — derived as LMP minus congestion minus loss, PJM's own identity; the feed omits it.e.g. 39.59 |
| lmp_congestionrequired | number | Congestion component, $/MWh.e.g. -15.74 |
| lmp_lossrequired | number | Loss component, $/MWh.e.g. 0.98 |
| source_published_at_utcrequired | timestamp | When PJM approved the IT SCED case this price came from, UTC — the vintage. Every case is kept, so one interval carries a row per case that priced it.e.g. 2026-09-10T02:21:37Z |
| collected_at_utcrequired | timestamp | When Dryos collected this row, UTC. Stamped by the platform.e.g. 2026-09-10T02:52:00Z |
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-itsced-lmp/query?node=NYIS&limit=12"The catalogue entry — every column, its type and the source
curl "https://api.dryos.ai/v1/datasets/pjm-itsced-lmp"Hourly averages for the last day
curl "https://api.dryos.ai/v1/datasets/pjm-itsced-lmp/query?node=NYIS&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 IT SCED LMP been at NYIS 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 · five_min_itsced_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, four intervals ahead; 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 LMPPJM
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.
every 5 min · 5m rows482 entitiespjm-realtime-lmp - 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