Docs → API reference

Power Demand API v1

Generated from core.contract.describe_power_demand_v1() and checked fixture-backed examples. Do not hand-edit the example JSON files.

Capability

• Capability: power.demand
• Primitive: query_power_demand_v1
• Status: available
• Current source: energy.eia.eia930
• Source publisher: U.S. Energy Information Administration
• Snapshot behavior: as_of = latest resolves to an exact snapshot date in every response.

What It Can Answer

• Hourly observed electricity demand (MW) for a balancing authority — EIA's Adjusted series, cited to the source row.
• The day-ahead demand forecast for the same BA-hours, and forecast-vs-actual misses.
• Which hours EIA imputed rather than metered (is_imputed).
• BA-level demand shape over time (daily/seasonal profiles at BA grain).
• Row-level detail records when include_records is true.
• Raw CSV row evidence for any returned row-level citation.

Represented Facts

• EIA-930 reports hourly observed electricity demand (MW) by balancing authority — EIA's Adjusted series, with the raw value and imputation flag preserved
• EIA-930 reports the day-ahead demand forecast (MW) on the same balancing-authority-hour rows

Data Point Contract

• Data point: power.demand
• Product spec: blocks/power_demand/card.md
• Grain: ba_hourly_flow
• Source basis: energy.eia.eia930
• Represented fact: EIA-930 reports hourly observed electricity demand (MW) by balancing authority — EIA's Adjusted series as the canonical value, with the raw series and the imputation flag preserved — plus the same row's day-ahead demand forecast, as a continuously revised hourly time series (history to 2015 H2).

Does not answer:

• plant, generator, county, or lat/lon attribution (structural — EIA-930 carries no such IDs; permanent refusal)
• state-level demand (BA footprints do not follow state lines)
• US48 or region totals as source rows (computed rollups; BA additivity is an open PD — gen-only BAs report no demand and the BA set is time-varying)
• installed capacity (EIA-860M), monthly plant generation (EIA-923), retail sales/customers (EIA-861)
• wholesale prices or transmission projects
• long-horizon demand forecasts (FERC-714, parked; the EIA-930 forecast is day-ahead only)
• reconciliation against EIA-923 or EIA-861 (different atoms by Rule 1/Rule 2; a discrepancy is a finding, never a canonical value)
• finality (the current half-year file is preliminary and continuously revisable)

REST Surface

• GET /v1/health
• GET /v1/capabilities
• GET /v1/power/demand/schema
• POST /v1/power/demand/query
• POST /v1/evidence/source-row

MCP Surface

• list_capabilities_v1
• describe_power_demand_v1
• query_power_demand_v1
• get_source_evidence_v1

Local MCP Setup

Some MCP clients launch servers from the user's home directory or ignore a configured cwd. Use uv run --directory so the server always starts from the repository project.

{
  "command": "uv",
  "args": [
    "run",
    "--directory",
    "/absolute/path/to/OSINT",
    "python",
    "-m",
    "core.mcp_server"
  ]
}

Leave EXASCALE_PARQUET_BASE / EXASCALE_RAW_BASE unset: the one server hosts every data point's tools, and with no override it resolves each block's promoted snapshots and raw archive from the repository layout. Setting either env var points ALL tools at one directory — a per-block path breaks every other block's tools. They exist only for single-source sandboxes and tests.

Request Schema

Filters:

• as_of
• balancing_authority_code
• region
• data_date
• hour_number
• is_imputed

Input field semantics:

Group by:

• balancing_authority_code
• region
• data_date
• hour_number
• datetime_utc
• is_imputed

Date range parameters:

• data_date_from
• data_date_to

Controls:

• include_records
• include_evidence
• limit
• order_by
• top_n
• order
• rollup_other

Ranking (how order_by / top_n / order join — order_by ranks groups by a metric, never a group_by dimension; top_n needs both a group_by and an order_by):

{
  "no_ranking": "Omit order_by and top_n to return all groups in group-key order.",
  "order": {
    "default": "desc",
    "valid_values": [
      "desc",
      "asc"
    ]
  },
  "order_by": {
    "accepts": "one of output.metrics",
    "note": "Ranks the groups by a metric (a measure). Not a group_by dimension \u2014 rows already come back grouped by each group_by field.",
    "requires": [
      "group_by"
    ],
    "valid_values": [
      "demand_mw",
      "demand_forecast_mw",
      "source_record_count"
    ]
  },
  "top_n": {
    "note": "Keeps the top N groups by order_by; the rest fold into one (other) remainder (additive metrics sum into it, non-additive ones are nulled) so the result still reconciles to summary.totals.",
    "requires": [
      "group_by",
      "order_by"
    ],
    "type": "positive integer"
  }
}

Output Schema

Aggregate metrics:

• demand_mw
• demand_forecast_mw
• source_record_count

Metric groups:

{
  "demand_mw": [
    "demand_mw",
    "demand_forecast_mw"
  ],
  "records": [
    "source_record_count"
  ]
}

Response summary fields:

• group_count
• totals

Accepted fact policy:

• Query responses contain accepted, gate-passed facts only.
• Gate, monitor, and audit quality signals are internal controls, not agent-facing answer caveats.
• If a source snapshot is not fit to serve, the source must fail closed before it reaches this API.

Metric metadata:

Rollup rules:

• summary.totals.<metric> is the authoritative total for the full matched query.
• Grouped row metrics may be summed only when additive_across_groups is true.
• Do not sum grouped values for these non-additive metrics: demand_mw, demand_forecast_mw.

Detail record fields returned when include_records is true:

• source_id
• sheet_name
• source_record_key
• report_period
• balancing_authority_code
• region
• data_date
• hour_number
• datetime_local
• datetime_utc
• demand_mw
• demand_mw_raw
• is_imputed
• demand_forecast_mw
• source_row_number
• as_of
• raw_file_sha256
• citation

Row-level citation fields:

• source_id
• source_url
• source_file
• sheet
• source_row
• raw_file_sha256
• as_of

Aggregate citation fields:

• source_id
• publisher
• source_url
• source_file
• raw_file_sha256
• as_of
• source_rows_count
• source_rows_sample
• verify
• lineage_filter

Codebooks

The complete machine-readable codebooks are included in capability-schema.json.

Checked Examples

The checked schema output is capability-schema.json.

Agent Workflow

1. Call list_capabilities_v1 and select power.demand.
2. Call describe_power_demand_v1 to inspect valid filters, groupings, metrics, and citation fields.
3. Call query_power_demand_v1 with bounded JSON params.
4. If the answer needs proof, pass a returned row-level citation object to get_source_evidence_v1.
5. Answer with the resolved as_of and relevant citations. Present returned metrics as authoritative for their declared source, snapshot, grain, and aggregation.