Ember Energy API

Name: Ember Energy API
Brand: Ember Energy API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsBusiness IntelligenceapiKey10 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Ember Energy API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ember Energy API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Ember Energy API.

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

GET STARTED

Start building with Ember Energy API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Ember Energy API for, with concrete tasks.

★ 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.

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.

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.

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.

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

10 endpoints — jentic publishes the only available openapi specification for ember energy api, keeping it validated and agent-ready.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Ember Energy API key is stored encrypted in the Jentic vault. Agents receive scoped access tokens — the raw key never enters the agent's context, and Jentic injects it into the X-API-Key header at execution time.

Intent-based discovery

Agents search by intent (e.g., 'electricity generation by country') and Jentic returns matching Ember operations with their input schemas, so the agent calls the right dataset endpoint without reading docs.

Time to first call

Direct Ember integration: half a day for client code, key handling, and dataset-specific query formatting. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Ember Energy API through Jentic.

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 at https://app.jentic.com/sign-up.

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.