Overview

Every CAISO location that carries a price, as three columns: location_id, name, and kind. 26,632 rows — node (26,048), interface (578), zone (6). This is the dimension the CAISO price, and where applicable constraint, tables join to, and it is the one place a location's type is decided: resolve "which hubs exist", "is this a zone or a node", or "give me the readable name for this id" here rather than inferring a type from a name prefix. For CAISO, name equals location_id (the pnode name). The same three columns exist for every market, so the equivalent question in another ISO is the same query against that ISO's table.

CAISO market Ask the agent about this dataset

Use with MCP

This table is readable two ways, over the same guarded boundary. Over HTTP: POST /api/v1/datasets/caiso_locations/query, described in the API reference. Or from an MCP client: connect a market below, then use search_data or describe_data to load its query contract before calling query_data.

CAISO MCP Server

Schema3

Column

Type

location_idLowCardinality(String)

nameLowCardinality(String)

kindLowCardinality(String)

Sample rows

location_id	name	kind
0096WD_7_N001	0096WD_7_N001	node
0096WD_7_N002	0096WD_7_N002	node
106THSO_LNODED1	106THSO_LNODED1	node
10TH_STW_1_1LNODE	10TH_STW_1_1LNODE	node
10TH_STW_1_2LNODE	10TH_STW_1_2LNODE	node
118THSO_LNODER1	118THSO_LNODER1	node
119TH_BP_LNODEXF1	119TH_BP_LNODEXF1	node
126THSO_LNODE_LDT1	126THSO_LNODE_LDT1	node
126THSO_LNODE_LDT2	126THSO_LNODE_LDT2	node
12STREET_LNODEEET1	12STREET_LNODEEET1	node
12STREET_LNODEEET2	12STREET_LNODEEET2	node
12TH_S_LNODENMZ	12TH_S_LNODENMZ	node
12TH_S_LNODEXWQ	12TH_S_LNODEXWQ	node
13THSO_LNODE-3	13THSO_LNODE-3	node
13THSO_LNODED2	13THSO_LNODED2	node
1501WDC2_7_ND001	1501WDC2_7_ND001	node
22ND_ST_LNODEC22	22ND_ST_LNODEC22	node
22ND_ST_LNODEC23	22ND_ST_LNODEC23	node
22ND_ST_LNODEC32	22ND_ST_LNODEC32	node
22ND_ST_LNODEC33	22ND_ST_LNODEC33	node
22ND_ST_LNODEDIST	22ND_ST_LNODEDIST	node
22ND_ST_LNODEDONED	22ND_ST_LNODEDONED	node
22ND_ST_LNODEIST2	22ND_ST_LNODEIST2	node
22ND_ST_LNODEIST3	22ND_ST_LNODEIST3	node
23RDST_LNODED3	23RDST_LNODED3	node

Coverage

No time-indexed data — coverage isn’t applicable to this dataset.

More data from CAISO

Battery Storage Net OutputObserved five-minute net output from standalone and hybrid battery storage across the CAISO footprint. The total supply_mw field is positive when batteries are discharging into the grid and negative when they are charging from the grid; standalone_batteries_mw and hybrid_batteries_mw are components of that total, not additional generation to add on top. This is the live operating series published in CAISO Today's Outlook, not nameplate capacity or state of charge.CAISO Day-Ahead Ancillary PricesCleared day-ahead ancillary-service capacity prices in CAISO, one row per hour, AS region and product. 2,172,326 rows, 2014-12 to now. Products: reg_up, reg_down, spin, non_spin, reg_mileage_up, reg_mileage_down. 12 CAISO ancillary-service regions (AS_CAISO, AS_NP26, AS_SP26 and their expanded variants). The expanded regions overlap the base ones by design — never sum across regions. price_usd_mw is a price for CAPACITY held in reserve — dollars per megawatt of commitment — not dollars per megawatt-hour of energy delivered. The two are different units and are not comparable to an LMP.CAISO Day-Ahead Binding ConstraintsWhich transmission facilities bound in CAISO's day-ahead market and what each one cost, one row per interval and constraint. 463,496 rows, 2015-01 to now. Columns: event_time, constraint_name, shadow_price_usd_mwh, plus constraint_cause. The shadow price is the marginal cost of the binding limit — what the market would have saved from one more megawatt of capability on that element. This is the table that answers WHY congestion appeared; a price spread between two locations shows that they separated but not which facility separated them.CAISO Day-Ahead Load ForecastCAISO's day-ahead demand forecast, one row per forecast hour with a system total and one column per TAC area. 75,727 hours, 2018-01 through the next delivery day. Column-for-column identical to CAISO Load (caiso_load) on purpose: system_mw, pge_mw, sce_mw, sdge_mw, vea_mw, mwd_mw. Forecast-versus-actual is therefore a plain join on event_time with no reshaping on either side. CAISO publishes no issue-time column for this feed, so there is no vintage axis here — this is the day-ahead market run for each hour, not a curve of successive forecasts. CAISO's other horizons (two-day, seven-day, real-time) live in caiso.load_forecast_horizons and only begin in May 2026.