# EU GHG Inventory Records — EEA (`nexgensignal/eu-ghg-inventory-records`) Actor

Keyless pay-per-record EEA EU GHG inventory — country/sector/gas/category/year observations, values+notation verbatim. Partition by country. EEA acknowledge. GOLD $0.05 ladder.

- **URL**: https://apify.com/nexgensignal/eu-ghg-inventory-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, Developer tools, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 ghg records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## EU GHG Inventory Records — EEA

**Keyless. Pay per record. Europe's national greenhouse-gas inventory — country, sector, gas, category, year — as one clean series.**

This actor turns the **European Environment Agency (EEA) EU Greenhouse Gas Inventory** into clean, per-observation records — the national GHG inventory submissions that member states report and the EEA compiles. Each run reads the EEA's keyless DiscoData SQL service for the country you choose and delivers one row per country / sector / gas / category / year observation: the country, the inventory year, the sector and sector number, the gas, the measure and classification, the parameter and unit, and the reported value with its notation. Country / sector / gas / category / year observation grain, structured for engineering use, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Every year, EU member states submit national greenhouse-gas inventories — how much of each gas each sector emitted or removed — and the EEA compiles them into a single dataset. This actor reads that dataset and flattens each observation into an analysis-ready record: the country and country code, the inventory year, the sector (Energy, Industrial Processes, Agriculture, LULUCF, Waste) and its IPCC sector number, the gas (CO₂, CH₄, N₂O, F-gases, aggregates), the measure (emissions, removals, activity) and classification, the parameter and unit, and the reported value with its reporting notation. Values are carried **verbatim** with their units, and a null value carrying a notation code (NO = not occurring, NE = not estimated, IE = included elsewhere) is preserved as exactly that — a reporting code, never a silent zero. It is the emissions-accounting layer of Europe's climate reporting. You are billed only for records actually delivered.

### Who buys this and for what job

- **Climate-analytics, ESG, and carbon-accounting teams** building national and sectoral emission time series across Europe.
- **Policy, research, and NGO products** tracking emissions by gas and sector against targets.
- **Sustainability-data and reporting platforms** that need a clean, sourced European inventory feed.
- **Data engineers** who want the EEA GHG inventory as clean rows without writing SQL and joining the variable dimension by hand.

### EEA licence — reuse with acknowledgement

One licence rider travels on every record. EEA data may be **reused, including commercially, provided the source is acknowledged**: "Source: European Environment Agency (EEA)." Where third-party content is marked, it keeps its own terms. The data is the national inventory as reported and compiled — not an independent verification of any country's figures.

### Observation grain — no person data

The unit of every record is a country / sector / gas / category / year observation — a measurement, never a person. The dataset carries no natural-person fields; countries, sectors, gases, categories, units, and values are the entire payload, and a person-key guard runs on every record as a pure backstop.

### A required partition — this is a multi-million-row dataset

The EU GHG Inventory is published as one very large observation table — **over 21.4 million rows**. This actor therefore **requires a partition**: every run must set a `countryCode`. The country bounds the run; there is no unbounded all-Europe pull. Optional `year` and `gas` filters narrow further, and `maxRecords` is the hard ceiling.

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `ghg_record` | $0.05 | $0.045 | $0.04 | $0.0335 |

Delivered before charged. Blocked runs and empty results cost nothing.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `countryCode` | string | — | **Required** country code (e.g. DE, FR, IT). |
| `year` | integer | — | Optional inventory year to filter (e.g. 2020). |
| `gas` | string | — | Optional gas to filter (e.g. CO2, CH4, N2O). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per observation. Real example (values as reported):

```json
{
  "record_id": "DE:1990:1fd58ccf-7058-4c7d-b897-746fb62668ad",
  "country": "Germany",
  "country_code": "DE",
  "inventory_year": 1990,
  "sector": "1. Energy",
  "sector_number": "1.A",
  "gas": "Aggregate GHGs",
  "measure": "Emissions",
  "classification": "Fuels",
  "parameter": "no parameter",
  "unit": "kt CO₂ equivalent",
  "value": 37904.41,
  "notation": null,
  "source": "EEA EU Greenhouse Gas Inventory",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "EU greenhouse-gas inventory observation records ... a null value with a notation key ... is a reporting code, not a zero ...",
  "observed_at": "2026-08-22T00:00:00Z"
}
```

An unbilled `RUN_RECEIPT` records the robots check, the country/year/gas filters, rows matched and delivered, and whether charged equals delivered.

### Field reference

Each record is one observation. Scope: `country`, `country_code`, and `inventory_year`. Category: `sector`, `sector_number`, `gas`, `measure`, and `classification`. Measurement: `parameter`, `unit`, `value`, and `notation` (the reporting code where a value is not a number). Key: `variable_uid` (the EEA variable identifier that ties the observation to its full category definition). Provenance: `source`, `source_url`, `licence`, `attribution`, `disclaimer`, and `observed_at`.

### How a run works

A run first re-reads the source host's robots posture from your runtime — the EEA DiscoData host — and stops at the door if that ever changes. It pages the inventory value table filtered to your `countryCode` (and optional `year`), enriches each value with its variable's sector, gas, measure, classification, parameter, and unit, applies your optional `gas` filter, and flattens each observation to one record — carrying the value and notation **verbatim** — delivered **before** it is charged, so a blocked or empty run costs you nothing. The actor stops at your `maxRecords` ceiling and records `charge_equals_delivered` in the receipt.

### Coverage and scope

The inventory spans the reporting countries and the full inventory time series, with **21.4 million+ observation rows** in total. Because each record carries the `country_code`, `inventory_year`, `sector`, and `gas`, building a national or sectoral emission time series, or comparing gases within a sector, is straightforward. Pull one country, or one gas within a country, to seed an emissions warehouse.

### Working with the inventory

The inventory is a time series waiting to be assembled, and the dimensions make it mechanical. Every record carries the `country_code`, `inventory_year`, `sector`, and `gas`, so a single filtered pull sorted by year reconstructs a sector's emission trajectory for a given gas, and the `unit` travels on every row so a downstream consumer never guesses a scale. The `measure` separates emissions from removals and activity data, so a LULUCF sink can be told from a source in a single filter, and the `notation` preserves the reporting reality — a "not estimated" cell stays distinguishable from a true zero, which matters for any honest total. Because the `sector_number` follows the IPCC classification, the dataset rolls cleanly from headline sectors down to sub-categories, and two country pulls can be diffed year over year to track progress against a baseline.

### Cost guidance

One `ghg_record` per delivered observation: cost = rows delivered × your plan's per-record price. Always scope with `countryCode` and narrow with `year` and `gas`. 1,000 observations is **$50** (Free) / **$33.50** (Gold). These are very large per-country slices, so filter and cap deliberately.

### Honest limitations

- **As reported.** Inventory figures are as submitted and compiled; this actor reformats and joins the category dimension, it does not verify or recompute.
- **Partition required.** Every run must set a `countryCode`.
- **Notation is not zero.** A null value with a notation code is a reporting code, preserved as such.
- **No person data** of any kind.

### Differentiation

This is a **net-new** category for the NexGenData fleet, and it sits in a cross-fleet climate family that this listing names so buyers pick the right one. The NexGenData fleet already ships **eurostat-ghg-sector-emissions** (Eurostat's aggregated sector emissions — a different publisher and a different, more aggregated series) and the **epa-ghgrp-** family (US EPA facility-level greenhouse-gas reporting — a different jurisdiction and a facility grain). This cell is the **EEA national-inventory** series at country / sector / gas / category / year observation grain — the EU's official submitted inventory, distinct from the Eurostat aggregates and the US facility reports.

### The NexGen Signal family

Part of the NexGen Signal family of pay-per-record data products:

- [EU Air Quality Measure Records — EEA AQ Plans](https://apify.com/nexgensignal/eu-air-quality-measure-records)
- [EU Air Quality Scenario Records — EEA AQ Plans](https://apify.com/nexgensignal/eu-air-quality-scenario-records)
- [EU Industrial Emissions Records — EEA IED Facilities](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [EU Vehicle CO2 Records — EEA](https://apify.com/nexgensignal/eu-vehicle-co2-records)
- [EU Bathing Water Quality Records — EEA BWD](https://apify.com/nexgensignal/eu-bathing-water-quality-records)

*Source: European Environment Agency (EEA), EU Greenhouse Gas Inventory (discodata.eea.europa.eu). EEA data may be reused, including commercially, provided the source is acknowledged: "Source: European Environment Agency (EEA)"; marked third-party content keeps its own terms. Country / sector / gas / category / year observation grain; values and reporting notation carried verbatim (a notation code is not a zero); no person data of any kind. National inventory as reported and compiled, not an independent verification.*

# Actor input Schema

## `countryCode` (type: `string`):

REQUIRED country code (e.g. DE, FR, IT) — the full inventory table is a MONSTER (21M+ rows) and cannot be pulled unbounded.

## `year` (type: `integer`):

Optional inventory year to filter (e.g. 2020).

## `gas` (type: `string`):

Optional gas to filter (e.g. CO2, CH4, N2O; matched against the variable's gas).

## `maxRecords` (type: `integer`):

Maximum records delivered and billed.

## Actor input object example

```json
{
  "countryCode": "DE",
  "maxRecords": 500
}
```

# Actor output Schema

## `results` (type: `string`):

Delivered records.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "countryCode": "DE",
    "maxRecords": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-ghg-inventory-records").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "countryCode": "DE",
    "maxRecords": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-ghg-inventory-records").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "countryCode": "DE",
  "maxRecords": 500
}' |
apify call nexgensignal/eu-ghg-inventory-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-ghg-inventory-records"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/VbjJ5dbybaA0CrhPu/builds/dnpGS2kcd3r5azmMN/openapi.json