exascale.build
api ↗Connect

Docs → API reference

Power Interconnection Queue (PJM) API v1

Generated from core.contract.describe_power_interconnection_queue_pjm_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": [
      "requested_max_output_mw",
      "requested_summer_mw",
      "requested_winter_mw",
      "in_service_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:

Metric groups:

{
  "built_mw": [
    "in_service_mw"
  ],
  "records": [
    "source_record_count"
  ],
  "requested_mw": [
    "requested_max_output_mw",
    "requested_summer_mw",
    "requested_winter_mw"
  ]
}

Response summary fields:

Accepted fact policy:

Metric metadata:

Metric Category Unit Aggregation Additive Across Groups Authoritative Total Definition
requested_max_output_mw requested_mw MW sum true summary.totals.requested_max_output_mw The project's Maximum Facility Output (MFO) — the headline requested size, as PJM reports it.
requested_summer_mw requested_mw MW sum true summary.totals.requested_summer_mw The project's requested Capacity interconnection (summer net) MW — PJM's MW Capacity column.
requested_winter_mw requested_mw MW sum true summary.totals.requested_winter_mw The project's requested net winter MW — PJM's MW Energy column (a winter MW figure, not MWh).
in_service_mw built_mw MW sum true summary.totals.in_service_mw The realized built MW once the project is in service — PJM's MW In Service column.
source_record_count records count count source records true summary.totals.source_record_count Count of queued PJM projects in the current result scope (one atom = one PJM project).

Rollup rules:

Detail record fields returned when include_records is true:

Row-level citation fields:

Aggregate citation fields:

Codebooks

Field Coverage Codes Examples Note
status the distinct status values observed in the served PJM snapshot 12 Active = Active — a live request still in the queue (requested, not built), Withdrawn = Withdrawn — the request left the queue (the queue is withdrawn-dominated), In Service = In Service — the project is built and operating, Under Construction = Under construction, Partially in Service - Under Construction = Partially in service, still under construction ALWAYS scope by status — the full queue is dominated by Withdrawn requests. Active is the live pipeline of REQUESTED (not built) capacity; In Service / Under Construction / Partially in Service - Under Construction are built or building; Withdrawn / Retracted / Deactivated / Annulled / Canceled have left the queue. A queue-MW total is requested capacity, never built — for built/operating capacity use query_power_capacity_v1 (or the in_service_mw field).
fuel the distinct fuel values observed in the served PJM snapshot 10 Natural Gas = Natural gas, Solar = Solar, Wind = Wind, Storage = Storage (battery / other), Solar; Storage = Solar + storage hybrid (is_hybrid = true) Filter fuel by PJM's EXACT value — e.g. Natural Gas (NOT 'Gas', unlike MISO). Hybrids are ';'-joined (e.g. 'Solar; Storage') and flagged with is_hybrid. Values are as-reported, so a request with no fuel is null, not a category.
project_type the distinct project-type values observed in the served PJM snapshot 4 Generation Interconnection = Generation interconnection (GI), Merchant Transmission = Merchant transmission, Long-Term Firm Transmission = Long-term firm transmission (LTFT), Upgrade Request = Upgrade request (UR) The PJM queue mixes generation with transmission/upgrade requests. Filter project_type = Generation Interconnection for generation; the others are transmission/upgrade. (PJM's own data dictionary abbreviates these GI/TI/LTFT/UR, but the served values are the long forms observed in the data.)

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

Checked Examples

Agent question Request params Checked output
How much requested capacity and how many projects sit in the PJM queue, by status? {"group_by": ["status"]} pjm-queue-by-status.json
Which states have the most requested interconnection capacity in PJM's queue? {"group_by": ["state"], "order_by": "requested_max_output_mw", "top_n": 10} requested-mw-by-state.json
What fuels are the active PJM interconnection requests, and how much capacity? {"group_by": ["fuel"], "status": "Active"} active-requests-by-fuel.json
Return one PJM queue project with a row-level citation. {"include_records": true, "limit": 1, "state": "PA"} 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_pjm.
  2. Call describe_power_interconnection_queue_pjm_v1 to inspect valid filters, groupings, metrics, and citation fields.
  3. Call query_power_interconnection_queue_pjm_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 ↗