# EU Plant Desulphurisation Records — EEA IED (`nexgensignal/eu-plant-desulphurisation-records`) Actor

Per-record monthly desulphurisation rate and fuel sulphur content for EU Large Combustion Plant parts from EEA IED. Keyless, pay per record, verbatim, no person data.

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

## Pricing

from $33.50 / 1,000 plant desulphurisation 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 Plant Desulphurisation Records — EEA IED

**Keyless. Pay per record. Monthly desulphurisation rate and fuel sulphur content for regulated combustion-plant parts — verbatim.**

This actor turns the **European Environment Agency (EEA) Industrial Emissions Directive (IED) Large Combustion Plant desulphurisation dataset** into clean, per-record data — the monthly desulphurisation performance reported for Europe's regulated Large Combustion Plant parts. Each run reads the keyless EEA DiscoData SQL service and delivers one row per plant-part month, structured for emissions-compliance and combustion-plant analysis, reusable with acknowledgement of the source, with no personal data of any kind.

### What this is, in one paragraph

Under the Industrial Emissions Directive, operators of Large Combustion Plants that use flue-gas desulphurisation report the monthly desulphurisation rate achieved and the sulphur content of the fuel burned. The EEA compiles those into the IED desulphurisation dataset. This actor reads that table and delivers one record per plant-part / month: the installation-part report id, the month, the desulphurisation RATE and the fuel SULPHUR CONTENT carried verbatim, and the control/source ids. It is the desulphurisation-performance layer of Europe's combustion-plant regulation — how well each plant part is stripping sulphur, month by month.

### Who buys this and for what job

- **Emissions-compliance analysts tracking desulphurisation performance across combustion plants**
- **Air-quality and industrial-regulation teams relating desulphurisation rates to fuel sulphur**
- **Researchers studying flue-gas desulphurisation performance across Europe**
- **Data engineers** who want the IED desulphurisation 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 values and labels as filed — not a compliance verdict.

### Plant-part / month grain — no person data

The unit of every record is one plant part's desulphurisation performance in one month — a performance figure, never a person. The identifiers are report/control ids; there is no contact, operator, or responsible-person field in the source, and none is selected or emitted; the free-text technical-justification narrative is excluded at field selection. A person-key guard runs on every record.

### Sample output

![Sample output — EU Plant Desulphurisation Records — EEA IED](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-plant-desulphurisation-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": "2459:OCT",
  "installation_part_report_id": "2459",
  "month": "OCT",
  "desulphurisation_rate": 0.967,
  "sulphur_content": 0.035,
  "control_file_id": "27",
  "source_row_id": "632",
  "source": "EEA Industrial Emissions Directive (IED) — Large Combustion Plant desulphurisation",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Industrial Emissions Directive (IED) registry. 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 (discodata.eea.europa.eu).",
  "disclaimer": "Monthly desulphurisation rate and fuel sulphur content for regulated Large Combustion Plant parts, at plant-part / month grain from the EEA Industrial Emissions Directive (IED) desulphurisation dataset. Each record carries the installation-part report id, the month, the desulphurisation RATE and the SULPHUR CONTENT VERBATIM, and control/source ids. The free-text technical-justification narrative is excluded at field selection. Plant-part grain — there is no contact, operator, or responsible-person field in the source, and none is selected or emitted; a person-key guard runs on every record.",
  "observed_at": "2026-09-25T17:33:33Z"
}
```

### Pricing

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

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

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per plant-part month. Real example (values as reported):

```json
{
  "record_id": "2459:OCT",
  "installation_part_report_id": "2459",
  "month": "OCT",
  "desulphurisation_rate": 0.967,
  "sulphur_content": 0.035,
  "control_file_id": "27",
  "source_row_id": "632",
  "source": "EEA Industrial Emissions Directive (IED) \u2014 Large Combustion Plant desulphurisation",
  "source_url": "https://discodata.eea.europa.eu/",
  "observed_at": "2026-08-25T00:00:00Z"
}
```

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

### Field reference

Each record is one plant-part month. Identity: `record_id` (part report id : month), `installation_part_report_id`, `month`, and `source_row_id`. Performance: `desulphurisation_rate` and `sulphur_content` (both verbatim). Plus `control_file_id`. Provenance travels on every record: `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 and stops at the door if that ever changes. It pages the IED desulphurisation source, and flattens each row to one record — carrying every value and label **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 table holds on the order of **5,851 rows** — small enough to pull whole in one bounded run, yet far above the fleet's minimum-viability floor. Because each record pairs a plant part with a month, monthly desulphurisation time series assemble directly, and a single unfiltered pull seeds a complete European desulphurisation-performance table that can be refreshed on a schedule as new IED reporting lands. There is no country partition needed at this size — the `maxRecords` ceiling is the only bound you set.

### Working with the data

The rates are a performance ledger, and the fields make them comparable. Because every record pairs a `desulphurisation_rate` with a `sulphur_content` for a plant part and month, an analyst can build a plant part's monthly desulphurisation profile, relate the rate achieved to the sulphur content of the fuel, and compare performance across parts and seasons. Values travel verbatim, so no unit or scale is assumed. A desulphurisation rate read next to the fuel's sulphur content is the honest way to judge abatement: a high rate on high-sulphur fuel is a very different picture from the same rate on clean fuel, and because both figures ride on one record, that comparison needs no join. The `month` field turns a pile of rows into a twelve-point annual curve per plant part, so seasonal patterns and reporting gaps show up at a glance.

### Identifiers and joins

Every record carries the `installation_part_report_id` and `control_file_id`, keying each desulphurisation month to the IED combustion-plant reporting for the same part, so performance can be read alongside the plant's emissions and energy-input records.

### Desulphurisation versus the combustion-plant emission cells

The IED Large Combustion Plant family reports several things: the ENERGY input, the EMISSIONS to air, and — for plants with flue-gas desulphurisation — the desulphurisation PERFORMANCE (this cell). Keeping desulphurisation as its own actor means a buyer studying sulphur abatement pulls the monthly rate/sulphur rows directly, at plant-part/month grain, rather than carrying the whole emissions table, and joins back on the part id when emissions or energy input are also needed.

### Cost guidance

One `plant_desulphurisation_record` per delivered row: cost = rows delivered × your plan's per-record price. 1,000 rows is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **As reported.** Values, labels, and flags are as filed; this actor reformats, it does not audit or recompute.
- **A label, not a verdict.** These are reported performance figures, not an independent compliance assessment.
- **Acknowledge the source.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

It is distinct from the combustion-plant EMISSION and ENERGY-INPUT cells — those carry what a plant emitted or burned, while this cell carries the monthly desulphurisation RATE and fuel SULPHUR CONTENT; abatement performance vs emissions/energy. Its specific job is the **IED Large Combustion Plant desulphurisation performance**.

### The NexGen Signal family

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

- [EU Industrial Secondary Activity Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-secondary-activity-records)
- [EU Industrial Facility Report Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-facility-report-records)
- [EU Industrial Production Volume Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-production-volume-records)
- [EU Industrial Permit Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-permit-records)
- [EU Industrial Waste Transfer Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-waste-transfer-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)". Plant-part / month grain; free-text technical-justification excluded; no contact/operator/responsible-person field selected or emitted. No natural-person data of any kind. Values and labels as filed, not a verdict.*

# Actor input Schema

## `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-plant-desulphurisation-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-plant-desulphurisation-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-plant-desulphurisation-records --silent --output-dataset

```

## MCP server setup

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