Name: ERCOT Grid Supply & Demand
Creator: ERCOT Supply and Demand dashboard

API access

Your AI client reaches ERCOT Grid Supply & Demand through one ParcelOps MCP endpoint, so there is no separate key to hold for it and no per-source client to write. Reaching it takes no credentials of your own.

Set up ERCOT Grid Supply & Demand in Claude, ChatGPT, or Cursor Get every fact on this page as JSON

Where it came from

PublisherERCOT Supply and Demand dashboard

Sourcehttps://www.ercot.com/api/1/services/read/dashboards/supply-demand.json

API basehttps://www.ercot.com/api/1/services/read/dashboards

Docshttps://www.ercot.com/gridmktinfo/dashboards/supplyanddemand

Freshness and coverage

FreshnessNear real-time · The public dashboard response currently advertises a 60-second cache lifetime.

Places coveredERCOT system-wide Texas grid context

Time coveredNot declared

CredentialsNo credentials required

What this source cannot tell you

⚠ Anything outside ERCOT system-wide Texas grid context. A request past that edge comes back empty rather than approximated.
⚠ Which years it spans, because the covered period is not declared.
⚠ Anything ERCOT Supply and Demand dashboard does not publish. ParcelOps returns this source as it stands and never fills a blank field from a different one.
⚠ System-wide dashboard values do not establish site, utility, substation, transmission, distribution, or interconnection capacity.
⚠ Current values are preliminary, not settlement-quality data.
⚠ The dashboard JSON schema and rate limit are undocumented, so this connector is beta.

Methods (3)

A method is one call your agent can make against this source.

getCurrentGridStatus
read
Get the latest actual dashboard row, next forecast row, and clearly labeled arithmetic headroom.
FreshnessNear real-time (source-level)
Input schema
```
{
  "type": "object",
  "properties": {},
  "required": [],
  "additionalProperties": false
}
```

getSupplyDemandForecast

read

Get bounded current-day or six-day supply and demand dashboard records.

What you must providescope

FreshnessNear real-time (source-level)

Input schema

{
  "type": "object",
  "properties": {
    "scope": {
      "type": "string",
      "enum": [
        "current-day",
        "six-day"
      ]
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 300
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "maximum": 300
    }
  },
  "required": [
    "scope"
  ],
  "additionalProperties": false
}

getServiceInfo
read
Return dashboard source, beta status, reuse terms, coverage, and limitations.
FreshnessNear real-time (source-level)
Input schema
```
{
  "type": "object",
  "properties": {},
  "required": [],
  "additionalProperties": false
}
```

Where this source is used

Texas grid and land screening
Put Texas grid context next to the state parcel record and the site constraints in one screening call.
Land research
Parcel records, ground conditions, and what reaches the property line, for raw and rural land.
Data center siting
Power, water, transport, airspace, and hazard screening for a site before anyone signs anything.
Which utility serves this property?
Who runs the grid at this site?

ERCOT Grid Supply & Demand API and MCP server