PJM · Ancillary
PJM real-time ancillary market results
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. Posted about three days late, on business days.
pjm-rt-reserve-resultsevery 5 min, posted ~3 days late · 5m rows4 entitiesWhat is in it
- Updates
- every 5 min, posted ~3 days late · 5m rows
- Entities
- 4 entities — REGULATION, SYNCHRONIZED, PRIMARY…
- Source timezone
- US Eastern — every timestamp Dryos serves is UTC
- Coverage
- 6 September 2026 to now
- Rows held
- 17,868
- 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-h
The service's market clearing price for the interval.
mcp - RequirementMW
The service's requirement.
as_req_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 | PJM_RTO, or MAD for the Mid-Atlantic/Dominion reserve subzone.e.g. PJM_RTO |
| as_typerequired | string | REGULATION, SYNCHRONIZED, PRIMARY (synchronized plus non-synchronized) or THIRTY_MINUTE — the vocabulary `pjm-dispatched-reserves` uses.e.g. SYNCHRONIZED |
| mcprequired | number | Market clearing price, $/MW for the interval's hour of capability.e.g. 0.14 |
| mcp_cappedrequired | number | The clearing price after PJM's cap, $/MW-hour.e.g. 0.14 |
| reg_ccp | number | Regulation's capability clearing price, $/MW-hour. |
| reg_pcp | number | Regulation's performance clearing price, $/MW-hour. |
| as_req_mw | number | The service's requirement, MW (PJM's `as_req_mw`). |
| total_mw | number | Total MW PJM counts toward the service, MW (PJM's `total_mw`). |
| as_mw | number | MW assigned through the market for the service (PJM's `as_mw`). |
| ss_mw | number | Self-scheduled MW (PJM's `ss_mw`). |
| ircmwt2 | number | PJM's `ircmwt2`, carried as published. |
| dsr_as_mw | number | Demand-resource MW toward the service (PJM's `dsr_as_mw`). |
| nsr_mw | number | Non-synchronized reserve MW, where PJM reports it (PJM's `nsr_mw`). |
| tier1_mw | number | Tier 1 synchronized reserve MW, where PJM reports it. |
| regd_mw | number | RegD MW, where PJM reports it. |
| 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-rt-reserve-results/query?node=REGULATION&limit=12"The catalogue entry — every column, its type and the source
curl "https://api.dryos.ai/v1/datasets/pjm-rt-reserve-results"Hourly averages for the last day
curl "https://api.dryos.ai/v1/datasets/pjm-rt-reserve-results/query?node=REGULATION&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 REGULATION 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-13
First collected, from PJM Data Miner 2.
PJM's ancillary market results, kept by PJM indefinitely. Reconciled against live responses on 2026-09-13, and checked price for price against PJM's two ancillary price feeds, which are copies of it and are not collected.
How this stream is checked
- Pulled straight from PJM Data Miner 2 · reserve_market_results — 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, posted ~3 days late; 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 dispatched reservesPJM
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.
every 5 min · 5m rows3 entitiespjm-dispatched-reserves - 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