# EU Vehicle CO2 Records — EEA New-Car Monitoring (`nexgensignal/eu-vehicle-co2-records`) Actor

Keyless, pay-per-record EEA new-passenger-car CO2 monitoring. One row per vehicle type — manufacturer, make, commercial name, fuel, WLTP/NEDC CO2, mass, engine. Partition required (year); vehicle grain, no person or VIN data; acknowledge EEA.

- **URL**: https://apify.com/nexgensignal/eu-vehicle-co2-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, Developer tools, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 vehicle 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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## EU Vehicle CO2 Records — EEA New-Car Monitoring

**Keyless. Pay per record. Every new car registered in the EU, with its official CO2 and technical figures.**

This actor turns the **European Environment Agency (EEA)** new-passenger-car CO2 monitoring dataset into clean, per-vehicle records — the official register of new cars registered across the EU under the CO2 monitoring regulation. Each run reads the EEA's keyless DiscoData SQL service for one monitoring year and delivers one row per vehicle-type registration: the manufacturer and make, the commercial name and category, the fuel, the WLTP and NEDC CO2 figures, the mass, and the engine and electric-consumption metrics. Vehicle/manufacturer technical grain, structured for engineering use, reusable with acknowledgement of the EEA, with no registration-holder, owner, personal-name, or VIN field of any kind.

### What this is, in one paragraph

Under EU Regulation (EU) 2019/631, member states report every new passenger car registered, and the EEA aggregates and publishes the monitoring data. This actor reads that dataset and flattens each vehicle-type record into a single analysis-ready row: the harmonised manufacturer and make, the commercial name, the vehicle and registration categories, the fuel type and mode, the specific CO2 emissions under both the WLTP and NEDC test cycles, the mass in running order, the engine capacity and power, the electric energy consumption, and the type-approval identifiers. It is the technical monitoring layer of Europe's vehicle fleet — not a vehicle-registration or owner database. Values are exactly as monitored and published. You are billed only for records actually delivered.

### Who buys this and for what job

- **Automotive-analytics and fleet-intelligence teams** studying CO2 performance, fuel-mix, and technical specifications across makes, models, and countries.
- **ESG, transport-policy, and decarbonization researchers** measuring the emissions profile of new registrations by year and member state.
- **OEM and supplier strategy teams** benchmarking their models' registered CO2 and powertrain metrics against competitors.
- **Data engineers** who want the EEA monitoring dataset as clean rows without writing SQL against the service or paging a hundred-million-row table.

### 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. This rider is carried in this README and on every single record. The data is monitoring data as reported by member states — not a compliance verdict, a recall notice, or a real-world emissions measurement.

### Vehicle/manufacturer grain — no person or VIN data

This actor works at vehicle-type/manufacturer grain: one record per monitored vehicle registration line. The monitoring dataset carries **no** registration-holder, owner, personal-name, or VIN field — it describes vehicle types and their manufacturers, not the people who own them — and this actor emits none. Only manufacturer, make, technical, and emissions columns are selected; a person/VIN-key guard runs on every record as a structural backstop against any future schema drift, and the acceptance suite feeds a deliberately person-and-VIN-shaped row and asserts none of it can ever appear in output.

### A required partition — this is a 100-million-row dataset

The full multi-year monitoring table runs to **over 100 million rows**, so this actor **requires a partition**: every run is bounded to a single `reportingYear` (defaulting to the most recent final monitoring year), and an unbounded pull of the whole table is structurally impossible in code — the year always bounds the query. Optional `countryCode`, `make`, and `fuelType` filters narrow it further, and `maxRecords` is the hard ceiling on delivery. A single country-year is still on the order of a few million rows, so scope and cap deliberately.

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `vehicle_record` | $0.05 | $0.045 | $0.04 | $0.0335 |

Delivered before charged. Blocked runs and empty results cost nothing.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `reportingYear` | integer | 2022 | Monitoring year to pull (required partition; the full multi-year table cannot be pulled unbounded). |
| `countryCode` | string | — | Optional 2-letter member-state code (e.g. DE, FR, IT). |
| `make` | string | — | Optional. Keep only vehicles of this make (e.g. BMW, VOLKSWAGEN). |
| `fuelType` | string | — | Optional. Keep only vehicles of this fuel type (e.g. PETROL, DIESEL, ELECTRIC). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per vehicle-type record. Real example (values as published by the EEA):

```json
{
  "record_id": "79595295",
  "monitoring_year": 2022,
  "country_code": "DE",
  "manufacturer_harmonised": "CHRYSLER",
  "manufacturer_name": "FCA US LLC",
  "make": "JEEP",
  "commercial_name": "RENEGADE",
  "vehicle_category": "M1",
  "fuel_type": "PETROL/ELECTRIC",
  "mass_kg": 1610,
  "co2_wltp_g_km": 44,
  "co2_nedc_g_km": null,
  "engine_capacity_cm3": 1332,
  "engine_power_kw": 140,
  "electric_consumption_wh_km": null,
  "type_approval_number": "e1*2007/46*...",
  "source": "European Environment Agency (EEA) CO2 cars monitoring",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Vehicle/manufacturer technical monitoring records ... no registration-holder ... or VIN ... emitted ...",
  "observed_at": "2026-08-21T00:00:00Z"
}
```

An unbilled `RUN_RECEIPT` records the robots check, the year and filters, rows seen and delivered, and whether charged equals delivered.

### Field reference

Each record is one vehicle-type monitoring row. Identity: `record_id`, `monitoring_year`, and `country_code`. Manufacturer: `manufacturer_harmonised`, `manufacturer_name`, and `make`. Vehicle: `commercial_name`, `vehicle_category`, and `registration_category`. Powertrain: `fuel_type`, `fuel_mode`, `engine_capacity_cm3`, `engine_power_kw`, and `electric_consumption_wh_km`. Emissions and mass: `co2_wltp_g_km`, `co2_nedc_g_km`, `co2_reduction_innovative_g_km`, `innovative_technology`, and `mass_kg`. Type approval: `type_approval_number`, `type`, `variant`, and `version`. Provenance: `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 then queries the CO2 monitoring table through the DiscoData SQL service, bounding the query to your `reportingYear` and pushing your optional country, make, and fuel filters into the WHERE clause so the dataset is bounded server-side, and pages through the results. Each row is flattened to one vehicle record — reading only manufacturer, technical, and emissions fields, never a person or VIN — 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 monitoring dataset holds **over 100 million** vehicle-type registration records across member states and monitoring years — one of the largest official vehicle datasets in Europe. A single year is on the order of ten million rows and a single country-year a few million, so always bound with `reportingYear` (required) and narrow with `countryCode`, `make`, or `fuelType`. Because each record carries the make, commercial name, fuel, and CO2 figures, the data joins cleanly to model catalogues and supports fleet-level CO2 and powertrain analysis.

### Cost guidance

One `vehicle_record` per delivered row: cost = rows delivered × your plan's per-record price. Always scope with `reportingYear` plus `countryCode`, `make`, or `fuelType`, and rely on `maxRecords` as the ceiling. 1,000 vehicles is **$50** (Free) / **$33.50** (Gold). Pulling a whole country-year (millions of rows) is possible but rarely what you want; scope and cap first.

### Honest limitations

- **Monitoring data, not a verdict.** These are CO2 monitoring records as reported by member states — not a compliance judgment, a recall, or a real-world emissions figure.
- **Very large dataset.** Bound it with `reportingYear` and further filters; unbounded pulls are structurally prevented, and even a country-year is millions of rows.
- **As published.** Values are exactly as the EEA distributes them; this actor reformats, it does not recompute.
- **Acknowledge the EEA.** Reuse requires acknowledging the EEA as the source; the acknowledgement travels on every record.
- **No person or VIN data** — the dataset carries none and this actor emits none.

### Differentiation

This is a **net-new** category for the NexGenData fleet — no existing fleet actor covers EU new-car CO2 monitoring at vehicle-type grain. It is distinct from the fleet's facility- and sector-level emissions cells (which carry industrial installations or industry gas accounts, not vehicles) and from any vehicle-recall or VIN cell: this actor is the **EEA new-passenger-car CO2 monitoring register** — make by make, model by model, with the official CO2 and powertrain figures — not a recall feed and not an owner database.

### The NexGen Signal family

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

- [EU Industrial Emissions Records — EEA IED Facilities](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [EU Regulatory Change Records — CELLAR](https://apify.com/nexgensignal/eu-regulatory-change-records)
- [Air Quality Monitor Records — US EPA AQS](https://apify.com/nexgensignal/air-quality-monitor-records)
- [EPA Facility Compliance Records — Envirofacts](https://apify.com/nexgensignal/epa-facility-compliance-records)
- [Organization Sanctions & LEI Risk](https://apify.com/nexgensignal/organization-sanctions-lei-risk)

*Source: European Environment Agency (EEA), CO2 emissions from new passenger cars dataset (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. Vehicle/manufacturer monitoring data, not a compliance verdict. Vehicle-type/manufacturer grain; no registration-holder, owner, personal-name, or VIN field is emitted.*

# Actor input Schema

## `reportingYear` (type: `integer`):

Monitoring year to pull (required partition; defaults to the most recent final year). The full multi-year table cannot be pulled unbounded.

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

Optional 2-letter member-state code (e.g. DE, FR, IT) to bound the query further.

## `make` (type: `string`):

Optional. Keep only vehicles of this make (e.g. BMW, VOLKSWAGEN).

## `fuelType` (type: `string`):

Optional. Keep only vehicles of this fuel type (e.g. PETROL, DIESEL, ELECTRIC).

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

Maximum records delivered and billed. Bounds this very large dataset.

## Actor input object example

```json
{
  "reportingYear": 2022,
  "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 = {
    "reportingYear": 2022,
    "maxRecords": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-vehicle-co2-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 = {
    "reportingYear": 2022,
    "maxRecords": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-vehicle-co2-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 '{
  "reportingYear": 2022,
  "maxRecords": 500
}' |
apify call nexgensignal/eu-vehicle-co2-records --silent --output-dataset

```

## MCP server setup

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