PJM forecast evidence, with the ISO reference status visible.
PJM is commercially important because zone-aware load, capacity exposure, and data-center growth can make small demand errors financially meaningful.
This page now shows current live evidence first. Historical low-MAPE backtests remain visible as research archive, but they are not current production claims.
What is still useful about Gramm in PJM.
The current public row reports Gramm production h24 MAPE while the canonical PJM ISO h24 reference is still marked pending.
PJM claims should center on evaluation discipline, Data Miner compatibility, and market-specific benchmarking until the paired ISO reference is complete.
Zone-level or customer-footprint claims should be made only after a scoped benchmark declares the zones, horizon, and audit period.
Live scorecard and archive.
Last updated May 22, 2026. A new PJM candidate must beat the live row in shadow mode before it can be promoted.
Evaluation path
PJM evaluation path.
A market-specific page should lead to a market-specific benchmark: confirm the live row, scope the period and horizon, then test payloads only after the evidence is clear.
- 01
Review live scorecard
Start with the current PJM h24 row and its ISO-reference status before using archive results.
Open scorecard - 02
Request scoped benchmark
Use PJM as the declared market, then add horizon, audit period, and decision context.
Request PJM benchmark - 03
Test API payloads
Confirm response shape, region code, horizon, and validation status before wiring production workflows.
View API docs - 04
Move to procurement or paid plan
Use trust, SLA, pricing, and enterprise materials once the scoped benchmark supports review.
Open procurement