# EU BAT Derogation Records — EEA IED (`nexgensignal/eu-bat-derogation-records`) Actor

Keyless pay-per-record EEA IED BAT derogations — derogation indicator, public reason URL, BAT-AEL and duration, verbatim, with installation identity. No operator/contact field, no person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-bat-derogation-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 bat derogation 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 BAT Derogation Records — EEA IED

**Keyless. Pay per record. Every IED installation holding a derogation from Best Available Techniques emission levels — with the public reason and the derogated limit.**

This actor turns the **European Environment Agency (EEA) Industrial Emissions Directive (IED) registry** into clean, per-installation records — the Best Available Techniques (BAT) derogations recorded against Europe's industrial installations. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per derogation entry: whether the installation holds a derogation from BAT-associated emission levels (BAT-AELs), the public reason URL and the BAT-AEL text carried verbatim, the derogation start and end dates, and the installation's identity (facility name, country, main IED activity). Installation grain, structured for regulatory analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Under the IED, a competent authority may grant an installation a derogation allowing emission levels less strict than the BAT-associated levels, provided the reasons are documented and made public. This actor reads that derogation table and flattens each entry into a single analysis-ready record: the derogation indicator, the public reason URL where the justification is published, the BAT-AEL text as filed, the derogation duration (start and end dates), and the installation it applies to — enriched with the installation's facility name (suppressed where flagged confidential), country, main IED Annex I activity, and status. Reasons and limits are carried **verbatim** exactly as filed; this actor never interprets a derogation or judges whether it was warranted. It is the BAT-derogation layer of Europe's industrial register. You are billed only for records actually delivered.

### Who buys this and for what job

- **Environmental-compliance and regulatory-intelligence teams** tracking which installations run under BAT derogations and why.
- **ESG and risk products** flagging installations operating above standard BAT emission levels.
- **Consultancies and NGOs** studying the use of BAT derogations across countries and sectors.
- **Data engineers** who want the IED BAT-derogation 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 registry entries as filed — not a compliance verdict.

### Installation grain — no person data

The unit of every record is a BAT-derogation entry keyed to an installation — an organisation-level entry, 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 derogation indicator, the public reason URL, the BAT-AEL text, the duration dates, and the installation/control identifiers. The installation's facility name is itself an organisation name, suppressed where the source flags it confidential. A person-key guard runs on every record as a backstop.

### Sample output

![Sample output — EU BAT Derogation Records — EEA IED](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-bat-derogation-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": "17706:13854",
  "bat_derogation_indicator": "False",
  "public_reason_url": null,
  "bat_ael": null,
  "derogation_start_date": null,
  "derogation_end_date": null,
  "installation_id": "17706",
  "installation_name": "Alytus district boiler",
  "country_code": "LT",
  "ied_annex_i_main_activity": "1.1",
  "installation_status": "functional",
  "reporting_year": "2017",
  "control_file_id": "59",
  "source": "EEA Industrial Emissions Directive (IED) registry",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Industrial Emissions Directive (IED) registry — installation BAT derogations. 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": "Installation BAT-derogation records at installation grain from the EEA IED registry: whether the installation holds a derogation from Best Available Techniques Associated Emission Levels, the public reason URL and the BATAEL text carried VERBATIM as filed, and the derogation start/end dates, with the installation's FACILITY name (an organisation, suppressed where flagged confidential), country, and main IED activity. Installation/organisation grain — 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. A registry entry, not a compliance verdict.",
  "observed_at": "2026-09-25T17:31:33Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `bat_derogation_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 of the installation (e.g. DE, FR). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per derogation entry. Real example (values as published):

```json
{
  "record_id": "17706:9",
  "bat_derogation_indicator": "Yes",
  "public_reason_url": "https://example.org/reason",
  "bat_ael": "NOx < 150 mg/Nm3",
  "derogation_start_date": "2018-01-01",
  "derogation_end_date": "2022-12-31",
  "installation_id": "17706",
  "installation_name": "Alytus district boiler",
  "country_code": "LT",
  "ied_annex_i_main_activity": "1.1",
  "installation_status": "functional",
  "reporting_year": "2018",
  "control_file_id": "2",
  "source": "EEA Industrial Emissions Directive (IED) registry",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "attribution": "Source: European Environment Agency (EEA), Industrial Emissions Directive (IED) registry.",
  "disclaimer": "Installation BAT-derogation records ... carried VERBATIM as filed ... no ... responsible-person field ...",
  "observed_at": "2026-08-22T00:00:00Z"
}
```

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

### Field reference

Each record is one derogation entry. Derogation: `bat_derogation_indicator`, `public_reason_url`, `bat_ael` (the derogated limit text, verbatim), `derogation_start_date`, and `derogation_end_date`. Installation: `installation_id`, `installation_name` (facility/org name, suppressed where confidential), `country_code`, `ied_annex_i_main_activity`, `installation_status`, and `reporting_year`. Keys: `record_id` and `control_file_id`. 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 BAT-derogation table ordered by installation, enriches each page's installation identity from the production-installation register, applies your optional `countryCode` filter, and flattens each entry to one record — carrying the reason URL and BAT-AEL text **verbatim**, 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 BAT-derogation table holds on the order of **345,000+ entries**. Because each record carries the `country_code`, the `bat_derogation_indicator`, and the installation identity, segmenting by country, sector, or derogation status is straightforward. Pull one country, or the whole table to seed a derogation-tracking warehouse.

### Working with the derogations

The derogations are a regulatory-risk signal, and the fields make them actionable. Because every entry carries a `bat_derogation_indicator` alongside the installation's `ied_annex_i_main_activity` and `country_code`, an analyst can count derogations by sector and country in a single group-by, and the `derogation_start_date` and `derogation_end_date` frame each one in time so expiring derogations can be surfaced. The `public_reason_url` links straight to the published justification, and the `bat_ael` records the derogated limit as filed, so a downstream consumer can compare it to the standard BAT-associated level without this actor ever interpreting the value. The enriched `installation_name` gives a human-readable anchor for QA.

### Identifiers and joins

Every entry carries an `installation_id`, the stable key back to the fleet's other IED cells — emissions, permit conditions, BAT conclusions, and the competent authority responsible for the installation — so a buyer can attach a derogation to an installation's full regulatory picture on an identifier rather than a fuzzy name match. Because reasons and limits are carried verbatim and nothing person-shaped is ever selected, the record stays a faithful, joinable regulatory fact: this installation holds this derogation, for this documented reason, until this date.

### Cost guidance

One `bat_derogation_record` per delivered entry: cost = entries delivered × your plan's per-record price. Scope with `countryCode` to keep runs bounded. The table is ~345,000 entries; 1,000 entries is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **As filed.** The derogation indicator, reason URL, and BAT-AEL are carried verbatim; this actor reformats, it does not audit or judge whether a derogation was warranted.
- **A registry entry, not a verdict.** These are recorded derogations, not a compliance assessment.
- **Enriched identity.** The installation name and activity come from the production-installation register, and the facility name is suppressed where flagged confidential.
- **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-bat-conclusion-records** (which links installations to the BAT *conclusions* they are resolved against) and **eu-stricter-permit-condition-records** (stricter-than-BAT permit conditions). A derogation is the opposite direction — a documented allowance to run *less strict* than a BAT-associated level — so this cell captures a distinct regulatory event. It is also distinct from **eu-industrial-inspection-records** (the competent-authority linkage). Its specific job is the **IED BAT-derogation table at installation grain** — indicator, reason, limit, and duration.

### The NexGen Signal family

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

- [EU Industrial BAT Conclusion Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-bat-conclusion-records)
- [EU Stricter Permit Condition Records — EEA IED](https://apify.com/nexgensignal/eu-stricter-permit-condition-records)
- [EU Industrial Inspection Authority Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-inspection-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)

*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. Installation grain; no operator, contact, or responsible-person field is selected or emitted; the installation facility name is an organisation, suppressed where confidential; no natural-person data of any kind. Reasons and BAT-AEL limits carried verbatim as filed, never interpreted; a registry entry, not a compliance verdict.*

# Actor input Schema

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

Optional 2-letter country code of the installation (e.g. DE, FR).

## `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-bat-derogation-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-bat-derogation-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-bat-derogation-records --silent --output-dataset

```

## MCP server setup

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