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

Keyless pay-per-record EEA air-quality assessment methods — regime-to-method link by zone, pollutant, objective type and assessment type, as filed. Method resolution not regime coverage. No person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-air-quality-assessment-method-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, 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 method 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 Method Records — EEA

**Keyless. Pay per record. How each European air-quality objective is officially assessed — regime, method, zone, and pollutant.**

This actor turns the **European Environment Agency (EEA) Air Quality e-Reporting dataflows** into clean, per-record data — the assessment methods member states officially use to judge each air-quality objective. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per assessment-method record, structured for air-quality methodology and coverage 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 is assessed by a declared method — fixed measurement, modelling, objective estimation, and so on. This actor reads that assessment-regime-methods dataflow and delivers one record per regime / method / zone / pollutant / year: the country, the assessment regime and the assessment METHOD linked to it, the zone, the pollutant, the protection target and objective type, the reporting metric, and the assessment type and description — all carried as filed. It is the method-resolution layer of Europe's air-quality assessment.

### Who buys this and for what job

- **Air-quality methodologists auditing how each objective is assessed across zones and pollutants**
- **Regulatory and consultancy teams tracing the assessment method behind an air-quality classification**
- **Researchers studying the mix of measurement vs modelling in air-quality assessment**
- **Data engineers** who want the air-quality assessment methods 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/method grain — no person data

The unit of every record is a regime-to-method link for a zone and pollutant — a methodology 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.

### Pricing

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

```json
{
  "record_id": "ARE-AT_60_00020_LV_aMean_2016:SPO.06.G10.65764.20.1",
  "country": "Austria",
  "country_code": "AT",
  "reporting_year": 2016,
  "assessment_regime_id": "ARE-AT_60_00020_LV_aMean_2016",
  "assessment_method_id": "SPO.06.G10.65764.20.1",
  "zone_id": "ZON-AT_60",
  "air_pollutant": "C6H6",
  "protection_target": "Health",
  "objective_type": "Limit Value (LV)",
  "assessment_type": "Fixed measurement",
  "source": "EEA Air Quality e-Reporting \u2014 assessment regime methods",
  "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 regime-method link. Identity: `record_id`, `country`, `country_code`, `reporting_year`, `preliminary`, `assessment_regime_id`, `assessment_method_id`, and `zone_id`. Objective: `air_pollutant`, `protection_target`, `objective_type`, and `reporting_metric`. Method: `assessment_type`, `assessment_type_description`, `assessment_method`, 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 methods 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 **802,938 rows**. Because each record carries the `assessment_regime_id`, `assessment_method_id`, `air_pollutant`, and `zone_id`, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

### Working with the data

The methods are an audit layer, and the fields make them traceable. Because every record links an `assessment_regime_id` to an `assessment_method_id` with the `assessment_type` (fixed measurement, modelling, objective estimation), an analyst can see exactly how a pollutant objective is assessed in a given zone, and count the mix of assessment types across zones. The `reporting_year` frames each method in its reporting cycle.

### Identifiers and joins

Every record carries the `assessment_regime_id` and `zone_id`, keying each method to the assessment-regime cell (the thresholds and coverage counts for the same regime) and, via zone/pollutant, to the station-statistics cell — on shared identifiers.

### Measurement versus modelling

A persistent question in air-quality policy is how much of the assessment rests on physical measurement versus modelling and objective estimation. Because every record carries the `assessment_type` and `assessment_method` for a specific regime, zone, and pollutant, this dataset answers that question directly: an analyst can quantify, per country or per pollutant, the share of objectives assessed by fixed measurement against those assessed by model or estimation, and track how that mix shifts across reporting years. Paired with the assessment-regime cell's coverage counts, it gives a complete view of both the method chosen and the monitoring effort behind it.

### Cost guidance

One `aq_assessment_method_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 stable methodological backbone

Because assessment methods change slowly and are reported every year, this dataset also serves as a longitudinal record of methodological continuity: an analyst can see when a zone switched a pollutant from objective estimation to fixed measurement, or introduced modelling, and align those transitions with changes in the reported station statistics. That makes the method table a natural companion to any air-quality trend analysis, where a break in a series is often a change of method rather than a change in the air.

### 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

This is a **net-new** category for the NexGenData fleet. It is distinct from **eu-air-quality-assessment-regime-records** — that cell carries the REGIME coverage (thresholds and monitoring/model counts per zone), while this cell resolves the specific METHOD used to assess each objective; method resolution vs regime coverage. Its specific job is the **EU air-quality assessment methods**.

### 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. Regime / method / zone / pollutant / year 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 year to filter.

## `maxRecords` (type: `integer`):

Maximum records delivered and billed.

## Actor input object example

```json
{
  "maxRecords": 500
}
```

# 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": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-air-quality-assessment-method-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": 500 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-air-quality-assessment-method-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": 500
}' |
apify call nexgensignal/eu-air-quality-assessment-method-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-method-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/Hk65TSDjSwB8mMrt0/builds/mL5oKKWv1uK7yeycU/openapi.json