Query the NYISO generator + load interconnection queue — New York ISO's public waiting line of projects that have REQUESTED to connect to the New York grid. Uniquely among ISOs, NYISO publishes a Load Projects tab — load interconnection requests (large-load demand), served as-reported — and since its 2026-07 edition tags each load request with its own End-Use class (end_use, e.g. DAT / DAT-AI / DAT-CM, served verbatim).

Returns cited, project-level records with NYISO's full published structure across every lifecycle tab (nine tabs through 2026-06; seven since NYISO's 2026-07 restructure): summer and winter peak megawatts kept SEPARATE (sp_mw = SP, the max summer output; wp_mw = WP, the max winter output), the Load Projects tab's peak_mw_load with NYISO's own end_use class and sis_bundle study-batch code (both 2026-07 onward, null before), the as-reported study-phase code (study_status_code — NYISO's numeric key, labeled S through 2026-06 and Project Status # / NYISO Status since), the request record_type and project_type, the type_fuel codebook, the energy-storage capability, the NYISO load zone (A–K), location (state, county, derived county_fips, point_of_interconnection, utility), and lifecycle dates (ir_date, last_update, the milestone dates, and the Year/Qualifier proposed_cod kept verbatim). Group or filter by application_status, sheet_name, state, county_fips, study_status_code, record_type, type_fuel, zone, utility, studies_available, or end_use; filter ir_date by the ir_date_from / ir_date_to range. Pass each parameter as a top-level key of params (flat — not nested). Example: {"application_status": "ACTIVE", "type_fuel": "S"} for active solar requests; {"sheet_name": "Load Projects"} for the load interconnection requests; {"end_use": "DAT-AI", "application_status": "ACTIVE"} for the load requests NYISO itself codes DAT-AI; {"group_by": ["application_status"]} for requested MW and project counts by lifecycle. Returns JSON aggregates with citations and optional row-level records when include_records is true; every value carries source, as_of, and a source_row verifiable with get_source_evidence_v1.

sp_mw / wp_mw / peak_mw_load are REQUESTED capacity, not built: historically the large majority of queued megawatts withdraw before they are built, so the queue is withdrawn-dominated. NEVER read a queue-MW total as installed or operating capacity — it is additive across distinct project-rows but is a REQUESTED total only. NYISO publishes summer (SP) and winter (WP) peak MW separately — they are served under NYISO's own names and never blended into one nameplate. Scope by application_status (ACTIVE / WITHDRAWN / IN_SERVICE / AFFECTED_SYSTEM / AFFECTED_SYSTEM_WITHDRAWN — the lifecycle tab's reading, overridden to the withdrawn form when a row carries NYISO's own status code 0, per the workbook's printed '0=Withdrawn' key) or by sheet_name; the In Service tab is the built reading. A project may appear on more than one tab (the grain is sheet + queue_position), so the counts are project-rows, not deduped projects. For built/operating capacity use query_power_capacity_v1.

NYISO only — never summed, deduped, or compared across ISOs. For the MISO interconnection queue use query_power_interconnection_queue_v1; for PJM use query_power_interconnection_queue_pjm_v1 (or query_power_interconnection_queue_pjm_cycle_v1 for PJM's cluster/cycle grid); for the CAISO (California) queue use query_power_interconnection_queue_caiso_v1; for the ISO-NE (New England) queue use query_power_interconnection_queue_isone_v1; for the ERCOT (Texas) queue use query_power_interconnection_queue_ercot_v1; for the SPP (central US) queue use query_power_interconnection_queue_spp_v1. NYISO's Load Projects tab is served as-reported: end_use is NYISO's OWN classification (NYISO publishes no key for the codes), and this tool does NOT infer an end use NYISO did not print — interpretation beyond the code is the analyst's, from cited rows.