Real-time market

ERCOT Settlement Prices

Settlement point price screen for ERCOT hubs, congestion, and intraday price shape.

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_lmp_prices

Visual target

Hub cards + intraday bars

Query inputs

query_contract
Claude setup

Portal handoff

Open

Gridleaf dataset: ERCOT Settlement Prices Tool: gridkit_ercot_lmp_prices Sources: ERCOT SPP, Gridleaf price screen Source readiness: Near real-time market screen / Trading screen Query contract: - Title: ERCOT price screen query contract - Primary entity: ERCOT settlement point - Time grain: Current or intraday interval - Visualization mode: Hub cards + intraday bars - Inputs: settlement_point (string, required) e.g. HB_HOUSTON; price_interval (time-range, optional) e.g. current interval; comparison_points (list, optional) e.g. HB_NORTH, HB_WEST; memo_context (string, optional) e.g. trader note - Example queries: Show current ERCOT Houston hub prices with North and West comparison.; Where is ERCOT congestion showing up this interval? Analysis plan contract: - Version: gridleaf-analysis-plan.v2 - Dataset: ERCOT Settlement Prices (ercot-lmp) - Tool: gridkit_ercot_lmp_prices - Workflow: ERCOT Settlement Prices baseline analysis - Output: Hub cards + intraday bars - Result preview: ERCOT hub price result (Hub price) - Query contract: ERCOT price screen query contract (Current or intraday interval) - Metrics: Hub price, Congestion component, Intraday spread, Basis signal - Sources: ERCOT SPP, Gridleaf price screen - Source readiness: Near real-time market screen (Trading screen) - Source caveats: Settlement point prices can revise after ERCOT settlement updates.; Congestion interpretation should be checked against current outage and constraint context. - Source next actions: Refresh source status before sending a price memo externally.; Attach the target hub, interval, and hedge context before decision-grade trading use. - 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: ERCOT hub price result - Chart: Hub price - Primary metric: Hub price - Fields: settlement_point, price_usd_per_mwh, congestion_usd_per_mwh, basis_signal - Example rows: HB Houston: $38.70/MWh (Moderate basis); HB North: $35.20/MWh (Light basis); HB West: $44.10/MWh (Watch) Dataset insight packet: - Version: gridleaf-dataset-insight.v1 - Contract key: dataset_insight - Dataset: ERCOT Settlement Prices (ercot-lmp) - Tool: gridkit_ercot_lmp_prices - Workflow: ERCOT Settlement Prices baseline analysis - Visualization: Hub cards + intraday bars - Fields: settlement_point, price_usd_per_mwh, congestion_usd_per_mwh, basis_signal - Rows: HB Houston: $38.70/MWh (Moderate basis); HB North: $35.20/MWh (Light basis); HB West: $44.10/MWh (Watch) - Source readiness: Near real-time market screen (Trading screen) - Next queries: Show current ERCOT Houston hub prices with North and West comparison.; Where is ERCOT congestion showing up this interval?; What are current ERCOT Houston hub prices?; Where is congestion showing up across ERCOT hubs? Show current ERCOT settlement point prices at the Houston hub with congestion, intraday price shape, and a Claude-ready market memo. Return a concise analytical memo, call out source freshness and caveats, and suggest the next Gridleaf portal query. User question: Show current ERCOT Houston hub prices with North and West comparison. query_contract: ERCOT price screen query contract Primary entity: ERCOT settlement point Time grain: Current or intraday interval Query inputs: - settlement_point: HB_HOUSTON (required) - price_interval: current interval (optional) - comparison_points: HB_NORTH, HB_WEST (optional) - memo_context: trader note (optional) Required inputs covered by provided values or contract examples. Return Hub cards + intraday 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_lmp_prices and return Hub cards + intraday bars for HB_HOUSTON.

answer_preview

Primary result

HB Houston: $38.70/MWh / Moderate basis

Visual

Hub price

Source

Near real-time market screen

Preview rows

HB Houston

$2.80 congestion

$38.70/MWh

Moderate basis

HB North

$1.10 congestion

$35.20/MWh

Light basis

HB West

$5.20 congestion

$44.10/MWh

Watch

Answer notes

Expected output fields: settlement_point, price_usd_per_mwh, congestion_usd_per_mwh, basis_signal.

Source readiness: Near real-time market screen (Trading screen).

Settlement point prices can revise after ERCOT settlement updates.

AI handoff package

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

Provider

Claude

Source readiness

Near real-time market screen

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

ERCOT hub price result

Hub cards, congestion component, intraday shape, and basis signal for ERCOT market memos.

Hub price

Hub price

$/MWh
Houston
39
North
35
West
44
South
37
Load
41

Example rows

HB Houston

$2.80 congestion

$38.70/MWh

Moderate basis

HB North

$1.10 congestion

$35.20/MWh

Light basis

HB West

$5.20 congestion

$44.10/MWh

Watch

settlement_pointprice_usd_per_mwhcongestion_usd_per_mwhbasis_signal
Query contract

ERCOT price screen query contract

Ask for settlement point prices with hub or load-zone filters, price interval, and congestion/basis context.

query_contract

Primary entity

ERCOT settlement point

Time grain

Current or intraday interval

Visualization

Hub cards + intraday bars

Inputs

Settlement point

settlement_point

Required

Hub, load zone, or settlement point to screen.

Example: HB_HOUSTON

Price interval

price_interval

Optional

Current interval, operating day, or intraday window.

Example: current interval

Comparison points

comparison_points

Optional

Additional hubs or zones for basis comparison.

Example: HB_NORTH, HB_WEST

Memo context

memo_context

Optional

Business context for the Gridleaf or Claude answer.

Example: trader note

Natural-language examples

Show current ERCOT Houston hub prices with North and West comparison.

Where is ERCOT congestion showing up this interval?

Analysis playbooks

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

2 workflows
Playbook

ERCOT hub price memo

Hub price comparison, congestion signal, and trader-ready note.

1Compare hub prices
2Flag congestion and basis
3Write a market memo for Claude

Claude + ChatGPT prompt

Gridleaf dataset: ERCOT Settlement Prices Tool: gridkit_ercot_lmp_prices Sources: ERCOT SPP, Gridleaf price screen Source readiness: Near real-time market screen / Trading screen Query contract: - Title: ERCOT price screen query contract - Primary entity: ERCOT settlement point - Time grain: Current or intraday interval - Visualization mode: Hub cards + intraday bars - Inputs: settlement_point (string, required) e.g. HB_HOUSTON; price_interval (time-range, optional) e.g. current interval; comparison_points (list, optional) e.g. HB_NORTH, HB_WEST; memo_context (string, optional) e.g. trader note - Example queries: Show current ERCOT Houston hub prices with North and West comparison.; Where is ERCOT congestion showing up this interval? Analysis plan contract: - Version: gridleaf-analysis-plan.v2 - Dataset: ERCOT Settlement Prices (ercot-lmp) - Tool: gridkit_ercot_lmp_prices - Workflow: ERCOT hub price memo - Output: Hub cards + intraday bars - Result preview: ERCOT hub price result (Hub price) - Query contract: ERCOT price screen query contract (Current or intraday interval) - Metrics: Hub price, Congestion component, Intraday spread, Basis signal - Sources: ERCOT SPP, Gridleaf price screen - Source readiness: Near real-time market screen (Trading screen) - Source caveats: Settlement point prices can revise after ERCOT settlement updates.; Congestion interpretation should be checked against current outage and constraint context. - Source next actions: Refresh source status before sending a price memo externally.; Attach the target hub, interval, and hedge context before decision-grade trading use. - Steps: Compare hub prices -> Flag congestion and basis -> Write a market memo for Claude Result preview contract: - Title: ERCOT hub price result - Chart: Hub price - Primary metric: Hub price - Fields: settlement_point, price_usd_per_mwh, congestion_usd_per_mwh, basis_signal - Example rows: HB Houston: $38.70/MWh (Moderate basis); HB North: $35.20/MWh (Light basis); HB West: $44.10/MWh (Watch) Dataset insight packet: - Version: gridleaf-dataset-insight.v1 - Contract key: dataset_insight - Dataset: ERCOT Settlement Prices (ercot-lmp) - Tool: gridkit_ercot_lmp_prices - Workflow: ERCOT hub price memo - Visualization: Hub cards + intraday bars - Fields: settlement_point, price_usd_per_mwh, congestion_usd_per_mwh, basis_signal - Rows: HB Houston: $38.70/MWh (Moderate basis); HB North: $35.20/MWh (Light basis); HB West: $44.10/MWh (Watch) - Source readiness: Near real-time market screen (Trading screen) - Next queries: Show current ERCOT Houston hub prices with North and West comparison.; Where is ERCOT congestion showing up this interval?; What are current ERCOT Houston hub prices?; Where is congestion showing up across ERCOT hubs? Show current ERCOT settlement point prices at the Houston hub with congestion, intraday price shape, and a Claude-ready market memo. Return a concise analytical memo, call out source freshness and caveats, and suggest the next Gridleaf portal query. Analysis playbook: ERCOT hub price memo Outcome: Hub price comparison, congestion signal, and trader-ready note. Workflow steps: 1. Compare hub prices 2. Flag congestion and basis 3. Write a market memo for Claude Playbook prompt: Build an ERCOT hub price memo. Compare Houston, North, West, and South hub prices, flag congestion and basis signals, explain source freshness, and write the next Claude prompt for a market analyst.

Run playbook in portal
Playbook

Load-zone congestion watch

Shortlist of hubs/zones to monitor through the next price interval.

1Screen settlement point shape
2Identify congestion outliers
3Suggest next portal query

Claude + ChatGPT prompt

Gridleaf dataset: ERCOT Settlement Prices Tool: gridkit_ercot_lmp_prices Sources: ERCOT SPP, Gridleaf price screen Source readiness: Near real-time market screen / Trading screen Query contract: - Title: ERCOT price screen query contract - Primary entity: ERCOT settlement point - Time grain: Current or intraday interval - Visualization mode: Hub cards + intraday bars - Inputs: settlement_point (string, required) e.g. HB_HOUSTON; price_interval (time-range, optional) e.g. current interval; comparison_points (list, optional) e.g. HB_NORTH, HB_WEST; memo_context (string, optional) e.g. trader note - Example queries: Show current ERCOT Houston hub prices with North and West comparison.; Where is ERCOT congestion showing up this interval? Analysis plan contract: - Version: gridleaf-analysis-plan.v2 - Dataset: ERCOT Settlement Prices (ercot-lmp) - Tool: gridkit_ercot_lmp_prices - Workflow: Load-zone congestion watch - Output: Hub cards + intraday bars - Result preview: ERCOT hub price result (Hub price) - Query contract: ERCOT price screen query contract (Current or intraday interval) - Metrics: Hub price, Congestion component, Intraday spread, Basis signal - Sources: ERCOT SPP, Gridleaf price screen - Source readiness: Near real-time market screen (Trading screen) - Source caveats: Settlement point prices can revise after ERCOT settlement updates.; Congestion interpretation should be checked against current outage and constraint context. - Source next actions: Refresh source status before sending a price memo externally.; Attach the target hub, interval, and hedge context before decision-grade trading use. - Steps: Screen settlement point shape -> Identify congestion outliers -> Suggest next portal query Result preview contract: - Title: ERCOT hub price result - Chart: Hub price - Primary metric: Hub price - Fields: settlement_point, price_usd_per_mwh, congestion_usd_per_mwh, basis_signal - Example rows: HB Houston: $38.70/MWh (Moderate basis); HB North: $35.20/MWh (Light basis); HB West: $44.10/MWh (Watch) Dataset insight packet: - Version: gridleaf-dataset-insight.v1 - Contract key: dataset_insight - Dataset: ERCOT Settlement Prices (ercot-lmp) - Tool: gridkit_ercot_lmp_prices - Workflow: Load-zone congestion watch - Visualization: Hub cards + intraday bars - Fields: settlement_point, price_usd_per_mwh, congestion_usd_per_mwh, basis_signal - Rows: HB Houston: $38.70/MWh (Moderate basis); HB North: $35.20/MWh (Light basis); HB West: $44.10/MWh (Watch) - Source readiness: Near real-time market screen (Trading screen) - Next queries: Show current ERCOT Houston hub prices with North and West comparison.; Where is ERCOT congestion showing up this interval?; What are current ERCOT Houston hub prices?; Where is congestion showing up across ERCOT hubs? Show current ERCOT settlement point prices at the Houston hub with congestion, intraday price shape, and a Claude-ready market memo. Return a concise analytical memo, call out source freshness and caveats, and suggest the next Gridleaf portal query. Analysis playbook: Load-zone congestion watch Outcome: Shortlist of hubs/zones to monitor through the next price interval. Workflow steps: 1. Screen settlement point shape 2. Identify congestion outliers 3. Suggest next portal query Playbook prompt: Create an ERCOT load-zone congestion watch. Screen settlement point prices for outliers, explain what changed intraday, and suggest the next Gridleaf portal query for basis risk.

Run playbook in portal
Source readiness

Use this dataset with clear source caveats.

fresh

Freshness

Near real-time market screen

Decision grade

Trading screen

Sources

2

Caveats

Settlement point prices can revise after ERCOT settlement updates.

Congestion interpretation should be checked against current outage and constraint context.

Next source actions

Refresh source status before sending a price memo externally.

Attach the target hub, interval, and hedge context before decision-grade trading use.

Coverage

ERCOT settlement point prices for major hubs and load zones with congestion and intraday shape signals.

Metric

Hub price

Metric

Congestion component

Metric

Intraday spread

Metric

Basis signal

Ask this dataset

What are current ERCOT Houston hub prices?

Where is congestion showing up across ERCOT hubs?

What price memo should I continue in Claude?

AI-ready prompt

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

Start prompt
Gridleaf dataset: ERCOT Settlement Prices
Tool: gridkit_ercot_lmp_prices
Sources: ERCOT SPP, Gridleaf price screen
Source readiness: Near real-time market screen / Trading screen

Query contract:
- Title: ERCOT price screen query contract
- Primary entity: ERCOT settlement point
- Time grain: Current or intraday interval
- Visualization mode: Hub cards + intraday bars
- Inputs: settlement_point (string, required) e.g. HB_HOUSTON; price_interval (time-range, optional) e.g. current interval; comparison_points (list, optional) e.g. HB_NORTH, HB_WEST; memo_context (string, optional) e.g. trader note
- Example queries: Show current ERCOT Houston hub prices with North and West comparison.; Where is ERCOT congestion showing up this interval?

Analysis plan contract:
- Version: gridleaf-analysis-plan.v2
- Dataset: ERCOT Settlement Prices (ercot-lmp)
- Tool: gridkit_ercot_lmp_prices
- Workflow: ERCOT Settlement Prices baseline analysis
- Output: Hub cards + intraday bars
- Result preview: ERCOT hub price result (Hub price)
- Query contract: ERCOT price screen query contract (Current or intraday interval)
- Metrics: Hub price, Congestion component, Intraday spread, Basis signal
- Sources: ERCOT SPP, Gridleaf price screen
- Source readiness: Near real-time market screen (Trading screen)
- Source caveats: Settlement point prices can revise after ERCOT settlement updates.; Congestion interpretation should be checked against current outage and constraint context.
- Source next actions: Refresh source status before sending a price memo externally.; Attach the target hub, interval, and hedge context before decision-grade trading use.
- 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: ERCOT hub price result
- Chart: Hub price
- Primary metric: Hub price
- Fields: settlement_point, price_usd_per_mwh, congestion_usd_per_mwh, basis_signal
- Example rows: HB Houston: $38.70/MWh (Moderate basis); HB North: $35.20/MWh (Light basis); HB West: $44.10/MWh (Watch)

Dataset insight packet:
- Version: gridleaf-dataset-insight.v1
- Contract key: dataset_insight
- Dataset: ERCOT Settlement Prices (ercot-lmp)
- Tool: gridkit_ercot_lmp_prices
- Workflow: ERCOT Settlement Prices baseline analysis
- Visualization: Hub cards + intraday bars
- Fields: settlement_point, price_usd_per_mwh, congestion_usd_per_mwh, basis_signal
- Rows: HB Houston: $38.70/MWh (Moderate basis); HB North: $35.20/MWh (Light basis); HB West: $44.10/MWh (Watch)
- Source readiness: Near real-time market screen (Trading screen)
- Next queries: Show current ERCOT Houston hub prices with North and West comparison.; Where is ERCOT congestion showing up this interval?; What are current ERCOT Houston hub prices?; Where is congestion showing up across ERCOT hubs?

Show current ERCOT settlement point prices at the Houston hub with congestion, intraday price shape, and a Claude-ready market memo.

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

Related datasets