CAISO · Grid

CAISO WEIM transfers, fifteen-minute

The fifteen-minute market's Western EIM transfers, tie by tie and direction by direction, posted about half an hour ahead, with the limit each ran against.

caiso-eim-transfers-15minevery 15 min, ~30 min ahead · 15m rows462 entities
CISO->SRP PVWEST
0.00MW
2026-09-18 05:15 UTC
SRP->CISO PVWEST
708MW
2026-09-18 05:15 UTC
NWMT->BPAT GARRISON
0.00MW
2026-09-18 05:15 UTC
Read from the Dryos API and cached for an hour; the stream itself updates every 15 min, ~30 min ahead.

What is in it

Updates
every 15 min, ~30 min ahead · 15m rows
Entities
462 entities — CISO->SRP PVWEST, SRP->CISO PVWEST, NWMT->BPAT GARRISON…
Source timezone
US Pacific — every timestamp Dryos serves is UTC
Coverage
14 September 2026 to now
Rows held
156,156
Primary key
iso, tie, from_baa, to_baa, interval_start_utc

What it measures

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

  • TransferMW

    Energy moving from the exporter to the importer over the tie.

    transfer_mw
  • LimitMW

    The transfer limit for the flow in the interval.

    limit_mw

Columns

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

ColumnTypeDescription
interval_start_utcrequiredtimestampStart of the interval, UTC, read from OASIS's GMT column.e.g. 2026-09-14T17:00:00Z
isorequiredstringPublishing ISO.e.g. CAISO
transferrequiredstringThe flow: exporter->importer and the tie, built from the three columns after it, so one flow is one series.e.g. CISO->SRP PVWEST
tierequiredstringThe tie as OASIS names it.e.g. PVWEST
from_baarequiredstringThe exporting balancing authority.e.g. CISO
to_baarequiredstringThe importing balancing authority.e.g. SRP
transfer_mwrequirednumberEnergy moving from from_baa to to_baa over the tie, MW. Zero is no flow; a few read negative, as published.e.g. 1109.34
limit_mwnumberThe transfer limit for the flow in the interval, MW.e.g. 2411
source_published_at_utctimestampWhen CAISO posted the interval (UPD_DATE, Pacific wall-clock), UTC.e.g. 2026-09-14T16:56:35Z
collected_at_utcrequiredtimestampWhen Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-09-14T17: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/caiso-eim-transfers-15min/query?node=CISO-%3ESRP%20PVWEST&limit=12"

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

shell
curl "https://api.dryos.ai/v1/datasets/caiso-eim-transfers-15min"

Hourly averages for the last day

shell
curl "https://api.dryos.ai/v1/datasets/caiso-eim-transfers-15min/query?node=CISO-%3ESRP%20PVWEST&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 Transfer been at CISO->SRP PVWEST 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 CAISO OASIS.

    The Western EIM transfers and their limits, the cause behind the WEIM areas' energy prices parting. Reconciled against a live response on 2026-09-14.

How this stream is checked

  • Pulled straight from CAISO OASIS · ENE_EIM_TRANSFER_TIE and ENE_EIM_TRANSFER_LIMITS_TIE (RTPD) — 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 15 min, ~30 min ahead; the interval timestamp is the start of the interval, in UTC.
  • CAISO's market clock is US Pacific; OASIS answers in UTC. Every timestamp Dryos serves is UTC.

Related streams