# EU Industrial Emissions Records — EEA IED Facilities (`nexgensignal/eu-industrial-emissions-records`) Actor

Keyless, pay-per-record EEA IED register — one row per EU industrial facility with site, country, activity, operator and reporting years. Reuse with EEA acknowledgement; facility grain, no person data.

- **URL**: https://apify.com/nexgensignal/eu-industrial-emissions-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, News, 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 facility 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 Industrial Emissions Records — EEA IED Facilities

**Keyless. Pay per record. Every EU industrial facility reporting under the Industrial Emissions Directive.**

This actor turns the **European Environment Agency (EEA)** Industrial Emissions Directive (IED) dataset into clean, per-facility records — the register of industrial installations across Europe that report their environmental performance. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per facility-reporting record: the facility and its site, the country, the industrial activity, the facility address, the reporting authority, and the reporting years and dates. Facility/reporting grain, structured for engineering use, reusable with acknowledgement of the EEA, with **facility contact person and contact email structurally excluded and never emitted.**

### What this is, in one paragraph

Under the EU Industrial Emissions Directive, large industrial installations — power, chemicals, metals, intensive agriculture, waste, and more — report to their member state, and the EEA aggregates and publishes the result. This actor reads that IED facility register and flattens each facility-reporting record into a single analysis-ready row: the site and facility names and their INSPIRE identifiers, the country, the industrial and main activity classifications, the facility address, the reporting organization, and the E-PRTR/EU-registry reporting years and dates. Values are exactly as published by the EEA. You are billed only for records actually delivered.

### Who buys this and for what job

- **ESG, environmental-risk, and supply-chain teams** mapping industrial facilities by country, activity, and operator across the EU.
- **Compliance and due-diligence products** locating regulated installations and their reporting status.
- **Researchers and NGOs** studying the footprint of industrial activity across Europe.
- **Data engineers** who want the IED facility register as clean rows without writing SQL against the EEA service or paging a very large table.

### 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. This rider is carried in this README and on every single record so downstream users always see the required acknowledgement. The data is a facility register as reported by member states — not a compliance verdict.

### Facility/reporting grain — no person data

This actor works at facility/reporting grain: one record per facility per reporting year. The IED table carries a **facility contact person** and a **contact email** — this actor emits **neither**. Those columns are not in the field map at all (structural exclusion), a person-key guard runs on every record as a backstop, and the acceptance suite feeds a record whose contact person and email are populated and asserts none of it can ever appear in output. The reporting organization (an authority or operator, an entity) and the facility address (a location) are retained as facility data.

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `facility_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 | — | Optional 2-letter country code (e.g. DE, FR, IE) to bound this large dataset. Recommended. |
| `reportingYear` | integer | — | Optional E-PRTR reporting year to filter (e.g. 2021). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed — bounds the dataset. |

### Output

One JSON object per facility-reporting record. Real example (values as published by the EEA):

```json
{
  "record_id": "IE.CAED/P0990.FACILITY:2021",
  "site_name": "Fay Pig Farms Limited",
  "facility_name": "Fay Pig Farms Limited",
  "facility_inspire_id": "IE.CAED/P0990.FACILITY",
  "site_inspire_id": "IE.CAED/P0990.SITE",
  "country_code": "IE",
  "country_name": "Ireland",
  "facility_address": "Pollabawn Cavan  IE",
  "facility_industrial_activity": "7(a)(ii)",
  "facility_main_activity": "Installations for the intensive rearing of pigs",
  "reporting_organization": "Environment Protection Agency",
  "eprtr_reporting_year": 2021,
  "eureg_reporting_year": 2021,
  "source": "European Environment Agency (EEA) IED",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Industrial facility reporting records ... facility contact person and email ... excluded ...",
  "observed_at": "2026-08-21T00:00:00Z"
}
```

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

### Field reference

Each record is one facility-reporting record. Identity: `record_id` (facility INSPIRE id + reporting year), `site_name`, `site_inspire_id`, `facility_name`, `facility_inspire_id`, and `facility_name_inspire_id`. Geography: `country_code`, `country_name`, and `facility_address`. Activity: `facility_industrial_activity` and `facility_main_activity`. Reporting: `reporting_organization`, `eureg_reporting_year`, `eprtr_reporting_year`, `eprtr_reporting_date`, and `eprtr_auth_last_updated`. 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 serves no robots file, a no-policy posture — and stops at the door if that ever changes. It then queries the EEA IED facility table through the DiscoData SQL service, pushing your optional `countryCode` and `reportingYear` filters into the query so the dataset is bounded server-side, and pages through the results. Each facility record is flattened to one row — reading only facility, site, activity, and reporting fields, **never** the contact person or email — 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 — a large dataset

The IED facility table holds on the order of **880,000+ facility-reporting records** across all reporting countries and years — this is a large dataset, so bounding it is important. Pass a `countryCode` to scope to one country (recommended), add a `reportingYear` to isolate a single year, and rely on `maxRecords` as the hard ceiling. A single country-year is typically a few hundred to a few thousand facilities. Because each record carries INSPIRE identifiers and the activity classifications, facilities join cleanly to other EU environmental datasets keyed on the same ids.

### Cost guidance

One `facility_record` per delivered record: cost = records delivered × your plan's per-record price. Always scope this dataset with `countryCode` (and optionally `reportingYear`) to keep runs bounded and cheap — one country-year is a few hundred to a few thousand records. 1,000 records is **$50** (Free) / **$33.50** (Gold). Pulling the full ~880,000-record table is possible but rarely what you want; scope first.

### Honest limitations

- **A register, not a verdict.** These are facility-reporting records as published by the EEA from member-state submissions — not a compliance judgment, penalty, or measured-emission figure.
- **Large dataset.** Bound it with `countryCode` and `reportingYear`; unbounded pulls are expensive and slow.
- **As published.** Values are exactly as the EEA distributes them; this actor reformats, it does not recompute.
- **Acknowledge the EEA.** Reuse requires acknowledging the EEA as the source; the acknowledgement travels on every record.
- **No person data** — facility contact person and email are excluded.

### Differentiation

This is a **net-new** category for the NexGenData fleet — no existing fleet actor covers EU IED facility-level industrial-emissions reporting. It is distinct from the fleet's sector-aggregate emissions cells (which carry industry/NACE-level air-emission accounts, not individual facilities) and from US emissions datasets: this actor is the **facility-level EU IED register** from the EEA — installation by installation, with activity and reporting metadata — not a national or sector total.

### The NexGen Signal family

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

- [EU Regulatory Change Records — CELLAR](https://apify.com/nexgensignal/eu-regulatory-change-records)
- [EPA Facility Compliance Records — Envirofacts](https://apify.com/nexgensignal/epa-facility-compliance-records)
- [Air Quality Monitor Records — US EPA AQS](https://apify.com/nexgensignal/air-quality-monitor-records)
- [Airport Facility Records — US FAA NASR](https://apify.com/nexgensignal/airport-facility-records)
- [Mine Operator & Safety Records — US MSHA](https://apify.com/nexgensignal/mine-operator-safety-records)

*Source: European Environment Agency (EEA), Industrial Emissions Directive (IED) dataset (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. Facility/reporting register, not a compliance verdict. Reformatted to facility records; facility contact person and email are structurally excluded and never emitted.*

# Actor input Schema

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

Optional 2-letter country code (e.g. DE, FR, IE) to bound this MONSTER dataset. Recommended.

## `reportingYear` (type: `integer`):

Optional E-PRTR reporting year to filter (e.g. 2021).

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

Maximum records delivered and billed. Bounds this large dataset.

## Actor input object example

```json
{
  "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 = {
    "maxRecords": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-industrial-emissions-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": 500 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-industrial-emissions-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": 500
}' |
apify call nexgensignal/eu-industrial-emissions-records --silent --output-dataset

```

## MCP server setup

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