PJM Day-Ahead Prices

PJM day-ahead locational marginal prices, one row per interval and location.

Prices data PJM market

Query with the agent

Native record

location x kind x delivery hour

hourly publication cadence

Evidence

Cleared day-ahead market

A market outcome, not a physical observation

Time basis

Interval-start records

UTC · event_time

Overview

1.00B rows, 2018-01 to the next delivery day. Carries price_usd_mwh plus energy_usd_mwh, congestion_usd_mwh and loss_usd_mwh. Locations are load, generator, aggregate, bus, interface, zone, hub; location_id joins atg.pjm_locations for the readable name, and kind is carried inline so a hub-only or zone-only question needs no join at all. Every market's day-ahead price table in this catalog has these same column names, so a cross-market price comparison is a UNION rather than a per-ISO rewrite. Revisions are already collapsed — read it plainly.

Query contract

One row is already the canonical price for (event_time, location_id, kind) — the refresh collapsed the source's revisions. Select the interval and the locations you need; do not de-duplicate again. Day-ahead rows for the next delivery day are published in a single late-evening batch, so max(event_time) runs ahead of the wall clock by design.

Analysis rules

Prices are intensive. Averaging across intervals gives a simple (unweighted) average price, which is not a settlement or load-weighted price; say which one you computed. Never sum prices across intervals or locations.
Do not add price_usd_mwh to its own components — they decompose it, they do not extend it.

Related analysis

resolving a location's readable name and type · join on location_id, and on kind where both carry it
day-ahead versus real-time basis at one location · aggregate the real-time intervals in the delivery hour before comparing

Interpretation

PJM posts the next day's day-ahead prices in the early afternoon Eastern time, by about 1:30 PM ET the day before delivery; they typically become available here later that afternoon. Earlier in the day, the next day's prices are not out yet.
A price difference between two locations is a basis. It is evidence that they separated, not evidence of which facility bound; that needs the congestion component or the constraints table.

Access

Query from your own tools

Use the guarded HTTP endpoint directly, or connect an MCP client and load the dataset contract with describe_data before calling query_data.

PJM MCP API reference

HTTP endpoint

POST /api/v1/datasets/pjm_prices_da/query

Need the full history of this dataset in Snowflake, Databricks or your own storage? Data services delivers it on a schedule.

Schema7

Column

Type

event_timeDateTime64(6, 'UTC')

location_idLowCardinality(String)

kindLowCardinality(String)

price_usd_mwhNullable(Float64)

energy_usd_mwhNullable(Float64)

congestion_usd_mwhNullable(Float64)

loss_usd_mwhNullable(Float64)

Sample data

event_time	location_id	kind	price_usd_mwh	energy_usd_mwh	congestion_usd_mwh	loss_usd_mwh
2026-10-15 02:00:00.000000	1084391529	generator	75.68	74.2	2.23	-0.75
2026-10-15 02:00:00.000000	1084391168	generator	74.01	74.2	1.08	-1.27
2026-10-15 02:00:00.000000	1084391159	generator	74.52	74.2	0.69	-0.37
2026-10-15 02:00:00.000000	1084391056	generator	46.43	74.2	-28.17	0.4
2026-10-15 02:00:00.000000	1084391055	generator	42.29	74.2	-28.54	-3.37
2026-10-15 02:00:00.000000	1084391028	generator	42.4	74.2	-28.83	-2.97
2026-10-15 02:00:00.000000	1084390988	generator	44.28	74.2	-27.39	-2.53
2026-10-15 02:00:00.000000	1084390987	generator	44.28	74.2	-27.39	-2.53
2026-10-15 02:00:00.000000	1084390986	generator	44.28	74.2	-27.39	-2.53
2026-10-15 02:00:00.000000	1084383671	load	79.26	74.2	4.52	0.54
2026-10-15 02:00:00.000000	1084390852	generator	56.74	74.2	-11.51	-5.95
2026-10-15 02:00:00.000000	1084390354	generator	44.4	74.2	-27.3	-2.5
2026-10-15 02:00:00.000000	1084390333	generator	44.96	74.2	-26.81	-2.43
2026-10-15 02:00:00.000000	1084390238	generator	47.44	74.2	-24.17	-2.59
2026-10-15 02:00:00.000000	1084390175	generator	46.26	74.2	-25.1	-2.84
2026-10-15 02:00:00.000000	1084386399	load	76.11	74.2	2.95	-1.04
2026-10-15 02:00:00.000000	1084386398	load	76.11	74.2	2.95	-1.04
2026-10-15 02:00:00.000000	1084390856	generator	47.46	74.2	-17.72	-9.02
2026-10-15 02:00:00.000000	1084384387	load	90.55	74.2	14.67	1.68
2026-10-15 02:00:00.000000	1084386162	load	77.97	74.2	3.04	0.73
2026-10-15 02:00:00.000000	1084383955	load	79.69	74.2	4.51	0.98
2026-10-15 02:00:00.000000	1084383930	load	77.49	74.2	0.68	2.61
2026-10-15 02:00:00.000000	1084384000	load	75.2	74.2	2.47	-1.47
2026-10-15 02:00:00.000000	1084383915	load	77.84	74.2	1.01	2.63
2026-10-15 02:00:00.000000	1084383896	load	78.54	74.2	3.21	1.13

Coverage

Showing the last 3,147 days of a 3,210-day history (Jan 1, 2018 → Oct 15, 2026). This dataset holds 1.02B rows — too many to count day by day on every visit — so the calendar and the figures below cover the window from Mar 5, 2018.

100.0% complete0 gap days3,147 days with data

Show coverage history

Coverage: 100.0%Days with data: 3,147Gaps: 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

gaplessmore

Related prices data

Related prices data
Dataset	Description
Day-Ahead Hourly LMPPJM · hourly (day-ahead)	Cleared day-ahead locational marginal prices for each PJM pricing node by delivery hour, with total LMP and its system-energy, congestion, and marginal-loss components in dollars per MWh. The table supports the posted next-day hourly curve, day-ahead-to-real-time basis, and node-level component attribution. A congestion component does not by itself identify which facility is expected to bind or establish a node-to-constraint relationship. Source: PJM Market Data.
PJM Real-Time PricesPJM · hourly	PJM real-time locational marginal prices, one row per interval and location. 991.1M rows, 2018-01 to now. Carries price_usd_mwh plus energy_usd_mwh, congestion_usd_mwh and loss_usd_mwh. Locations are load, generator, aggregate, bus, interface, zone, hub; location_id joins atg.pjm_locations for the readable name, and kind is carried inline so a hub-only or zone-only question needs no join at all. Every market's real-time price table in this catalog has these same column names, so a cross-market price comparison is a UNION rather than a per-ISO rewrite. Revisions are already collapsed — read it plainly.
Real-Time 5-Minute LMP (Unverified)PJM · 5-minute	Locational marginal prices from PJM's real-time energy market, published every five minutes for each pricing node (pnode) before settlement verification. Each row carries total LMP plus congestion and marginal-loss components in dollars per MWh. Components support node-level price decomposition, but price differences do not identify a named binding facility or prove topology. This is the freshest PJM price feed; use the settled hourly feed for the verified record published roughly 18 hours later. Point classes span transmission zones, trading hubs, external interfaces, and aggregate nodes. Source: PJM Market Data.
Real-Time Hourly LMP (Verified)PJM · hourly (settled ~18h lag)	PJM's verified real-time locational marginal prices at hourly granularity for every pricing node, with total LMP and its system-energy, congestion, and marginal-loss components in dollars per MWh. These are the settled, authoritative real-time prices — published on roughly an 18-hour lag behind the operating hour — and history reaches back to 2018, making this the table for real-time price history, day-over-day basis, and volatility studies. For prices in the current hour use the unverified 5-minute feed instead. Source: PJM Market Data.