PJM · Load

PJM dispatch case load bias

The load bias PJM's operators applied to each approved real-time SCED, intermediate-term SCED and pricing calculator case — their adjustment to the load forecast the case solved against — about every five minutes.

pjm-load-biasevery 15 min · 5m rows3 entities
RT_SCED
400MW
2026-11-22 17:14 UTC
IT_SCED
0.00MW
2026-11-22 17:10 UTC
LPC
400MW
2026-11-22 17:14 UTC
Read from the Dryos API and cached for an hour; the stream itself updates every 15 min.

What is in it

Updates
every 15 min · 5m rows
Entities
3 entities — RT_SCED, IT_SCED, LPC…
Source timezone
US Eastern — every timestamp Dryos serves is UTC
Coverage
16 November 2026 to now
Rows held
5,394
Primary key
iso, case_type, interval_start_utc

What it measures

Every value, its unit, and what the source means by it.

  • Load biasMW

    The operator's adjustment to the case's load forecast, positive up.

    load_bias_mw

Columns

Exactly what a request answers with, read from the API rather than written here.

ColumnTypeDescription
interval_start_utcrequiredtimestampStart of the interval, UTC, read from PJM's own UTC column.e.g. 2026-09-09T12:30:00Z
isorequiredstringPublishing ISO.e.g. PJM
case_typerequiredstringWhich dispatch case the bias was applied to: RT_SCED (real-time security-constrained economic dispatch), IT_SCED (intermediate-term SCED) or LPC (locational pricing calculator).e.g. RT_SCED
load_bias_mwrequirednumberThe load bias on the approved case, MW: the operator's adjustment to the load forecast the case solved against, positive up.e.g. -400
source_published_at_utctimestampWhen PJM published the row, UTC.
collected_at_utcrequiredtimestampWhen 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

shell
curl "https://api.dryos.ai/v1/datasets/pjm-load-bias/query?node=RT_SCED&limit=12"

The catalogue entry — every column, its type and the source

shell
curl "https://api.dryos.ai/v1/datasets/pjm-load-bias"

Hourly averages for the last day

shell
curl "https://api.dryos.ai/v1/datasets/pjm-load-bias/query?node=RT_SCED&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.

shell
claude mcp add --transport http dryos https://api.dryos.ai/mcp

Then ask:

What has Load bias been at RT_SCED 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.

  1. 2026-11-15

    First collected, from PJM Data Miner 2.

    Three small feeds PJM keeps seven years, one number per approved case each, taken as one stream. Reconciled against live responses on 2026-11-15.

How this stream is checked

  • Pulled straight from PJM Data Miner 2 · rt_sced_bias, it_sced_bias, lpc_bias — 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 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