SPP · Pricing

SPP real-time binding constraints

Every transmission constraint in SPP's real-time dispatch, five minutes at a time — binding, breached, or activated at a zero price — with the contingency it is monitored for, its limits and its shadow price.

spp-rt-shadow-pricesevery 5 min · 5m rows88 entities
TMP845_30027
$0.00
2026-09-18 05:05 UTC
TMP459_32122
$0.00
2026-09-18 05:05 UTC
TP1125_33384
$0.00
2026-09-18 05:05 UTC
Read from the Dryos API and cached for an hour; the stream itself updates every 5 min.

What is in it

Updates
every 5 min · 5m rows
Entities
88 entities — TMP845_30027, TMP459_32122, TP1125_33384…
Source timezone
US Central — every timestamp Dryos serves is UTC
Coverage
14 September 2026 to now
Rows held
97,950
Primary key
iso, constraint_name, contingency, interval_start_utc

What it measures

Every value, its unit, and what the source means by it.

  • Shadow price$/MWh

    The constraint's shadow price for the interval, in SPP's sign — zero or negative. Zero on every activated, non-binding constraint.

    shadow_price

Columns

Exactly what a request answers with, read from the API rather than written here.

ColumnTypeDescription
interval_start_utcrequiredtimestampStart of the interval, UTC. SPP stamps the interval's end.e.g. 2026-09-14T19:55:00Z
isorequiredstringPublishing ISO.e.g. SPP
constraint_namerequiredstringThe constraint as SPP names it, verbatim: often a temporary flowgate (`TMP845_30027`), otherwise a name built from its elements.e.g. TMP845_30027
contingencyrequiredstringThe outaged element the constraint is monitored for, SPP's Contingent Facility verbatim; BASE when none.e.g. WR:MARSHAL3 SSEN:115:2:12
constraint_typerequiredstringSPP's type code: FG (flowgate) and M2M (market-to-market, coordinated with MISO) in real time; FG, MA and MCE in the day-ahead market.e.g. FG
staterequiredstringBINDING, BREACHED (past its limit), or ACTIVATED — in the dispatch but not binding, at a shadow price of zero (real time only).e.g. BINDING
shadow_pricerequirednumberThe constraint's shadow price for the interval, $/MWh, in SPP's sign: zero or negative almost always.e.g. -36.9883
monitored_facilityrequiredstringThe element whose flow the constraint limits, as SPP spells it.e.g. LN MARSHAL3 - KNOB
nerc_idstringNERC's flowgate id.e.g. 30027
interconnectstringThe interconnection the constraint sits in: E (Eastern) on every row read.e.g. E
tlr_levelrequiredstringNERC transmission loading relief level in force: CME on almost every row (3A on 35 of 19,436 over 2026-09-13).e.g. CME
source_limitrequirednumberThe facility's limit from its source rating, MW.e.g. 70
rt_effective_limitrequirednumberThe limit in effect in the real-time run, MW.e.g. 63.7
initial_effective_limitrequirednumberThe initial effective limit, MW.e.g. 67.9
source_published_at_utctimestampWhen SPP published the row.
collected_at_utcrequiredtimestampWhen Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-09-14T20:01:12Z

Read it

Public, read-only, no key and no sign-up. Relative times stay relative, so a URL keeps working.

The newest rows

shell
curl "https://api.dryos.ai/v1/datasets/spp-rt-shadow-prices/query?node=TMP845_30027&limit=12"

The catalogue entry — every column, its type and the source

shell
curl "https://api.dryos.ai/v1/datasets/spp-rt-shadow-prices"

Hourly averages for the last day

shell
curl "https://api.dryos.ai/v1/datasets/spp-rt-shadow-prices/query?node=TMP845_30027&start=-24h&interval=1h&agg=avg"

Full parameters — bucketing, aggregation, filters and search — are on the API reference.

Ask an agent

The same stream through the Model Context Protocol, so Claude, ChatGPT, Cursor or any MCP client can query it directly.

shell
claude mcp add --transport http dryos https://api.dryos.ai/mcp

Then ask:

What has Shadow price been at TMP845_30027 over the last 24 hours, and when did it peak?

Setup for every client is on the MCP server page.

Changes to this collector

A change in the collector is a change in the data. Anyone reading a step in a series is owed the day it moved under them.

  1. 2026-09-14

    First collected, from SPP's marketplace portal.

    CAISO's and PJM's binding constraints were here and SPP's were not. Reconciled against the live files on 2026-09-14: every check passed; activated constraints are kept beside the binding ones.

How this stream is checked

  • Pulled straight from SPP Marketplace Portal · RTBM Binding Constraints — no reseller in between — and compared against that file before it is served.
  • Null means the source did not report it — never zero.
  • A reading lands every 5 min; the interval timestamp is the start of the interval, in UTC.
  • SPP publishes on US Central prevailing time, with a UTC column on every row. Every timestamp Dryos serves is UTC.

Related streams