canonical: https://jentic.com/apis/ember-energy.org/ember-energy

# Ember Energy API

Jentic publishes the only available OpenAPI specification for Ember Energy API, keeping it validated and agent-ready. Ember Energy provides curated electricity datasets covering generation, demand, carbon intensity, power-sector emissions, and installed capacity at country and regional level. The API exposes yearly and monthly time series so analysts and data products can query the data without scraping reports. Use it for energy transition dashboards, carbon reporting, and research models that need a clean, citable source.

## For AI agents

Query Ember's curated electricity and emissions datasets - generation, demand, carbon intensity, and installed capacity - at yearly or monthly resolution.

## Scope

Does not handle real-time grid telemetry, market price feeds, or transactions - use for curated historical electricity datasets only.

## Capabilities

- Query yearly and monthly electricity generation by country and fuel type
- Pull carbon intensity time series for grid emissions reporting
- Retrieve electricity demand data at yearly and monthly resolution
- Fetch power-sector emissions data for net-zero tracking dashboards
- Look up installed generation capacity by technology and region
- Discover available filter options for any dataset before issuing a query

## Use cases

### Net-Zero Reporting Dashboards

Build internal or public-facing dashboards that track grid carbon intensity and power-sector emissions over time using Ember's curated dataset. The API exposes yearly and monthly endpoints per dataset so a dashboard can chart progress against decarbonisation targets without scraping PDFs. Climate strategy teams use this as a citable source for board reports and investor disclosures.

Example prompt: Call GET `/carbon-intensity/yearly` and GET `/power-sector-emissions/yearly` for the target countries and emit a JSON payload sized for the dashboard renderer.

### Energy Transition Research

Pull electricity generation and installed capacity data into research notebooks to model the pace of fossil-fuel displacement and renewables growth. The API returns structured rows that drop straight into pandas or a SQL warehouse, with monthly and yearly resolutions for trend analysis. Researchers use this to publish reports backed by a single curated dataset rather than reconciling multiple national sources.

Example prompt: Call GET `/electricity-generation/monthly` and GET `/installed-capacity/monthly` for the target countries and load the response into a pandas DataFrame keyed by date and fuel type.

### Carbon Procurement Planning

Procurement and sustainability teams use carbon intensity time series to plan when and where to source electricity for low-emissions operations. The API provides yearly and monthly carbon intensity at the country level, enabling comparison across markets. Combined with internal load data, it informs PPA siting and 24/7 carbon-free energy strategies.

Example prompt: Call GET `/carbon-intensity/monthly` across candidate markets and rank them by 12-month rolling carbon intensity for the procurement decision document.

### Agent-Driven Energy Brief

An analyst-style agent compiles an electricity market brief by querying generation, demand, and carbon intensity for a country and producing a structured summary. Through Jentic the agent searches by intent, loads each dataset's schema, and executes the calls without bespoke client code. The brief that previously took a half-day of manual data fetching is produced in minutes.

Example prompt: Search Jentic for 'electricity generation by country', execute GET `/electricity-generation/yearly`, GET `/electricity-demand/yearly`, and GET `/carbon-intensity/yearly` for the target country, and synthesise the results into a one-page brief.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/carbon-intensity/yearly` | Yearly carbon intensity by country |
| GET | `/carbon-intensity/monthly` | Monthly carbon intensity by country |
| GET | `/electricity-generation/yearly` | Yearly electricity generation by fuel type |
| GET | `/electricity-generation/monthly` | Monthly electricity generation by fuel type |
| GET | `/electricity-demand/yearly` | Yearly electricity demand |
| GET | `/power-sector-emissions/yearly` | Yearly power-sector emissions |
| GET | `/installed-capacity/monthly` | Monthly installed capacity by technology |
| GET | `/options/{dataset}/{temporal_resolution}/{filter_name}` | Available filter values for a dataset |

## Key resources

- **Carbon Intensity** — Yearly and monthly grid carbon intensity by country and region
- **Electricity Generation** — Generation by fuel type at yearly and monthly resolution
- **Electricity Demand** — Demand time series at yearly and monthly resolution
- **Power Sector Emissions** — Yearly and monthly emissions from electricity generation
- **Installed Capacity** — Installed generation capacity by technology
- **Options** — Available filter values for each dataset and resolution

## Why Jentic

- **Setup:** Wiring Ember Energy API by hand means handling its X-API-Key header, learning the yearly and monthly dataset routes for carbon intensity, generation, demand, and capacity, and building your own query handling against https://api.ember-energy.org/v1. Through Jentic you install once, import Ember Energy API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Ember Energy API is read-only, exposing GET queries over curated electricity datasets with the dataset and resolution in the path (`/options/{dataset}/{temporal_resolution}/{filter_name}`), so scope it by operation: limit the agent to the queries it needs, such as reading yearly carbon intensity or monthly generation, and leave the others out of the allowed set unless you add them.
- **Credential handling:** Your Ember Energy API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get yearly carbon intensity data' or 'fetch monthly electricity generation', and Jentic returns the matching Ember Energy operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Abstract IP Geolocation API** — Resolve user location to a country before querying Ember
- **Particle Device Cloud API** — Stream real-time device data alongside grid statistics
- **Stripe API** — Bill customers for analytics built on Ember data

## FAQ

### Why is there no official OpenAPI spec for Ember Energy API?

Ember does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Ember Energy API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Ember Energy API use?

The API uses an API key passed in the X-API-Key request header. Through Jentic, the key is stored encrypted in the vault and injected at execution time, so the raw value never enters an agent's context.

### Can I get monthly carbon intensity with the Ember Energy API?

Yes. GET `/carbon-intensity/monthly` returns monthly carbon intensity rows. The yearly counterpart at GET `/carbon-intensity/yearly` is available for longer-horizon analysis.

### How do I find the available filter values for a dataset through Jentic?

Search Jentic for 'available filter options Ember', load the schema for GET `/options/{dataset}/{temporal_resolution}/{filter_name}`, and execute it. The response lists valid filter values to use on subsequent dataset queries.

### What are the rate limits for the Ember Energy API?

The OpenAPI spec does not declare quantitative rate limits; Ember enforces limits at the API key level. Treat HTTP 429 responses as authoritative and back off using the Retry-After header where present.

### Can I retrieve installed capacity data by technology?

Yes. GET `/installed-capacity/monthly` returns installed generation capacity broken down by fuel or technology, suitable for renewables tracking dashboards.

### Can I limit what my agent is allowed to do with the Ember Energy API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and the Ember Energy API is read-only, so you scope it by operation. Allow only the GET queries the agent needs, such as reading yearly carbon intensity or monthly electricity generation, and leave the demand, emissions, installed-capacity, or options endpoints out of the allowed set. The stored API key is injected at execution time and never enters the agent's prompt or logs.