# Dutch Property Climate Flood and Elevation Risk Screener (`eloquent_mountain/klimaat-risico-nl`) Actor

Screen property ground level relative to NAP, primary flood depth, and soil subsidence via AHN and Klimaateffectatlas.

- **URL**: https://apify.com/eloquent_mountain/klimaat-risico-nl.md
- **Developed by:** [Paco](https://apify.com/eloquent_mountain) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1,760.00 / 1,000 screen property climate, flood, and elevation risk in the netherlands

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Dutch Property Climate Flood and Elevation Risk Screener

Flood depth, flood probability, cloudburst ponding, subsidence and NAP ground level of a Dutch address (AHN, KEA).

### Who it's for

Commercial real estate investors, property developers, logistics operators and insurers who need a first physical climate screening of a Dutch address: ground level, flood exposure, cloudburst ponding and soil subsidence.

### What you get

One screening dossier per address from official Dutch open data:

- **Ground and surface level (AHN)**: ground level (Maaiveld, DTM) and surface or roof level (DSM) relative to NAP. When the address point lies on a building, the ground level comes from the nearest bare ground and the distance is stated.
- **Flood depth (Klimaateffectatlas)**: the highest modelled water depth within 40 m of the address in the extreme flood scenario, covering primary and regional flood defences and outside-dike areas. "None modelled" is stated as such, never as 0 m.
- **Flood probability**: the national location-bound flood probability class (1 to 5, from less than 1 in 30,000 to more than 1 in 30 per year), with its meaning.
- **Cloudburst ponding**: the modelled water depth band (5-10 cm up to more than 30 cm) after 140 mm of rain in 2 hours, an event of about once in 1,000 years in today's climate.
- **Soil subsidence**: projected subsidence by 2050 and 2100 under the KNMI'14 high climate scenario, with a low, moderate or high band.
- **Screening flag** (low, review or high) with the rules that fired, plus the municipality and water board from the BAG address register.

Flood, probability and cloudburst values are read at the address point and 16 points 15 m and 40 m around it, because the address point usually falls on a building where those maps hold no value. Errors are never charged.

### Example

"Check the physical climate and flood risk for a logistics site at Distributieweg 5 in Delfgauw: what is the ground level relative to NAP, the flood depth in the worst case, and the soil subsidence risk?"

### Limits

- Addresses in the European Netherlands that the PDOK Locatieserver can find.
- National models at 0.5 m (AHN), 5 m (flood depth), 2 m (cloudburst) and 100 m (subsidence) resolution: screening indicators for due diligence, not a CSRD, EU Taxonomy or insurance assessment, and no substitute for on-site geotechnical or structural surveys.
- Nothing is stored after the run.

### How to use

- **Run it** in Apify Console or through the API: choose what to do, fill in the fields for that tool and start. The result is one item in the run's dataset.
- **From an AI assistant** through Apify's MCP server (mcp.apify.com), which finds and runs this Actor with the same fields. What each choice does:
  - `screen_climate_risk`: Screen a Dutch address for ground and surface level relative to NAP (AHN), the highest modelled flood depth and flood probability class within 40 m, cloudburst ponding depth and projected soil subsidence (Klimaateffectatlas), with a screening flag and the rules behind it.

### Pricing

- Screen Property Climate, Flood, and Elevation Risk in the Netherlands: $1.76

Failed calls are never charged.

# Actor input Schema

## `tool` (type: `string`):

screen_climate_risk: Screen a Dutch address for ground and surface level relative to NAP (AHN), the highest modelled flood depth and flood probability class within 40 m, cloudburst ponding depth and projected soil subsidence (Klimaateffectatlas), with a screening flag and the rules behind it.

## `address` (type: `string`):

Dutch street address or postal code with house number (e.g.

## Actor input object example

```json
{
  "tool": "screen_climate_risk",
  "address": "Distributieweg 5 Delfgauw"
}
```

# Actor output Schema

## `results` (type: `string`):

The tool result as a dataset item, shown in the overview view.

# 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 = {
    "address": "Distributieweg 5 Delfgauw"
};

// Run the Actor and wait for it to finish
const run = await client.actor("eloquent_mountain/klimaat-risico-nl").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 = { "address": "Distributieweg 5 Delfgauw" }

# Run the Actor and wait for it to finish
run = client.actor("eloquent_mountain/klimaat-risico-nl").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 '{
  "address": "Distributieweg 5 Delfgauw"
}' |
apify call eloquent_mountain/klimaat-risico-nl --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,eloquent_mountain/klimaat-risico-nl"
        }
    }
}
```

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/nEsRVE0PfaGgs65rY/builds/HPwaipsysdkjYp2Zk/openapi.json