# EU Chemical Status Grouping Provenance Records — EEA WISE (`nexgensignal/eu-chemical-status-grouping-provenance-records`) Actor

Keyless pay-per-record EEA WISE WFD chemical-status grouping provenance — water body, donor water body code, chemical status, assessment confidence, target date, verbatim. No person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-chemical-status-grouping-provenance-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 grouping provenance 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 Chemical Status Grouping Provenance Records — EEA WISE

**Keyless. Pay per record. Which donor water bodies support Europe's grouped chemical-status classifications — with status, confidence, and target date.**

This actor turns the **European Environment Agency (EEA) WISE Water Framework Directive (WFD) database** into clean, per-record data — the provenance of grouped chemical-status classifications: which donor water body supports each grouped assessment. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per provenance row, structured for water-status methodology and provenance 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, a member state may assign a water body's chemical status by GROUPING it with a monitored 'donor' water body rather than monitoring it directly. This actor reads that table and delivers one record per grouped classification: the country, river basin, and water body; its chemical status value; the assessment year and CONFIDENCE; the expected achievement date; and the DONOR water body code that supports the grouped status — all carried verbatim. It is the provenance layer behind Europe's grouped chemical-status classifications.

### Who buys this and for what job

- **Water-status methodologists auditing how grouped chemical-status classifications were derived**
- **Assessment-quality teams tracing which water bodies were monitored vs grouped and with what confidence**
- **Researchers studying the use and confidence of grouping in status assessment**
- **Data engineers** who want the WISE WFD chemical-status grouping 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 grouped chemical-status classification with its donor — a provenance line, 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 where a grouping donor is present (`swChemicalStatusGrouping != 'None'`) — **284,801 rows** as verified by an exact `COUNT(*)` at build time, matching the index exactly. Where a water body's chemical status was assigned by grouping, this field carries the donor water body code that supports the classification.

### Sample output

![Sample output — EU Chemical Status Grouping Provenance Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-chemical-status-grouping-provenance-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": "ATOK1000010000:ATOK1001040041:2022",
  "reporting_year": 2022,
  "country_code": "AT",
  "country_name": "Austria",
  "eu_rbd_code": "AT1000",
  "rbd_name": "DANUBE",
  "eu_surface_water_body_code": "ATOK1000010000",
  "surface_water_body_name": "NO INTERNATIONAL NAME",
  "surface_water_body_category": "RW",
  "chemical_status_value": "3",
  "chemical_assessment_year": "2016--2021",
  "chemical_assessment_confidence": "Medium",
  "chemical_status_expected_achievement_date": "2027 or earlier",
  "donor_water_body_code": "ATOK1001040041",
  "file_url": "https://cdr.eionet.europa.eu/at/eu/wfd2022/districts/at1000/envzodafw/SWB_AT_AT1000_20220810.xml",
  "source": "EEA WISE Water Framework Directive (WFD) — chemical-status grouping provenance",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE Water Framework Directive (WFD) — chemical-status grouping provenance. 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": "Provenance of GROUPED chemical-status classifications: for surface water bodies whose chemical status was assigned by grouping, the DONOR water body code that supports the grouped classification, with the chemical status, assessment year, assessment CONFIDENCE (carried VERBATIM), and expected achievement date — at water-body / donor / reporting-cycle grain from the EEA WISE Water Framework Directive database (rows where a grouping donor is present). Water-body 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:32Z"
}
```

### Pricing

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

```json
{
  "record_id": "ATOK1500100:ATOK100350000:2016",
  "reporting_year": 2016,
  "country_code": "AT",
  "country_name": "Austria",
  "eu_rbd_code": "AT1000",
  "rbd_name": "DANUBE",
  "eu_surface_water_body_code": "ATOK1500100",
  "surface_water_body_name": "Example Reach",
  "chemical_status_value": "2",
  "chemical_assessment_year": "2015",
  "chemical_assessment_confidence": "Medium",
  "donor_water_body_code": "ATOK100350000",
  "source": "EEA WISE Water Framework Directive (WFD) \u2014 chemical-status grouping provenance",
  "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 grouped classification. Identity: `record_id`, `country_code`, `country_name`, `eu_rbd_code`, `rbd_name`, `eu_surface_water_body_code`, `surface_water_body_name`, `surface_water_body_category`, and `reporting_year`. Status and provenance: `chemical_status_value`, `chemical_assessment_year`, `chemical_assessment_confidence`, `chemical_status_expected_achievement_date`, and `donor_water_body_code`. 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 chemical-status grouping table (rows where a grouping donor is present), 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 **284,801 rows**. Because each record carries the `donor_water_body_code`, `chemical_status_value`, and `chemical_assessment_confidence`, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

### Working with the data

The provenance rows are a methodology audit trail, and the fields make them traceable. Because every record links a water body to its `donor_water_body_code` with the `chemical_assessment_confidence`, an analyst can see how much of a basin's chemical status rests on grouping rather than direct monitoring, and at what confidence — a data-quality signal for anyone relying on the status. The `reporting_year` frames each classification in its cycle.

### Why grouping provenance matters

Grouping is a legitimate but confidence-reducing shortcut in status assessment: a water body classified by grouping inherits its status from a donor rather than direct monitoring. Surfacing the donor code and the assessment confidence on every record lets a downstream consumer weight or flag grouped classifications explicitly, rather than treating a grouped status as if it were directly measured.

### Identifiers and joins

Every record carries both the `eu_surface_water_body_code` and the `donor_water_body_code`, so this table doubles as a graph linking assessed water bodies to their monitored donors — joinable to the fleet's water-body status and monitoring-schedule cells on shared identifiers.

### Cost guidance

One `grouping_provenance_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 status and exemption cells — this cell exposes the PROVENANCE of grouped chemical-status classifications (which donor supports each grouped status, with what confidence), not the status label itself. Its specific job is the **WFD chemical-status grouping provenance**.

### 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. Water-body / donor / cycle 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-chemical-status-grouping-provenance-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-chemical-status-grouping-provenance-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-chemical-status-grouping-provenance-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-chemical-status-grouping-provenance-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/AaScITpvrmGadJTn8/builds/C9S5e3laoBOROVA26/openapi.json