# EU Habitat Conservation Status Records — EEA BISE (`nexgensignal/eu-habitat-conservation-status-records`) Actor

Per-record EU habitat conservation status by country and biogeographic region (Habitats Directive Art 17) from EEA BISE. Keyless, pay per record, labels verbatim, no person data.

- **URL**: https://apify.com/nexgensignal/eu-habitat-conservation-status-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 habitat conservation status 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 Habitat Conservation Status Records — EEA BISE

**Keyless. Pay per record. The official conservation condition of each protected habitat, by country and biogeographic region — assessment labels verbatim.**

This actor turns the **European Environment Agency (EEA) Biodiversity Information System for Europe (BISE) habitat-conservation-status dataset** into clean, per-record data — the official conservation condition of Europe's protected habitats, country by country and region by region. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per status assessment, structured for conservation-status and biodiversity-reporting analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Under the Habitats Directive Article 17, each member state assesses the conservation status of every habitat type of Union interest in each biogeographic region. The EEA's Biodiversity Information System for Europe (BISE) compiles those assessments. This actor reads the by-member-state table and delivers one record per habitat / country / region: the Natura 2000 habitat code (code_2000), the country, the biogeographic region, the area name, and the assessment CONCLUSION carried verbatim (the label — Favourable, Unfavourable-Inadequate, Unfavourable-Bad, Unknown — and its conclusion code). It is the CONDITION layer of Europe's habitat reporting — how each habitat is doing, where.

### Who buys this and for what job

- **Conservation-status analysts tracking habitat condition by country and biogeographic region**
- **Biodiversity-reporting teams assembling Article 17 status pictures across Europe**
- **Researchers comparing habitat conservation status across regions and member states**
- **Data engineers** who want the BISE habitat-conservation-status 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 and labels as filed — not a compliance verdict.

### Habitat / country / region grain — no person data

The unit of every record is a habitat's conservation-status assessment in one country and region — a condition line, never a person. The habitat is a code, the country and region are place labels; there is no contact, operator, assessor, or responsible-person field in the source, and none is selected or emitted. A person-key guard runs on every record as a backstop.

### Sample output

![Sample output — EU Habitat Conservation Status Records — EEA BISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-habitat-conservation-status-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": "1110:BE:Marine Atlantic",
  "habitat_code_2000": "1110",
  "country_code": "BE",
  "region_name": "Marine Atlantic",
  "area_name_en": "Belgium",
  "assessment_label": "Poor",
  "assessment_conclusion_code": "U1",
  "source": "EEA Biodiversity Information System for Europe (BISE) — habitat conservation status by member state",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Biodiversity Information System for Europe (BISE) — habitat conservation status assessments. 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), Biodiversity Information System for Europe (BISE).",
  "disclaimer": "Official habitat conservation-status (condition) assessments by country and biogeographic region, at habitat / country / region grain from the EEA Biodiversity Information System for Europe (BISE) habitat-conservation-status-by-member-state dataset (Habitats Directive Article 17 reporting). Each record names the Natura 2000 habitat code (code_2000), the country, the biogeographic region, and the assessment CONCLUSION carried VERBATIM (the label such as Favourable / Unfavourable-Inadequate / Unfavourable-Bad and its conclusion code). This is the CONDITION layer — how a habitat is doing — distinct from the conservation MEASURES taken and from where it occurs. There is no contact, operator, assessor, 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:32:53Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `habitat_status_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). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per status assessment. Real example (values as reported):

```json
{
  "record_id": "4060:AT:Alpine",
  "habitat_code_2000": "4060",
  "country_code": "AT",
  "region_name": "Alpine",
  "area_name_en": "Austria",
  "assessment_label": "Good",
  "assessment_conclusion_code": "FV",
  "source": "EEA Biodiversity Information System for Europe (BISE) \u2014 habitat conservation status by member state",
  "source_url": "https://discodata.eea.europa.eu/",
  "observed_at": "2026-08-25T00: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 status assessment. Identity: `record_id` (habitat code : country : region), `habitat_code_2000`, `country_code`, `region_name`, and `area_name_en`. Assessment: `assessment_label` (verbatim) and `assessment_conclusion_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 BISE habitat-conservation-status table (filtered to your optional `countryCode` and your `maxRecords` ceiling), and flattens each row to one record — carrying every value and label **verbatim**, never anything person-shaped — delivered **before** it is charged, so a blocked or empty run costs you nothing. The actor records `charge_equals_delivered` in the receipt.

### Coverage and scope

The table holds on the order of **3,246 rows**. Because each record carries the `habitat_code_2000`, the `country_code`, and the biogeographic region, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

### Working with the data

The assessments are a condition ledger, and the fields make them comparable. Because every record pairs a `habitat_code_2000` with an `assessment_label` in a named `country_code` and `region_name`, an analyst can map which habitats are Favourable versus Unfavourable across a country's biogeographic regions, or track one habitat's status across every member state that reports it. The conclusion code travels alongside the label so the four-way status can be filtered directly. Because the biogeographic region is carried explicitly, the same habitat can be compared where it is doing well against where it is struggling — a distinction the headline country figure hides — and rolling the conclusions up by region or by habitat group produces the exact cross-tabulation that Article 17 status summaries are built on. The whole table is small enough to pull in one bounded run per country, or in full to seed a European habitat-status matrix.

### Identifiers and joins

Every record carries the `habitat_code_2000` and `country_code`, keying each status to the companion conservation-MEASURES cell (what is being done) and the protected-site habitat-inventory cell (where the habitat occurs) — so condition, intervention, and occurrence line up on a shared habitat code.

### Status versus measures versus occurrence

This cell is the CONDITION half of a deliberate pair with the conservation-measures cell: measures say what is being done for a habitat, status says how it is faring. Keeping them separate lets a buyer pay for the layer they need, and joining the two on the habitat code shows whether the measures applied to a habitat track with its reported condition — the core question of Article 17 reporting — without stitching two datasets together by hand.

### Cost guidance

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

### Honest limitations

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

### Differentiation

It is distinct from **eu-habitat-conservation-measure-records** (the interventions taken) and from the protected-site inventory cells (where a habitat occurs) — this cell carries the conservation STATUS (the condition); condition vs interventions vs occurrence. Its specific job is the **BISE habitat conservation status by country and biogeographic region**.

### The NexGen Signal family

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

- [EU Habitat Conservation Status Records — EEA BISE](https://apify.com/nexgensignal/eu-habitat-conservation-status-records)
- [EU Protected Site Negative Impact Records — EEA BISE](https://apify.com/nexgensignal/eu-protected-site-negative-impact-records)
- [EU Species Legal Protection Records — EEA BISE](https://apify.com/nexgensignal/eu-species-legal-protection-records)
- [EU Protected Site Species Inventory Records — EEA BISE](https://apify.com/nexgensignal/eu-protected-site-species-inventory-records)
- [EU Protected Site Habitat Inventory Records — EEA BISE](https://apify.com/nexgensignal/eu-protected-site-habitat-inventory-records)

*Source: European Environment Agency (EEA), Biodiversity Information System for Europe (BISE) (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. Habitat / country / region grain; habitat is a code, country and region are place labels; no contact/operator/assessor/responsible-person field selected or emitted. No natural-person data of any kind. Values and labels as filed, not a compliance verdict.*

# Actor input Schema

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

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

## `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-habitat-conservation-status-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-habitat-conservation-status-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-habitat-conservation-status-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-habitat-conservation-status-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/x9Cp9X7o8LBwlVFai/builds/Ll2ieflCWYjL3yMya/openapi.json