exascale.build

Reviewed 1d ago.

• tools: 66 tools scanned
• metadata: scanned

No findings.

Tools (66)

• list_capabilities_v1

  List available exascale.build data capabilities for agent discovery before querying. Also call this BEFORE stating that a capability is not available — client tool lists are cached and this surface grows; anything listed here is reachable via query_capability_v1 even if your tool list predates it.

• get_source_evidence_v1

  Fetch and hash-verify the raw source row behind a returned citation. Pass a citation object inside `params`. Two ready-to-pass shapes come straight from the query tools: each aggregate row's `citations[ref].verify` object, or a detail record's `citation` (from include_records). Either proves the number with no re-query. The tool verifies the raw workbook SHA-256 before returning source-header row values. Use this when an agent must prove an answer from the underlying source row.

• describe_capability_v1

  Describe any served capability by name — the generic twin of the named describe tools. Pass `capability` as either a capability id from list_capabilities_v1 (e.g. "power.capacity") or a query primitive name (e.g. "query_power_capacity_v1"). Returns the same schema payload as the named describe tool: valid filters, groupings, metrics, detail fields, and citation fields. Use the generic pair (this + query_capability_v1) when list_capabilities_v1 names a capability that has no named tool in your client's tool list — clients cache tool lists, and capabilities shipped after that cache are still fully reachable here.

• query_capability_v1

  Query any served capability by name — the generic twin of the named query tools, reaching every capability including ones newer than your client's cached tool list. Pass `capability` as either a capability id from list_capabilities_v1 (e.g. "power.price_ercot") or a query primitive name (e.g. "query_power_price_ercot_v1"), and `params` as the same flat JSON object the named query tool accepts — call describe_capability_v1 first for valid filters, e.g. {"capability": "power.capacity", "params": {"state": "TX", "group_by": ["energy_source_code"]}}. Returns the identical cited envelope as the named tool: same rows, same citations, same as_of.

• describe_power_capacity_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for power.capacity.

• query_power_capacity_v1

  Query verified U.S. generator-level operating, planned, retired, or canceled power capacity from EIA-860M. Use this for capacity questions by state/jurisdiction, county FIPS, source-reported balancing authority code, fuel, prime mover, technology, lifecycle, or year. Pass filters inside the `params` object. The operating/planned/retired/canceled selector is `lifecycle` (e.g. `lifecycle: "operating"`, the default) — there is no `status` or `status_group` parameter. Returns JSON aggregates with citations and optional generator-level records when `include_records` is true. Does not determine electricity supplied, generation MWh, real-time dispatch, capacity factor, battery storage throughput/duration, demand/load, prices, data-center load, or transmission deliverability. For capacity REQUESTED in an ISO interconnection queue (projects pending interconnection, not yet built), use the relevant ISO's queue tool: query_power_interconnection_queue_v1 (MISO), query_power_interconnection_queue_

• describe_power_generation_v1

  Describe valid filters, groupings, atoms, metrics, detail fields, and citation fields for power.generation.

• query_power_generation_v1

  Query verified U.S. monthly net electricity generation (MWh) from EIA-923. Use this for "how much was generated" questions by state, source-reported balancing authority code, fuel, prime mover, sector, plant, or generator, for a given month. For a fuel total or a fuel mix (e.g. "coal generation", "top fuels"), filter or group by `fuel_group` — it sums the several energy_source_code values a fuel spans (coal alone is 6 codes), so a total is correct-by-construction; use the raw `energy_source_code` only when you want one exact as-reported code, since it splits coal/biomass across sub-codes. Select one `atom`: `by_fuel` (default — the complete plant total) or `by_generator` (generator-level, joinable to EIA-860M); never sum across atoms. History runs monthly from 2014-01 onward and is served by default: a bare `data_month` anywhere in that window answers from the newest promoted vintage covering it, and the response `as_of` is that knowledge cut (pin `as_of` to any date to reproduce what

• describe_power_asset_ownership_v1

  Describe annual EIA-860 ownership filters, convention, metrics, and exact-cell citations.

• query_power_asset_ownership_v1

  Query verified annual EIA-860 generator ownership. Returns the Owner schedule's raw owner names and ownership shares for each `eia_plant_id` + `generator_id`. `percent_owned` is the workbook's raw fraction of one (0.6 = 60%), not a whole-number percent. Filter by plant, generator, exact raw owner name, state, owner state, annual vintage, or source-reported balancing authority code; `{"state":"TX","balancing_authority_code":"ERCO"}` returns an ERCOT slice in one call. Owner-name matching is exact and intentionally performs no normalization or entity resolution. Critical EIA convention: the Owner schedule contains only jointly owned generators and generators wholly owned by an entity other than the operator. A generator absent from it is wholly owned by the operator in that same annual EIA-860 Generator schedule. An exact plant+generator query exposes this as `ownership_resolution`; it does not fabricate an Owner row or a 1.0 source share. Annual vintages remain independently queryable

• describe_power_fuel_cost_v1

  Describe EIA-923 receipt/cost filters, raw units, missing semantics, and exact-cell citations.

• query_power_fuel_cost_v1

  Query verified raw EIA-923 fuel receipts and delivered fuel costs. Returns one Page 5 Fuel Receipts and Costs row per published receipt: plant/month, fuel, supplier, purchase type, source physical quantity, and delivered cost in EIA's stated cents/MMBtu. Filter by plant, month/range, exact source strings, state, fuel, cost status, or source-reported balancing authority code; `{"state":"TX","balancing_authority_code":"ERCO"}` returns an ERCOT slice in one call. Quantity units remain fuel-specific (short tons, barrels, or Mcf). EIA withholds costs for some plants. The raw `.` marker is preserved in `fuel_cost_raw`, the numeric cost is null, and `fuel_cost_status` explicitly reports `withheld` for unregulated receipts. Missing is never zero or imputed. This tool does not derive heat rates, efficiency, marginal cost, generation cost, or $/MWh; combine the cited raw atoms outside exascale.build if analysis requires those judgments. Every quantity or cost can be verified against its exact

• describe_power_plant_costs_v1

  Describe native-XBRL Form 1 plant-cost facts, units, coverage, and exact-fact citations.

• query_power_plant_costs_v1

  Query accepted native-XBRL FERC Form 1 large-steam plant facts. Returns one separately cited XBRL fact per respondent, report year, raw plant name, and source concept: installed capacity, net generation, plant-cost balance items, fuel expense, and individual operation and maintenance lines. Values and units are as filed; nominal dollars are not adjusted, allocated, divided by generation, or combined into a derived O&M total. Plant names remain raw strings with no EIA ID matching. Every value verifies against its exact archive member, XBRL fact ID, context, concept, and SHA-256. Coverage is the Form 1 filing population, not the full fleet. ERCOT-only merchant entities largely do not file, so ERCOT coverage is partial and plant absence means not present in served filings—not zero. `ercot_relevance=true` is a one-call filter based only on the respondent's raw states-served disclosure mentioning Texas; it is not a plant-location claim. v0 covers accepted native XBRL (report year 2021 onw

• describe_natural_gas_prices_v1

  Describe the EIA Henry Hub and state electric-power gas-price atoms, units, aggregate grain, missingness, vintages, and citations.

• query_natural_gas_prices_v1

  Query verified EIA natural-gas price records from two public series. `atom="henry_hub_daily_spot"` returns one trading-day Henry Hub spot price in EIA's published $/MMBtu unit (series RNGWHHD). `atom="state_electric_power_monthly"` returns one state-month average price paid by electric-power consumers in EIA's published $/Mcf unit; `{"atom":"state_electric_power_monthly","state":"TX"}` is the Texas power-sector proxy slice in one call. Filter either atom by `date`, `date_from`/`date_to`, series, state, or price status. The state series is an aggregate of what the state's power sector paid that month, not a plant-level fact. EIA null values remain explicit `price=null` records with `price_status="source_missing"`—never zero or imputed. The two source units are never converted or blended; mixed-unit avg/min/max are null. This tool does not assign proxies to plants or derive heat rates, $/MWh, spark spreads, or any ratio. API revisions are preserved as immutable capture vintages selecte

• describe_power_demand_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for power.demand.

• query_power_demand_v1

  Query verified U.S. hourly electricity demand (MW) by balancing authority from EIA-930. Use this for "how much load" questions at the hourly balancing-authority grain: filter or group by `balancing_authority_code`, `region`, `data_date` (or the `data_date_from`/`data_date_to` range), `hour_number`, `datetime_utc`, or `is_imputed`. Pass filters inside the `params` object. Returns JSON aggregates with citations and optional row-level records when `include_records` is true. `demand_mw` is EIA's own cleaned (Adjusted) series, with receipts: the as-reported `demand_mw_raw` and the `is_imputed` flag ride every detail record. `demand_forecast_mw` is the same row's day-ahead forecast, so forecast-vs-actual misses need no second query. History runs hourly from 2015-07-01 onward and is served by default: a bare `data_date` anywhere in that window answers from the newest promoted vintage covering it, and the response `as_of` is that knowledge cut. A query with NO calendar window (no `data_date`,

• describe_power_demand_rollup_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for power.demand_rollup.

• query_power_demand_rollup_v1

  Query verified U.S. hourly electricity demand (MW) as EIA's own published national and regional totals from the EIA Grid Monitor (region-data). Use this for "how much load for the whole country, or a region" questions. Filter by `respondent` (US48 = the Lower-48 national total, or one of the 13 EIA regions — CAL, CAR, CENT, FLA, MIDA, MIDW, NE, NW, NY, SE, SW, TEN, TEX), `data_date` (one day) or the `data_date_from`/`data_date_to` range, and `hour_number`. To pin one specific UTC hour, combine `data_date` + `hour_number`. Group by any of `respondent`, `respondent_level` (national vs region), `data_date`, `hour_number`, or `datetime_utc`. `datetime_utc` and `respondent_level` are grouping/output axes only — not filters. Pass each parameter as a top-level key of `params` (flat — not nested under a `filter`, `filters`, or `where` key). Example: `{"respondent": "US48", "data_date": "2026-06-10", "hour_number": 14}` for the US48 total at one hour; add `"group_by": ["datetime_utc"]` over a

• describe_power_retail_sales_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for power.retail_sales.

• query_power_retail_sales_v1

  Query verified U.S. annual retail electricity sales — billed MWh, revenue, and customer counts — by utility, state, and customer sector from EIA-861. Use this for "who sold how much power to whom" questions at the annual utility×state×sector grain: filter or group by `data_year`, `state`, `sector` (residential / commercial / industrial / transportation), `part`, `service_type`, `ownership`, `ba_code`, `data_type`, `eia_utility_id`, or `utility_name`. Pass filters inside the `params` object. Returns JSON aggregates with citations down to the exact stacked sector/measure cell, and optional row-level records when `include_records` is true. Defaults keep totals faithful: the in-row `total` sector block is excluded unless named explicitly (it duplicates the four sectors); EIA's state-level Adjustment (99999) and Withheld (88888) sentinel rows stay in state totals but are auto-excluded from any utility-keyed query; territories are excluded unless `included_in_default_us_metrics` is false. A

• describe_power_interconnection_queue_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue.

• query_power_interconnection_queue_v1

  Query the MISO generator interconnection queue — the public waiting line of projects that have REQUESTED to connect to the MISO grid (the 15-state Midwest/South footprint). Returns cited, project-level records: requested megawatts (net summer / net winter), location (`state`, `county`, derived `county_fips`), fuel and technology as MISO reports them, three independent status dimensions (`application_status`, `study_phase`, `post_gia_status`), and queue / withdrawn / in-service dates. Group or filter by `state`, `county_fips`, `application_status`, `study_phase`, `post_gia_status`, `fuel_type`, `facility_type`, `service_type`, `study_group`, `study_cycle`, or `is_hybrid`; filter `queue_date` by the `queue_date_from` / `queue_date_to` range. Pass each parameter as a top-level key of `params` (flat — not nested). Example: `{"state": "IN", "fuel_type": "Solar", "application_status": "Active"}` for active solar requests in Indiana; `{"group_by": ["application_status"]}` for requested MW an

• describe_power_interconnection_queue_pjm_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_pjm.

• query_power_interconnection_queue_pjm_v1

  Query the PJM New Services (interconnection) queue — the public waiting line of projects that have REQUESTED to connect to the PJM grid (the mid-Atlantic RTO incl. Northern Virginia, PA, NJ, MD, OH, VA, WV and more). Returns cited, project-level records with PJM's full published structure: requested megawatts (`requested_max_output_mw` = MFO, `requested_summer_mw` = MW Capacity / summer net, `requested_winter_mw` = MW Energy / winter net), the realized built `in_service_mw` for completed projects, location (`state`, `county`, derived `county_fips`), `fuel` and `project_type` as PJM reports them, the single as-reported `status`, the study-document URLs and per-stage statuses, and lifecycle dates. Group or filter by `state`, `county_fips`, `status`, `project_type`, `capacity_or_energy`, `fuel`, `project_ac_dc`, `transmission_owner`, the study statuses, or (group only) `is_hybrid`; filter `submitted_date` by the `submitted_date_from` / `submitted_date_to` range. Pass each parameter as a

• describe_power_interconnection_queue_pjm_cycle_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_pjm_cycle.

• query_power_interconnection_queue_pjm_cycle_v1

  Query PJM's cluster/cycle service-request grid — the cluster view of PJM's interconnection process: the TC1/TC2 transition cycles (re-processing the pre-Order-2023 serial backlog) and the reopened steady-state cycles (C01+, the new intake). A SEPARATE PJM publication from the full New Services queue (query_power_interconnection_queue_pjm_v1) — richer per-project cluster detail; the two share rows and are never combined. Returns cited, project-level records with PJM's full cluster schema: the cluster `cycle` (TC1 / TC2 / C01 …) and `stage` (phase / decision point), the `developer`, requested megawatts (`requested_max_output_mw` = MFO, `requested_summer_mw`, `requested_winter_mw`), the realized built `in_service_mw`, long-term-firm transmission `ltf_mw`, location (`state`, `county`, derived `county_fips`), `fuel` and `project_type` as PJM reports them, the single `status`, and the phased System-Impact-Study report URLs + statuses. Group or filter by `cycle`, `stage`, `status`, `state`,

• describe_power_interconnection_queue_caiso_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_caiso.

• query_power_interconnection_queue_caiso_v1

  Query the CAISO generator interconnection queue — California ISO's public Public Queue Report, the waiting line of projects that have REQUESTED to connect to the CAISO grid (California, plus the out-of-state edges it studies: NV, AZ). Returns cited, project-level records with CAISO's full published structure: the net megawatts to grid (`net_mw_to_grid`, CAISO's own headline figure) and the per-component Type/Fuel/MW triplets for hybrids (`type_1..3`, `fuel_1..3`, `mw_1..3`, plus an `is_hybrid` flag), the as-reported `application_status`, the cluster `study_process` (C01..C14, plus serial/legacy tracks), the three-valued deliverability status (`deliverability_status` = Full Capacity / Partial Capacity / Energy Only) with `tpd_allocation_percentage` / `tpd_allocation_group` / `offpeak_deliverability`, location (`state`, `county`, derived `county_fips`, `utility`, `pto_study_region`), the per-phase study statuses, and lifecycle dates (`ir_receive_date`, `queue_date`, `proposed_online_dat

• describe_power_interconnection_queue_nyiso_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_nyiso.

• query_power_interconnection_queue_nyiso_v1

  Query the NYISO generator + load interconnection queue — New York ISO's public waiting line of projects that have REQUESTED to connect to the New York grid. Uniquely among ISOs, NYISO publishes a Load Projects tab — load interconnection requests (large-load demand), served as-reported — and since its 2026-07 edition tags each load request with its own `End-Use` class (`end_use`, e.g. DAT / DAT-AI / DAT-CM, served verbatim). Returns cited, project-level records with NYISO's full published structure across every lifecycle tab (nine tabs through 2026-06; seven since NYISO's 2026-07 restructure): summer and winter peak megawatts kept SEPARATE (`sp_mw` = SP, the max summer output; `wp_mw` = WP, the max winter output), the Load Projects tab's `peak_mw_load` with NYISO's own `end_use` class and `sis_bundle` study-batch code (both 2026-07 onward, null before), the as-reported study-phase code (`study_status_code` — NYISO's numeric key, labeled `S` through 2026-06 and `Project Status #` / `NYI

• describe_power_interconnection_queue_isone_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_isone.

• query_power_interconnection_queue_isone_v1

  Query the ISO-NE generator interconnection queue — ISO New England's public IRTT "public queue" report, the waiting line of projects that have REQUESTED to connect to the New England grid (CT, MA, ME, NH, RI, VT). Returns cited, project-level records with ISO-NE's full published structure (all 31 columns of the rendered report): the three megawatt readings kept SEPARATE (`net_mw`, `summer_mw` = max summer output, `winter_mw` = max winter output — `net_mw` is 0 for the many Capacity-Network-Resource-only requests, a real value, not missing), the request `request_type` (G = Generation / ETU = Elective Transmission Upgrade / TS = Transmission Service), the space-delimited multi-value `fuel_type` (EIA energy-source codes, e.g. "SUN BAT"), the `unit_type` and service code `serv` (CNR = Capacity Network Resource / NR = Network Resource), the `jurisdiction` (F = FERC / N = Non-FERC), the ISO-NE load `zone`, the per-stage study statuses (`fs_status` … `ia_status`) with their study-document li

• describe_power_interconnection_queue_ercot_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_ercot.

• query_power_interconnection_queue_ercot_v1

  Query the ERCOT generator interconnection queue — ERCOT's public GIS Report (EMIL PG7-200-ER), the waiting line of generation projects that have REQUESTED to connect to the ERCOT (Texas) grid. Returns cited, project-level records with ERCOT's full published structure across four lifecycle sheets (Large Gen + Small Gen = active; Inactive Projects; Cancellation Update): the requested `capacity_mw` (ERCOT publishes ONE capacity figure — no summer/winter split), the ERCOT `fuel` and `technology` codes (e.g. SOL/PV solar, OTH/BA battery, GAS/CC combined-cycle, WIN/WT wind — HYD is HYDROGEN, hydro is WAT), the `cdr_reporting_zone` (NORTH/SOUTH/WEST/COASTAL/HOUSTON/PANHANDLE), the `interconnecting_entity`, the `poi_location`, the composite `gim_study_phase` token string, and the milestone dates (`screening_study_started`, `fis_approved`, `ia_signed`, `construction_start`/`construction_end`, `approved_for_energization`/`approved_for_synchronization`, `projected_cod`). Group or filter by `appl

• describe_power_interconnection_queue_spp_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_spp.

• query_power_interconnection_queue_spp_v1

  Query the SPP generator interconnection queue — Southwest Power Pool's public GI Summary report, the waiting line of generation projects that have REQUESTED to connect to the SPP grid (the ~14-state central-US RTO: OK, KS, TX panhandle, NE, NM, MO, CO, ND, SD, AR, LA and more). Returns cited, project-level records with SPP's full published structure: the requested `capacity_mw` (SPP's headline `Capacity` figure) PLUS five other labeled MW columns SPP publishes — `max_summer_mw`, `max_winter_mw`, `requested_max_injection_mw`, `requested_nrd_mw`, `nameplate_capacity_mw` — served separately and NEVER blended; the `generation_type` (Wind / Solar / Battery/Storage / Thermal / Hybrid / Hydro — SPP encodes hybrids natively as `Hybrid`, so no is-hybrid is invented) and free-text `fuel_type` (slash-delimited combos like `Solar/Storage` kept whole); the study `current_cluster` (e.g. `DISIS-2024-001`, `Surplus`, `RTOE Transitional Cluster`) and regional `cluster_group` (`01 NORTH` … `05 SOUTHWES

• describe_power_price_ercot_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for power.price_ercot.

• query_power_price_ercot_v1

  Query verified ERCOT wholesale electricity prices — ERCOT's Day-Ahead Market Settlement Point Prices ($/MWh, EMIL NP4-190-CD), the price cleared the day before each operating day at every ERCOT (Texas) settlement point, served hourly. Returns cited prices for each (`settlement_point`, `delivery_date`, `hour_ending`): the per-hour `price_usd_per_mwh` in detail records, plus `avg_price_usd_per_mwh`, `min_price_usd_per_mwh`, and `max_price_usd_per_mwh` over the result scope. Each `settlement_point` is one of ERCOT's locations — a trading Hub (e.g. `HB_NORTH`, `HB_HOUSTON` — the regional benchmark prices), a Load Zone (e.g. `LZ_HOUSTON`), a Resource Node (one generator's connection point), or a DC-tie — and `settlement_point_type` carries ERCOT's OWN verbatim classification code (`HU`/`LZ`/`RN`/`LZ_DC` and finer codes) so an agent can tell a regional benchmark from a single-plant node. Filter or group by `settlement_point`, `settlement_point_type`, `hour_ending`, or `delivery_date`; filte

• describe_power_capacity_accreditation_pjm_v1

  Describe PJM ELCC document identities, class dimensions, metrics, and citations.

• query_power_capacity_accreditation_pjm_v1

  Query cited PJM marginal ELCC class ratings by document kind, auction, delivery year, and resource class. Preliminary, final, and incremental-auction documents remain separate; no value is preferred or reconciled. Requires an API key ($49/mo or $490/yr, 7-day full refund, at https://exascale.build/pro) while the source's redistribution terms are under review. This data point is not included in the 25 free queries.

• describe_power_capacity_market_pjm_v1

  Describe PJM RPM delivery-year/LDA filters, UCAP metrics, and citations.

• query_power_capacity_market_pjm_v1

  Query cited PJM Base Residual Auction UCAP clearing prices, RTO cleared MW, reliability requirement, and published administrative price collar by delivery year and LDA. Requires an API key ($49/mo or $490/yr, 7-day full refund, at https://exascale.build/pro) while the source's redistribution terms are under review. This data point is not included in the 25 free queries.

• describe_power_capacity_accreditation_miso_v1

  Describe MISO accreditation document kinds, resource classes, ratios, suppressions, and citations.

• query_power_capacity_accreditation_miso_v1

  Query cited MISO Schedule 53 class-average and indicative-DLOL seasonal accreditation ratios, including published unit counts, storage variants, and explicit suppression atoms. Requires an API key ($49/mo or $490/yr, 7-day full refund, at https://exascale.build/pro) while the source's redistribution terms are under review. This data point is not included in the 25 free queries.

• describe_power_capacity_market_miso_v1

  Describe MISO PRA planning-year, season, zone, parameter, and citation fields.

• query_power_capacity_market_miso_v1

  Query cited MISO Planning Resource Auction seasonal zonal ACP, verbatim ERZ values, published CONE parameters, and IMM conduct thresholds. Requires an API key ($49/mo or $490/yr, 7-day full refund, at https://exascale.build/pro) while the source's redistribution terms are under review. This data point is not included in the 25 free queries.

• describe_ai_infrastructure_construction_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for ai_infrastructure.construction.

• query_ai_infrastructure_construction_v1

  Query verified U.S. private construction spending ($ millions) for data centers and semiconductor/computer-electronics manufacturing plants, from the U.S. Census Bureau's Value of Construction Put in Place (C30). Use this for "how much is being spent BUILDING data centers (or chip fabs) in the US" questions — the construction buildout in dollars, not capacity or investment. Filter by `category` ("data_center" — Census's named subcategory under Office; or "computer_electronic_electrical" — the semiconductor/computer-electronics manufacturing line under Manufacturing), `basis` ("seasonally_adjusted" = a seasonally-adjusted ANNUAL RATE, or "not_seasonally_adjusted" = the NOT-adjusted MONTHLY LEVEL), `data_month` (one month, ISO first-of-month e.g. "2026-04-01") or the `data_month_from`/`data_month_to` range, `year`, and `revision_status` ("preliminary", "revised", or "final"). Group by any of `category`, `basis`, `data_month`, `year`, or `revision_status`. Pass each parameter as a top-le

• describe_ai_infrastructure_trade_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for ai_infrastructure.trade.

• query_ai_infrastructure_trade_v1

  Query verified U.S. monthly IMPORTS of integrated circuits (HS-8542) — customs value (USD) by country of origin — from the U.S. Census Bureau's International Trade data. Use this for "how much $ of chips did the US import (from Taiwan / South Korea / in total) and how is it trending" questions. HS-8542 is ALL integrated circuits (processors, memory, amplifiers, parts) — NOT AI-accelerator / GPU-specific. Filter by `country` (the verbatim Census name, e.g. "TAIWAN", "KOREA, SOUTH"), `cty_code` (the Census country code, e.g. "5830"), `country_level` ("total" = the all-countries TOTAL, "country" = an individual country, "grouping" = a Census bloc/continent like ASIA / APEC / EU), `year`, `data_month` (one month, ISO first-of-month e.g. "2026-04-01") or the `data_month_from`/`data_month_to` range. Group by any of `country`, `cty_code`, `country_level`, `data_month`, or `year`. Pass each parameter as a top-level key of `params` (flat — not nested under a `filter`, `filters`, or `where` key

• describe_ai_infrastructure_equipment_trade_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for ai_infrastructure.equipment_trade.

• query_ai_infrastructure_equipment_trade_v1

  Query verified U.S. monthly IMPORTS of semiconductor-manufacturing EQUIPMENT (HS-8486) — customs value (USD) by country of origin — from the U.S. Census Bureau's International Trade data. Use this for "is the fab buildout actually tooling up, and who supplies the machines" questions — the equipment leg of the fab lifecycle: construction spending (ai_infrastructure.construction) measures the shell, this measures the tools flowing in, and chip imports (ai_infrastructure.trade) measure the output side. HS-8486 covers machines and apparatus used solely or principally to MANUFACTURE semiconductor boules/wafers, devices, and integrated circuits — AND flat-panel displays (Census does not split them at this level); it is NOT the chips themselves (those are HS-8542). Filter by `country` (the verbatim Census name, e.g. "JAPAN", "NETHERLANDS", "KOREA, SOUTH"), `cty_code` (the Census country code), `country_level` ("total" = the all-countries TOTAL, "country" = an individual country, "grouping" =

• describe_ai_infrastructure_production_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for ai_infrastructure.production.

• query_ai_infrastructure_production_v1

  Query verified U.S. semiconductor & electronic-component PRODUCTION and CAPACITY UTILIZATION — the Federal Reserve's monthly G.17 industrial-production index (2017=100) and capacity-utilization rate (percent) for NAICS 3344 — from the Board's own release, history to 1972. Use this for "are the domestic fabs actually producing / how hot are they running" questions — the OUTPUT leg of the fab lifecycle: construction spending (ai_infrastructure.construction) measures the shell, equipment imports (ai_infrastructure.equipment_trade) the tools flowing in, chip imports (ai_infrastructure.trade) what crosses the border; this measures domestic production and how much of the installed capacity is in use. NAICS 3344 is "semiconductor and OTHER electronic component" manufacturing — the finest split the Fed publishes here (broader than semiconductors alone, and NOT the same slice as QCEW's 334413). Filter by `series_kind` ("ip" = the production index, on both bases; "capacity_utilization" = percen

• describe_robotics_trade_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for robotics.trade.

• query_robotics_trade_v1

  Query verified U.S. monthly IMPORTS of INDUSTRIAL ROBOTS — customs value (USD) AND unit counts (number of robots) — by country of origin, from the U.S. Census Bureau's International Trade data. Use this for "how many robots is the US importing, from whom, and what are they worth" questions — the only high-frequency official U.S. robotics series. Covers the nomenclature's two robot-specific HS-10 codes, served as the `commodity` dimension: "8479500000" (INDUSTRIAL ROBOTS, NESOI — multipurpose: welding/assembly arms, AMRs) and "8428700000" (INDUSTRIAL ROBOTS FOR LIFTING, HANDLING, LOADING OR UNLOADING — created by HS 2022; no data before 2022-01, a structural absence, never zero). Filter by `commodity`, `country` (the verbatim Census name, e.g. "JAPAN", "CHINA", "KOREA, SOUTH"), `cty_code` (the Census country code), `country_level` ("total" = the all-countries TOTAL, "country" = an individual country, "grouping" = a Census bloc/continent like ASIA / APEC / EU), `year`, `data_month` (one

• describe_robotics_adoption_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for robotics.adoption.

• query_robotics_adoption_v1

  Query the verified share of US manufacturing plants USING industrial robots — plus workers exposed and robotics capex — from the Census Industrial Robotic Equipment product (the first official federal robotics-adoption statistics). Use this for "are factories actually adopting robots" questions — the INSTALLED-BASE reading the import data cannot see. Serves the percent of plants with robots and the percent of employees at plants with robots (both published as FRACTIONS of 1: 0.121 = 12.1%), Census's demeaned variants, and capital expenditures for robotic equipment ($1000) — by manufacturing industry (`naics_code`, 2/3-digit), by `state`, and by `plant_size` band. Filter by `edition` ("asm_2018_2021" = the ASM annual series; "ec_2022" = the 2022 Economic Census), `table` (the workbook sheet — exactly one of: "Percent of... NAICS", "Percent of... Geo", "Percent of... Geo demean", "Robot adopters vs not", "Robot adoption and plant size", "CapEx... NAICS", "CapEx... Geo", "CapEx and plant

• describe_space_satellite_filings_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for space.satellite_filings.

• query_space_satellite_filings_v1

  Query the verified FCC satellite licensing docket — every space-station (SAT) filing in the FCC's own daily IBFS database dump, back to the 1960s — by applicant, application type, status, and filing date. Use this for "who is authorized to operate what in orbit, what has been filed, and where does each filing stand" questions — the satellite-buildout licensing pipeline. Each filing carries the FCC's public filing key (`file_number`, e.g. "SATLOA2025061800149"), the `callsign` (e.g. "S3069" = SpaceX Gen2), the application type and status in the FCC's OWN vocabulary — verbatim codes plus the FCC's own decode text from the same dump vintage (`app_type_code` "LOA" = Launch and Operating Authority, "STA" = Special Temporary Authority, "MOD" = Modification; `status_code` "A/C" = Action Complete, "ATPN" = Action Taken Public Notice — codebooks in describe) — the full lifecycle date family (filed / granted / expires / …), the FCC's plain-English `description` of the filing, and the applicant

• describe_space_satellite_notices_v1

  Describe valid filters, groupings, metrics, detail fields, and citation fields for space.satellite_notices.

• query_space_satellite_notices_v1

  Query the FCC Space Bureau's weekly satellite public notices since the ICFS cutover (2025-06-18) — every satellite application the FCC accepted for filing and every action it took (grants, partial grants, dismissals, surrenders), as printed. Use this for "what satellite filings has the FCC received or acted on since mid-2025" questions — the current licensing pipeline, which the pre-cutover docket (query_space_satellite_filings_v1) does not carry. Each record is one listing of a filing in one notice: the notice (`report_number` e.g. "SAT-02040", `notice_kind` "Applications Accepted for Filing" or "Actions Taken", `release_date`), the FCC `file_number` (e.g. "SAT-MOD-20260603-00225") and its `filing_type_code` (LOA, MOD, STA, AMD, T/C…), the `call_sign`, the `applicant` as printed (e.g. "Space Exploration Holdings, LLC"), the printed `date_filed` and `filing_type`, on Actions Taken notices the `action` (e.g. "Grant of Authority") and `action_date`, and the entry's full text as printed

• describe_capacity_factor_v1

  Describe capacity factor: net generation / (operating nameplate × hours), joined across EIA-860M and EIA-923.

• query_capacity_factor_v1

  Query verified U.S. capacity factor — how hard a fleet actually runs — by joining EIA-860M capacity and EIA-923 generation. Requires `data_month`: one ISO month start, e.g. "2026-01-01". If the user names no month, ask which one (or state the month you chose); if a month is not covered, the error lists the months that are — do not retry blindly. capacity_factor = net generation (MWh) / (operating nameplate capacity (MW) × hours in the month), computed over plant×fuel present in BOTH sources, so scope is auto-aligned. Optional `group_by` of `state` and/or `fuel_group`, and `state`/`fuel_group` filters. Returns the capacity factor per group with its generation and capacity, a `coverage` declaration (what share of in-scope capacity/generation matched), and a citation to BOTH the capacity and the generation source row. Basis is nameplate; storage is excluded; the capacity snapshot is matched to the month. Does not determine per-generator capacity factor, a net-summer/winter basis, or mon