> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gdeltcloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Energy Data

> Methodology, provenance, and field conventions for Global Energy Monitor asset data in GDELT Cloud.

## Overview

GDELT Cloud Energy Data exposes asset registries from [Global Energy Monitor](https://globalenergymonitor.org/) through the V2 API. Use it to anchor event, story, and entity analysis to physical energy infrastructure: power plants, mines, terminals, pipelines, extraction fields, renewable assets, LNG carriers, and ownership relationships.

<Info>
  Cite Global Energy Monitor for upstream asset facts. Cite GDELT Cloud for the API shape, derived rollups, geography expansion, parsed ownership arrays, and workflow outputs.
</Info>

## Coverage

Current GEM asset and ownership coverage is loaded from the May 2026 Global Energy Monitor releases, including the May 2026 Global Coal Mine Tracker and Global Energy Ownership Tracker.

The V2 Energy API reads from 15 GEM asset trackers:

| Tracker              | Asset type                    | Native capacity                 |
| -------------------- | ----------------------------- | ------------------------------- |
| `coal_plants`        | Coal plant units              | MW                              |
| `coal_mines`         | Coal mines                    | Mtpa                            |
| `coal_terminals`     | Coal import/export terminals  | Mt                              |
| `oil_gas_plants`     | Oil and gas power plants      | MW                              |
| `oil_gas_extraction` | Oil and gas extraction fields | Not populated in the main sheet |
| `lng_terminals`      | LNG import/export terminals   | Mtpa or Bcm/y                   |
| `nuclear`            | Nuclear reactors              | MW                              |
| `geothermal`         | Geothermal power assets       | MW                              |
| `bioenergy`          | Bioenergy power assets        | MW                              |
| `hydropower`         | Hydropower projects           | MW                              |
| `solar`              | Utility-scale solar assets    | MW                              |
| `wind`               | Wind power assets             | MW                              |
| `gas_pipelines`      | Gas pipelines                 | Bcm/y or MMcf/d                 |
| `oil_pipelines`      | Oil and NGL pipelines         | bpd                             |
| `lng_carriers`       | LNG carriers                  | cbm                             |

Stationary infrastructure is returned by default with `asset_class=fixed`. LNG carriers are mobile assets; request `asset_class=mobile` or `asset_class=all` when vessel coverage matters.

## Geography

Energy geography follows the same country, region, and continent expansion as V2 Events. You can use plain English country names, ISO-3 codes, or supported legacy aliases:

```bash theme={null}
country=United States
region=Middle East
continent=Asia
```

For cross-border assets, such as pipelines and binational hydropower projects, filters match either `country_iso3` or `secondary_country_iso3`.

## Capacity

Every asset card includes a native `capacity.value` and `capacity.unit`. `capacity.mw` is populated only for power-generation trackers:

```json theme={null}
{
  "capacity": {
    "value": 5000,
    "unit": "MW",
    "mw": 5000,
    "mw_secondary": null
  }
}
```

Do not sum `capacity_mw_total` across mixed unit families. For capacity rollups, constrain `tracker` to power-generation trackers or group by tracker and interpret each bucket separately.

## Ownership

GEM owner, operator, and parent fields are exposed in two forms:

| Field                                        | Meaning                                           |
| -------------------------------------------- | ------------------------------------------------- |
| `owners_raw`, `operators_raw`, `parents_raw` | Verbatim source strings from GEM                  |
| `owners`, `operators`, `parents`             | Parsed arrays of `{ name, entity_id, stake_pct }` |

Use `owner_search` for fuzzy text search against the raw owner string. Use `owner_entity_id` for exact GEM entity matching across owners, operators, and parents.

For owner-first workflows, resolve the canonical GEM entity first:

```bash theme={null}
curl "https://gdeltcloud.com/api/v2/energy/owners?search=Vattenfall&limit=5" \
  -H "Authorization: Bearer $GDELT_CLOUD_API_KEY"
```

Then pivot from the returned `entity_id` into assets:

```bash theme={null}
curl "https://gdeltcloud.com/api/v2/energy/assets?owner_entity_id=E100002021305&asset_class=all&limit=50" \
  -H "Authorization: Bearer $GDELT_CLOUD_API_KEY"
```

`GET /api/v2/energy/owners/{entity_id}` returns registration/headquarters metadata, parent GEM entities, external IDs, and a cross-tracker portfolio summary. `include_exposure=1` requests admin-gated exposure summaries when the caller has access.

## Refresh Cadence

GEM trackers are refreshed a few times per year as Global Energy Monitor publishes updated tracker files. GDELT Cloud updates Energy Data after those releases are available; do not expect daily or weekly tracker-level changes.

## API Surface

The official V2 Energy API reference documents:

* `GET /api/v2/energy/assets`
* `GET /api/v2/energy/assets/summary`
* `GET /api/v2/energy/assets/map`
* `GET /api/v2/energy/assets/{tracker}/{gem_id}`
* `GET /api/v2/energy/owners`
* `GET /api/v2/energy/owners/{entity_id}`

See [API v2](/api-reference/v2) for authentication, response envelope conventions, and generated endpoint pages.