PJM · Pricing
PJM dispatch rates
The dispatch signal PJM sends each of its 20 transmission zones, in $/MWh, every fifteen seconds — the price the control room is steering generators to at the instant, not a settlement price. PJM keeps fifteen days.
pjm-dispatch-ratesevery 15 s · 15s rows20 entitiesWhat is in it
- Updates
- every 15 s · 15s rows
- Entities
- 20 entities — COMED, DOM, PS…
- Source timezone
- US Eastern — every timestamp Dryos serves is UTC
- Coverage
- 9 September 2026 to now
- Rows held
- 976,140
- Primary key
- iso, zone, interval_start_utc
What it measures
Every value, its unit, and what the source means by it.
- Dispatch rate$/MWh
The dispatch rate sent to the zone at the scan.
dispatch_rate
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 interval, UTC, read from PJM's own UTC column.e.g. 2026-09-09T12:30:00Z |
| isorequired | string | Publishing ISO.e.g. PJM |
| zonerequired | string | Transmission zone the signal is sent to, in PJM's short spelling (AEP, COMED, DOM, PS, PE, ...).e.g. COMED |
| dispatch_raterequired | number | The dispatch rate PJM is sending the zone's generators, $/MWh — the price the dispatch is steering to at the instant, not a settlement price.e.g. 30.27 |
| source_published_at_utc | timestamp | When PJM published the row, UTC. |
| collected_at_utcrequired | timestamp | When Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-09-09T12:35:12Z |
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-dispatch-rates/query?node=COMED&limit=12"The catalogue entry — every column, its type and the source
curl "https://api.dryos.ai/v1/datasets/pjm-dispatch-rates"Hourly averages for the last day
curl "https://api.dryos.ai/v1/datasets/pjm-dispatch-rates/query?node=COMED&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 Dispatch rate been at COMED 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 · inst_dispatch_rates — 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 15 s; 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