ERCOT forecast evidence, measured before it is marketed.
ERCOT forecast errors matter quickly because scarcity pricing, weather ramps, and retail exposure turn demand misses into direct commercial risk.
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 ERCOT.
The historical ERCOT backtest was promising, but the current production h24 row is behind the ISO reference and must be treated as a rebuild target.
The best next claim is a customer-specific benchmark over the operating period a desk actually trades, not a blended archive percentage.
Generation mix, wind ramps, weather vintage, and load-zone scope can still make ERCOT a strong candidate once live validation catches up.
Live scorecard and archive.
Last updated May 22, 2026. A new ERCOT candidate must beat the live row in shadow mode before it can be promoted.
Evaluation path
ERCOT 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 ERCOT h24 row and its ISO-reference status before using archive results.
Open scorecard - 02
Request scoped benchmark
Use ERCOT as the declared market, then add horizon, audit period, and decision context.
Request ERCOT 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