# EU Industrial Secondary Activity Records — EEA IED (`nexgensignal/eu-industrial-secondary-activity-records`) Actor

Per-record EU regulated installations resolved to additional IED activity codes, enriched with name/country/status, from EEA IED. Keyless, pay per record, confidential names suppressed.

- **URL**: https://apify.com/nexgensignal/eu-industrial-secondary-activity-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 industrial secondary activity 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 Secondary Activity Records — EEA IED

**Keyless. Pay per record. Each regulated installation resolved to its additional IED activity codes — with installation name, country, and status.**

This actor turns the **European Environment Agency (EEA) Industrial Emissions Directive (IED) registry** into clean, per-record data — the additional (secondary) regulated activities carried out at Europe's industrial installations. Each run reads the keyless EEA DiscoData SQL service and delivers one row per installation activity, structured for industrial-regulation and installation-profiling 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, an installation has a main regulated activity but may also carry out ADDITIONAL (secondary) Annex I activities. The EEA registry records those. This actor reads the installation-other-activity table and delivers one record per installation / additional-activity: the installation id, the additional IED Annex I activity code carried verbatim, and — enriched from the installation registry — the installation name (SUPPRESSED where the source marks it confidential), the country, the IED main activity, and the operating status. It is the secondary-activity layer of Europe's industrial regulation — the full activity mix of each regulated installation.

### Who buys this and for what job

- **Industrial-regulation analysts profiling the full activity mix of regulated installations**
- **Permitting and compliance teams resolving installations to all their Annex I activities**
- **Researchers studying secondary industrial activities across Europe**
- **Data engineers** who want the IED secondary-activity 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.

### Installation / activity grain — no person data

The unit of every record is one additional activity at one installation — a regulated-activity line, never a person. The installation is an id/name; there is no contact, operator, or responsible-person field in the source, and none is selected or emitted; confidential installation names are suppressed. A person-key guard runs on every record as a backstop.

### Sample output

![Sample output — EU Industrial Secondary Activity Records — EEA IED](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-industrial-secondary-activity-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:4.3",
  "installation_id": "1",
  "other_activity": "4.3",
  "control_file_id": "15",
  "installation_name": "Molycorp Silmet AS, Sillamäe haruldaste muldmetallide tehas",
  "installation_name_confidential": "false",
  "country_code": "EE",
  "ied_main_activity": "2.5(a)",
  "installation_status": "functional",
  "source": "EEA Industrial Emissions Directive (IED) — installation additional IED activities",
  "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": "Regulated industrial installations resolved to their ADDITIONAL (secondary) IED Annex I activity codes, at installation / activity grain from the EEA Industrial Emissions Directive (IED) registry. Each record carries the installation id, the additional activity code VERBATIM, and — enriched from the installation registry — the installation name (SUPPRESSED where the source marks the name confidential), the country, the IED main activity, and the operating status. Installation grain — there is no contact, operator, or responsible-person field selected or emitted; confidential names are suppressed; a person-key guard runs on every record as a backstop.",
  "observed_at": "2026-09-25T17:33:06Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `industrial_secondary_activity_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 installation activity. Real example (values as reported):

```json
{
  "record_id": "1:4.3",
  "installation_id": "1",
  "other_activity": "4.3",
  "control_file_id": "15",
  "installation_name": "Molycorp Silmet AS",
  "installation_name_confidential": "false",
  "country_code": "EE",
  "ied_main_activity": "4.3",
  "installation_status": "functional",
  "source": "EEA Industrial Emissions Directive (IED) \u2014 installation additional IED activities",
  "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 installation activity. Identity: `record_id` (installation id : activity), `installation_id`, and `control_file_id`. Activity: `other_activity` (verbatim). Enriched installation context: `installation_name` (null when `installation_name_confidential` is true), `country_code`, `ied_main_activity`, and `installation_status`. 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 secondary-activity 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 **44,742 rows**, each an installation-to-additional-activity link enriched with the installation's country and status. Because each record carries the installation id, country, and activity code, segmenting by country or activity is straightforward, and a full pull seeds a warehouse table of the complete European secondary-activity matrix. The enrichment is done in-run against the installation registry, so the country and name arrive already resolved rather than as a foreign key you must join yourself.

### Working with the data

The activities are an installation profile, and the enrichment makes them legible. Because every record pairs an `installation_id` with an `other_activity` and the installation's `country_code` and `ied_main_activity`, an analyst can list every additional activity an installation runs, or every installation performing a given activity in a country, without a second lookup. Where the source marks a name confidential, the name is suppressed but the record — id, country, activity — is still delivered, so coverage stays complete without exposing a protected name. Because the IED main activity rides on every row alongside the secondary one, an analyst can immediately see which installations diversify beyond their headline activity and into what — the kind of profile that a raw activity-link table, without the enrichment, could not give without a second query.

### Identifiers and joins

Every record carries the `installation_id` and `country_code`, keying each secondary activity to the IED installation, permit, and emission cells for the same installation, on a shared identifier — so an installation's full activity mix, its permit, and its emissions line up on one key without a fuzzy name match.

### Secondary activities versus the main-activity registry

The installation registry records each installation's MAIN regulated activity; this cell records the ADDITIONAL activities it also carries out. Keeping them separate means a buyer who needs the complete activity mix pulls the secondary-activity rows and joins to the main-activity registry on the installation id, reconstructing the full Annex I footprint of each installation — with confidential names respected on both sides.

### Cost guidance

One `industrial_secondary_activity_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 registry facts, 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 IED installation/permit cells (which carry the installation's identity, permit, and MAIN activity) — this cell carries the ADDITIONAL Annex I activities; secondary-activity mix vs main registry. Its specific job is the **IED installation additional activities**.

### 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)". Installation / activity grain; confidential installation names suppressed; 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-industrial-secondary-activity-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-secondary-activity-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-secondary-activity-records --silent --output-dataset

```

## MCP server setup

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