Documentation Index
Fetch the complete documentation index at: https://powersignals.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Power Signals API
Power Signals provides real-time, structured energy data through a clean, predictable REST API. We are a primary-source data provider of Eskom grid data — every system-state reading is collected, parsed, and served by us directly. We ingest data the moment it is published, normalise it into machine-ready formats, and expose it via API. Data is typically available within seconds of publication. All timestamps are returned in UTC; see Data Provenance for details.What You Can Access
Our underlying coverage spans 2,400+ generation, transmission, and distribution assets with 5+ years of history. The API currently exposes grid-level signals derived from this coverage at hourly resolution; per-asset endpoints are on the roadmap. Available datasets today:- Grid System State — Hourly generation mix (coal, nuclear, gas, hydro, wind, solar), imports/exports, residual demand, and derived metrics.
- Grid Stress Index — A derived signal indicating overall grid stress level, computed from system-state data.
Coming soon
- Generation Mix — Per-source generation at finer resolution as a standalone dataset.
- System Demand Forecasts — Day-ahead and intraday forecast demand.
- Loadshedding — Eskom stage announcements, area schedules, and historical time-series.
- SAPP Day-Ahead Prices — Hourly clearing prices (ZAR), volumes, and revision history.
- NERSA Filings — MYPD submissions, tariff decisions, and licensing records.
Built For
- AI energy-market agents and LLM pipelines
- Quantitative research desks and trading firms
- IPP developers and project-finance analysts
- Grid operators, regulators, and demand-response platforms
- Risk, policy, and sustainability researchers
Design Principles
The API follows four principles:- Primary source — We collect directly from official sources (currently Eskom; SAPP and NERSA coming soon).
- Cleanly typed — All responses follow a consistent
meta+dataenvelope. - Version-stable — Breaking changes only happen on major version bumps.
- Never silent — If a feed upstream is late, the API returns a structured
data_delayresponse instead of stale values.

