# EU Industrial Air Release Records — EEA IED (`nexgensignal/eu-industrial-air-release-records`) Actor

Keyless pay-per-record EEA IED emissions to air — one row per pollutant release: pollutant and total tonnes (TNE), verbatim, keyed to the installation-part report. No operator/contact field, no person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-industrial-air-release-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 air release 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 Industrial Air Release Records — EEA IED

**Keyless. Pay per record. Every pollutant released to air by Europe's industrial installations — pollutant by pollutant, in tonnes.**

This actor turns the **European Environment Agency (EEA) Industrial Emissions Directive (IED) registry** into clean, per-release records — the pollutant releases to air reported by the combustion and process parts of Europe's industrial installations. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per air release: the pollutant, the total quantity released in tonnes (TNE), any confidentiality reason, and the installation-part-report id that keys the release back to the reporting unit. Release / pollutant / tonnes 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, the parts of an industrial installation report the pollutants they release to air. This actor reads that emissions-to-air table and flattens each release line into a single analysis-ready record: the pollutant name (nitrogen oxides, sulphur oxides, carbon dioxide, particulate matter, heavy metals, and so on), the total quantity released in tonnes for the reporting period, any confidentiality reason attached at source, and the installation-part-report id that keys the line back to the part that filed it. Quantities are carried **verbatim** in the source unit (tonnes, TNE). It is the air-emissions layer of Europe's industrial register at release grain. You are billed only for records actually delivered.

### Who buys this and for what job

- **Air-quality, environmental, and decarbonisation teams** quantifying pollutant loads to air across Europe's industrial base.
- **ESG and carbon-accounting products** attributing air releases by pollutant and installation.
- **Researchers and NGOs** studying industrial air pollution by pollutant and magnitude.
- **Data engineers** who want the IED emissions-to-air 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 releases as filed — not an audit.

### Release grain — no person data

The unit of every record is a pollutant-release 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 table, and none is selected or emitted: the query reads only the pollutant, the quantity, the confidentiality reason, and the report identifiers. A person-key guard runs on every record as a backstop. The payload is a pollutant, a tonnage, and a report id.

### Sample output

![Sample output — EU Industrial Air Release Records — EEA IED](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-industrial-air-release-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",
  "pollutant": "SO2",
  "total_pollutant_quantity_tne": 635,
  "confidentiality_reason": null,
  "installation_part_report_id": "1",
  "control_file_id": "2",
  "source": "EEA Industrial Emissions Directive (IED) — emissions to air",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Industrial Emissions Directive (IED) registry — pollutant releases to air. 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": "Pollutant releases to air at installation-part-report grain from the EEA IED registry: the pollutant and the total quantity released, in tonnes (TNE), carried VERBATIM as published, keyed to the installation-part report that filed it. Installation/organisation grain — there is no operator, contact, or responsible-person field in the source table, and none is emitted (only pollutant, quantity, and report identifiers are selected); a person-key guard runs on every record as a backstop. A reported release, not a compliance verdict.",
  "observed_at": "2026-09-25T17:32:54Z"
}
```

### Pricing

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

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

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `pollutantContains` | string | — | Optional. Keep only releases whose pollutant contains this text (e.g. Nitrogen, Carbon, Mercury). |
| `maxRecords` | integer | 10 | Ceiling on records delivered and billed. |

**Default changed on 30 Sep 2026:** if you leave `maxRecords` out, a run now returns up to **10** records (it was 500). Set `maxRecords` yourself to get more — the maximum is unchanged.

### Output

One JSON object per air release. Real example (values as published):

```json
{
  "record_id": "1",
  "pollutant": "Nitrogen oxides (NOX)",
  "total_pollutant_quantity_tne": 123.4,
  "confidentiality_reason": null,
  "installation_part_report_id": "7",
  "control_file_id": "1",
  "source": "EEA Industrial Emissions Directive (IED) — emissions to air",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "attribution": "Source: European Environment Agency (EEA), Industrial Emissions Directive (IED) registry.",
  "disclaimer": "Pollutant releases to air ... 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 air-release line. Identity: `record_id` and `installation_part_report_id` (the key back to the installation-part report). Measurement: `pollutant` and `total_pollutant_quantity_tne` (tonnes, verbatim). 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 emissions-to-air table, applies your optional `pollutantContains` filter, and flattens each release to one record — carrying the quantity **verbatim** in tonnes, 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 emissions-to-air table holds on the order of **92,000+ release lines**. Because each record carries the `pollutant`, the `total_pollutant_quantity_tne`, and the `installation_part_report_id`, segmenting by pollutant and joining to the reporting part is straightforward. Pull one pollutant, or the whole table to seed an air-emissions warehouse.

### Working with the releases

The releases are the air-emissions backbone, and the fields make them additive. Because every line pairs a `pollutant` with a `total_pollutant_quantity_tne` in a shared unit, a pollutant-load total by type across installations is a single group-by, and there is no scale-guessing. The `installation_part_report_id` keys each line back to its reporting part, so the release attaches to the part's combustion category, operating hours, and fuel mix from the fleet's other IED cells — a full picture of what each asset emits and how it runs. The `confidentiality_reason`, where present, tells a downstream consumer which values the operator flagged, rather than treating a gap as missing data.

### Units and joins

Quantities are carried in tonnes (TNE) exactly as reported, so the figures are additive across pollutants and installations without any unit conversion or re-basing on this actor's part — a pollutant-load total is a straight sum. The `installation_part_report_id` is the join key back to the installation-part report, so a buyer can attach each release line to its part's category, operating hours, and fuel input, turning a bare emission figure into a full picture of what an asset emits and how hard it runs. Because every field is carried verbatim and nothing person-shaped is ever selected, the record stays a clean, faithful, joinable measurement.

### Cost guidance

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

### Honest limitations

- **As filed.** Quantities are as reported in tonnes; this actor reformats, it does not audit.
- **Report-keyed.** Each line carries its installation-part-report id; join to the combustion-part or facility-report cell for category, hours, and stack attributes.
- **Air medium only.** This is the emissions-to-air table specifically; off-site pollutant and waste transfers are separate fleet cells.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

It is distinct from the fleet's **eu-industrial-emissions-records** (facility-level emissions summary), from **eu-offsite-pollutant-transfer-records** (pollutants transferred *off-site* in waste water, in kilograms), and from **eu-industrial-waste-transfer-records** (waste tonnages transferred off-site). Its specific job is the **IED emissions-to-air table at release grain** — pollutant and tonnes released to air, line by line.

### The NexGen Signal family

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

- [EU Industrial Emissions Records — EEA IED Facilities](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [EU Offsite Pollutant Transfer Records — EEA IED](https://apify.com/nexgensignal/eu-offsite-pollutant-transfer-records)
- [EU Industrial Waste Transfer Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-waste-transfer-records)
- [EU Combustion Installation Part Records — EEA IED](https://apify.com/nexgensignal/eu-combustion-installation-part-records)
- [EU Combustion Plant Fuel Input Records — EEA IED](https://apify.com/nexgensignal/eu-combustion-plant-fuel-input-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. Release / pollutant / tonnes grain; no operator, contact, or responsible-person field is selected or emitted, no natural-person data of any kind. Quantities as filed in the source unit (tonnes, TNE), not audited.*

# Actor input Schema

## `pollutantContains` (type: `string`):

Optional. Keep only releases whose pollutant contains this text (e.g. Nitrogen, Carbon, Mercury).

## `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-industrial-air-release-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-industrial-air-release-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-industrial-air-release-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-industrial-air-release-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/qNXM7rhFexPdYGlsr/builds/UkpretqKfgCQeoF7Z/openapi.json