Power Forward Demand (data-center/large-load wedge by year) [beta]
sec_power_demand_forwardForward large-load demand from utility disclosures: data-center / hyperscaler / industrial / hydrogen / crypto MW commitments by year, firm vs pipeline. The answer to 'how much data-center load are utilities actually committing to' without rereading every PJM IRP.
Spec-validated headline: firm DC load 2.6 → 45 GW from 2024 to 2026 disclosures (the AI-buildout wedge). Live status enum (verified from data, the originally-spec'd values were renamed during extraction): firm side = 'contract', 'in_service', 'executed', 'firm', 'permitting'; pipeline side = 'mou', 'in_negotiation', 'announced', 'planned', 'pipeline'. Don't pass 'contracted' or 'signed_LOA' — those silently return 0 rows.
Filter by ticker_or_cik (per-utility), counterparty_type (data_center / industrial / crypto / hydrogen / ev_charging / mixed), iso, status, or year range. Returns one row per (filer, counterparty, start_year) deduped to latest filing, with the full source_accession + snippet.
Two caveats that bite per-ticker consumers hardest (power-sec 2026-07-23): (1) The firm-vs-speculative split is load-bearing, NOT cosmetic. The response separates firm_total_mw from pipeline_total_mw (and per-year in summary_by_year) — read the FIRM total, not a blended sum. Pipeline rows are interconnection-queue entries that double-count across overlapping territories and mostly never get built. Concrete trap: AEP's only demand rows are 2 pipeline entries totalling 200,000 MW — a blended read prints a 200 GW headline for one utility; its firm_total_mw is 0. (2) expected_load_mw is NULL on a meaningful share of FIRM rows (e.g. EVRG, ETR have firm events with no MW) — so sum(mw) under-represents coverage vs n_events. A null MW ≠ 'no commitment'; use n_events for count, the MW totals for magnitude, and don't conflate them.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "sec_power_demand_forward"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| iso | No | ISO/RTO scope (PJM / ERCOT / CAISO / MISO / NYISO / ISO-NE / SPP / non-RTO). | |
| as_of | No | ISO date for PIT (default: latest disclosures). | |
| limit | No | ||
| status | No | Filter by commitment status (LIVE enum: 'contract' / 'in_service' / 'executed' / 'firm' / 'permitting' on the firm side; 'mou' / 'in_negotiation' / 'announced' / 'planned' / 'pipeline' on the pipeline side). NB: the originally-spec'd 'contracted' and 'signed_LOA' values silently return 0 rows — use 'contract' / 'executed' / 'firm' instead. | |
| year_to | No | ||
| year_from | No | ||
| ticker_or_cik | No | Filter to one filer. | |
| include_undated | No | Default false. When false, rows with `timeline_start_year IS NULL` are EXCLUDED (per futures smoke 2026-06-12: undated rows were bypassing the year_from filter and returning 2003/2011-2014 vintage disclosures + a 15,277 MW 'unknown' bucket alongside current commitments). Set true to inspect the full undated set. | |
| counterparty_type | No | Filter to one segment (data_center / industrial / crypto / hydrogen / ev_charging / mixed). |