Real-time market

ERCOT 4CP Monitor

WSL-adjusted coincident-peak risk, curtailment window, and TCOS exposure for ERCOT C&I loads.

Natural language query

Ask a dataset

Compose once, then run the prompt in Gridleaf or copy it into Claude or ChatGPT with the dataset context attached.

gridkit_ercot_4cp_monitor

Visual target

Risk gauge + interval bars

Query inputs

query_contract
Claude setup

Portal handoff

Open

Gridleaf dataset: ERCOT 4CP Monitor Tool: gridkit_ercot_4cp_monitor Sources: ERCOT load forecast, ERCOT storage/WSL, Gridleaf 4CP model Source readiness: Market-day monitoring / Operations screening Query contract: - Title: 4CP curtailment query contract - Primary entity: ERCOT load zone or facility - Time grain: 15-minute intervals - Visualization mode: Risk gauge + interval bars - Inputs: operating_date (date, required) e.g. today; site_or_zone (string, required) e.g. Houston data center; interval_load_mw (number, optional) e.g. 18 MW; curtailment_mw (number, optional) e.g. 4 MW - Example queries: Monitor 4CP risk for a Houston data center today with 18 MW load.; Which ERCOT intervals should I curtail if I can shed 4 MW? Analysis plan contract: - Version: gridleaf-analysis-plan.v2 - Dataset: ERCOT 4CP Monitor (ercot-4cp) - Tool: gridkit_ercot_4cp_monitor - Workflow: ERCOT 4CP Monitor baseline analysis - Output: Risk gauge + interval bars - Result preview: 4CP risk window result (4CP risk score) - Query contract: 4CP curtailment query contract (15-minute intervals) - Metrics: 4CP risk score, Estimated CP load, Headroom MW, Curtailment value - Sources: ERCOT load forecast, ERCOT storage/WSL, Gridleaf 4CP model - Source readiness: Market-day monitoring (Operations screening) - Source caveats: ERCOT settlement and WSL inputs can revise after the operating day.; Account exposure remains model-assisted until interval load and tariff data are attached. - Source next actions: Refresh source status before issuing a curtailment instruction.; Confirm facility interval load before treating modeled value as billing-grade. - Steps: Route the natural-language question to the right Gridleaf dataset. -> Run or prepare the matching Gridleaf portal tool with source-status caveats. -> Return a decision-ready answer and the next Claude or ChatGPT prompt. Result preview contract: - Title: 4CP risk window result - Chart: Interval risk - Primary metric: 4CP risk score - Fields: interval, risk_score, headroom_mw, curtailment_value_usd_per_mw - Example rows: 15:00 CT: 81 risk ($5.2k/MW); 16:00 CT: 94 risk ($7.8k/MW); 17:00 CT: 73 risk ($4.1k/MW) Dataset insight packet: - Version: gridleaf-dataset-insight.v1 - Contract key: dataset_insight - Dataset: ERCOT 4CP Monitor (ercot-4cp) - Tool: gridkit_ercot_4cp_monitor - Workflow: ERCOT 4CP Monitor baseline analysis - Visualization: Risk gauge + interval bars - Fields: interval, risk_score, headroom_mw, curtailment_value_usd_per_mw - Rows: 15:00 CT: 81 risk ($5.2k/MW); 16:00 CT: 94 risk ($7.8k/MW); 17:00 CT: 73 risk ($4.1k/MW) - Source readiness: Market-day monitoring (Operations screening) - Next queries: Monitor 4CP risk for a Houston data center today with 18 MW load.; Which ERCOT intervals should I curtail if I can shed 4 MW?; Should I curtail a Texas facility this afternoon?; Which intervals are most likely to become a 4CP event? Monitor ERCOT 4CP risk for a Houston data center today. Show peak-risk windows, WSL adjustment, curtailment value, and what I should ask Claude to analyze next. Return a concise analytical memo, call out source freshness and caveats, and suggest the next Gridleaf portal query. User question: Monitor 4CP risk for a Houston data center today with 18 MW load. query_contract: 4CP curtailment query contract Primary entity: ERCOT load zone or facility Time grain: 15-minute intervals Query inputs: - operating_date: today (required) - site_or_zone: Houston data center (required) - interval_load_mw: 18 MW (optional) - curtailment_mw: 4 MW (optional) Required inputs covered by provided values or contract examples. Return Risk gauge + interval bars with source_status_policy caveats, result_preview fields, and the next Gridleaf portal or Claude follow-up.

Gridleaf answer preview

Gridleaf will route this ask to gridkit_ercot_4cp_monitor and return Risk gauge + interval bars for today.

answer_preview

Primary result

15:00 CT: 81 risk / $5.2k/MW

Visual

Interval risk

Source

Market-day monitoring

Preview rows

15:00 CT

1.8 GW headroom

81 risk

$5.2k/MW

16:00 CT

0.9 GW headroom

94 risk

$7.8k/MW

17:00 CT

2.4 GW headroom

73 risk

$4.1k/MW

Answer notes

Expected output fields: interval, risk_score, headroom_mw, curtailment_value_usd_per_mw.

Source readiness: Market-day monitoring (Operations screening).

ERCOT settlement and WSL inputs can revise after the operating day.

AI handoff package

Copy a provider-ready package with source readiness, analysis steps, and the Gridleaf return URL.

Provider

Claude

Source readiness

Market-day monitoring

Return

Gridleaf portal

Return to Gridleaf

External AI return

Bring the Claude or ChatGPT answer back with the external_ai_return contract and source checks.

Result preview

4CP risk window result

Ranked interval risk, WSL-adjusted system load context, and account-level curtailment economics.

4CP risk score

Interval risk

risk
14:00
42
15:00
81
16:00
94
17:00
73
18:00
44

Example rows

15:00 CT

1.8 GW headroom

81 risk

$5.2k/MW

16:00 CT

0.9 GW headroom

94 risk

$7.8k/MW

17:00 CT

2.4 GW headroom

73 risk

$4.1k/MW

intervalrisk_scoreheadroom_mwcurtailment_value_usd_per_mw
Query contract

4CP curtailment query contract

Ask for market-day 4CP risk with a site, operating date, interval load, and optional curtailment amount.

query_contract

Primary entity

ERCOT load zone or facility

Time grain

15-minute intervals

Visualization

Risk gauge + interval bars

Inputs

Operating date

operating_date

Required

Market day or forecast day to screen for coincident-peak risk.

Example: today

Site or zone

site_or_zone

Required

Facility, load zone, or account context for curtailment economics.

Example: Houston data center

Interval load

interval_load_mw

Optional

Facility load used to estimate CP exposure.

Example: 18 MW

Curtailment amount

curtailment_mw

Optional

Controllable load to value against peak risk.

Example: 4 MW

Natural-language examples

Monitor 4CP risk for a Houston data center today with 18 MW load.

Which ERCOT intervals should I curtail if I can shed 4 MW?

Analysis playbooks

Run a structured workflow in the portal, then carry the same prompt into Claude or ChatGPT.

2 workflows
Playbook

4CP operations brief

Curtailment window, account exposure, and Claude-ready ops memo.

1Check system peak risk
2Estimate site curtailment value
3Draft operator action memo

Claude + ChatGPT prompt

Gridleaf dataset: ERCOT 4CP Monitor Tool: gridkit_ercot_4cp_monitor Sources: ERCOT load forecast, ERCOT storage/WSL, Gridleaf 4CP model Source readiness: Market-day monitoring / Operations screening Query contract: - Title: 4CP curtailment query contract - Primary entity: ERCOT load zone or facility - Time grain: 15-minute intervals - Visualization mode: Risk gauge + interval bars - Inputs: operating_date (date, required) e.g. today; site_or_zone (string, required) e.g. Houston data center; interval_load_mw (number, optional) e.g. 18 MW; curtailment_mw (number, optional) e.g. 4 MW - Example queries: Monitor 4CP risk for a Houston data center today with 18 MW load.; Which ERCOT intervals should I curtail if I can shed 4 MW? Analysis plan contract: - Version: gridleaf-analysis-plan.v2 - Dataset: ERCOT 4CP Monitor (ercot-4cp) - Tool: gridkit_ercot_4cp_monitor - Workflow: 4CP operations brief - Output: Risk gauge + interval bars - Result preview: 4CP risk window result (4CP risk score) - Query contract: 4CP curtailment query contract (15-minute intervals) - Metrics: 4CP risk score, Estimated CP load, Headroom MW, Curtailment value - Sources: ERCOT load forecast, ERCOT storage/WSL, Gridleaf 4CP model - Source readiness: Market-day monitoring (Operations screening) - Source caveats: ERCOT settlement and WSL inputs can revise after the operating day.; Account exposure remains model-assisted until interval load and tariff data are attached. - Source next actions: Refresh source status before issuing a curtailment instruction.; Confirm facility interval load before treating modeled value as billing-grade. - Steps: Check system peak risk -> Estimate site curtailment value -> Draft operator action memo Result preview contract: - Title: 4CP risk window result - Chart: Interval risk - Primary metric: 4CP risk score - Fields: interval, risk_score, headroom_mw, curtailment_value_usd_per_mw - Example rows: 15:00 CT: 81 risk ($5.2k/MW); 16:00 CT: 94 risk ($7.8k/MW); 17:00 CT: 73 risk ($4.1k/MW) Dataset insight packet: - Version: gridleaf-dataset-insight.v1 - Contract key: dataset_insight - Dataset: ERCOT 4CP Monitor (ercot-4cp) - Tool: gridkit_ercot_4cp_monitor - Workflow: 4CP operations brief - Visualization: Risk gauge + interval bars - Fields: interval, risk_score, headroom_mw, curtailment_value_usd_per_mw - Rows: 15:00 CT: 81 risk ($5.2k/MW); 16:00 CT: 94 risk ($7.8k/MW); 17:00 CT: 73 risk ($4.1k/MW) - Source readiness: Market-day monitoring (Operations screening) - Next queries: Monitor 4CP risk for a Houston data center today with 18 MW load.; Which ERCOT intervals should I curtail if I can shed 4 MW?; Should I curtail a Texas facility this afternoon?; Which intervals are most likely to become a 4CP event? Monitor ERCOT 4CP risk for a Houston data center today. Show peak-risk windows, WSL adjustment, curtailment value, and what I should ask Claude to analyze next. Return a concise analytical memo, call out source freshness and caveats, and suggest the next Gridleaf portal query. Analysis playbook: 4CP operations brief Outcome: Curtailment window, account exposure, and Claude-ready ops memo. Workflow steps: 1. Check system peak risk 2. Estimate site curtailment value 3. Draft operator action memo Playbook prompt: Build an ERCOT 4CP operations brief for a Houston data center. Identify the top risk intervals, estimate curtailment value per MW, explain WSL adjustment caveats, and draft the Claude follow-up memo for the energy operations team.

Run playbook in portal
Playbook

Peak-risk watchlist

Daily monitoring questions for 4CP risk and demand response.

1Rank likely CP intervals
2Separate weather and load drivers
3Recommend next monitoring queries

Claude + ChatGPT prompt

Gridleaf dataset: ERCOT 4CP Monitor Tool: gridkit_ercot_4cp_monitor Sources: ERCOT load forecast, ERCOT storage/WSL, Gridleaf 4CP model Source readiness: Market-day monitoring / Operations screening Query contract: - Title: 4CP curtailment query contract - Primary entity: ERCOT load zone or facility - Time grain: 15-minute intervals - Visualization mode: Risk gauge + interval bars - Inputs: operating_date (date, required) e.g. today; site_or_zone (string, required) e.g. Houston data center; interval_load_mw (number, optional) e.g. 18 MW; curtailment_mw (number, optional) e.g. 4 MW - Example queries: Monitor 4CP risk for a Houston data center today with 18 MW load.; Which ERCOT intervals should I curtail if I can shed 4 MW? Analysis plan contract: - Version: gridleaf-analysis-plan.v2 - Dataset: ERCOT 4CP Monitor (ercot-4cp) - Tool: gridkit_ercot_4cp_monitor - Workflow: Peak-risk watchlist - Output: Risk gauge + interval bars - Result preview: 4CP risk window result (4CP risk score) - Query contract: 4CP curtailment query contract (15-minute intervals) - Metrics: 4CP risk score, Estimated CP load, Headroom MW, Curtailment value - Sources: ERCOT load forecast, ERCOT storage/WSL, Gridleaf 4CP model - Source readiness: Market-day monitoring (Operations screening) - Source caveats: ERCOT settlement and WSL inputs can revise after the operating day.; Account exposure remains model-assisted until interval load and tariff data are attached. - Source next actions: Refresh source status before issuing a curtailment instruction.; Confirm facility interval load before treating modeled value as billing-grade. - Steps: Rank likely CP intervals -> Separate weather and load drivers -> Recommend next monitoring queries Result preview contract: - Title: 4CP risk window result - Chart: Interval risk - Primary metric: 4CP risk score - Fields: interval, risk_score, headroom_mw, curtailment_value_usd_per_mw - Example rows: 15:00 CT: 81 risk ($5.2k/MW); 16:00 CT: 94 risk ($7.8k/MW); 17:00 CT: 73 risk ($4.1k/MW) Dataset insight packet: - Version: gridleaf-dataset-insight.v1 - Contract key: dataset_insight - Dataset: ERCOT 4CP Monitor (ercot-4cp) - Tool: gridkit_ercot_4cp_monitor - Workflow: Peak-risk watchlist - Visualization: Risk gauge + interval bars - Fields: interval, risk_score, headroom_mw, curtailment_value_usd_per_mw - Rows: 15:00 CT: 81 risk ($5.2k/MW); 16:00 CT: 94 risk ($7.8k/MW); 17:00 CT: 73 risk ($4.1k/MW) - Source readiness: Market-day monitoring (Operations screening) - Next queries: Monitor 4CP risk for a Houston data center today with 18 MW load.; Which ERCOT intervals should I curtail if I can shed 4 MW?; Should I curtail a Texas facility this afternoon?; Which intervals are most likely to become a 4CP event? Monitor ERCOT 4CP risk for a Houston data center today. Show peak-risk windows, WSL adjustment, curtailment value, and what I should ask Claude to analyze next. Return a concise analytical memo, call out source freshness and caveats, and suggest the next Gridleaf portal query. Analysis playbook: Peak-risk watchlist Outcome: Daily monitoring questions for 4CP risk and demand response. Workflow steps: 1. Rank likely CP intervals 2. Separate weather and load drivers 3. Recommend next monitoring queries Playbook prompt: Create a 4CP peak-risk watchlist for today. Rank intervals by risk, separate weather-sensitive load from system load drivers, and recommend follow-up questions to run in Gridleaf and Claude.

Run playbook in portal
Source readiness

Use this dataset with clear source caveats.

fresh

Freshness

Market-day monitoring

Decision grade

Operations screening

Sources

3

Caveats

ERCOT settlement and WSL inputs can revise after the operating day.

Account exposure remains model-assisted until interval load and tariff data are attached.

Next source actions

Refresh source status before issuing a curtailment instruction.

Confirm facility interval load before treating modeled value as billing-grade.

Coverage

ERCOT system load, wholesale storage load adjustment, monthly peak-risk windows, and account-level curtailment economics.

Metric

4CP risk score

Metric

Estimated CP load

Metric

Headroom MW

Metric

Curtailment value

Ask this dataset

Should I curtail a Texas facility this afternoon?

Which intervals are most likely to become a 4CP event?

What should I take into Claude for a data-center energy ops memo?

AI-ready prompt

Use the same prompt shape in the portal, Claude, or ChatGPT when this dataset is selected.

Start prompt
Gridleaf dataset: ERCOT 4CP Monitor
Tool: gridkit_ercot_4cp_monitor
Sources: ERCOT load forecast, ERCOT storage/WSL, Gridleaf 4CP model
Source readiness: Market-day monitoring / Operations screening

Query contract:
- Title: 4CP curtailment query contract
- Primary entity: ERCOT load zone or facility
- Time grain: 15-minute intervals
- Visualization mode: Risk gauge + interval bars
- Inputs: operating_date (date, required) e.g. today; site_or_zone (string, required) e.g. Houston data center; interval_load_mw (number, optional) e.g. 18 MW; curtailment_mw (number, optional) e.g. 4 MW
- Example queries: Monitor 4CP risk for a Houston data center today with 18 MW load.; Which ERCOT intervals should I curtail if I can shed 4 MW?

Analysis plan contract:
- Version: gridleaf-analysis-plan.v2
- Dataset: ERCOT 4CP Monitor (ercot-4cp)
- Tool: gridkit_ercot_4cp_monitor
- Workflow: ERCOT 4CP Monitor baseline analysis
- Output: Risk gauge + interval bars
- Result preview: 4CP risk window result (4CP risk score)
- Query contract: 4CP curtailment query contract (15-minute intervals)
- Metrics: 4CP risk score, Estimated CP load, Headroom MW, Curtailment value
- Sources: ERCOT load forecast, ERCOT storage/WSL, Gridleaf 4CP model
- Source readiness: Market-day monitoring (Operations screening)
- Source caveats: ERCOT settlement and WSL inputs can revise after the operating day.; Account exposure remains model-assisted until interval load and tariff data are attached.
- Source next actions: Refresh source status before issuing a curtailment instruction.; Confirm facility interval load before treating modeled value as billing-grade.
- Steps: Route the natural-language question to the right Gridleaf dataset. -> Run or prepare the matching Gridleaf portal tool with source-status caveats. -> Return a decision-ready answer and the next Claude or ChatGPT prompt.

Result preview contract:
- Title: 4CP risk window result
- Chart: Interval risk
- Primary metric: 4CP risk score
- Fields: interval, risk_score, headroom_mw, curtailment_value_usd_per_mw
- Example rows: 15:00 CT: 81 risk ($5.2k/MW); 16:00 CT: 94 risk ($7.8k/MW); 17:00 CT: 73 risk ($4.1k/MW)

Dataset insight packet:
- Version: gridleaf-dataset-insight.v1
- Contract key: dataset_insight
- Dataset: ERCOT 4CP Monitor (ercot-4cp)
- Tool: gridkit_ercot_4cp_monitor
- Workflow: ERCOT 4CP Monitor baseline analysis
- Visualization: Risk gauge + interval bars
- Fields: interval, risk_score, headroom_mw, curtailment_value_usd_per_mw
- Rows: 15:00 CT: 81 risk ($5.2k/MW); 16:00 CT: 94 risk ($7.8k/MW); 17:00 CT: 73 risk ($4.1k/MW)
- Source readiness: Market-day monitoring (Operations screening)
- Next queries: Monitor 4CP risk for a Houston data center today with 18 MW load.; Which ERCOT intervals should I curtail if I can shed 4 MW?; Should I curtail a Texas facility this afternoon?; Which intervals are most likely to become a 4CP event?

Monitor ERCOT 4CP risk for a Houston data center today. Show peak-risk windows, WSL adjustment, curtailment value, and what I should ask Claude to analyze next.

Return a concise analytical memo, call out source freshness and caveats, and suggest the next Gridleaf portal query.

Related datasets