# EU Air Quality Assessment Regime Records — EEA (`nexgensignal/eu-air-quality-assessment-regime-records`) Actor

Keyless pay-per-record EEA air-quality assessment regimes — zone, pollutant, assessment threshold exceedance band verbatim, monitoring/model coverage counts, as filed. No person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-air-quality-assessment-regime-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 aq assessment regime 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 Air Quality Assessment Regime Records — EEA

**Keyless. Pay per record. The assessment regime for each European air-quality zone — threshold band and monitoring/model coverage.**

This actor turns the **European Environment Agency (EEA) Air Quality e-Reporting dataflows** into clean, per-record data — the pollutant assessment regimes of Europe's official air-quality zones. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per assessment-regime record, structured for air-quality coverage and compliance analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Under the EU Air Quality Directives, each pollutant objective in each zone sits within an assessment regime defined by where the zone falls against the assessment thresholds and how it is monitored. This actor reads that assessment-regimes dataflow and delivers one record per regime: the country and zone, the pollutant, the protection target and objective type, the reporting metric, the ASSESSMENT THRESHOLD EXCEEDANCE band (carried verbatim), and the monitoring/model coverage counts — fixed, fixed-random, and indicative sampling points, points for objective estimation, and number of models. It is the regime-coverage layer of Europe's air-quality assessment.

### Who buys this and for what job

- **Air-quality analysts mapping which zones sit above or below assessment thresholds by pollutant**
- **Regulatory teams auditing monitoring and modelling coverage per zone and objective**
- **Researchers studying assessment-regime structure across Europe**
- **Data engineers** who want the air-quality assessment regimes 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.

### Zone grain — no person data

The unit of every record is a zone-pollutant assessment regime — a coverage 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.

### Sample output

![Sample output — EU Air Quality Assessment Regime Records — EEA](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-air-quality-assessment-regime-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": "ARE.CZ_CZ_ACET_MO_NA_NA_2023:2023",
  "country": "Czechia",
  "country_code": "CZ",
  "reporting_year": 2023,
  "preliminary": "No",
  "assessment_regime_id": "ARE.CZ_CZ_ACET_MO_NA_NA_2023",
  "zone_id": null,
  "classification_year": 2024,
  "air_pollutant": "HC=CH",
  "protection_target": "Not applicable",
  "objective_type": "Monitoring objective (MO)",
  "reporting_metric": "Not applicable",
  "assessment_threshold_exceedance": "Not Applicable",
  "nr_of_fixed_spos": 2,
  "nr_of_fixed_random_spos": 0,
  "nr_of_indicative_spos": 0,
  "nr_of_spos_for_objective_estimation": 0,
  "nr_of_models": 0,
  "source_data_url": "http://cdr.eionet.europa.eu/cz/eu/aqd/c/envzurp9a/CZ_C_2023.xml",
  "source": "EEA Air Quality e-Reporting — assessment regimes",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Air Quality e-Reporting — air-quality assessment regimes. 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), Air Quality e-Reporting (AQ dataflows).",
  "disclaimer": "Air-quality assessment regimes at regime / zone / pollutant grain from the EEA Air Quality e-Reporting dataflows. Each record carries, for a pollutant objective in an official zone, the ASSESSMENT THRESHOLD EXCEEDANCE band (carried VERBATIM), the protection target and objective type, and the monitoring/model coverage counts (fixed, fixed-random, and indicative sampling points, points for objective estimation, and number of models). Zone 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:30Z"
}
```

### Pricing

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

### Output

One JSON object per assessment-regime record. Real example (values as reported):

```json
{
  "record_id": "ARE-BG0001_00001_LV_daysAbove:2014",
  "country": "Bulgaria",
  "country_code": "BG",
  "reporting_year": 2014,
  "assessment_regime_id": "ARE-BG0001_00001_LV_daysAbove",
  "zone_id": "ZON-BG0001",
  "classification_year": 2014,
  "air_pollutant": "SO2",
  "protection_target": "Health",
  "objective_type": "Limit Value (LV)",
  "assessment_threshold_exceedance": "Between Lower and Upper Assessment Threshold",
  "nr_of_fixed_spos": 2,
  "nr_of_models": 0,
  "source": "EEA Air Quality e-Reporting \u2014 assessment regimes",
  "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 assessment regime. Identity: `record_id`, `country`, `country_code`, `reporting_year`, `preliminary`, `assessment_regime_id`, `zone_id`, and `classification_year`. Objective: `air_pollutant`, `protection_target`, `objective_type`, and `reporting_metric`. Regime: `assessment_threshold_exceedance`. Coverage: `nr_of_fixed_spos`, `nr_of_fixed_random_spos`, `nr_of_indicative_spos`, `nr_of_spos_for_objective_estimation`, `nr_of_models`, and `source_data_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 air-quality assessment regimes table (filtered to your optional `countryCode` and optional `year`), 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 **305,678 rows**. Because each record carries the `assessment_regime_id`, `zone_id`, `air_pollutant`, and `assessment_threshold_exceedance`, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

### Working with the data

The regimes are a coverage map, and the fields make them measurable. Because every record carries the `assessment_threshold_exceedance` band alongside the monitoring/model coverage counts, an analyst can see which zones sit above the upper assessment threshold (requiring the most monitoring) and how each is actually covered by fixed points and models. The `reporting_year` and `classification_year` frame each regime in time.

### Identifiers and joins

Every record carries the `assessment_regime_id` and `zone_id`, keying each regime to the assessment-method cell (the specific methods used within the same regime) and, via zone/pollutant, to the station-statistics cell — on shared identifiers.

### Reading the threshold band

The `assessment_threshold_exceedance` band is the heart of each regime: it says whether a zone sits below the lower assessment threshold, between the lower and upper thresholds, or above the upper threshold for a pollutant — and that band drives how much monitoring the directive requires. Carrying it verbatim alongside the fixed, fixed-random, and indicative sampling-point counts and the number of models lets an analyst check, zone by zone, whether the monitoring effort actually matches the regime the zone falls into, and flag zones that appear under-monitored for their threshold band.

### Cost guidance

One `aq_assessment_regime_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).

### A companion to the statistics

The regime table frames every measured statistic: a pollutant level only means something against the threshold band and objective type of the zone it sits in. Joining the assessment regime to the station statistics on zone and pollutant lets an analyst move from a raw concentration to a compliance-relevant reading — is this level below the lower assessment threshold, or is the zone one where the directive expects intensive monitoring — without ever leaving the fleet.

### Honest limitations

- **As reported.** Values, flags, and thresholds are as filed; this actor reformats, it does not audit or recompute.
- **A label, not a verdict.** These are reported statistics/regimes/volumes/loads, 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 **eu-air-quality-assessment-method-records** — that cell resolves the specific METHOD used to assess each objective, while this cell carries the REGIME coverage (threshold band and monitoring/model counts per zone); regime coverage vs method resolution. Its specific job is the **EU air-quality assessment regimes**.

### The NexGen Signal family

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

- [EU Air Quality Assessment Method Records — EEA](https://apify.com/nexgensignal/eu-air-quality-assessment-method-records)
- [EU Air Quality Assessment Regime Records — EEA](https://apify.com/nexgensignal/eu-air-quality-assessment-regime-records)
- [EU Air Quality Measure Records — EEA](https://apify.com/nexgensignal/eu-air-quality-measure-records)
- [EU Air Quality Scenario Records — EEA](https://apify.com/nexgensignal/eu-air-quality-scenario-records)
- [Air Quality Monitor Records](https://apify.com/nexgensignal/air-quality-monitor-records)

*Source: European Environment Agency (EEA), Air Quality e-Reporting dataflows (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. Zone / pollutant / regime grain; thresholds carried verbatim, 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 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-air-quality-assessment-regime-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-air-quality-assessment-regime-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-air-quality-assessment-regime-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-air-quality-assessment-regime-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/ftehWXXR5TdbBsIxW/builds/vBpIrHaFYOC9LHa2P/openapi.json