See where large power loads will connect.

teleon.dev/docs/grid tracks datacenter interconnection requests of 100 MW and more at ERCOT, PJM and CAISO, with LMP pricing at each node.

v32.0teleon.dev/docs/gridPower feedhttpsjson

Read the docs Copy the agent prompt

Requests of 100 MW and more

RequestSize

1ERCOT County600 MWIn study since Nov 2025, node LMP $38.70/MWhStudy

2PJM Valley300 MWFacilities study, node LMP $52.10/MWhStudy

3CAISO Bay150 MWQueued Jun 2026, node LMP $44.90/MWhQueued

Each request shows its queue stage and the 30-day average LMP at its node, so sites with low, steady prices stand out.

What it does

Requests of 100 MW and more

Large datacenter loads are tracked in the ERCOT, PJM and CAISO queues.

Queue status over time

Each request keeps its queue position, study stage and every change to them.

Prices at the node

LMP pricing at each request's node shows what power costs where the load would connect.

The contract

A request names its operator, size, node and queue status, with the queue report behind it, its license and read time.

StoreS113, added in v32.0

SourcesERCOT, PJM and CAISO queues

ScopeDatacenter requests of 100 MW and more, LMP

RecordsEach record carries its source, license and read time

Identifiers

grid.request
grid.node_lmp

Execution contracts

Request and responseCopy

GET /v1/grid/requests?iso=ERCOT,PJM&min_mw=100&kind=datacenter&limit=2
Host: api.teleon.dev

# Response
{
  "requests": [
    {"id": "gq_2291", "iso": "ERCOT", "mw": 600, "kind": "datacenter load",
     "county": "Meridian County", "status": "in study",
     "queued": "2025-11-04", "lmp_30d_avg": 38.7,
     "source": "ERCOT queue report", "license": "terms:ercot",
     "read_at": "2026-10-24T12:00:00Z"},
    {"id": "gq_2310", "iso": "PJM", "mw": 300, "kind": "datacenter load",
     "county": "Meridian Valley", "status": "facilities study",
     "queued": "2026-02-17", "lmp_30d_avg": 52.1,
     "source": "PJM queue data", "license": "terms:pjm",
     "read_at": "2026-10-24T12:00:00Z"}
  ],
  "next_cursor": "c_47e9"
}

Endpoints

Method	Path	Access	What it does
`GET`	`/v1/grid/requests`	RING-3	List requests by operator, size or status
`GET`	`/v1/grid/requests/{id}`	RING-3	Read one request with its queue history and node LMP
`GET`	`/v1/grid/changes?since={cursor}`	RING-3	Stream queue changes and price readings since a cursor
`POST`	`/v1/grid/watches`	RING-2	Alert when a request changes stage or a node price crosses a level

Listed paths appear in the service’s published files today. This surface comes from the Teleon Omnibus Codex v1.0 to v50.0, Oct 25, 2026. In the one-host plan every path here is served under api.teleon.dev/v1/grid.

How it connects

Reads from

Permits and deedsteleon.dev/docs/permits Entitiesteleon.dev/docs/entities

Feeds into

Catalyst fusionteleon.dev/docs/catalysts Earnings and realityteleon.dev/docs/transcripts

Queuesaq261-aq350

StoresS113 Interconnection Queues and LMP Pricing

For agents

Give your agent the read-only guide first. It reports back before any write.

Agent prompt

Read https://teleon.dev/docs/grid.md and list datacenter requests of 100 MW and more in one operator's queue. Read only.

Copy

llms.txt Agent card

Words on this page

Full glossary

Interconnection queue: A grid operator's ordered list of projects waiting for studies and approval to connect, such as power plants, batteries and large loads like datacenters.
LMP: Locational marginal price: the wholesale price of electricity at one grid node, made up of energy, congestion and loss components.
Read time: When Teleon fetched a record from its source. It sits beside the source's own dates, so readers can judge how fresh each record is.
Change cursor: A position in a feed's change stream. A reader sends the last cursor it saw and gets every change after it, in order.