# EU Water Use Records — EEA WISE (`nexgensignal/eu-water-use-records`) Actor

Keyless pay-per-record EEA WISE SOE water use volumes — spatial unit, use parameter, reference period and observed volume in million m3, as filed. Basin/country grain, no person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-water-use-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** 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 water use 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 Water Use Records — EEA WISE

**Keyless. Pay per record. How much water Europe uses, by sector, basin and period.**

This actor turns the **European Environment Agency (EEA) WISE State of Environment (SOE) Waterbase** into clean, per-record data — the water USE and abstraction volumes European countries and basins report, split by use type: domestic supply, industry, agriculture, and more. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per observation, structured for water-resource and economic analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Alongside how much renewable water a territory has, the EEA tracks how much it actually uses. This actor reads the Waterbase water-use table and delivers one record per reported observation: the country, the spatial unit (a country or river basin district, with its identifier scheme), the observed USE PARAMETER, the reference period, and the observed VOLUME in million cubic metres — all carried as filed. It is the water-demand layer of Europe's state-of-environment reporting, the companion to the renewable-resource and abstraction cells.

### Who buys this and for what job

- **Water-resource and drought analysts** benchmarking demand against renewable supply by basin.
- **Utilities and agri-economics teams** sizing sectoral water use over time.
- **Climate and sustainability researchers** tracking use intensity across countries.
- **Data engineers** who want the WISE SOE water-use 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 modelled estimate of this actor's making.

### Basin / country grain — no person data

The unit of every record is a water-use observation for a spatial unit — a basin or country and its reported volume, never a person. WISE SOE Waterbase reporting is at spatial-unit level: there is **no contact, operator, or responsible-person field** in the source table, and none is selected or emitted — the query keeps only the spatial-unit identity, the use parameter, the period, and the volume with its status flags. The free-text remarks and metadata-statements fields are **EXCLUDED at field selection**. A person-key guard runs on every record as a backstop.

### A note on scale, honestly

The source table holds **13,153 rows** as verified by an exact `COUNT(*)` at build time, which matches the planning index for this category exactly. It spans reporting countries, spatial units, use parameters, and years. The live count above is authoritative.

### Sample output

![Sample output — EU Water Use Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-water-use-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": "AL:WU_DOM:2016",
  "country_code": "AL",
  "spatial_unit_identifier": "AL",
  "spatial_unit_scheme": "countryCode",
  "observed_property": "WU_DOM",
  "phenomenon_time_period": "2016",
  "phenomenon_year": "2016",
  "phenomenon_month": null,
  "result_observed_volume_hm3": 96.6968,
  "result_observation_status": "A",
  "observation_status": "A",
  "status_code": "stable",
  "source_uid": "11819",
  "source": "EEA WISE State of Environment (SOE) — water use volumes (Waterbase T_WISE3)",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE database under EU environmental reporting. 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 State of Environment (SOE) Waterbase (discodata.eea.europa.eu).",
  "disclaimer": "Water USE and abstraction volumes reported by European countries and basins under the EEA WISE State of Environment Waterbase, at spatial-unit / period / use-type grain. Each record carries the country, the spatial unit (identifier and scheme), the observed USE PARAMETER (e.g. domestic, industrial, agricultural supply), the reference period, and the observed VOLUME in million cubic metres VERBATIM, plus observation status flags. The free-text remarks and metadata-statements fields are EXCLUDED at field selection. Basin/country grain — no contact, operator, or responsible-person field is selected or emitted, and a person-key guard runs on every record.",
  "observed_at": "2026-09-25T17:34:47Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `water_use_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 reference year to filter (e.g. 2016, 2020). |
| `maxRecords` | integer | 10 | Ceiling on records delivered and billed. |

**Default changed on 30 Sep 2026:** if you leave `maxRecords` out, a run now returns up to **10** records (it was 500). Set `maxRecords` yourself to get more — the maximum is unchanged.

### Output

One JSON object per observation. Representative example (values as reported):

```json
{
  "record_id": "AL:WU_DOM:2016",
  "country_code": "AL",
  "spatial_unit_identifier": "AL",
  "spatial_unit_scheme": "countryCode",
  "observed_property": "WU_DOM",
  "phenomenon_time_period": "2016",
  "phenomenon_year": "2016",
  "result_observed_volume_hm3": 320.5,
  "status_code": "experimental",
  "source": "EEA WISE State of Environment (SOE) — water use volumes (Waterbase T_WISE3)",
  "observed_at": "2026-08-30T00: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 water-use observation. Identity: `record_id`, `country_code`, `spatial_unit_identifier`, `spatial_unit_scheme`, and `source_uid`. Observation: `observed_property` (the use parameter), `phenomenon_time_period`, `phenomenon_year`, `phenomenon_month`, and `result_observed_volume_hm3` (million cubic metres). Status: `result_observation_status`, `observation_status`, and `status_code`. 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 SOE water-use table (filtered to your optional `countryCode` and `year`), ordered by the high-cardinality spatial-unit identifier, and flattens each row to one record — carrying every value **verbatim**, never anything person-shaped and never the free-text remarks — 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 **13,153 rows** across reporting countries, spatial units, use parameters, and reference years. Because each record carries the `country_code`, the `spatial_unit_identifier`, the `observed_property`, and the `phenomenon_year`, segmenting by country, basin, use type, or year is straightforward. Pull one country, one use parameter, or the whole table to seed a water-resource warehouse.

### Working with the data

The use volumes are a demand layer, and the fields make them actionable. Because every record pairs a spatial unit with an `observed_property` and a `result_observed_volume_hm3` for a period, an analyst can build a time series of water use by sector and basin, and — joined to the renewable-freshwater and abstraction cells on the spatial unit — compute a use-to-availability ratio to flag stressed basins.

### Cost guidance

One `water_use_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.** Volumes and parameters are as filed by countries for the SOE reporting; this actor reformats, it does not audit or recompute.
- **Experimental status kept verbatim.** Some observations are flagged experimental; the status is carried through as reported.
- **Parameters vary.** The `observed_property` distinguishes domestic, industrial and agricultural use — filter on it for a single sector.
- **Acknowledge the EEA**, and note there is **no person data** of any kind.

### Differentiation

It is the water-DEMAND layer, a distinct source table from the live **eu-water-abstraction-records** (Waterbase T\_WISE3 abstraction) and **eu-renewable-freshwater-resource-records** (the renewable supply). Its specific job is the **WISE SOE water-use volumes**.

### The NexGen Signal family

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

- [EU Water Abstraction Records — EEA](https://apify.com/nexgensignal/eu-water-abstraction-records)
- [EU Renewable Freshwater Resource Records — EEA](https://apify.com/nexgensignal/eu-renewable-freshwater-resource-records)
- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-records)
- [EU Historical Flood Event Records — EEA](https://apify.com/nexgensignal/eu-historical-flood-event-records)
- [EU Protected Site Positive Impact Records — EEA](https://apify.com/nexgensignal/eu-protected-site-positive-impact-records)

*Source: European Environment Agency (EEA), WISE State of Environment (SOE) Waterbase (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. Basin/country grain; the free-text remarks are excluded; no contact, operator, or responsible-person field is selected or emitted, no natural-person data of any kind. Reported values as filed, not a modelled estimate.*

# Actor input Schema

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

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

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

Optional reference year to filter (e.g. 2016, 2020).

## `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-water-use-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-water-use-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-water-use-records --silent --output-dataset

```

## MCP server setup

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