# EU Offsite Pollutant Transfer Records — EEA E-PRTR (`nexgensignal/eu-offsite-pollutant-transfer-records`) Actor

Keyless pay-per-record EEA E-PRTR offsite pollutant transfers — pollutant, quantity kg, method, facility report. No operator/person field. EEA acknowledge. GOLD $0.05 ladder.

- **URL**: https://apify.com/nexgensignal/eu-offsite-pollutant-transfer-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 offsite transfer 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 Offsite Pollutant Transfer Records — EEA E-PRTR

**Keyless. Pay per record. Every pollutant transferred offsite by Europe's industrial facilities — substance, quantity, and method.**

This actor turns the **European Environment Agency (EEA) industrial / E-PRTR registry** into clean, per-transfer records — the pollutants that European facilities transfer offsite (in wastewater destined for treatment elsewhere) rather than release directly. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per offsite pollutant transfer: the pollutant, the total quantity transferred (kg), the method used to determine it, any confidentiality reason, and the facility report it belongs to. Facility-report / pollutant / method / quantity 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 European Pollutant Release and Transfer Register (E-PRTR), facilities report not only what they release to air and water on site, but what they transfer **offsite** — pollutants in wastewater sent elsewhere for treatment. This actor reads the offsite-pollutant-transfer table and flattens each transfer into a single analysis-ready record: the pollutant, the total quantity transferred offsite in kilograms, the method code (measured, calculated, estimated), any confidentiality reason and further details, and the facility-report id that ties the transfer to its facility. Quantities and codes are carried **verbatim**. It is the offsite-transfer layer that complements on-site pollutant releases. You are billed only for records actually delivered.

### Who buys this and for what job

- **Environmental-compliance, water, and consultancy teams** analysing offsite pollutant transfers by substance and facility.
- **ESG and industrial-intelligence products** building a complete pollutant picture — on-site release plus offsite transfer.
- **Researchers and NGOs** studying which pollutants move offsite and in what quantities across Europe.
- **Data engineers** who want the E-PRTR offsite-transfer 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. Quantities are reported as filed — this actor reformats, it does not audit.

### Facility grain — no person data

The unit of every record is an offsite transfer keyed to a facility report — an organisation-level report, never a person. 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. The payload is a pollutant, a quantity, a method, and the facility-report id.

### Sample output

![Sample output — EU Offsite Pollutant Transfer Records — EEA E-PRTR](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-offsite-pollutant-transfer-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": "NPANDNPES",
  "total_pollutant_quantity_kg": 13,
  "method_code": "C",
  "confidentiality_reason": null,
  "further_details": null,
  "facility_report_id": "3",
  "control_file_id": "1",
  "source": "EEA Industrial Emissions / E-PRTR registry",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Industrial Emissions / E-PRTR registry — offsite pollutant transfers. 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 / E-PRTR registry.",
  "disclaimer": "Offsite pollutant-transfer records at facility-report / pollutant / method / quantity grain, from the EEA industrial registry. Each record carries a pollutant, the total quantity transferred offsite (kg), the transfer method code, and any confidentiality reason, keyed to the facility report. Facility/organisation grain — no natural-person data; there is no operator, contact, or responsible-person field in the source, and none is emitted. Quantities and codes carried VERBATIM as reported.",
  "observed_at": "2026-09-25T17:33:33Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `offsite_transfer_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 transfers whose pollutant contains this text (e.g. Mercury, Zinc). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

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

```json
{
  "record_id": "42",
  "pollutant": "Mercury and compounds (as Hg)",
  "total_pollutant_quantity_kg": 12.5,
  "method_code": "M",
  "confidentiality_reason": null,
  "further_details": "recovery R4",
  "facility_report_id": "900",
  "control_file_id": "55",
  "source": "EEA Industrial Emissions / E-PRTR registry",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Offsite pollutant-transfer records ... 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 offsite transfer. Identity: `record_id` and `facility_report_id` (the key back to the facility report). Transfer: `pollutant`, `total_pollutant_quantity_kg`, `method_code`, `confidentiality_reason`, and `further_details`. Provenance: `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 offsite-pollutant-transfer table, applies your optional `pollutantContains` filter, and flattens each transfer to one record — carrying the quantity and method **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 offsite-transfer table holds on the order of **65,000+ transfers**. Because each record carries the `pollutant`, `method_code`, and `facility_report_id`, segmenting by pollutant or joining to facility data is straightforward. Pull one pollutant, or the whole table to seed an offsite-transfer warehouse.

### Working with the transfers

The transfers complete the pollutant picture, and the fields make that join clean. Because every record carries the `facility_report_id`, the offsite transfers attach directly to the facility that reported them, and the `pollutant` with `total_pollutant_quantity_kg` supports a substance-level total across facilities in a single group-by. The `method_code` separates measured from calculated and estimated quantities, so a careful consumer can weight the figures by determination method, and the `confidentiality_reason`, where present, marks transfers whose details are withheld. Because quantities are carried verbatim, two pulls can be diffed to track how a facility's offsite transfers changed between reporting years.

### Determination methods and totals

The `method_code` on every transfer records how the reported quantity was arrived at — measured, calculated, or estimated — and carrying it verbatim lets a careful consumer weight or filter figures by determination quality rather than treating every number as equally certain. Because the pollutant name and the quantity in kilograms travel together, a substance-level total across all reporting facilities is a single group-by, and joining on the `facility_report_id` attaches each transfer to the facility that reported it. Where a `confidentiality_reason` is present, the transfer is flagged as one whose details the reporter withheld, so a downstream total can note the coverage gap honestly rather than silently under-counting.

### Cost guidance

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

### Honest limitations

- **As filed.** Quantities and method codes are as reported; this actor reformats, it does not audit.
- **Report-keyed.** Each transfer carries its facility-report id; join to facility data yourself for names and locations.
- **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** (on-site pollutant *releases* to air and water) — this cell carries **offsite transfers** (pollutants sent elsewhere), a different table for a different job. It is the offsite-transfer member of a five-cell EEA industrial/water family (stricter-permit conditions, BAT conclusions, ETS linkage, pesticide monitoring).

### 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 Stricter Permit Condition Records — EEA IED](https://apify.com/nexgensignal/eu-stricter-permit-condition-records)
- [EU Industrial BAT Conclusion Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-bat-conclusion-records)
- [EU Industrial ETS Linkage Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-ets-linkage-records)
- [EU Pesticide Water Monitoring Records — EEA WISE](https://apify.com/nexgensignal/eu-pesticide-water-monitoring-records)

*Source: European Environment Agency (EEA), Industrial Emissions / E-PRTR 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. Facility-report / pollutant / method / quantity grain; no operator, contact, or responsible-person field, no natural-person data of any kind. Quantities as filed, not audited.*

# Actor input Schema

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

Optional. Keep only transfers whose pollutant contains this text (e.g. Mercury, Zinc).

## `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-offsite-pollutant-transfer-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-offsite-pollutant-transfer-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-offsite-pollutant-transfer-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-offsite-pollutant-transfer-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/TjqZ1S1st315TODt2/builds/RrzzgeiLSkS2cdFJH/openapi.json