PJM · Ancillary
PJM dispatched reserves
Synchronized, primary and thirty-minute reserve every five minutes: the megawatts the dispatch held against each requirement, the clearing price, and whether PJM called the interval short. A product is one series; the row carries which zone (the RTO or Mid-Atlantic/Dominion) it is.
pjm-dispatched-reservesevery 5 min · 5m rows3 entitiesWhat is in it
- Updates
- every 5 min · 5m rows
- Entities
- 3 entities — SYNCHRONIZED, PRIMARY, THIRTY_MINUTE…
- Source timezone
- US Eastern — every timestamp Dryos serves is UTC
- Coverage
- 8 September 2026 to now
- Rows held
- 13,515
- Primary key
- iso, zone, as_type, interval_start_utc
What it measures
Every value, its unit, and what the source means by it.
- Clearing price$/MW
Reserve market clearing price, $/MW per hour.
mcp - DispatchedMW
Reserve dispatched in the look-ahead solution.
quantity_mw - RequirementMW
The requirement the dispatch was meeting.
requirement_mw
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 | Reserve zone as PJM names it: PJM_RTO, or the Mid-Atlantic/Dominion sub-zone.e.g. PJM_RTO |
| as_typerequired | string | Reserve product: SYNCHRONIZED, PRIMARY (synchronized plus non-synchronized) or THIRTY_MINUTE. Thirty-minute reserve clears for the RTO only.e.g. SYNCHRONIZED |
| mcprequired | number | Reserve market clearing price for the product in the zone, $/MW per hour.e.g. 0.14 |
| quantity_mwrequired | number | Reserve dispatched in the look-ahead solution, MW.e.g. 2290 |
| requirement_mwrequired | number | The requirement the dispatch was meeting, MW: the reliability requirement plus the extended requirement, after any adjustment.e.g. 2290 |
| reliability_requirement_mwrequired | number | The reliability component of the requirement, MW.e.g. 2100 |
| extended_requirement_mwrequired | number | The extended (economic) component of the requirement, MW.e.g. 190 |
| adjustment_mwrequired | number | Operator adjustment applied to the requirement, MW.e.g. 0 |
| shortagerequired | boolean | Whether PJM flagged the interval short of the requirement.e.g. false |
| 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-dispatched-reserves/query?node=SYNCHRONIZED&limit=12"The catalogue entry — every column, its type and the source
curl "https://api.dryos.ai/v1/datasets/pjm-dispatched-reserves"Hourly averages for the last day
curl "https://api.dryos.ai/v1/datasets/pjm-dispatched-reserves/query?node=SYNCHRONIZED&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 Clearing price been at SYNCHRONIZED 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 · dispatched_reserves — 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 regulation pricesPJM
The five-minute regulation clearing price for the PJM RTO, split into its capability and performance components, with the megawatts cleared against the requirement.
every 5 min · 5m rows1 entitypjm-regulation-prices - PJM real-time ancillary market resultsPJM
PJM's settled real-time results for regulation, synchronized, primary and thirty-minute reserve, every five minutes, for the RTO and the Mid-Atlantic/Dominion subzone: clearing prices, requirements and the megawatts behind them.
every 5 min, posted ~3 days late · 5m rows4 entitiespjm-rt-reserve-results - PJM day-ahead ancillary market resultsPJM
PJM's day-ahead results for synchronized, primary and thirty-minute reserve, hourly, for the RTO and the Mid-Atlantic/Dominion subzone: clearing prices, requirements and the megawatts behind them, posted with tomorrow's market.
daily, for tomorrow · 1h rows3 entitiespjm-da-reserve-results - PJM operational reservesPJM
The megawatts of synchronized, primary and thirty-minute reserve PJM is holding against each requirement, as the control room sees them every fifteen seconds, for the RTO and the Mid-Atlantic/Dominion sub-zone.
every 15 s · 15s rows13 entitiespjm-operational-reserves - 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