# EU Combustion Plant Fuel Input Records — EEA IED (`nexgensignal/eu-combustion-plant-fuel-input-records`) Actor

Keyless pay-per-record EEA IED combustion fuel/energy input — fuel type + energy in TJ, keyed to the installation-part report. No persons. EEA acknowledge. $0.05 per record on the Free plan, $0.0335 on Gold.

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

## Pricing

from $33.50 / 1,000 fuel input 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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## EU Combustion Plant Fuel Input Records — EEA IED

**Keyless. Pay per record. The fuel mix and energy input of Europe's combustion plants — fuel by fuel, in terajoules.**

This actor turns the **European Environment Agency (EEA) Industrial Emissions Directive (IED) registry** into clean, per-fuel-input records — the fuel mix and energy input reported by the combustion parts of Europe's industrial installations. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per fuel input: the fuel input type, the energy input in terajoules (TJ), and other gaseous/solid fuel detail, keyed to the installation-part report. Part / fuel / TJ / report grain, structured for engineering use, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Under the IED, combustion parts report the fuels they burn and how much energy each contributes. This actor reads that energy-input table and flattens each fuel line into a single analysis-ready record: the fuel input type (natural gas, coal, biomass, other gaseous, other solid, and so on), the energy input in terajoules, the free-form other-gaseous and other-solid fuel detail, any confidentiality reason, and the installation-part-report id that keys the line back to its combustion part. Energy values are carried **verbatim** in the source unit (TJ). It is the fuel-mix layer of Europe's combustion register. You are billed only for records actually delivered.

### Who buys this and for what job

- **Energy, decarbonisation, and fuel-switching teams** analysing the fuel mix and energy input of Europe's combustion base.
- **Carbon-accounting and ESG products** attributing energy input by fuel type across installations.
- **Power-market and biomass-supply teams** sizing fuel demand from the combustion register.
- **Data engineers** who want the IED fuel-input table as clean rows from a keyless source.

### 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. These are reported energy inputs as filed — not an audit.

### Part/fuel grain — no person data

The unit of every record is a fuel-input line keyed to an installation-part report — an organisation-level report, never a person. There is **no operator, contact, or responsible-person field** in the source, and none is emitted; a person-key guard runs on every record as a backstop. The payload is a fuel type, an energy figure, and the report id.

### Sample output

![Sample output — EU Combustion Plant Fuel Input Records — EEA IED](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-combustion-plant-fuel-input-records.png)

*Real rows from a live run of this actor (first 5 rows, selected columns).*

One full record from the same run, exactly as delivered:

```json
{
  "record_id": "1",
  "fuel_input": "OtherGases",
  "energy_input_tj": 0,
  "other_gaseous_fuel": null,
  "other_solid_fuel": null,
  "confidentiality_reason": null,
  "installation_part_report_id": "218",
  "control_file_id": "2",
  "source": "EEA Industrial Emissions Directive (IED) — combustion energy input",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Industrial Emissions Directive (IED) registry — combustion plant fuel and energy input. Reuse is permitted, including for commercial purposes, provided the source is acknowledged: 'Source: European Environment Agency (EEA)'. Third-party content, where marked, keeps its own terms.",
  "attribution": "Source: European Environment Agency (EEA), Industrial Emissions Directive (IED) registry.",
  "disclaimer": "Combustion plant-part fuel and energy-input records at part / fuel / TJ / report grain from the EEA IED registry: the fuel input type, the energy input in terajoules (TJ), and other gaseous/solid fuel detail, keyed to the installation-part report. Installation/organisation grain — no natural-person data; there is no operator, contact, or responsible-person field in the source, and none is emitted. Energy values carried VERBATIM in the source unit (TJ).",
  "observed_at": "2026-09-25T17:32:10Z"
}
```

### Pricing

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

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

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `fuelContains` | string | — | Optional. Keep only rows whose fuel input contains this text (e.g. gas, coal, biomass). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per fuel input. Real example (values as published):

```json
{
  "record_id": "1",
  "fuel_input": "NaturalGas",
  "energy_input_tj": 123.4,
  "other_gaseous_fuel": null,
  "other_solid_fuel": null,
  "confidentiality_reason": null,
  "installation_part_report_id": "7",
  "control_file_id": "1",
  "source": "EEA Industrial Emissions Directive (IED) — combustion energy input",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Combustion plant-part fuel and energy-input records ... no operator, contact, or responsible-person field ...",
  "observed_at": "2026-08-22T00:00:00Z"
}
```

An unbilled `RUN_RECEIPT` records the robots check, the filter, rows seen and delivered, and whether charged equals delivered.

### Field reference

Each record is one fuel-input line. Identity: `record_id` and `installation_part_report_id` (the key back to the combustion-part report). Fuel: `fuel_input`, `energy_input_tj`, `other_gaseous_fuel`, and `other_solid_fuel`. Provenance: `confidentiality_reason`, `control_file_id`, `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 energy-input table, applies your optional `fuelContains` filter, and flattens each fuel line to one record — carrying the energy figure **verbatim** in TJ, never anything person-shaped — 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 energy-input table holds on the order of **283,000+ fuel-input lines**. Because each record carries the `fuel_input`, `energy_input_tj`, and `installation_part_report_id`, segmenting by fuel type and joining to the combustion part is straightforward. Pull one fuel type, or the whole table to seed a fuel-mix warehouse.

### Working with the fuel inputs

The fuel inputs are the fuel-mix backbone, and the fields make them additive. Because every line pairs a `fuel_input` type with an `energy_input_tj`, a fuel-mix total by type across installations is a single group-by, and the shared unit (terajoules) means no scale-guessing. The `installation_part_report_id` keys each line back to its combustion part, so the fuel mix attaches to the part's category, operating hours, and district-heating share from the fleet's combustion-part cell — a full picture of what each asset burns and how it runs. The `other_gaseous_fuel` and `other_solid_fuel` detail captures the long tail of fuels the standard categories miss.

### Units and joins

Energy input is carried in terajoules exactly as reported, so the figures are additive across fuels and plants without any unit conversion or re-basing on this actor's part — a fuel-mix total is a straight sum. The `installation_part_report_id` is the join key back to the combustion-part report, so a buyer can attach each fuel line to its part's category, operating hours, and district-heating share, turning a bare fuel figure into a full picture of what an asset burns and how hard it runs. The `other_gaseous_fuel` and `other_solid_fuel` fields capture the long tail of fuels that do not fit the standard categories, so a fuel-demand model built on this data does not silently drop the unusual streams that matter for biomass and waste-derived fuels.

### Cost guidance

One `fuel_input_record` per delivered line: cost = lines delivered × your plan's per-record price. Scope with `fuelContains` to keep runs bounded. The table is ~283,000 lines; 1,000 lines is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **As filed.** Energy figures are as reported in TJ; this actor reformats, it does not audit.
- **Report-keyed.** Each line carries its installation-part-report id; join to the combustion-part cell for category and operating hours.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

Its specific job is the **IED combustion fuel and energy input** — fuel type and TJ, line by line.

### The NexGen Signal family

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

- [EU Combustion Plant Records — EEA IED LCP](https://apify.com/nexgensignal/eu-combustion-plant-operating-hour-records)
- [EU Combustion Installation Part Records — EEA IED](https://apify.com/nexgensignal/eu-combustion-installation-part-records)
- [EU Industrial Facility Report Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-facility-report-records)
- [EU Industrial Emissions Records — EEA IED Facilities](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [EU Forest Carbon Stock Records — EEA FISE](https://apify.com/nexgensignal/eu-forest-carbon-stock-records)

*Source: European Environment Agency (EEA), Industrial Emissions Directive (IED) registry (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. Part / fuel / TJ / report grain; no operator, contact, or responsible-person field, no natural-person data of any kind. Energy values as filed in the source unit (TJ), not audited.*

# Actor input Schema

## `fuelContains` (type: `string`):

Optional. Keep only rows whose fuel input contains this text (e.g. gas, coal, biomass).

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

Maximum records delivered and billed.

## Actor input object example

```json
{
  "maxRecords": 10
}
```

# 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 = {
    "maxRecords": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-combustion-plant-fuel-input-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 = { "maxRecords": 10 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-combustion-plant-fuel-input-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 '{
  "maxRecords": 10
}' |
apify call nexgensignal/eu-combustion-plant-fuel-input-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-combustion-plant-fuel-input-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/uaZwQFNsCGQEsXqL2/builds/pUp6ikbd5eFDebaHs/openapi.json