PJM · Generation

PJM solar output

Metered utility-scale solar output across the whole of PJM every five minutes. Behind-the-meter solar is not in it; PJM sees that as missing load.

pjm-solar-genevery 5 min · 5m rows1 entity

What is in it

Updates
every 5 min · 5m rows
Entities
1 entity
Source timezone
US Eastern — every timestamp Dryos serves is UTC
Coverage
8 September 2026 to now
Rows held
2,704
Primary key
iso, interval_start_utc

What it measures

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

  • SolarMW

    Utility-scale solar output across PJM for the interval.

    gen_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
gen_mwrequirednumberMetered utility-scale solar output across the PJM RTO for the five-minute interval, MW.e.g. 52.86
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-solar-gen/query?limit=12"

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

shell
curl "https://api.dryos.ai/v1/datasets/pjm-solar-gen"

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:

Show me Solar on PJM solar output over the last 24 hours.

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-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 · five_min_solar_generation — 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