# EU Basin Pollutant Input Total Records — EEA WISE (`nexgensignal/eu-basin-pollutant-input-total-records`) Actor

Keyless pay-per-record EEA WISE WFD basin pollutant input totals — chemical, point/diffuse type, value and unit in source units, methodology, data-quality flag, verbatim. No person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-basin-pollutant-input-total-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 input total 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 Basin Pollutant Input Total Records — EEA WISE

**Keyless. Pay per record. Total point-and-diffuse pollutant inputs to Europe's river basins — by chemical, with method, unit, and data quality.**

This actor turns the **European Environment Agency (EEA) WISE Water Framework Directive (WFD) programme of measures** into clean, per-record data — the total point-and-diffuse pollutant inputs reported for Europe's river basins. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per input-total row, structured for pollutant-load and catchment analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Under the Water Framework Directive programme of measures, member states report a pollutant input inventory — the total loads entering each river basin from point and diffuse sources. This actor reads that input-total table and delivers one record per reported input total: the country and river basin district (and sub-unit), the chemical substance, the input-total type (point / diffuse / point-and-diffuse), the value and UNIT in the source units, the inventory methodology, the input year period, and the DATA-QUALITY flag — all carried verbatim. It is the pollutant-load layer of Europe's catchment assessment.

### Who buys this and for what job

- **Catchment and pollutant-load analysts quantifying inputs to river basins by chemical and source type**
- **Water-policy and modelling teams feeding official input inventories into load models**
- **Researchers comparing point vs diffuse pollutant contributions across basins**
- **Data engineers** who want the WISE WFD basin input-inventory 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 as filed — not a compliance verdict.

### Water-body grain — no person data

The unit of every record is a reported input total for a chemical in a river basin — a load figure, never a person. 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 as a backstop. The `file_url` points to the official Eionet/CDR reporting file.

### A note on scale, honestly

This actor delivers the rows of the WFD input-inventory input-total table that carry a reported input-total type (point, diffuse, or point-and-diffuse) — **12,249 rows** as verified by an exact `COUNT(*)` at build time. The full table also holds rows without a total type, which are not input totals; those are excluded so every record is an actual reported input total.

### Sample output

![Sample output — EU Basin Pollutant Input Total Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-basin-pollutant-input-total-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": "AT1000:CAS_104-40-5 - 4-nonylphenol:Total point and diffuse sources:2016",
  "reporting_year": 2016,
  "country_code": "AT",
  "country_name": "Austria",
  "eu_rbd_code": "AT1000",
  "rbd_name": "DANUBE",
  "eu_sub_unit_code": "AT1001",
  "sub_unit_name": "DANUBE",
  "chemical_substance": "CAS_104-40-5 - 4-nonylphenol",
  "upbt": "No",
  "reported_under_soe_emissions": "Yes",
  "inventory_methodology": "Approach 1 + 2",
  "input_year_period": "2003",
  "input_total_type": "Total point and diffuse sources",
  "input_data_quality": "Medium",
  "input_total_value": "1913.76334964",
  "input_total_unit": "kg/a",
  "number_of_water_bodies_failing_in_rbd": null,
  "file_url": "http://cdr.eionet.europa.eu/at/eu/wfd2016/districts/at1000/envwvttw/RBMPPoM_AT_20170628.xml",
  "source": "EEA WISE Water Framework Directive (WFD) — basin pollutant input totals",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE Water Framework Directive (WFD) programme of measures — basin pollutant input inventories. 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), WISE (Water Information System for Europe).",
  "disclaimer": "Total point-and-diffuse pollutant inputs by river basin district / sub-unit / chemical / period, from the EEA WISE Water Framework Directive programme-of-measures input inventory (rows with a reported input-total type). Each record carries the chemical substance, the input-total type (point / diffuse / point-and-diffuse), the value and UNIT in the source units, the inventory methodology, and the DATA-QUALITY flag — all carried VERBATIM as reported. River-basin 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 as a backstop.",
  "observed_at": "2026-09-25T17:31:31Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `input_total_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). |
| `year` | integer | — | Optional reporting cycle year to filter. |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per input-total row. Real example (values as reported):

```json
{
  "record_id": "AT1000:Cadmium:Total point and diffuse sources:2022",
  "reporting_year": 2022,
  "country_code": "AT",
  "country_name": "Austria",
  "eu_rbd_code": "AT1000",
  "rbd_name": "DANUBE",
  "chemical_substance": "Cadmium",
  "input_total_type": "Total point and diffuse sources",
  "input_total_value": "12.5",
  "input_total_unit": "kg/year",
  "input_data_quality": "Medium",
  "input_year_period": "2016-2021",
  "source": "EEA WISE Water Framework Directive (WFD) \u2014 basin pollutant input totals",
  "observed_at": "2026-08-22T00:00:00Z"
}
```

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

### Field reference

Each record is one input total. Identity: `record_id`, `country_code`, `country_name`, `eu_rbd_code`, `rbd_name`, `eu_sub_unit_code`, `sub_unit_name`, and `reporting_year`. Substance and input: `chemical_substance`, `upbt`, `reported_under_soe_emissions`, `input_total_type`, `input_total_value`, `input_total_unit`, and `input_year_period`. Method and quality: `inventory_methodology`, `input_data_quality`, and `number_of_water_bodies_failing_in_rbd`. Plus `file_url`. 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 — the EEA DiscoData host — and stops at the door if that ever changes. It pages the WISE WFD basin input-inventory table (rows with a reported input-total type), and flattens each row to one record — carrying every value **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 **12,249 rows**. Because each record carries the `chemical_substance`, `input_total_type`, and `input_total_value`, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

### Working with the data

The input totals are a load ledger, and the fields make them additive. Because every record pairs a `chemical_substance` with an `input_total_value` and `input_total_unit` and the `input_total_type` (point / diffuse / combined), an analyst can compare point vs diffuse contributions of a pollutant across basins, and the `input_data_quality` flag travels so weak figures can be down-weighted rather than silently trusted. The `reporting_year` frames each total in its cycle.

### Identifiers and joins

Every record carries the `eu_rbd_code`, keying each input total to the fleet's other WISE cells for that river basin — the failing pollutants, the river-basin-specific standards, and the pressure-substance crosswalk — so a buyer can line up the reported pollutant loads against the standards and failures for the same basin, on a shared identifier.

### Cost guidance

One `input_total_record` per delivered row: cost = rows delivered × your plan's per-record price. Scope with `countryCode` and `year` to keep runs bounded. 1,000 rows is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

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

### Differentiation

It is distinct from the fleet's monitoring and status cells — this cell quantifies pollutant INPUT LOADS to basins (point and diffuse), not monitored concentrations or status classifications. It differs entirely from the Nitrates, Bathing Water, and Urban Waste Water directive cells. Its specific job is the **WFD basin pollutant input inventory totals**.

### The NexGen Signal family

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

- [EU Water Monitoring Parameter Schedule Records — EEA WISE](https://apify.com/nexgensignal/eu-water-monitoring-parameter-schedule-records)
- [EU Surface Water Ecological Exemption Records — EEA WISE](https://apify.com/nexgensignal/eu-surface-water-ecological-exemption-records)
- [EU Waterbody Pesticide Exceedance Records — EEA WISE](https://apify.com/nexgensignal/eu-waterbody-pesticide-exceedance-records)
- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-records)
- [EU Nitrate Monitoring Records — EEA](https://apify.com/nexgensignal/eu-nitrate-monitoring-records)

*Source: European Environment Agency (EEA), WISE (Water Information System for Europe) (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. River-basin / chemical / input-total-type grain; no contact/operator/responsible-person field selected or emitted. No natural-person data of any kind. Values as filed, not a compliance verdict.*

# Actor input Schema

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

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

## `year` (type: `integer`):

Optional reporting cycle year to filter.

## `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-basin-pollutant-input-total-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-basin-pollutant-input-total-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-basin-pollutant-input-total-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-basin-pollutant-input-total-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/HpwFVNkD119FFSH0p/builds/TS3CR8q6nWx2Ttln7/openapi.json