exascale.build
api ↗Connect

Docs → API reference

Power Interconnection Queue (CAISO) API v1

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

Capability

What It Can Answer

Represented Facts

Data Point Contract

Does not answer:

REST Surface

MCP Surface

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:

Group by:

Date range parameters:

Controls:

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": [
      "net_mw_to_grid",
      "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:

Metric groups:

{
  "net_mw": [
    "net_mw_to_grid"
  ],
  "records": [
    "source_record_count"
  ]
}

Response summary fields:

Accepted fact policy:

Metric metadata:

Metric Category Unit Aggregation Additive Across Groups Authoritative Total Definition
net_mw_to_grid net_mw MW sum true summary.totals.net_mw_to_grid The project's Net MWs to Grid, as CAISO reports it — the net export capacity of the request.
source_record_count records count count source records true summary.totals.source_record_count Count of CAISO queue projects in the current result scope (one atom = one project, across the Active/Completed/Withdrawn tabs).

Rollup rules:

Detail record fields returned when include_records is true:

Row-level citation fields:

Aggregate citation fields:

Codebooks

Field Coverage Codes Examples Note
application_status the distinct application_status values observed in the served CAISO snapshot 3 ACTIVE = Active — a live request still in the queue (requested, not built), COMPLETED = Completed — the project is built and in service (actual_online_date set), WITHDRAWN = Withdrawn — the request left the queue (the report is withdrawn-dominated) ALWAYS scope by application_status — the report is dominated by WITHDRAWN requests. ACTIVE is the live pipeline of REQUESTED (not built) capacity; COMPLETED is built and in service (carries an actual_online_date); WITHDRAWN left the queue. A queue-MW total is requested capacity, never built — for built/operating capacity use query_power_capacity_v1.
deliverability_status the distinct deliverability values observed in the served CAISO snapshot 3 Full Capacity = Full Capacity Deliverability Status, Partial Capacity = Partial Capacity Deliverability Status, Energy Only = Energy Only (no capacity deliverability) CAISO's deliverability is three-valued and first-class: Full Capacity and Partial Capacity count toward resource adequacy (with a TPD allocation), Energy Only does not. Filter by CAISO's EXACT value. This is a CAISO concept MISO/PJM do not carry.
fuel_1 the distinct primary-fuel values observed in the served CAISO snapshot 5 Battery = Battery storage, Solar = Solar photovoltaic, Wind Turbine = Wind, Natural Gas = Natural gas, Water = Hydro / pumped storage Filter fuel_1 by CAISO's EXACT value — e.g. Battery, Solar, Wind Turbine, Natural Gas. Hybrids carry a second/third Type/Fuel/MW triplet (fuel_2 / fuel_3) and are flagged with is_hybrid; filter on fuel_1 for the primary fuel. Values are as-reported, so a request with no fuel is null.

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

Checked Examples

Agent question Request params Checked output
How much net MW and how many projects sit in the CAISO queue, by lifecycle status? {"group_by": ["application_status"]} caiso-queue-by-status.json
Which states have the most active requested interconnection capacity in CAISO's queue? {"application_status": "ACTIVE", "group_by": ["state"], "order_by": "net_mw_to_grid", "top_n": 10} active-net-mw-by-state.json
What is the active CAISO pipeline split by deliverability (Full / Partial / Energy Only)? {"application_status": "ACTIVE", "group_by": ["deliverability_status"]} active-by-deliverability.json
Return one CAISO queue project with a row-level citation. {"include_records": true, "limit": 1, "state": "CA"} queue-detail-with-citation.json
Verify the raw workbook row behind a returned citation citations[ref].verify (aggregate) or records[0].citation (detail) source-row-evidence.json
Dogfood the tool sequence as an agent list -> describe -> query -> evidence agent-dogfood-transcript.json

The checked schema output is capability-schema.json.

Agent Workflow

  1. Call list_capabilities_v1 and select power.interconnection_queue_caiso.
  2. Call describe_power_interconnection_queue_caiso_v1 to inspect valid filters, groupings, metrics, and citation fields.
  3. Call query_power_interconnection_queue_caiso_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.
Generated from the tested API contract. Compare with the live capability map ↗