{ "agent_answer": { "answer": "The FCC's notice SAT-02040 (2026-09-25) lists SAT-RPL-20260727-00312 \u2014 Replacement Satellite Application (no new frequency bands), filed 2026-09-03 by Sirius XM Radio LLC \u2014 as of 2026-09-27, cited to its line in the notice text.", "citation": { "as_of": "2026-09-27", "file_number": "SAT-RPL-20260727-00312", "raw_file_sha256": "3da714e4ddea2f246d8eaaf3b84e992cd37e20b187038ee73b834c8e8699b868", "sheet": "DOC-425356A1", "source_file": "sat_notices_sample.json", "source_id": "space.fcc.sat_public_notices", "source_row": 45, "source_url": "https://docs.fcc.gov/public/attachments/DOC-425356A1.txt" }, "question": "Which satellite application in an FCC public notice can be verified back to the printed notice?", "verification": { "hash_verified": true, "raw_file_sha256": "3da714e4ddea2f246d8eaaf3b84e992cd37e20b187038ee73b834c8e8699b868", "sheet": "DOC-425356A1", "source_file": "sat_notices_sample.json", "source_row": 45 } }, "goal": "Use the agent-facing tool contract to discover, query, and verify space.satellite_notices.", "steps": [ { "params": {}, "result": { "capabilities": [ { "access": "open", "anchors": [ "county_fips", "state", "lat", "lon", "eia_plant_id", "generator_id", "balancing_authority_code" ], "answers": [ "operating generator capacity by location, fuel, technology, and source-reported balancing authority code", "planned generator capacity by location, fuel, technology, source-reported balancing authority code, and planned online year", "retired generator capacity by location, fuel, technology, source-reported balancing authority code, and retirement year" ], "current_sources": [ "energy.eia.eia860m" ], "id": "power.capacity", "primitive": "query_power_capacity_v1", "product_spec": "blocks/power_capacity/card.md", "represented_facts": [ "EIA-860M reports operating generator capacity by location, fuel, technology, status, and source-reported balancing authority code", "EIA-860M reports planned generator capacity by location, fuel, technology, status, source-reported balancing authority code, and planned online year", "EIA-860M reports retired generator capacity by location, fuel, technology, status, source-reported balancing authority code, and retirement year" ], "status": "available", "title": "Power Capacity" }, { "access": "open", "anchors": [ "eia_plant_id", "state", "balancing_authority_code", "generator_id" ], "answers": [ "monthly net generation (MWh) by plant, prime mover, and fuel", "monthly net generation (MWh) by individual generator, joinable to EIA-860M", "generation mix by state, balancing-authority code, and fuel over time", "total and electric-only fuel consumption (MMBtu), aligned to Page 1 net generation across the served 2014-to-present history" ], "current_sources": [ "energy.eia.eia923" ], "id": "power.generation", "primitive": "query_power_generation_v1", "product_spec": "blocks/power_generation/card.md", "represented_facts": [ "EIA-923 reports monthly net electricity generation (MWh) by plant, prime mover, and fuel (Page 1)", "The same Page 1 source row reports total fuel consumed and fuel consumed for electricity separately in MMBtu", "EIA-923 reports monthly net electricity generation (MWh) by individual generator (Page 4), joinable to EIA-860M" ], "status": "available", "title": "Power Generation" }, { "access": "open", "anchors": [ "state", "eia_plant_id", "generator_id", "balancing_authority_code" ], "answers": [ "raw annual EIA-860 owner names and fractional ownership shares by plant and generator", "ownership rows for a raw owner-name string, with no name normalization or entity matching", "same-vintage state and source-reported balancing-authority slices, including ERCO", "the explicit EIA default that absence from the Owner schedule means wholly owned by the operator" ], "current_sources": [ "energy.eia.eia860_owner" ], "id": "power.asset_ownership", "primitive": "query_power_asset_ownership_v1", "product_spec": "blocks/power_asset_ownership/card.md", "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." ], "status": "available", "title": "Power Asset Ownership" }, { "access": "open", "anchors": [ "state", "eia_plant_id", "balancing_authority_code" ], "answers": [ "raw receipt-level delivered fuel costs in cents per MMBtu and physical quantities", "receipt rows by plant, month, fuel, state, supplier, purchase type, or source-reported balancing authority", "explicit counts and records for reported versus withheld fuel costs" ], "current_sources": [ "energy.eia.eia923_receipts_cost" ], "id": "power.fuel_cost", "primitive": "query_power_fuel_cost_v1", "product_spec": "blocks/power_fuel_cost/card.md", "represented_facts": [ "EIA-923 Page 5 reports individual fossil-fuel receipts by plant and month, including raw physical quantity and delivered fuel cost in cents per MMBtu. Confidential or otherwise unpublished costs remain explicit missing values; they are never zero-filled, imputed, or converted into heat rates or $/MWh.", "Withheld EIA fuel-cost cells are explicit nulls with the raw marker preserved." ], "status": "available", "title": "Power Fuel Receipts and Costs" }, { "access": "open", "anchors": [], "answers": [ "as-filed large-steam plant capacity, net generation, plant balances, fuel expense, and separate O&M line items", "raw respondent and plant-name searches without normalization or EIA matching", "which Form 1 respondents and raw plant names have served data for a report year", "a one-call ERCOT-relevance slice based only on the respondent's raw states-served disclosure" ], "current_sources": [ "energy.ferc.form1_plant_costs" ], "id": "power.plant_costs", "primitive": "query_power_plant_costs_v1", "product_spec": "blocks/power_plant_costs/card.md", "represented_facts": [ "Accepted native-XBRL FERC Form 1 filings report as-filed large steam-electric plant statistics by respondent, year, and raw plant name: installed capacity, net generation, plant-cost balance facts, and separate production-expense line items. Dollar values are nominal and are never inflation-adjusted, allocated, or summed into a derived O&M total." ], "status": "available", "title": "FERC Form 1 Plant Costs" }, { "access": "open", "anchors": [ "state" ], "answers": [ "daily Henry Hub spot prices in EIA's published dollars-per-MMBtu unit", "monthly state-average prices paid by electric-power consumers in EIA's published dollars-per-Mcf unit", "exact source-null state-month records, never zero-filled", "Texas monthly electric-power prices in one state-filtered call", "per-series coverage windows and separately queryable revision vintages" ], "current_sources": [ "energy.eia.natural_gas_prices" ], "id": "natural_gas.prices", "primitive": "query_natural_gas_prices_v1", "product_spec": "blocks/natural_gas_prices/card.md", "represented_facts": [ "EIA publishes the daily Henry Hub natural-gas spot price in dollars per MMBtu and monthly state-average natural-gas prices paid by electric-power consumers in dollars per Mcf. The state series is an aggregate of what the state's power sector paid in that month, not a plant-level price. Source-null state-month values remain explicit nulls and revisions remain separate capture vintages.", "Source-null state-month prices remain explicit nulls, and mixed source units are never blended." ], "status": "available", "title": "Natural Gas Prices" }, { "access": "open", "anchors": [ "balancing_authority_code" ], "answers": [ "hourly observed electricity demand (MW) for a balancing authority (Adjusted series, cited to the source row)", "the day-ahead demand forecast for the same BA-hours \u2014 forecast-vs-actual misses", "which hours EIA imputed rather than metered (is_imputed)", "BA-level demand shape over time (daily/seasonal profiles, growth at BA grain)" ], "current_sources": [ "energy.eia.eia930" ], "id": "power.demand", "primitive": "query_power_demand_v1", "product_spec": "blocks/power_demand/card.md", "represented_facts": [ "EIA-930 reports hourly observed electricity demand (MW) by balancing authority \u2014 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" ], "status": "available", "title": "Power Demand" }, { "access": "open", "anchors": [], "answers": [ "hourly observed electricity demand (MW) for the US48 national total (cited to the source record)", "hourly observed demand for any of the 13 EIA regions (CAL, CAR, CENT, FLA, MIDA, MIDW, NE, NW, NY, SE, SW, TEN, TEX)", "the day-ahead demand forecast for the same respondent-hours \u2014 forecast-vs-actual misses", "national / regional demand shape over time (daily/seasonal profiles, growth) from EIA's own published totals" ], "current_sources": [ "energy.eia.eia930_rollup" ], "id": "power.demand_rollup", "primitive": "query_power_demand_rollup_v1", "product_spec": "blocks/power_demand_rollup/card.md", "represented_facts": [ "EIA-930 reports hourly observed electricity demand (MW) as EIA's own published rollup totals \u2014 US48 (the Lower-48 national total) and the 13 EIA regions (the Adjusted series, served verbatim, not a sum)", "EIA-930 reports the day-ahead demand forecast (MW) on the same respondent-hour rows" ], "status": "available", "title": "Power Demand (national / region rollup)" }, { "access": "open", "anchors": [ "state", "eia_utility_id" ], "answers": [ "annual retail electricity sales (billed MWh) by utility, state, and customer sector", "annual retail revenue (thousand dollars) and customer counts at the same grain", "industrial / commercial demand-growth signals by state and utility (year over year, as vintages accumulate)", "service-type structure (bundled vs energy-only vs delivery-only) per utility and state" ], "current_sources": [ "energy.eia.eia861" ], "id": "power.retail_sales", "primitive": "query_power_retail_sales_v1", "product_spec": "blocks/power_retail_sales/card.md", "represented_facts": [ "EIA-861 reports annual retail electricity sold to ultimate customers \u2014 billed sales (MWh), revenue, and customer counts \u2014 by utility, state, and customer sector", "EIA-861 reports the filing part and service type (bundled / energy-only / delivery-only) behind each utility\u00d7state row" ], "status": "available", "title": "Power Retail Sales" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which generation projects have requested to connect to the MISO grid, by state/county, fuel, technology, and status", "the requested (net summer / net winter) megawatts of each queued project, cited to its source row", "the as-reported application status, study phase, and post-GIA status of each project (kept separate, never collapsed)", "the count of queued projects in a scope (active vs withdrawn vs done \u2014 by filtering application_status)" ], "current_sources": [ "energy.miso.giqueue" ], "id": "power.interconnection_queue", "primitive": "query_power_interconnection_queue_v1", "product_spec": "blocks/power_interconnection_queue/card.md", "represented_facts": [ "MISO's generator interconnection queue reports each project's REQUESTED interconnection capacity (net summer / net winter MW) \u2014 a request, not built capacity", "MISO's queue reports each project's location (state, county), fuel and technology, three as-reported status dimensions (application status, study phase, post-GIA status), and lifecycle dates (queue, withdrawn, in-service, done)", "MISO also reports two sparse lifecycle dates served under MISO's own field labels \u2014 gia_to_exec_date and neg_in_service_date; MISO publishes no data dictionary, so these are served as-reported and not reinterpreted (present where MISO reports them, null otherwise)" ], "status": "available", "title": "Power Interconnection Queue (MISO)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which projects have requested to connect to the PJM grid, by state/county, fuel, project type, and status", "the requested (max-facility-output / net summer / net winter) megawatts of each queued project, cited to its source row", "the as-reported status of each PJM project (Active / Withdrawn / In Service / Under Construction / \u2026), kept verbatim", "the realized in-service (built) megawatts of completed PJM projects (in_service_mw), separate from requested MW", "the count of queued projects in a scope (active vs withdrawn vs in service \u2014 by filtering status)" ], "current_sources": [ "energy.pjm.queue" ], "id": "power.interconnection_queue_pjm", "primitive": "query_power_interconnection_queue_pjm_v1", "product_spec": "blocks/power_interconnection_queue_pjm/card.md", "represented_facts": [ "PJM's New Services (interconnection) queue reports each project's REQUESTED interconnection capacity (MFO / net summer / net winter MW) \u2014 a request, not built capacity", "PJM's queue reports each project's location (state, POI county), fuel and project type, the single as-reported status, the study-document URLs and per-stage statuses, and lifecycle dates", "PJM also reports in_service_mw \u2014 the realized BUILT MW for in-service projects \u2014 carried under its own name, never as a requested figure" ], "status": "available", "title": "Power Interconnection Queue (PJM)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which projects are in PJM's cluster cycles (TC1/TC2 transition, C01+ reopened), by cycle, stage, state, fuel, and status", "the requested (MFO / net summer / net winter) megawatts of each cluster-cycle project, cited to its source row", "the cluster stage / decision point and developer of each project, as PJM reports them", "the realized in-service (built) megawatts and long-term-firm transmission MW, separate from requested MW", "the count of cluster-cycle projects in a scope (e.g. cycle=C01, status=Active)" ], "current_sources": [ "energy.pjm.cycle" ], "id": "power.interconnection_queue_pjm_cycle", "primitive": "query_power_interconnection_queue_pjm_cycle_v1", "product_spec": "blocks/power_interconnection_queue_pjm_cycle/card.md", "represented_facts": [ "PJM's cluster/cycle grid reports each project's cluster cycle (TC1/TC2 transition, C01+ reopened steady-state) and stage, with its REQUESTED interconnection capacity (MFO / net summer / net winter MW) \u2014 a request, not built capacity", "PJM's cycle grid reports each project's developer, location (state, county), fuel, phased System-Impact-Study report URLs + statuses, and lifecycle dates", "PJM also reports in_service_mw (realized built MW) and ltf_mw (long-term firm transmission MW), carried under their own names; this is a separate publication from PJM's New Services queue and is never merged with it" ], "status": "available", "title": "Power Interconnection Queue (PJM cluster/cycle)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which projects have requested to connect to the CAISO grid, by state/county, fuel/technology, cluster, deliverability, and status", "the net megawatts to grid of each queued CAISO project, cited to its source row", "the as-reported application status of each CAISO project (Active / Completed / Withdrawn), kept verbatim by tab", "each project's deliverability status (Full Capacity / Partial Capacity / Energy Only), TPD allocation, and cluster (study process), as CAISO reports it", "the count of projects in a scope (active vs completed vs withdrawn \u2014 by filtering application_status)" ], "current_sources": [ "energy.caiso.queue" ], "id": "power.interconnection_queue_caiso", "primitive": "query_power_interconnection_queue_caiso_v1", "product_spec": "blocks/power_interconnection_queue_caiso/card.md", "represented_facts": [ "CAISO's Public Queue Report reports each project's REQUESTED interconnection capacity (Net MWs to Grid) \u2014 a request, not built capacity \u2014 across the Active, Completed, and Withdrawn lifecycle tabs", "CAISO's queue reports each project's location (state, county), the Type/Fuel/MW hybrid triplets, the three-valued deliverability status (Full Capacity / Partial Capacity / Energy Only) with TPD allocation, the cluster study process, the per-phase study statuses, and lifecycle dates", "CAISO carries the requested-vs-built distinction in application_status + the lifecycle tab \u2014 a COMPLETED project carries an actual_online_date (the realized in-service date); CAISO publishes no separate built-MW column" ], "status": "available", "title": "Power Interconnection Queue (CAISO)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which projects have requested to connect to the NYISO grid, by state/county, fuel/technology, zone, and status", "the summer-peak (sp_mw) and winter-peak (wp_mw) megawatts of each queued NYISO project, cited to its source row", "NYISO load interconnection requests (the Load Projects tab) with their peak_mw_load, served as-reported", "the as-reported lifecycle status of each NYISO project (active / withdrawn / in-service / affected-system), kept by tab", "the as-reported study-phase code (study_status_code) and which studies are available, as NYISO reports them", "NYISO's own End-Use class per load request (end_use, 2026-07 edition onward, e.g. DAT / DAT-AI / DAT-CM, served verbatim) and the SIS study bundle (sis_bundle)", "the count of projects in a scope (active vs withdrawn vs in-service \u2014 by filtering application_status or sheet_name)" ], "current_sources": [ "energy.nyiso.queue" ], "id": "power.interconnection_queue_nyiso", "primitive": "query_power_interconnection_queue_nyiso_v1", "product_spec": "blocks/power_interconnection_queue_nyiso/card.md", "represented_facts": [ "NYISO's Interconnection Queue reports each project's REQUESTED interconnection capacity \u2014 summer (SP) and winter (WP) peak MW, kept separate \u2014 across every lifecycle tab NYISO publishes (nine through 2026-06; seven since the 2026-07 restructure folded the load/affected-system withdrawn lists into the active tabs under NYISO's own 0=Withdrawn code); a request, not built capacity", "NYISO uniquely publishes a Load Projects tab \u2014 load interconnection requests with their own peak_mw_load, and (since 2026-07) NYISO's own End-Use class per request (end_use, e.g. DAT / DAT-AI / DAT-CM, served verbatim \u2014 NYISO publishes no key for these codes) plus the SIS Bundle study-batch code (sis_bundle)", "NYISO carries the requested-vs-built distinction in application_status (the lifecycle tab's reading, overridden to the withdrawn form on NYISO's own status code 0) + study_status_code; the In Service tab is the built reading, and a project may appear on more than one tab (grain = sheet + queue_position)" ], "status": "available", "title": "Power Interconnection Queue (NYISO)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which projects have requested to connect to the ISO-NE grid, by state/county, fuel/technology, zone, and status", "the net / summer-peak / winter-peak megawatts of each queued ISO-NE project, cited to its source row", "the as-reported lifecycle status of each project (A=Active / C=Commercial / W=Withdrawn), kept separate from build-progress project_status", "the build-progress project_status (Under Study / Under Construction / In Service / \u2026), as ISO-NE reports it, never collapsed into application_status", "the request type (G=Generation / ETU=Elective Transmission Upgrade / TS=Transmission Service) and per-stage study statuses, as ISO-NE reports them", "the count of projects in a scope (active vs commercial vs withdrawn \u2014 by filtering application_status)" ], "current_sources": [ "energy.isone.queue" ], "id": "power.interconnection_queue_isone", "primitive": "query_power_interconnection_queue_isone_v1", "product_spec": "blocks/power_interconnection_queue_isone/card.md", "represented_facts": [ "ISO-NE's IRTT public-queue report lists each project's REQUESTED interconnection capacity \u2014 net, summer-peak and winter-peak MW, kept separate \u2014 for generation, elective-transmission-upgrade and transmission-service requests; a request, not built capacity", "ISO-NE carries the requested-vs-built distinction in application_status (A=Active / C=Commercial / W=Withdrawn) and a SEPARATE build-progress project_status (Under Study / Under Construction / In Service / \u2026), never collapsed; a Commercial project is the built reading", "ISO-NE publishes no load/data-center request type (all rows are generation or transmission); the queue-position (QP) is a non-unique reference reused across historical projects, so the grain is the published row ordinal" ], "status": "available", "title": "Power Interconnection Queue (ISO-NE)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which generation projects have requested to connect to the ERCOT (Texas) grid, by county, fuel, technology, CDR reporting zone, lifecycle, and size", "the requested capacity (MW) of each queued ERCOT project, cited to its source row", "the as-reported lifecycle of each project (ACTIVE / INACTIVE / CANCELLED, derived from ERCOT's own sheet structure), kept separate from build progress", "the build-progress signal \u2014 the GIM Study Phase token string and the milestone dates (screening study, FIS, IA signed, construction, energization), as ERCOT reports them", "the count of projects in a scope (active vs inactive vs cancelled \u2014 by filtering application_status)" ], "current_sources": [ "energy.ercot.queue" ], "id": "power.interconnection_queue_ercot", "primitive": "query_power_interconnection_queue_ercot_v1", "product_spec": "blocks/power_interconnection_queue_ercot/card.md", "represented_facts": [ "ERCOT's GIS Report lists each generation project's REQUESTED interconnection capacity (capacity_mw \u2014 one figure, no summer/winter split) across four lifecycle sheets (Large/Small Gen active, plus Inactive and Cancellation); a request, not built capacity", "ERCOT publishes no status column, so application_status (ACTIVE / INACTIVE / CANCELLED) is derived from the sheet the project is filed on (sheet_name served verbatim), and the build-progress reading is carried SEPARATELY in gim_study_phase + the milestone dates, never collapsed", "ERCOT files a hybrid project's legs as separate INR rows linked only by a shared poi_location (no in-row hybrid encoding); the GIS Report is generation-only and reports no load/data-center type" ], "status": "available", "title": "Power Interconnection Queue (ERCOT)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which generation projects have requested to connect to the SPP grid, by state, county, generation type, fuel, study cluster, transmission owner, and status", "the requested capacity (MW) of each queued SPP project, cited to its source row (and the five other MW columns SPP publishes, each labeled and never blended)", "the as-reported SPP status of each project (SPP's own vocabulary, kept verbatim with a per-source codebook), so an agent can scope to active vs withdrawn vs terminated", "the study cluster (DISIS-YYYY-NNN / Surplus / RTOE Transitional) and SPP regional cluster group, as SPP reports them", "the count of projects in a scope (by filtering native_status, state, generation_type, \u2026)" ], "current_sources": [ "energy.spp.queue" ], "id": "power.interconnection_queue_spp", "primitive": "query_power_interconnection_queue_spp_v1", "product_spec": "blocks/power_interconnection_queue_spp/card.md", "represented_facts": [ "SPP's GI Summary lists each generation project's REQUESTED interconnection capacity (capacity_mw \u2014 SPP's headline figure, with five other labeled MW columns served and never blended); a request, not built capacity", "SPP publishes a native Status column whose vocabulary it controls, so native_status is served VERBATIM with a codebook (never mapped to a lifecycle enum); ~66% of rows are WITHDRAWN, so a total is scoped by native_status, never read as built", "SPP spans ~14 central-US states (state is a real anchor), carries only a free-text town-or-county (county_fips derived by name where it resolves, else null), encodes hybrids natively as a Hybrid generation_type (no is_hybrid invented), and is generation-only (no load/data-center type)" ], "status": "available", "title": "Power Interconnection Queue (SPP)" }, { "access": "open", "anchors": [ "state" ], "answers": [ "the day-ahead wholesale price ($/MWh) at an ERCOT settlement point for a given delivery day and hour, cited to its source row", "the price at a named hub (e.g. HB_NORTH, HB_HOUSTON) or load zone (e.g. LZ_HOUSTON) \u2014 the regional benchmark prices", "the daily price shape at a settlement point (the 24 hourly day-ahead prices), and average / minimum / maximum price over a window", "how a settlement point is classified by ERCOT (Hub / Load Zone / Resource Node / DC-tie, as ERCOT's own verbatim code), so a single-plant node is not mistaken for a regional benchmark", "the price spread across settlement points or types for a given hour or day" ], "current_sources": [ "energy.ercot.prices" ], "id": "power.price_ercot", "primitive": "query_power_price_ercot_v1", "product_spec": "blocks/power_price_ercot/card.md", "represented_facts": [ "ERCOT's Day-Ahead Market Settlement Point Prices (NP4-190-CD) \u2014 the price ($/MWh) cleared the day before each operating day at every ERCOT settlement point, served hourly and point by point as a TOTAL (no energy/congestion/loss split; none is synthesized)", "a price is intensive ($/MWh): it is averaged / min'd / max'd over a scope, never summed; ERCOT's own hour-ending label and DST flag are carried verbatim (24 hours normally, 25 on the fall-back date, 23 on spring-forward)", "settlement_point_type is ERCOT's OWN verbatim classification (HU hub / LZ load zone / RN resource node / DC-tie \u2026), joined from ERCOT's published settlement-points list and never collapsed; a settlement point is electrical/aggregate, not a plant \u2014 the only geography anchor is state = TX", "historical delivery coverage begins 2014-05-02 from ERCOT's Data Access Portal archives; settlement-point names remain exactly as published in each vintage, and an older name absent from the current type reference receives a null type rather than a rewrite or guess" ], "status": "available", "title": "Power Prices (ERCOT day-ahead)" }, { "access": "key", "anchors": [], "answers": [ "PJM's cited marginal ELCC accreditation fraction for a resource class in a named auction document", "how preliminary-outlook ratings differ from final-auction or incremental-auction ratings without reconciling them", "all PJM resource classes in a linked class-ratings table, with the verbatim class name and normalized family" ], "current_sources": [ "energy.pjm.elcc" ], "id": "power.capacity_accreditation_pjm", "primitive": "query_power_capacity_accreditation_pjm_v1", "product_spec": "blocks/power_capacity_accreditation_pjm/card.md", "represented_facts": [ "PJM-published marginal Effective Load Carrying Capability (ELCC) class ratings, as a fraction of nameplate capacity, for each resource class and delivery year in each linked final Base Residual Auction document, Incremental Auction document, or preliminary multi-year outlook. Document identity is a dimension: preliminary and final ratings for the same delivery year are separate cited atoms and are never merged, preferred, reconciled, or corrected by this block." ], "status": "available", "title": "PJM ELCC Class Ratings (internal)" }, { "access": "key", "anchors": [], "answers": [ "RTO-wide and separated-LDA UCAP capacity-market clearing prices for a named PJM delivery year", "cleared RTO UCAP MW and the report-stated RTO reliability requirement where published", "the administrative price cap and floor as each stating document publishes them, making a cap-bound clearing visible", "for auctions with no stated collar, which documents were searched, so a None cap is provably not-stated", "documented coverage from delivery year 2018/2019 onward, with unsupported source formats recorded as exceptions" ], "current_sources": [ "energy.pjm.capacity_market" ], "id": "power.capacity_market_pjm", "primitive": "query_power_capacity_market_pjm_v1", "product_spec": "blocks/power_capacity_market_pjm/card.md", "represented_facts": [ "PJM Reliability Pricing Model Base Residual Auction results: UCAP-basis resource clearing prices in USD per MW-day for the RTO and published LDAs, RTO cleared UCAP MW, the stated RTO reliability requirement, and any administrative price cap and floor stated in the auction results report or the planning-period-parameters workbook/report \u2014 each on the basis its stating document uses, quoted verbatim in cap_basis. Documents searched for a collar that state none yield a collar_search atom, so absence is provably \"not stated\", never \"not parsed\". Workbook and report facts remain separate cited atoms at their exact source coordinates." ], "status": "available", "title": "PJM RPM Capacity-Market Results (internal)" }, { "access": "key", "anchors": [], "answers": [ "the Schedule 53 class-average ISAC/ICAP ratio for a named resource class, season, and planning year, with its count of contributing units", "indicative DLOL class-level UCAP/ICAP ratios per season ahead of the Schedule 53A go-live, including each published storage modeling variant", "which resource classes MISO suppressed below its 30-unit threshold, so a missing ratio is provably not-published", "the fleetwide Schedule 53 class average that suppressed classes are granted", "preliminary vs indicative document identity for the same planning year as separate cited atoms" ], "current_sources": [ "energy.miso.accreditation" ], "id": "power.capacity_accreditation_miso", "primitive": "query_power_capacity_accreditation_miso_v1", "product_spec": "blocks/power_capacity_accreditation_miso/card.md", "represented_facts": [ "MISO-published seasonal capacity accreditation ratios per resource class, as a fraction of installed capacity (ICAP), from two coexisting tariff constructs kept apart by document_kind: Schedule 53 class-average ISAC/ICAP ratios (the construct binding until Planning Year 2027-2028) and indicative Direct Loss of Load class-level UCAP/ICAP ratios published under Schedule 53A ahead of its 2028-2029 implementation. Storage classes served under multiple DLOL modeling variants are separate cited atoms carrying the stated variant, never blended. Classes MISO suppresses for data-integrity/confidentiality (<30 contributing units) yield a suppression atom, so absence is provably \"not published\", never \"not parsed\". Ratios from different documents or constructs are never merged, preferred, or reconciled by this block." ], "status": "available", "title": "MISO Capacity Accreditation (internal)" }, { "access": "key", "anchors": [], "answers": [ "the seasonal zonal Auction Clearing Price for a named MISO planning year, season, and zone", "the External Resource Zone clearing exactly as stated, including verbatim price ranges", "seasonal subregional CONE and annual zonal CONE as the posting publishes them, making cap-adjacent clearings visible", "the IMM conduct threshold published beside the auction results", "documented seasonal coverage from the 2024 PRA posting onward, corrections postings as distinct cited documents" ], "current_sources": [ "energy.miso.pra" ], "id": "power.capacity_market_miso", "primitive": "query_power_capacity_market_miso_v1", "product_spec": "blocks/power_capacity_market_miso/card.md", "represented_facts": [ "MISO Planning Resource Auction results as published in the annual PRA results posting: seasonal zonal Auction Clearing Prices in USD per MW-day of Seasonal Accredited Capacity for Zones 1-10, External Resource Zone clearing quoted verbatim where the document states a range, seasonal subregional and annual zonal Cost of New Entry values, and the Independent Market Monitor conduct thresholds the posting publishes beside them. CONE is recorded as the document's stated administrative parameter \u2014 the price-cap analog \u2014 on the basis its stating document uses, never interpreted, annualized, or converted by this block. A corrections posting is a distinct document identity: its atoms cite the corrections file, and earlier postings are never silently replaced." ], "status": "available", "title": "MISO PRA Capacity-Market Results (internal)" }, { "access": "open", "anchors": [], "answers": [ "monthly private data-center construction spending ($ millions), seasonally-adjusted annual rate or not-adjusted monthly level (cited to the source cell)", "monthly private computer/electronic/electrical (semiconductor-fab) construction spending ($ millions)", "the data-center vs fab construction-spending trend over time (each as its own per-month series)", "whether a given month's value is preliminary, revised, or final (the Census revision status, carried verbatim)" ], "current_sources": [ "construction.census.c30_vip" ], "id": "ai_infrastructure.construction", "primitive": "query_ai_infrastructure_construction_v1", "product_spec": "blocks/ai_infrastructure_construction/card.md", "represented_facts": [ "Census C30 (Value of Construction Put in Place) reports the monthly value of private DATA-CENTER construction put in place ($ millions), served both seasonally-adjusted (annual rate) and not-seasonally-adjusted (monthly level), verbatim and cited", "Census C30 reports the monthly value of private COMPUTER/ELECTRONIC/ELECTRICAL (semiconductor-fab) construction put in place ($ millions) on the same two bases" ], "status": "available", "title": "AI Infrastructure Construction (data centers + fabs)" }, { "access": "open", "anchors": [], "answers": [ "monthly U.S. import value (USD) of all integrated circuits \u2014 HS-8542 \u2014 cited to the source row", "chip imports by country of origin (e.g. Taiwan, Malaysia, South Korea, Israel) \u2014 supply-source concentration", "the U.S. chip-import trend over time (each country / grouping / the national total as its own monthly series)", "general imports value vs imports-for-consumption value at the same grain" ], "current_sources": [ "trade.census.intltrade_imports_hs" ], "id": "ai_infrastructure.trade", "primitive": "query_ai_infrastructure_trade_v1", "product_spec": "blocks/ai_infrastructure_trade/card.md", "represented_facts": [ "Census International Trade reports the monthly customs value (USD) of U.S. imports of HS-8542 'Electronic integrated circuits' \u2014 ALL integrated circuits (processors, memory, amplifiers, parts), not AI-accelerator-specific \u2014 by country of origin, as general imports and imports-for-consumption value, served verbatim and cited", "Census reports these imports across overlapping country GROUPINGS (ASIA, APEC, EU, OECD, ASEAN, the continents) and an all-countries TOTAL; the groupings overlap each other and the countries, so they are never summed \u2014 the served TOTAL is the only national figure" ], "status": "available", "title": "AI Infrastructure Trade (chip imports)" }, { "access": "open", "anchors": [], "answers": [ "monthly U.S. import value (USD) of semiconductor-manufacturing equipment \u2014 HS-8486 \u2014 cited to the source row", "equipment imports by country of origin (e.g. Japan, the Netherlands, South Korea, Singapore) \u2014 tool-supply concentration", "the fab-buildout TOOLING trend \u2014 equipment flowing in between construction (C30) and chip output (HS-8542)", "general imports value vs imports-for-consumption value at the same grain" ], "current_sources": [ "trade.census.intltrade_equipment_hs" ], "id": "ai_infrastructure.equipment_trade", "primitive": "query_ai_infrastructure_equipment_trade_v1", "product_spec": "blocks/ai_infrastructure_equipment_trade/card.md", "represented_facts": [ "Census International Trade reports the monthly customs value (USD) of U.S. imports of HS-8486 'Machines and apparatus for the manufacture of semiconductor boules/wafers, devices, integrated circuits or flat panel displays' \u2014 the chip-MAKING equipment (which includes flat-panel-display machinery), NOT the chips themselves \u2014 by country of origin, as general imports and imports-for-consumption value, served verbatim and cited", "Census reports these imports across overlapping country GROUPINGS (ASIA, APEC, EU, OECD, ASEAN, the continents) and an all-countries TOTAL; the groupings overlap each other and the countries, so they are never summed \u2014 the served TOTAL is the only national figure" ], "status": "available", "title": "AI Infrastructure Equipment Trade (chip-making tools)" }, { "access": "open", "anchors": [], "answers": [ "the monthly industrial-production index (2017=100) for semiconductor & other electronic component manufacturing (NAICS 3344), seasonally adjusted or not adjusted, cited to the Fed's source observation", "monthly capacity utilization (percent, seasonally adjusted) for the same industry \u2014 how hot the domestic fabs and component plants are running", "the monthly capacity index (2017=100) behind the utilization rate", "the production / utilization trend over time (each series as its own per-month reading, averaged \u2014 never summed \u2014 over windows)" ], "current_sources": [ "production.fed.g17" ], "id": "ai_infrastructure.production", "primitive": "query_ai_infrastructure_production_v1", "product_spec": "blocks/ai_infrastructure_production/card.md", "represented_facts": [ "Fed G.17 reports the monthly industrial-production index (2017=100, seasonally adjusted and not adjusted) for semiconductor and other electronic component manufacturing (NAICS 3344) \u2014 the finest split G.17 publishes for this family, served verbatim and cited to the Board's SDMX observation", "Fed G.17 reports monthly capacity utilization (percent) and the capacity index (2017=100) for the same industry, seasonally adjusted only; an index or a rate is intensive \u2014 averaged over a window, never summed" ], "status": "available", "title": "AI Infrastructure Production (semiconductor output and utilization)" }, { "access": "open", "anchors": [], "answers": [ "monthly U.S. imports of industrial robots in DOLLARS and in UNITS (robot counts) \u2014 cited to the source row", "robot imports by country of origin (e.g. Japan, China, South Korea, Germany, Mexico) \u2014 supply concentration", "the two robot categories separately \u2014 multipurpose robots (8479.50) vs lifting/handling robots (8428.70)", "general imports vs imports-for-consumption at the same grain, value and units" ], "current_sources": [ "trade.census.intltrade_robotics_hs" ], "id": "robotics.trade", "primitive": "query_robotics_trade_v1", "product_spec": "blocks/robotics_trade/card.md", "represented_facts": [ "Census International Trade reports the monthly customs value (USD) AND unit count (number of robots) of U.S. imports of industrial robots \u2014 HS-10 8479500000 'INDUSTRIAL ROBOTS, NESOI' (multipurpose) and 8428700000 'INDUSTRIAL ROBOTS FOR LIFTING, HANDLING, LOADING OR UNLOADING' (created by HS 2022; no data before 2022-01) \u2014 by country of origin, as general imports and imports-for-consumption, served verbatim and cited", "Census reports these imports across overlapping country GROUPINGS (ASIA, APEC, EU, OECD, ASEAN, the continents) and an all-countries TOTAL; the groupings overlap each other and the countries, so they are never summed \u2014 the served TOTAL is the only national figure" ], "status": "available", "title": "Robotics Trade (industrial-robot imports, value + robot counts)" }, { "access": "open", "anchors": [ "state" ], "answers": [ "what share of US manufacturing plants use industrial robots \u2014 nationally, by state, by industry (NAICS), by plant size \u2014 the only official installed-base adoption series", "what share of manufacturing employees work at plants with robots, at the same grains", "robotics capital expenditures ($1000) by industry, state, and plant size", "how adoption differs across plant sizes (small plants barely automate; large plants dominate)", "each edition separately (ASM 2018-2021 annual series; EC 2022 census snapshot), with the coverage break between them named, never spliced" ], "current_sources": [ "robotics.census.robotic_equipment" ], "id": "robotics.adoption", "primitive": "query_robotics_adoption_v1", "product_spec": "blocks/robotics_adoption/card.md", "represented_facts": [ "The Census Industrial Robotic Equipment product (experimental \u2014 the first official federal robotics-adoption statistics) reports the percent of manufacturing plants with industrial robots, the percent of manufacturing employees at plants with robots, and robotics capital expenditures ($1000) by NAICS industry, state, and plant size, in two editions (ASM 2018-2021 and the 2022 Economic Census), served verbatim and cited to the exact workbook cell-group", "The two editions measure different coverage universes (the 2022 Economic Census reaches small plants the ASM sample does not \u2014 US plants-with-robots 12.1% ASM-2021 vs 6.4% EC-2022), so editions are compared, never spliced into one series (PD-066)" ], "status": "available", "title": "Robotics Adoption (share of plants using robots, workers exposed, robotics capex)" }, { "access": "open", "anchors": [ "state" ], "answers": [ "every FCC space-station filing on record \u2014 by applicant, application type, status, and filing date \u2014 each cited to its exact record in the FCC's own database dump", "the licensing trail of any satellite system or operator (e.g. every SpaceX / Intelsat / Kuiper filing), with the FCC's own description text", "where each filing stood when the FCC last generated the dump (2026-07-16) \u2014 the FCC's own status vocabulary, decoded from the same dump vintage (granted, pending, dismissed, surrendered)", "filing counts by applicant, type, status, state (applicant address), or period \u2014 the satellite-buildout pipeline signal back to the 1960s", "the lifecycle dates of any filing (filed, granted, expires, \u2026), e.g. when an authorization expires" ], "current_sources": [ "space.fcc.ibfs_sat" ], "id": "space.satellite_filings", "primitive": "query_space_satellite_filings_v1", "product_spec": "blocks/space_satellite_filings/card.md", "represented_facts": [ "The FCC's IBFS daily bulk database dump records every space-station (SAT-subsystem) filing in the FCC satellite licensing docket back to the 1960s \u2014 file number, call sign, application type and status in the FCC's own vocabulary (verbatim codes plus the FCC's own decode text from the same dump vintage), the full lifecycle date family, the FCC's plain-English description, and the applicant identity joined by the source's own address_key \u2014 served as-reported and cited to the exact record", "New-filing intake into IBFS structurally ended at the FCC's ICFS system cutover (~mid-2025; measured: zero 2026-filed records), and ICFS publishes no bulk data \u2014 so filings submitted after the cutover are not in this source (PD-064, engraved as a refusal); they are served from the FCC's weekly satellite public notices as space.satellite_notices (PD-077)", "The FCC has not regenerated the IBFS dump since 2026-07-16 (it previously updated daily), so status changes after that date are not reflected in this source" ], "status": "available", "title": "Space Satellite Filings (FCC satellite licensing docket)" }, { "access": "open", "anchors": [], "answers": [ "which satellite applications the FCC accepted for filing since mid-2025 (the ICFS era), with applicant, call sign, filing type, Date filed and the FCC's own description \u2014 each cited to its line in the notice", "which satellite filings the FCC granted, partly granted, dismissed or otherwise acted on, and the printed date of each action", "the ICFS-era licensing trail of an operator or call sign (e.g. every SpaceX, Amazon Kuiper or AST SpaceMobile listing since mid-2025)", "counts of notice listings by kind, filing type, action, applicant or release period" ], "current_sources": [ "space.fcc.sat_public_notices" ], "id": "space.satellite_notices", "primitive": "query_space_satellite_notices_v1", "product_spec": "blocks/space_satellite_notices/card.md", "represented_facts": [ "The FCC Space Bureau publishes two satellite public notices each week \u2014 Applications Accepted for Filing and Actions Taken \u2014 listing each filing's FCC file number, call sign, applicant, Date filed and filing type, and on Actions Taken notices the action and its Date of Action; every listing since the 2025-06-18 ICFS cutover is served as printed and cited to its line in the notice text", "The notices are the FCC's public announcement record, not its full docket: they carry no status history, omit filings the FCC has not noticed, and can print a different Date filed or applicant name for the same filing in different weeks (PD-077)" ], "status": "available", "title": "Space Satellite Notices (FCC weekly satellite public notices)" } ], "combinable_on": { "balancing_authority_code": [ "power.asset_ownership", "power.capacity", "power.demand", "power.fuel_cost", "power.generation" ], "county_fips": [ "power.capacity", "power.interconnection_queue", "power.interconnection_queue_caiso", "power.interconnection_queue_ercot", "power.interconnection_queue_isone", "power.interconnection_queue_nyiso", "power.interconnection_queue_pjm", "power.interconnection_queue_pjm_cycle", "power.interconnection_queue_spp" ], "eia_plant_id": [ "power.asset_ownership", "power.capacity", "power.fuel_cost", "power.generation" ], "generator_id": [ "power.asset_ownership", "power.capacity", "power.generation" ], "state": [ "natural_gas.prices", "power.asset_ownership", "power.capacity", "power.fuel_cost", "power.generation", "power.interconnection_queue", "power.interconnection_queue_caiso", "power.interconnection_queue_ercot", "power.interconnection_queue_isone", "power.interconnection_queue_nyiso", "power.interconnection_queue_pjm", "power.interconnection_queue_pjm_cycle", "power.interconnection_queue_spp", "power.price_ercot", "power.retail_sales", "robotics.adoption", "space.satellite_filings" ] }, "compounds": [ { "definition": "capacity_factor = sum(net_generation_mwh) / (sum(operating nameplate_mw) \u00d7 hours_in_month), over plant\u00d7fuel present in BOTH EIA-923 (generation) and EIA-860M operating capacity (snapshot matched to the month). Storage excluded; basis = nameplate.", "id": "power.capacity_factor", "kind": "compound", "metric": "capacity_factor", "primitive": "query_capacity_factor_v1", "sources": [ "energy.eia.eia860m", "energy.eia.eia923" ], "title": "Power Capacity Factor" } ], "domains": [ { "capabilities": [ { "access": "open", "anchors": [ "county_fips", "state", "lat", "lon", "eia_plant_id", "generator_id", "balancing_authority_code" ], "answers": [ "operating generator capacity by location, fuel, technology, and source-reported balancing authority code", "planned generator capacity by location, fuel, technology, source-reported balancing authority code, and planned online year", "retired generator capacity by location, fuel, technology, source-reported balancing authority code, and retirement year" ], "current_sources": [ "energy.eia.eia860m" ], "id": "power.capacity", "primitive": "query_power_capacity_v1", "product_spec": "blocks/power_capacity/card.md", "represented_facts": [ "EIA-860M reports operating generator capacity by location, fuel, technology, status, and source-reported balancing authority code", "EIA-860M reports planned generator capacity by location, fuel, technology, status, source-reported balancing authority code, and planned online year", "EIA-860M reports retired generator capacity by location, fuel, technology, status, source-reported balancing authority code, and retirement year" ], "status": "available", "title": "Power Capacity" }, { "access": "open", "anchors": [ "eia_plant_id", "state", "balancing_authority_code", "generator_id" ], "answers": [ "monthly net generation (MWh) by plant, prime mover, and fuel", "monthly net generation (MWh) by individual generator, joinable to EIA-860M", "generation mix by state, balancing-authority code, and fuel over time", "total and electric-only fuel consumption (MMBtu), aligned to Page 1 net generation across the served 2014-to-present history" ], "current_sources": [ "energy.eia.eia923" ], "id": "power.generation", "primitive": "query_power_generation_v1", "product_spec": "blocks/power_generation/card.md", "represented_facts": [ "EIA-923 reports monthly net electricity generation (MWh) by plant, prime mover, and fuel (Page 1)", "The same Page 1 source row reports total fuel consumed and fuel consumed for electricity separately in MMBtu", "EIA-923 reports monthly net electricity generation (MWh) by individual generator (Page 4), joinable to EIA-860M" ], "status": "available", "title": "Power Generation" }, { "access": "open", "anchors": [ "state", "eia_plant_id", "generator_id", "balancing_authority_code" ], "answers": [ "raw annual EIA-860 owner names and fractional ownership shares by plant and generator", "ownership rows for a raw owner-name string, with no name normalization or entity matching", "same-vintage state and source-reported balancing-authority slices, including ERCO", "the explicit EIA default that absence from the Owner schedule means wholly owned by the operator" ], "current_sources": [ "energy.eia.eia860_owner" ], "id": "power.asset_ownership", "primitive": "query_power_asset_ownership_v1", "product_spec": "blocks/power_asset_ownership/card.md", "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." ], "status": "available", "title": "Power Asset Ownership" }, { "access": "open", "anchors": [ "state", "eia_plant_id", "balancing_authority_code" ], "answers": [ "raw receipt-level delivered fuel costs in cents per MMBtu and physical quantities", "receipt rows by plant, month, fuel, state, supplier, purchase type, or source-reported balancing authority", "explicit counts and records for reported versus withheld fuel costs" ], "current_sources": [ "energy.eia.eia923_receipts_cost" ], "id": "power.fuel_cost", "primitive": "query_power_fuel_cost_v1", "product_spec": "blocks/power_fuel_cost/card.md", "represented_facts": [ "EIA-923 Page 5 reports individual fossil-fuel receipts by plant and month, including raw physical quantity and delivered fuel cost in cents per MMBtu. Confidential or otherwise unpublished costs remain explicit missing values; they are never zero-filled, imputed, or converted into heat rates or $/MWh.", "Withheld EIA fuel-cost cells are explicit nulls with the raw marker preserved." ], "status": "available", "title": "Power Fuel Receipts and Costs" }, { "access": "open", "anchors": [], "answers": [ "as-filed large-steam plant capacity, net generation, plant balances, fuel expense, and separate O&M line items", "raw respondent and plant-name searches without normalization or EIA matching", "which Form 1 respondents and raw plant names have served data for a report year", "a one-call ERCOT-relevance slice based only on the respondent's raw states-served disclosure" ], "current_sources": [ "energy.ferc.form1_plant_costs" ], "id": "power.plant_costs", "primitive": "query_power_plant_costs_v1", "product_spec": "blocks/power_plant_costs/card.md", "represented_facts": [ "Accepted native-XBRL FERC Form 1 filings report as-filed large steam-electric plant statistics by respondent, year, and raw plant name: installed capacity, net generation, plant-cost balance facts, and separate production-expense line items. Dollar values are nominal and are never inflation-adjusted, allocated, or summed into a derived O&M total." ], "status": "available", "title": "FERC Form 1 Plant Costs" }, { "access": "open", "anchors": [ "state" ], "answers": [ "daily Henry Hub spot prices in EIA's published dollars-per-MMBtu unit", "monthly state-average prices paid by electric-power consumers in EIA's published dollars-per-Mcf unit", "exact source-null state-month records, never zero-filled", "Texas monthly electric-power prices in one state-filtered call", "per-series coverage windows and separately queryable revision vintages" ], "current_sources": [ "energy.eia.natural_gas_prices" ], "id": "natural_gas.prices", "primitive": "query_natural_gas_prices_v1", "product_spec": "blocks/natural_gas_prices/card.md", "represented_facts": [ "EIA publishes the daily Henry Hub natural-gas spot price in dollars per MMBtu and monthly state-average natural-gas prices paid by electric-power consumers in dollars per Mcf. The state series is an aggregate of what the state's power sector paid in that month, not a plant-level price. Source-null state-month values remain explicit nulls and revisions remain separate capture vintages.", "Source-null state-month prices remain explicit nulls, and mixed source units are never blended." ], "status": "available", "title": "Natural Gas Prices" }, { "access": "open", "anchors": [ "balancing_authority_code" ], "answers": [ "hourly observed electricity demand (MW) for a balancing authority (Adjusted series, cited to the source row)", "the day-ahead demand forecast for the same BA-hours \u2014 forecast-vs-actual misses", "which hours EIA imputed rather than metered (is_imputed)", "BA-level demand shape over time (daily/seasonal profiles, growth at BA grain)" ], "current_sources": [ "energy.eia.eia930" ], "id": "power.demand", "primitive": "query_power_demand_v1", "product_spec": "blocks/power_demand/card.md", "represented_facts": [ "EIA-930 reports hourly observed electricity demand (MW) by balancing authority \u2014 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" ], "status": "available", "title": "Power Demand" }, { "access": "open", "anchors": [], "answers": [ "hourly observed electricity demand (MW) for the US48 national total (cited to the source record)", "hourly observed demand for any of the 13 EIA regions (CAL, CAR, CENT, FLA, MIDA, MIDW, NE, NW, NY, SE, SW, TEN, TEX)", "the day-ahead demand forecast for the same respondent-hours \u2014 forecast-vs-actual misses", "national / regional demand shape over time (daily/seasonal profiles, growth) from EIA's own published totals" ], "current_sources": [ "energy.eia.eia930_rollup" ], "id": "power.demand_rollup", "primitive": "query_power_demand_rollup_v1", "product_spec": "blocks/power_demand_rollup/card.md", "represented_facts": [ "EIA-930 reports hourly observed electricity demand (MW) as EIA's own published rollup totals \u2014 US48 (the Lower-48 national total) and the 13 EIA regions (the Adjusted series, served verbatim, not a sum)", "EIA-930 reports the day-ahead demand forecast (MW) on the same respondent-hour rows" ], "status": "available", "title": "Power Demand (national / region rollup)" }, { "access": "open", "anchors": [ "state", "eia_utility_id" ], "answers": [ "annual retail electricity sales (billed MWh) by utility, state, and customer sector", "annual retail revenue (thousand dollars) and customer counts at the same grain", "industrial / commercial demand-growth signals by state and utility (year over year, as vintages accumulate)", "service-type structure (bundled vs energy-only vs delivery-only) per utility and state" ], "current_sources": [ "energy.eia.eia861" ], "id": "power.retail_sales", "primitive": "query_power_retail_sales_v1", "product_spec": "blocks/power_retail_sales/card.md", "represented_facts": [ "EIA-861 reports annual retail electricity sold to ultimate customers \u2014 billed sales (MWh), revenue, and customer counts \u2014 by utility, state, and customer sector", "EIA-861 reports the filing part and service type (bundled / energy-only / delivery-only) behind each utility\u00d7state row" ], "status": "available", "title": "Power Retail Sales" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which generation projects have requested to connect to the MISO grid, by state/county, fuel, technology, and status", "the requested (net summer / net winter) megawatts of each queued project, cited to its source row", "the as-reported application status, study phase, and post-GIA status of each project (kept separate, never collapsed)", "the count of queued projects in a scope (active vs withdrawn vs done \u2014 by filtering application_status)" ], "current_sources": [ "energy.miso.giqueue" ], "id": "power.interconnection_queue", "primitive": "query_power_interconnection_queue_v1", "product_spec": "blocks/power_interconnection_queue/card.md", "represented_facts": [ "MISO's generator interconnection queue reports each project's REQUESTED interconnection capacity (net summer / net winter MW) \u2014 a request, not built capacity", "MISO's queue reports each project's location (state, county), fuel and technology, three as-reported status dimensions (application status, study phase, post-GIA status), and lifecycle dates (queue, withdrawn, in-service, done)", "MISO also reports two sparse lifecycle dates served under MISO's own field labels \u2014 gia_to_exec_date and neg_in_service_date; MISO publishes no data dictionary, so these are served as-reported and not reinterpreted (present where MISO reports them, null otherwise)" ], "status": "available", "title": "Power Interconnection Queue (MISO)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which projects have requested to connect to the PJM grid, by state/county, fuel, project type, and status", "the requested (max-facility-output / net summer / net winter) megawatts of each queued project, cited to its source row", "the as-reported status of each PJM project (Active / Withdrawn / In Service / Under Construction / \u2026), kept verbatim", "the realized in-service (built) megawatts of completed PJM projects (in_service_mw), separate from requested MW", "the count of queued projects in a scope (active vs withdrawn vs in service \u2014 by filtering status)" ], "current_sources": [ "energy.pjm.queue" ], "id": "power.interconnection_queue_pjm", "primitive": "query_power_interconnection_queue_pjm_v1", "product_spec": "blocks/power_interconnection_queue_pjm/card.md", "represented_facts": [ "PJM's New Services (interconnection) queue reports each project's REQUESTED interconnection capacity (MFO / net summer / net winter MW) \u2014 a request, not built capacity", "PJM's queue reports each project's location (state, POI county), fuel and project type, the single as-reported status, the study-document URLs and per-stage statuses, and lifecycle dates", "PJM also reports in_service_mw \u2014 the realized BUILT MW for in-service projects \u2014 carried under its own name, never as a requested figure" ], "status": "available", "title": "Power Interconnection Queue (PJM)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which projects are in PJM's cluster cycles (TC1/TC2 transition, C01+ reopened), by cycle, stage, state, fuel, and status", "the requested (MFO / net summer / net winter) megawatts of each cluster-cycle project, cited to its source row", "the cluster stage / decision point and developer of each project, as PJM reports them", "the realized in-service (built) megawatts and long-term-firm transmission MW, separate from requested MW", "the count of cluster-cycle projects in a scope (e.g. cycle=C01, status=Active)" ], "current_sources": [ "energy.pjm.cycle" ], "id": "power.interconnection_queue_pjm_cycle", "primitive": "query_power_interconnection_queue_pjm_cycle_v1", "product_spec": "blocks/power_interconnection_queue_pjm_cycle/card.md", "represented_facts": [ "PJM's cluster/cycle grid reports each project's cluster cycle (TC1/TC2 transition, C01+ reopened steady-state) and stage, with its REQUESTED interconnection capacity (MFO / net summer / net winter MW) \u2014 a request, not built capacity", "PJM's cycle grid reports each project's developer, location (state, county), fuel, phased System-Impact-Study report URLs + statuses, and lifecycle dates", "PJM also reports in_service_mw (realized built MW) and ltf_mw (long-term firm transmission MW), carried under their own names; this is a separate publication from PJM's New Services queue and is never merged with it" ], "status": "available", "title": "Power Interconnection Queue (PJM cluster/cycle)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which projects have requested to connect to the CAISO grid, by state/county, fuel/technology, cluster, deliverability, and status", "the net megawatts to grid of each queued CAISO project, cited to its source row", "the as-reported application status of each CAISO project (Active / Completed / Withdrawn), kept verbatim by tab", "each project's deliverability status (Full Capacity / Partial Capacity / Energy Only), TPD allocation, and cluster (study process), as CAISO reports it", "the count of projects in a scope (active vs completed vs withdrawn \u2014 by filtering application_status)" ], "current_sources": [ "energy.caiso.queue" ], "id": "power.interconnection_queue_caiso", "primitive": "query_power_interconnection_queue_caiso_v1", "product_spec": "blocks/power_interconnection_queue_caiso/card.md", "represented_facts": [ "CAISO's Public Queue Report reports each project's REQUESTED interconnection capacity (Net MWs to Grid) \u2014 a request, not built capacity \u2014 across the Active, Completed, and Withdrawn lifecycle tabs", "CAISO's queue reports each project's location (state, county), the Type/Fuel/MW hybrid triplets, the three-valued deliverability status (Full Capacity / Partial Capacity / Energy Only) with TPD allocation, the cluster study process, the per-phase study statuses, and lifecycle dates", "CAISO carries the requested-vs-built distinction in application_status + the lifecycle tab \u2014 a COMPLETED project carries an actual_online_date (the realized in-service date); CAISO publishes no separate built-MW column" ], "status": "available", "title": "Power Interconnection Queue (CAISO)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which projects have requested to connect to the NYISO grid, by state/county, fuel/technology, zone, and status", "the summer-peak (sp_mw) and winter-peak (wp_mw) megawatts of each queued NYISO project, cited to its source row", "NYISO load interconnection requests (the Load Projects tab) with their peak_mw_load, served as-reported", "the as-reported lifecycle status of each NYISO project (active / withdrawn / in-service / affected-system), kept by tab", "the as-reported study-phase code (study_status_code) and which studies are available, as NYISO reports them", "NYISO's own End-Use class per load request (end_use, 2026-07 edition onward, e.g. DAT / DAT-AI / DAT-CM, served verbatim) and the SIS study bundle (sis_bundle)", "the count of projects in a scope (active vs withdrawn vs in-service \u2014 by filtering application_status or sheet_name)" ], "current_sources": [ "energy.nyiso.queue" ], "id": "power.interconnection_queue_nyiso", "primitive": "query_power_interconnection_queue_nyiso_v1", "product_spec": "blocks/power_interconnection_queue_nyiso/card.md", "represented_facts": [ "NYISO's Interconnection Queue reports each project's REQUESTED interconnection capacity \u2014 summer (SP) and winter (WP) peak MW, kept separate \u2014 across every lifecycle tab NYISO publishes (nine through 2026-06; seven since the 2026-07 restructure folded the load/affected-system withdrawn lists into the active tabs under NYISO's own 0=Withdrawn code); a request, not built capacity", "NYISO uniquely publishes a Load Projects tab \u2014 load interconnection requests with their own peak_mw_load, and (since 2026-07) NYISO's own End-Use class per request (end_use, e.g. DAT / DAT-AI / DAT-CM, served verbatim \u2014 NYISO publishes no key for these codes) plus the SIS Bundle study-batch code (sis_bundle)", "NYISO carries the requested-vs-built distinction in application_status (the lifecycle tab's reading, overridden to the withdrawn form on NYISO's own status code 0) + study_status_code; the In Service tab is the built reading, and a project may appear on more than one tab (grain = sheet + queue_position)" ], "status": "available", "title": "Power Interconnection Queue (NYISO)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which projects have requested to connect to the ISO-NE grid, by state/county, fuel/technology, zone, and status", "the net / summer-peak / winter-peak megawatts of each queued ISO-NE project, cited to its source row", "the as-reported lifecycle status of each project (A=Active / C=Commercial / W=Withdrawn), kept separate from build-progress project_status", "the build-progress project_status (Under Study / Under Construction / In Service / \u2026), as ISO-NE reports it, never collapsed into application_status", "the request type (G=Generation / ETU=Elective Transmission Upgrade / TS=Transmission Service) and per-stage study statuses, as ISO-NE reports them", "the count of projects in a scope (active vs commercial vs withdrawn \u2014 by filtering application_status)" ], "current_sources": [ "energy.isone.queue" ], "id": "power.interconnection_queue_isone", "primitive": "query_power_interconnection_queue_isone_v1", "product_spec": "blocks/power_interconnection_queue_isone/card.md", "represented_facts": [ "ISO-NE's IRTT public-queue report lists each project's REQUESTED interconnection capacity \u2014 net, summer-peak and winter-peak MW, kept separate \u2014 for generation, elective-transmission-upgrade and transmission-service requests; a request, not built capacity", "ISO-NE carries the requested-vs-built distinction in application_status (A=Active / C=Commercial / W=Withdrawn) and a SEPARATE build-progress project_status (Under Study / Under Construction / In Service / \u2026), never collapsed; a Commercial project is the built reading", "ISO-NE publishes no load/data-center request type (all rows are generation or transmission); the queue-position (QP) is a non-unique reference reused across historical projects, so the grain is the published row ordinal" ], "status": "available", "title": "Power Interconnection Queue (ISO-NE)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which generation projects have requested to connect to the ERCOT (Texas) grid, by county, fuel, technology, CDR reporting zone, lifecycle, and size", "the requested capacity (MW) of each queued ERCOT project, cited to its source row", "the as-reported lifecycle of each project (ACTIVE / INACTIVE / CANCELLED, derived from ERCOT's own sheet structure), kept separate from build progress", "the build-progress signal \u2014 the GIM Study Phase token string and the milestone dates (screening study, FIS, IA signed, construction, energization), as ERCOT reports them", "the count of projects in a scope (active vs inactive vs cancelled \u2014 by filtering application_status)" ], "current_sources": [ "energy.ercot.queue" ], "id": "power.interconnection_queue_ercot", "primitive": "query_power_interconnection_queue_ercot_v1", "product_spec": "blocks/power_interconnection_queue_ercot/card.md", "represented_facts": [ "ERCOT's GIS Report lists each generation project's REQUESTED interconnection capacity (capacity_mw \u2014 one figure, no summer/winter split) across four lifecycle sheets (Large/Small Gen active, plus Inactive and Cancellation); a request, not built capacity", "ERCOT publishes no status column, so application_status (ACTIVE / INACTIVE / CANCELLED) is derived from the sheet the project is filed on (sheet_name served verbatim), and the build-progress reading is carried SEPARATELY in gim_study_phase + the milestone dates, never collapsed", "ERCOT files a hybrid project's legs as separate INR rows linked only by a shared poi_location (no in-row hybrid encoding); the GIS Report is generation-only and reports no load/data-center type" ], "status": "available", "title": "Power Interconnection Queue (ERCOT)" }, { "access": "open", "anchors": [ "state", "county_fips" ], "answers": [ "which generation projects have requested to connect to the SPP grid, by state, county, generation type, fuel, study cluster, transmission owner, and status", "the requested capacity (MW) of each queued SPP project, cited to its source row (and the five other MW columns SPP publishes, each labeled and never blended)", "the as-reported SPP status of each project (SPP's own vocabulary, kept verbatim with a per-source codebook), so an agent can scope to active vs withdrawn vs terminated", "the study cluster (DISIS-YYYY-NNN / Surplus / RTOE Transitional) and SPP regional cluster group, as SPP reports them", "the count of projects in a scope (by filtering native_status, state, generation_type, \u2026)" ], "current_sources": [ "energy.spp.queue" ], "id": "power.interconnection_queue_spp", "primitive": "query_power_interconnection_queue_spp_v1", "product_spec": "blocks/power_interconnection_queue_spp/card.md", "represented_facts": [ "SPP's GI Summary lists each generation project's REQUESTED interconnection capacity (capacity_mw \u2014 SPP's headline figure, with five other labeled MW columns served and never blended); a request, not built capacity", "SPP publishes a native Status column whose vocabulary it controls, so native_status is served VERBATIM with a codebook (never mapped to a lifecycle enum); ~66% of rows are WITHDRAWN, so a total is scoped by native_status, never read as built", "SPP spans ~14 central-US states (state is a real anchor), carries only a free-text town-or-county (county_fips derived by name where it resolves, else null), encodes hybrids natively as a Hybrid generation_type (no is_hybrid invented), and is generation-only (no load/data-center type)" ], "status": "available", "title": "Power Interconnection Queue (SPP)" }, { "access": "open", "anchors": [ "state" ], "answers": [ "the day-ahead wholesale price ($/MWh) at an ERCOT settlement point for a given delivery day and hour, cited to its source row", "the price at a named hub (e.g. HB_NORTH, HB_HOUSTON) or load zone (e.g. LZ_HOUSTON) \u2014 the regional benchmark prices", "the daily price shape at a settlement point (the 24 hourly day-ahead prices), and average / minimum / maximum price over a window", "how a settlement point is classified by ERCOT (Hub / Load Zone / Resource Node / DC-tie, as ERCOT's own verbatim code), so a single-plant node is not mistaken for a regional benchmark", "the price spread across settlement points or types for a given hour or day" ], "current_sources": [ "energy.ercot.prices" ], "id": "power.price_ercot", "primitive": "query_power_price_ercot_v1", "product_spec": "blocks/power_price_ercot/card.md", "represented_facts": [ "ERCOT's Day-Ahead Market Settlement Point Prices (NP4-190-CD) \u2014 the price ($/MWh) cleared the day before each operating day at every ERCOT settlement point, served hourly and point by point as a TOTAL (no energy/congestion/loss split; none is synthesized)", "a price is intensive ($/MWh): it is averaged / min'd / max'd over a scope, never summed; ERCOT's own hour-ending label and DST flag are carried verbatim (24 hours normally, 25 on the fall-back date, 23 on spring-forward)", "settlement_point_type is ERCOT's OWN verbatim classification (HU hub / LZ load zone / RN resource node / DC-tie \u2026), joined from ERCOT's published settlement-points list and never collapsed; a settlement point is electrical/aggregate, not a plant \u2014 the only geography anchor is state = TX", "historical delivery coverage begins 2014-05-02 from ERCOT's Data Access Portal archives; settlement-point names remain exactly as published in each vintage, and an older name absent from the current type reference receives a null type rather than a rewrite or guess" ], "status": "available", "title": "Power Prices (ERCOT day-ahead)" }, { "access": "key", "anchors": [], "answers": [ "PJM's cited marginal ELCC accreditation fraction for a resource class in a named auction document", "how preliminary-outlook ratings differ from final-auction or incremental-auction ratings without reconciling them", "all PJM resource classes in a linked class-ratings table, with the verbatim class name and normalized family" ], "current_sources": [ "energy.pjm.elcc" ], "id": "power.capacity_accreditation_pjm", "primitive": "query_power_capacity_accreditation_pjm_v1", "product_spec": "blocks/power_capacity_accreditation_pjm/card.md", "represented_facts": [ "PJM-published marginal Effective Load Carrying Capability (ELCC) class ratings, as a fraction of nameplate capacity, for each resource class and delivery year in each linked final Base Residual Auction document, Incremental Auction document, or preliminary multi-year outlook. Document identity is a dimension: preliminary and final ratings for the same delivery year are separate cited atoms and are never merged, preferred, reconciled, or corrected by this block." ], "status": "available", "title": "PJM ELCC Class Ratings (internal)" }, { "access": "key", "anchors": [], "answers": [ "RTO-wide and separated-LDA UCAP capacity-market clearing prices for a named PJM delivery year", "cleared RTO UCAP MW and the report-stated RTO reliability requirement where published", "the administrative price cap and floor as each stating document publishes them, making a cap-bound clearing visible", "for auctions with no stated collar, which documents were searched, so a None cap is provably not-stated", "documented coverage from delivery year 2018/2019 onward, with unsupported source formats recorded as exceptions" ], "current_sources": [ "energy.pjm.capacity_market" ], "id": "power.capacity_market_pjm", "primitive": "query_power_capacity_market_pjm_v1", "product_spec": "blocks/power_capacity_market_pjm/card.md", "represented_facts": [ "PJM Reliability Pricing Model Base Residual Auction results: UCAP-basis resource clearing prices in USD per MW-day for the RTO and published LDAs, RTO cleared UCAP MW, the stated RTO reliability requirement, and any administrative price cap and floor stated in the auction results report or the planning-period-parameters workbook/report \u2014 each on the basis its stating document uses, quoted verbatim in cap_basis. Documents searched for a collar that state none yield a collar_search atom, so absence is provably \"not stated\", never \"not parsed\". Workbook and report facts remain separate cited atoms at their exact source coordinates." ], "status": "available", "title": "PJM RPM Capacity-Market Results (internal)" }, { "access": "key", "anchors": [], "answers": [ "the Schedule 53 class-average ISAC/ICAP ratio for a named resource class, season, and planning year, with its count of contributing units", "indicative DLOL class-level UCAP/ICAP ratios per season ahead of the Schedule 53A go-live, including each published storage modeling variant", "which resource classes MISO suppressed below its 30-unit threshold, so a missing ratio is provably not-published", "the fleetwide Schedule 53 class average that suppressed classes are granted", "preliminary vs indicative document identity for the same planning year as separate cited atoms" ], "current_sources": [ "energy.miso.accreditation" ], "id": "power.capacity_accreditation_miso", "primitive": "query_power_capacity_accreditation_miso_v1", "product_spec": "blocks/power_capacity_accreditation_miso/card.md", "represented_facts": [ "MISO-published seasonal capacity accreditation ratios per resource class, as a fraction of installed capacity (ICAP), from two coexisting tariff constructs kept apart by document_kind: Schedule 53 class-average ISAC/ICAP ratios (the construct binding until Planning Year 2027-2028) and indicative Direct Loss of Load class-level UCAP/ICAP ratios published under Schedule 53A ahead of its 2028-2029 implementation. Storage classes served under multiple DLOL modeling variants are separate cited atoms carrying the stated variant, never blended. Classes MISO suppresses for data-integrity/confidentiality (<30 contributing units) yield a suppression atom, so absence is provably \"not published\", never \"not parsed\". Ratios from different documents or constructs are never merged, preferred, or reconciled by this block." ], "status": "available", "title": "MISO Capacity Accreditation (internal)" }, { "access": "key", "anchors": [], "answers": [ "the seasonal zonal Auction Clearing Price for a named MISO planning year, season, and zone", "the External Resource Zone clearing exactly as stated, including verbatim price ranges", "seasonal subregional CONE and annual zonal CONE as the posting publishes them, making cap-adjacent clearings visible", "the IMM conduct threshold published beside the auction results", "documented seasonal coverage from the 2024 PRA posting onward, corrections postings as distinct cited documents" ], "current_sources": [ "energy.miso.pra" ], "id": "power.capacity_market_miso", "primitive": "query_power_capacity_market_miso_v1", "product_spec": "blocks/power_capacity_market_miso/card.md", "represented_facts": [ "MISO Planning Resource Auction results as published in the annual PRA results posting: seasonal zonal Auction Clearing Prices in USD per MW-day of Seasonal Accredited Capacity for Zones 1-10, External Resource Zone clearing quoted verbatim where the document states a range, seasonal subregional and annual zonal Cost of New Entry values, and the Independent Market Monitor conduct thresholds the posting publishes beside them. CONE is recorded as the document's stated administrative parameter \u2014 the price-cap analog \u2014 on the basis its stating document uses, never interpreted, annualized, or converted by this block. A corrections posting is a distinct document identity: its atoms cite the corrections file, and earlier postings are never silently replaced." ], "status": "available", "title": "MISO PRA Capacity-Market Results (internal)" } ], "id": "power" }, { "capabilities": [ { "access": "open", "anchors": [], "answers": [ "monthly private data-center construction spending ($ millions), seasonally-adjusted annual rate or not-adjusted monthly level (cited to the source cell)", "monthly private computer/electronic/electrical (semiconductor-fab) construction spending ($ millions)", "the data-center vs fab construction-spending trend over time (each as its own per-month series)", "whether a given month's value is preliminary, revised, or final (the Census revision status, carried verbatim)" ], "current_sources": [ "construction.census.c30_vip" ], "id": "ai_infrastructure.construction", "primitive": "query_ai_infrastructure_construction_v1", "product_spec": "blocks/ai_infrastructure_construction/card.md", "represented_facts": [ "Census C30 (Value of Construction Put in Place) reports the monthly value of private DATA-CENTER construction put in place ($ millions), served both seasonally-adjusted (annual rate) and not-seasonally-adjusted (monthly level), verbatim and cited", "Census C30 reports the monthly value of private COMPUTER/ELECTRONIC/ELECTRICAL (semiconductor-fab) construction put in place ($ millions) on the same two bases" ], "status": "available", "title": "AI Infrastructure Construction (data centers + fabs)" }, { "access": "open", "anchors": [], "answers": [ "monthly U.S. import value (USD) of all integrated circuits \u2014 HS-8542 \u2014 cited to the source row", "chip imports by country of origin (e.g. Taiwan, Malaysia, South Korea, Israel) \u2014 supply-source concentration", "the U.S. chip-import trend over time (each country / grouping / the national total as its own monthly series)", "general imports value vs imports-for-consumption value at the same grain" ], "current_sources": [ "trade.census.intltrade_imports_hs" ], "id": "ai_infrastructure.trade", "primitive": "query_ai_infrastructure_trade_v1", "product_spec": "blocks/ai_infrastructure_trade/card.md", "represented_facts": [ "Census International Trade reports the monthly customs value (USD) of U.S. imports of HS-8542 'Electronic integrated circuits' \u2014 ALL integrated circuits (processors, memory, amplifiers, parts), not AI-accelerator-specific \u2014 by country of origin, as general imports and imports-for-consumption value, served verbatim and cited", "Census reports these imports across overlapping country GROUPINGS (ASIA, APEC, EU, OECD, ASEAN, the continents) and an all-countries TOTAL; the groupings overlap each other and the countries, so they are never summed \u2014 the served TOTAL is the only national figure" ], "status": "available", "title": "AI Infrastructure Trade (chip imports)" }, { "access": "open", "anchors": [], "answers": [ "monthly U.S. import value (USD) of semiconductor-manufacturing equipment \u2014 HS-8486 \u2014 cited to the source row", "equipment imports by country of origin (e.g. Japan, the Netherlands, South Korea, Singapore) \u2014 tool-supply concentration", "the fab-buildout TOOLING trend \u2014 equipment flowing in between construction (C30) and chip output (HS-8542)", "general imports value vs imports-for-consumption value at the same grain" ], "current_sources": [ "trade.census.intltrade_equipment_hs" ], "id": "ai_infrastructure.equipment_trade", "primitive": "query_ai_infrastructure_equipment_trade_v1", "product_spec": "blocks/ai_infrastructure_equipment_trade/card.md", "represented_facts": [ "Census International Trade reports the monthly customs value (USD) of U.S. imports of HS-8486 'Machines and apparatus for the manufacture of semiconductor boules/wafers, devices, integrated circuits or flat panel displays' \u2014 the chip-MAKING equipment (which includes flat-panel-display machinery), NOT the chips themselves \u2014 by country of origin, as general imports and imports-for-consumption value, served verbatim and cited", "Census reports these imports across overlapping country GROUPINGS (ASIA, APEC, EU, OECD, ASEAN, the continents) and an all-countries TOTAL; the groupings overlap each other and the countries, so they are never summed \u2014 the served TOTAL is the only national figure" ], "status": "available", "title": "AI Infrastructure Equipment Trade (chip-making tools)" }, { "access": "open", "anchors": [], "answers": [ "the monthly industrial-production index (2017=100) for semiconductor & other electronic component manufacturing (NAICS 3344), seasonally adjusted or not adjusted, cited to the Fed's source observation", "monthly capacity utilization (percent, seasonally adjusted) for the same industry \u2014 how hot the domestic fabs and component plants are running", "the monthly capacity index (2017=100) behind the utilization rate", "the production / utilization trend over time (each series as its own per-month reading, averaged \u2014 never summed \u2014 over windows)" ], "current_sources": [ "production.fed.g17" ], "id": "ai_infrastructure.production", "primitive": "query_ai_infrastructure_production_v1", "product_spec": "blocks/ai_infrastructure_production/card.md", "represented_facts": [ "Fed G.17 reports the monthly industrial-production index (2017=100, seasonally adjusted and not adjusted) for semiconductor and other electronic component manufacturing (NAICS 3344) \u2014 the finest split G.17 publishes for this family, served verbatim and cited to the Board's SDMX observation", "Fed G.17 reports monthly capacity utilization (percent) and the capacity index (2017=100) for the same industry, seasonally adjusted only; an index or a rate is intensive \u2014 averaged over a window, never summed" ], "status": "available", "title": "AI Infrastructure Production (semiconductor output and utilization)" } ], "id": "ai_infrastructure" }, { "capabilities": [ { "access": "open", "anchors": [], "answers": [ "monthly U.S. imports of industrial robots in DOLLARS and in UNITS (robot counts) \u2014 cited to the source row", "robot imports by country of origin (e.g. Japan, China, South Korea, Germany, Mexico) \u2014 supply concentration", "the two robot categories separately \u2014 multipurpose robots (8479.50) vs lifting/handling robots (8428.70)", "general imports vs imports-for-consumption at the same grain, value and units" ], "current_sources": [ "trade.census.intltrade_robotics_hs" ], "id": "robotics.trade", "primitive": "query_robotics_trade_v1", "product_spec": "blocks/robotics_trade/card.md", "represented_facts": [ "Census International Trade reports the monthly customs value (USD) AND unit count (number of robots) of U.S. imports of industrial robots \u2014 HS-10 8479500000 'INDUSTRIAL ROBOTS, NESOI' (multipurpose) and 8428700000 'INDUSTRIAL ROBOTS FOR LIFTING, HANDLING, LOADING OR UNLOADING' (created by HS 2022; no data before 2022-01) \u2014 by country of origin, as general imports and imports-for-consumption, served verbatim and cited", "Census reports these imports across overlapping country GROUPINGS (ASIA, APEC, EU, OECD, ASEAN, the continents) and an all-countries TOTAL; the groupings overlap each other and the countries, so they are never summed \u2014 the served TOTAL is the only national figure" ], "status": "available", "title": "Robotics Trade (industrial-robot imports, value + robot counts)" }, { "access": "open", "anchors": [ "state" ], "answers": [ "what share of US manufacturing plants use industrial robots \u2014 nationally, by state, by industry (NAICS), by plant size \u2014 the only official installed-base adoption series", "what share of manufacturing employees work at plants with robots, at the same grains", "robotics capital expenditures ($1000) by industry, state, and plant size", "how adoption differs across plant sizes (small plants barely automate; large plants dominate)", "each edition separately (ASM 2018-2021 annual series; EC 2022 census snapshot), with the coverage break between them named, never spliced" ], "current_sources": [ "robotics.census.robotic_equipment" ], "id": "robotics.adoption", "primitive": "query_robotics_adoption_v1", "product_spec": "blocks/robotics_adoption/card.md", "represented_facts": [ "The Census Industrial Robotic Equipment product (experimental \u2014 the first official federal robotics-adoption statistics) reports the percent of manufacturing plants with industrial robots, the percent of manufacturing employees at plants with robots, and robotics capital expenditures ($1000) by NAICS industry, state, and plant size, in two editions (ASM 2018-2021 and the 2022 Economic Census), served verbatim and cited to the exact workbook cell-group", "The two editions measure different coverage universes (the 2022 Economic Census reaches small plants the ASM sample does not \u2014 US plants-with-robots 12.1% ASM-2021 vs 6.4% EC-2022), so editions are compared, never spliced into one series (PD-066)" ], "status": "available", "title": "Robotics Adoption (share of plants using robots, workers exposed, robotics capex)" } ], "id": "robotics" }, { "capabilities": [ { "access": "open", "anchors": [ "state" ], "answers": [ "every FCC space-station filing on record \u2014 by applicant, application type, status, and filing date \u2014 each cited to its exact record in the FCC's own database dump", "the licensing trail of any satellite system or operator (e.g. every SpaceX / Intelsat / Kuiper filing), with the FCC's own description text", "where each filing stood when the FCC last generated the dump (2026-07-16) \u2014 the FCC's own status vocabulary, decoded from the same dump vintage (granted, pending, dismissed, surrendered)", "filing counts by applicant, type, status, state (applicant address), or period \u2014 the satellite-buildout pipeline signal back to the 1960s", "the lifecycle dates of any filing (filed, granted, expires, \u2026), e.g. when an authorization expires" ], "current_sources": [ "space.fcc.ibfs_sat" ], "id": "space.satellite_filings", "primitive": "query_space_satellite_filings_v1", "product_spec": "blocks/space_satellite_filings/card.md", "represented_facts": [ "The FCC's IBFS daily bulk database dump records every space-station (SAT-subsystem) filing in the FCC satellite licensing docket back to the 1960s \u2014 file number, call sign, application type and status in the FCC's own vocabulary (verbatim codes plus the FCC's own decode text from the same dump vintage), the full lifecycle date family, the FCC's plain-English description, and the applicant identity joined by the source's own address_key \u2014 served as-reported and cited to the exact record", "New-filing intake into IBFS structurally ended at the FCC's ICFS system cutover (~mid-2025; measured: zero 2026-filed records), and ICFS publishes no bulk data \u2014 so filings submitted after the cutover are not in this source (PD-064, engraved as a refusal); they are served from the FCC's weekly satellite public notices as space.satellite_notices (PD-077)", "The FCC has not regenerated the IBFS dump since 2026-07-16 (it previously updated daily), so status changes after that date are not reflected in this source" ], "status": "available", "title": "Space Satellite Filings (FCC satellite licensing docket)" }, { "access": "open", "anchors": [], "answers": [ "which satellite applications the FCC accepted for filing since mid-2025 (the ICFS era), with applicant, call sign, filing type, Date filed and the FCC's own description \u2014 each cited to its line in the notice", "which satellite filings the FCC granted, partly granted, dismissed or otherwise acted on, and the printed date of each action", "the ICFS-era licensing trail of an operator or call sign (e.g. every SpaceX, Amazon Kuiper or AST SpaceMobile listing since mid-2025)", "counts of notice listings by kind, filing type, action, applicant or release period" ], "current_sources": [ "space.fcc.sat_public_notices" ], "id": "space.satellite_notices", "primitive": "query_space_satellite_notices_v1", "product_spec": "blocks/space_satellite_notices/card.md", "represented_facts": [ "The FCC Space Bureau publishes two satellite public notices each week \u2014 Applications Accepted for Filing and Actions Taken \u2014 listing each filing's FCC file number, call sign, applicant, Date filed and filing type, and on Actions Taken notices the action and its Date of Action; every listing since the 2025-06-18 ICFS cutover is served as printed and cited to its line in the notice text", "The notices are the FCC's public announcement record, not its full docket: they carry no status history, omit filings the FCC has not noticed, and can print a different Date filed or applicant name for the same filing in different weeks (PD-077)" ], "status": "available", "title": "Space Satellite Notices (FCC weekly satellite public notices)" } ], "id": "space" } ], "version": "v1" }, "tool": "list_capabilities_v1" }, { "params": {}, "result": { "anchors": [], "capability": "space.satellite_notices", "codebooks": {}, "data_point": { "does_not_answer": [ "the full status history or current status of a filing (the notices announce acceptances and actions only; there is no ICFS bulk docket)", "filings the FCC has not listed in a public notice, or listed before the ICFS cutover (those are space.satellite_filings)", "a count of distinct filings from source_record_count (one filing can be listed in several notices)", "satellites in orbit, an orbital catalog, launch activity or a satellite count", "earth-station (SES) or other non-SAT notices", "technical parameters beyond the entry text as printed (frequencies and orbits are not structured)" ], "grain": "notice_entry", "id": "space.satellite_notices", "note": "These are the FCC Space Bureau's weekly satellite public notices since the ICFS cutover (2025-06-18), served as printed: every filing listed as accepted for filing and every action the FCC took. One record is one listing in one notice, so a filing can appear several times and source_record_count counts listings, not distinct filings. The notices carry no status history and omit filings the FCC has not noticed. Filings before the cutover are query_space_satellite_filings_v1. A filing is never a satellite count, an orbital catalog or launch activity.", "product_spec": "blocks/space_satellite_notices/card.md", "represented_fact": "The FCC Space Bureau's weekly satellite (SAT) public notices since the ICFS cutover (2025-06-18, DA 25-510), served as printed: every filing listed in an \"Applications Accepted for Filing\" notice (new applications) or an \"Actions Taken\" notice (grants, partial grants, dismissals, surrenders, consummations, withdrawals), one atom per listing. Each carries the notice (report number, kind, release date, DA number, links), the FCC file number (SAT-MOD-20260603-00225) and its type code, the call sign, the applicant as printed, the printed Date filed, the filing type, and on Actions Taken notices the action and its printed Date of Action, plus the entry text verbatim. Values are what each notice prints \u2014 the same filing can be listed in several notices and can print a different Date filed or applicant name in each. The notices carry no status history and omit filings the FCC never notices; they are the FCC's public announcement record, not its full docket. Filings before the cutover are space.satellite_filings (the IBFS docket, whose bulk dump stopped updating on 2026-07-16). A filing is an authorization request or action, never a satellite count, an orbital catalog or launch activity.", "source_basis": [ "space.fcc.sat_public_notices" ], "source_decisions": [ "docs/product/decisions/PD-077-space-satellite-notices-serve-fcc-weekly-sat-notices.md" ] }, "input": { "controls": [ "include_records", "include_evidence", "limit", "order_by", "top_n", "order", "rollup_other" ], "date_range_params": [ "report_period_from", "report_period_to", "date_filed_from", "date_filed_to", "action_date_from", "action_date_to" ], "date_ranges": [ "report_period", "date_filed", "action_date" ], "field_metadata": { "action_date": { "answer_label": "date of action (as printed)", "counting_definition": "A date, not a number; filter with action_date_from / action_date_to.", "definition": "On an Actions Taken notice, the date printed for \"Date of Action\". Null when the notice prints none; the notice states that its release date is then the effective date. Always null on Accepted for Filing notices.", "semantics": "fcc_notice_printed_action_date", "source_field": "action_date" }, "applicant": { "answer_label": "applicant (as printed)", "counting_definition": "A label, not a number; group by applicant for per-operator counts.", "definition": "The applicant or licensee name exactly as this notice prints it (a name wrapped across two lines is rejoined). The printed name can differ over time: filing SAT-MOD-20240508-00096 is Maxar License Inc. in the IBFS docket and Vantor License Inc. in 2026 notices. Null when the notice prints no name. Matched case-insensitively.", "semantics": "fcc_notice_printed_applicant", "source_field": "applicant" }, "date_filed": { "answer_label": "date filed (as printed)", "counting_definition": "A date, not a number; filter with date_filed_from / date_filed_to.", "definition": "The \"Date filed\" this notice prints for the filing. The same filing can print a different date in different notices (e.g. an acceptance notice and a later action notice); each listing keeps its own.", "semantics": "fcc_notice_printed_date_filed", "source_field": "date_filed" }, "entry_text": { "answer_label": "entry text (as printed)", "counting_definition": "Free text, never aggregated.", "definition": "Every line the notice prints for this filing, verbatim (page footers removed), including the FCC's description of the request or action and any columns the notice does not label. Served on DETAIL records.", "semantics": "fcc_notice_entry_text_verbatim", "source_field": "entry_text" }, "informative": { "answer_label": "listed as informative", "counting_definition": "A flag; filter informative=false to exclude informative listings.", "definition": "True when the notice lists the filing under its INFORMATIVE: heading rather than as an action or acceptance of that week.", "semantics": "fcc_notice_informative_section", "source_field": "informative" } }, "filters": [ "as_of", "notice_kind", "filing_type_code", "action", "applicant", "report_number", "file_number", "call_sign", "informative", "report_period", "date_filed", "action_date" ], "group_by": [ "notice_kind", "filing_type_code", "action", "applicant", "report_number" ], "ranking": { "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": [ "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": { "aggregate_citation_fields": [ "source_id", "publisher", "source_url", "source_file", "raw_file_sha256", "as_of", "source_rows_count", "source_rows_sample", "verify", "lineage_filter" ], "citation_fields": [ "source_id", "source_url", "source_file", "sheet", "source_row", "file_number", "raw_file_sha256", "as_of" ], "detail_fields": [ "source_id", "sheet_name", "notice_doc_id", "report_number", "notice_kind", "da_number", "notice_url", "notice_pdf_url", "file_number", "filing_type_code", "call_sign", "applicant", "filing_type", "action", "entry_text", "source_record_key", "informative", "release_date", "date_filed", "action_date", "report_period", "source_row_number", "as_of", "raw_file_sha256", "citation" ], "metric_groups": { "records": [ "source_record_count" ] }, "metric_metadata": { "source_record_count": { "additive_across_groups": true, "aggregation": "count source records", "authoritative_total_path": "summary.totals.source_record_count", "category": "records", "definition": "Count of filing listings in the FCC Space Bureau's weekly satellite public notices in the current result scope. A filing listed in several notices counts once per listing \u2014 never a count of distinct filings or of satellites.", "description": "Number of notice listings contributing to the value. To count distinct filings, group or filter by file_number; the notices list only what the FCC announced (accepted applications and actions), not its full docket.", "display_name": "Notice listing count", "display_precision": "Integer.", "grain": "notice listing", "null_handling": "Always an integer count. An empty scope means no matching listings \u2014 not a measured zero of filing activity.", "rollup_behavior": "additive_partition_metric", "row_metric_path": "rows[].metrics.source_record_count", "source_fields": [ "source_record_key" ], "unit": "count" } }, "metrics": [ "source_record_count" ], "summary_fields": [ "group_count", "totals" ] }, "primitive": "query_space_satellite_notices_v1", "status": "available" }, "tool": "describe_space_satellite_notices_v1" }, { "params": { "file_number": "SAT-RPL-20260727-00312", "include_records": true, "limit": 1 }, "result": { "as_of": "2026-09-27", "citations": { "c1": { "source_rows_count": 1, "verify": { "as_of": "2026-09-27", "file_number": "SAT-RPL-20260727-00312", "raw_file_sha256": "3da714e4ddea2f246d8eaaf3b84e992cd37e20b187038ee73b834c8e8699b868", "sheet": "DOC-425356A1", "source_file": "sat_notices_sample.json", "source_id": "space.fcc.sat_public_notices", "source_row": 45, "source_url": "https://docs.fcc.gov/public/attachments/DOC-425356A1.txt" } } }, "notes": [ { "code": "notice_scope", "field": "source_record_count", "message": "These are the FCC Space Bureau's weekly satellite public notices since the ICFS cutover (2025-06-18), served as printed: 'Applications Accepted for Filing' (new applications) and 'Actions Taken' (grants, partial grants, dismissals, surrenders and similar). One entry is one listing of a filing in one notice, so the same filing can appear in several notices and source_record_count counts listings, not distinct filings. Values are what each notice prints: the same filing can show a different date_filed in different notices, and applicant is the name printed at that time. action_date is null when the notice prints none; the notice states its release date is the effective date unless one is specified. The notices carry no status history, and a filing the FCC has not listed is absent. For filings before the cutover use query_space_satellite_filings_v1. A filing is an authorization request or action, never a satellite count, an orbital catalog or launch activity. Pass filters INSIDE a `params` object, e.g. {\"params\": {\"notice_kind\": \"Actions Taken\"}}." } ], "primitive": "query_space_satellite_notices_v1", "query": { "as_of": "2026-09-27", "file_number": [ "SAT-RPL-20260727-00312" ], "group_by": [], "include_records": true, "limit": 1 }, "records": [ { "action": null, "action_date": null, "applicant": "Sirius XM Radio LLC", "as_of": "2026-09-27", "call_sign": "S00935", "citation": { "as_of": "2026-09-27", "file_number": "SAT-RPL-20260727-00312", "raw_file_sha256": "3da714e4ddea2f246d8eaaf3b84e992cd37e20b187038ee73b834c8e8699b868", "sheet": "DOC-425356A1", "source_file": "sat_notices_sample.json", "source_id": "space.fcc.sat_public_notices", "source_row": 45, "source_url": "https://docs.fcc.gov/public/attachments/DOC-425356A1.txt" }, "da_number": null, "date_filed": "2026-09-03", "entry_text": "SAT-RPL-20260727-00312 S00935 Sirius XM Radio LLC\nDate filed: 2026-09-03\nReplacement Satellite Application (no new frequency bands)\n\nSirius XM Radio LLC (Sirius XM) requests authority to launch and operate the SXM-12 satellite to \nreplace its FM-5 satellite. Sirius XM proposes to perform in-orbit testing at a test orbital location, then \ndrift SXM-12 to its assigned orbital location at 86.15\u00b0 W.L. +/- 0.1 degrees. Sirius XM requests \nflexibility to reposition and operate SXM-12 at any of its orbit locations (85.15\u00b0 W.L, 86.15\u00b0 W.L, \n115.25\u00b0 W.L., or 116.15\u00b0 W.L.) in order to meet service requirements as needed.\n \nSirius XM requests authority to operate in the following frequencies:\nSatellite Audio Digital Radio Systems (SDARS):\n\n \u2022 2320-2345 MHz (space-to-Earth)\n \u2022 7025-7075 MHz (Earth-to-space)\n\n \nWireless Communication Services (WCS):\n\n \u2022 2315-2320 MHz (C Block)\n \u2022 2345-2350 MHz (D Block)\n\n \nTelemetry, Tracking, and Command (TT&C):\n\n \u2022 2315-2350 MHz (space-to-Earth)\n \u2022 7025-7075 MHz (Earth-to-space)\n \u2022 4196-4198.5 MHz (space-to-Earth) (limited to orbit raising)\n \u2022 6422-6425 MHz (Earth-to-space) (limited to orbit raising)\n\n \nSirius XM requests waiver of the following sections of the Commission\u2019s rules:\n\n \u2022 47 CFR \u00a7 25.118(e)\n \u2022 47 CFR \u00a7 25.202(g)\n \u2022 47 CFR \u00a7 25.210(j)", "file_number": "SAT-RPL-20260727-00312", "filing_type": "Replacement Satellite Application (no new frequency bands)", "filing_type_code": "RPL", "informative": false, "notice_doc_id": "DOC-425356A1", "notice_kind": "Applications Accepted for Filing", "notice_pdf_url": "https://docs.fcc.gov/public/attachments/DOC-425356A1.pdf", "notice_url": "https://docs.fcc.gov/public/attachments/DOC-425356A1.txt", "raw_file_sha256": "3da714e4ddea2f246d8eaaf3b84e992cd37e20b187038ee73b834c8e8699b868", "release_date": "2026-09-25", "report_number": "SAT-02040", "report_period": "2026-09-25", "sheet_name": "DOC-425356A1", "source_id": "space.fcc.sat_public_notices", "source_record_key": "DOC-425356A1#45", "source_row_number": 45 } ], "records_available": 1, "records_returned": 1, "rows": [ { "group": {}, "lineage": { "citation_ref": "c1" }, "metrics": { "source_record_count": 1 } } ], "source_id": "space.fcc.sat_public_notices", "summary": { "group_count": 1, "totals": { "source_record_count": 1 } } }, "tool": "query_space_satellite_notices_v1" }, { "params": { "as_of": "2026-09-27", "file_number": "SAT-RPL-20260727-00312", "raw_file_sha256": "3da714e4ddea2f246d8eaaf3b84e992cd37e20b187038ee73b834c8e8699b868", "sheet": "DOC-425356A1", "source_file": "sat_notices_sample.json", "source_id": "space.fcc.sat_public_notices", "source_row": 45, "source_url": "https://docs.fcc.gov/public/attachments/DOC-425356A1.txt" }, "result": { "as_of": "2026-09-27", "cited_file_number": "SAT-RPL-20260727-00312", "hash_verified": true, "raw_file_sha256": "3da714e4ddea2f246d8eaaf3b84e992cd37e20b187038ee73b834c8e8699b868", "row_values": { "cited_line": "SAT-RPL-20260727-00312 S00935 Sirius XM Radio LLC", "entry_text": "SAT-RPL-20260727-00312 S00935 Sirius XM Radio LLC\nDate filed: 2026-09-03\nReplacement Satellite Application (no new frequency bands)\n\nSirius XM Radio LLC (Sirius XM) requests authority to launch and operate the SXM-12 satellite to \nreplace its FM-5 satellite. Sirius XM proposes to perform in-orbit testing at a test orbital location, then \ndrift SXM-12 to its assigned orbital location at 86.15\u00b0 W.L. +/- 0.1 degrees. Sirius XM requests \nflexibility to reposition and operate SXM-12 at any of its orbit locations (85.15\u00b0 W.L, 86.15\u00b0 W.L, \n115.25\u00b0 W.L., or 116.15\u00b0 W.L.) in order to meet service requirements as needed.\n \nSirius XM requests authority to operate in the following frequencies:\nSatellite Audio Digital Radio Systems (SDARS):\n\n \u2022 2320-2345 MHz (space-to-Earth)\n \u2022 7025-7075 MHz (Earth-to-space)\n\n \nWireless Communication Services (WCS):\n\n \u2022 2315-2320 MHz (C Block)\n \u2022 2345-2350 MHz (D Block)\n\n \nTelemetry, Tracking, and Command (TT&C):\n\n \u2022 2315-2350 MHz (space-to-Earth)\n \u2022 7025-7075 MHz (Earth-to-space)\n \u2022 4196-4198.5 MHz (space-to-Earth) (limited to orbit raising)\n \u2022 6422-6425 MHz (Earth-to-space) (limited to orbit raising)\n\n \nSirius XM requests waiver of the following sections of the Commission\u2019s rules:\n\n \u2022 47 CFR \u00a7 25.118(e)\n \u2022 47 CFR \u00a7 25.202(g)\n \u2022 47 CFR \u00a7 25.210(j)", "notice_kind": "Applications Accepted for Filing", "notice_url": "https://docs.fcc.gov/public/attachments/DOC-425356A1.txt", "release_date": "2026-09-25", "report_number": "SAT-02040" }, "sheet": "DOC-425356A1", "source_file": "sat_notices_sample.json", "source_id": "space.fcc.sat_public_notices", "source_row": 45, "source_url": "https://www.fcc.gov/edocs" }, "tool": "get_source_evidence_v1" } ] }