Docs → API reference

Power Asset Ownership API v1

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

Capability

• Capability: power.asset_ownership
• Primitive: query_power_asset_ownership_v1
• Status: available
• Current source: energy.eia.eia860_owner
• 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

• Raw annual EIA-860 owner names and fractional ownership shares by plant and generator.
• The documented absent-row convention: a generator omitted from Owner is wholly owned by its same-vintage operator.
• Exact raw owner-name, state, plant, generator, and source-reported balancing-authority slices.
• Row-level detail records and exact Percent Owned cell evidence.

Represented Facts

• Annual EIA-860 reports the raw ownership shares and owner identities for generators that are jointly owned or wholly owned by an entity other than the operator. A generator absent from the Owner schedule is wholly owned by its operator, as EIA explicitly documents; the block carries same-vintage generator/operator context so consumers can apply that default without treating absence as unknown ownership.
• Owner-schedule absence means wholly owned by the same-vintage generator operator.

Data Point Contract

• Data point: power.asset_ownership
• Product spec: blocks/power_asset_ownership/card.md
• Grain: plant_generator_owner_annual
• Source basis: energy.eia.eia860_owner
• Represented fact: Annual EIA-860 reports the raw ownership shares and owner identities for generators that are jointly owned or wholly owned by an entity other than the operator. A generator absent from the Owner schedule is wholly owned by its operator, as EIA explicitly documents; the block carries same-vintage generator/operator context so consumers can apply that default without treating absence as unknown ownership.

Does not answer:

• normalized or matched corporate identity across owner-name variants
• beneficial ownership, parent-company control, voting rights, or economic control
• market value, acquisition cost, or probability of an ownership change
• operator ownership inferred from a later or earlier vintage

REST Surface

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

MCP Surface

• list_capabilities_v1
• describe_power_asset_ownership_v1
• query_power_asset_ownership_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
• vintage_year
• eia_plant_id
• generator_id
• owner_name
• owner_state
• state
• balancing_authority_code

Group by:

• vintage_year
• eia_plant_id
• generator_id
• owner_name
• owner_state
• state
• balancing_authority_code

Date range parameters:

Controls:

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

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": [
      "percent_owned",
      "source_record_count",
      "distinct_generator_count",
      "distinct_plant_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:

• percent_owned
• source_record_count
• distinct_generator_count
• distinct_plant_count

Metric groups:

{
  "entities": [
    "distinct_generator_count",
    "distinct_plant_count"
  ],
  "ownership": [
    "percent_owned"
  ],
  "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: percent_owned, distinct_generator_count, distinct_plant_count.

Detail record fields returned when include_records is true:

• source_id
• record_kind
• sheet_name
• vintage_year
• source_record_key
• source_row_number
• eia_plant_id
• plant_name
• generator_id
• operator_id
• operator_name
• owner_id
• owner_name
• owner_city
• owner_state
• percent_owned
• percent_owned_unit
• state
• balancing_authority_code
• as_of
• raw_file_sha256
• citation
• balancing_authority_citation

Row-level citation fields:

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

Aggregate citation fields:

• source_id
• publisher
• source_url
• source_file
• source_member
• 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.asset_ownership.
2. Call describe_power_asset_ownership_v1 to inspect valid filters, groupings, metrics, and citation fields.
3. Call query_power_asset_ownership_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.