Foundational models.
A registry of models for the power grid — a geotemporal time-series foundation model, and the spike, event, and outage-reschedule models built around it. Open any card to read how it works, what it reads, what it emits, and the three ways to consume it.
One base model
The Geotemporal Foundation Model is the backbone — a time-series foundation model pretrained on years of ISO history jointly with the grid's geography. The other models are built from it.
Post-trained and physical derivatives
Some models sharpen the base on a task, like the price and congestion tails. Others reason over a physical power-flow model of the network to anticipate stress and outages.
Three ways to consume each one
Every model reaches the same three surfaces: in the product, over a typed developer inference service (not MCP), and as MCP tools for your own agent.
The models.
Four models for the physical grid. Open any one to read its full card.
Foundation model · time-series + geospatial
Our base model — a time-series foundation model pretrained on years of ISO history jointly with the grid's geography, so a forecast at one location carries what's happening around it.
02Post-trained · probabilistic tails
A GTFM derivative post-trained to model the extreme tails — the price and congestion spikes that matter most and are hardest to forecast.
03Physical · outage & grid stress
Where the foundation model reads history, the Event Model reasons over the physical network — given a power-flow model of the grid, it anticipates where stress and outages are likely to emerge.
04Physical · maintenance timing
Planned outages are frequently rescheduled; this model predicts which scheduled maintenance events are likely to shift, and in which direction, from grid-stress and market heuristics.
Beyond the models above
The four cards are the models we run against the grid. Ongoing research at the desk explores the methods behind them and what comes next.
Read the researchConsume any model.
Every card reaches the same three surfaces. The model output carries its source and as-of no matter which one you reach for.
In the product
The models power Ask the Grid directly — the live map, the radar, and the grid agent read them in place.
Inference service
A direct, typed inference API for forecasts and embeddings by node and horizon. This is not MCP — it is a plain endpoint for your pipelines and services.
See the developer surfaceMCP
The same model outputs exposed as tools for your own agent. Point a compatible client at the Ask the Grid MCP server.
Build with MCPSee the models where the grid is live.
The agent that reads the grid lives on its own page — these models are the machinery underneath it and the research beside it.