# EU Open Data Landscape (`alka-labs/eu-open-data-landscape`) Actor

Counts, not records: how many EU open datasets exist per country, theme, format and licence, for any slice you filter. One row per facet value.

- **URL**: https://apify.com/alka-labs/eu-open-data-landscape.md
- **Developed by:** [Igor Lima](https://apify.com/alka-labs) (community)
- **Categories:** Developer tools, AI, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 facet count row returneds

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

## EU Open Data Landscape

**Counts, not records.** How many datasets on [data.europa.eu](https://data.europa.eu) exist
per country, per data theme, per format, per licence — for any slice you filter. One row per
facet value, with the count, its rank inside the facet and its share of the slice.

The search endpoint answers *which datasets*. This Actor answers *how many, and where*, which
is the question you have before you decide what to download. Getting the same answer from a
search endpoint means one request per value you are curious about: forty countries, fourteen
themes, hundreds of formats. The portal computes all of it in a single response.

### What a row looks like

```json
{
  "id": "country:de",
  "facet": "country",
  "facet_title": "Provenance",
  "facet_meaning": "publishing country",
  "value": "de",
  "value_label": "Germany",
  "dataset_count": 31482,
  "share_of_total": 0.336041,
  "rank": 1
}
```

That row came from the live API on 2026-09-17 for `query: "air quality"`, where
`total_matches` was 93,685.

### Input

Every field is optional. With no input you get the default breakdown of the whole portal.

| Field | What it does |
|---|---|
| `query` | full-text filter, same syntax as the portal search |
| `country` | lowercase ISO codes, as the portal spells them: `be`, `de`, `fr` |
| `catalogue` | catalogue ids such as `data-gov-be` — get them from *EU Open Data Catalogue Directory* |
| `categories` | EU data theme codes: `ENVI`, `TECH`, `AGRI`, `SOCI`, `EDUC`, `ECON`, `ENER`, `GOVE`, `HEAL`, `INTR`, `JUST`, `REGI`, `TRAN` |
| `formats` | `CSV`, `JSON`, `XML`, … |
| `licenses` | licence ids as the portal publishes them |
| `breakdown_by` | which facets to break the slice down by. Default: `country`, `categories`, `format`, `license` |
| `min_count` | drop values below this count |
| `max_values_per_facet` | how many values per facet, 1 to 250. Default 25 |
| `language` | which language to collapse multilingual labels to. Default `en` |

The filters narrow the slice **and** the counts: `query: "air quality"` with `country: ["be"]`
returned 1,445 datasets on 2026-09-17, and the `format` breakdown then described those 1,445
and nothing else.

#### The facets you can break down by

`country`, `catalog`, `categories`, `format`, `formatTypes`, `license`, `publisher`,
`keywords`, `subject`, `dataScope`, `is_hvd`, `hvdCategory`, `source_type`, `superCatalog`,
`in_series`, `corporate-body-classification`, `scoring`.

Naming anything else fails the run with the list, instead of quietly returning an empty
breakdown.

### Two things the output says out loud

- **`shares_may_exceed_one`.** A dataset can carry several values of the same facet — two
  formats, three keywords — so the shares inside one facet can add up to more than 1. The
  field is always there so you never have to guess whether your arithmetic is wrong.
- **`facets_absent`.** When the slice has no value at all for a facet you asked for, the
  portal drops that facet from its answer. The name shows up here instead, because an empty
  breakdown is a measurement and should not look like a failure.

### Licensing and attribution

Portal metadata is dedicated to the public domain under CC0 1.0
([legal notice](https://data.europa.eu/en/legal-notice)). The `source` block on every run
carries the terms URL and the notice, so a stored result explains its own licence.

**No personal data.** The upstream records carry contact fields; this Actor never reads them,
and the run fails before writing anything if one shows up in the output.

### Billing

You are charged per row delivered to your dataset. A run that matches nothing delivers no
rows and costs nothing.

# Actor input Schema

## `query` (type: `string`):

Full-text filter. The counts describe the slice this query matches, not the whole portal.

## `breakdown_by` (type: `array`):

Which facets to count. Allowed: country, catalog, categories, format, formatTypes, license, publisher, keywords, subject, dataScope, is\_hvd, hvdCategory, source\_type, superCatalog, in\_series, corporate-body-classification, scoring. Anything else fails the run with the list.

## `country` (type: `array`):

Publishing country, as the portal spells it: lowercase ISO codes such as be, de, fr. Empty means every country.

## `catalogue` (type: `array`):

Catalogue ids such as data-gov-be, govdata, datos-gob-es. Get them from the EU Open Data Catalogue Directory Actor. Empty means every catalogue.

## `categories` (type: `array`):

EU data theme codes: ENVI, TECH, AGRI, SOCI, EDUC, ECON, ENER, GOVE, HEAL, INTR, JUST, REGI, TRAN.

## `formats` (type: `array`):

Distribution formats such as CSV, JSON, XML. Empty means every format.

## `licenses` (type: `array`):

Licence ids as the portal publishes them, such as CC\_BY\_4\_0. Empty means every licence.

## `min_count` (type: `integer`):

Drop facet values with fewer datasets than this. 0 keeps everything the portal returns.

## `max_values_per_facet` (type: `integer`):

How many values to return for each facet, largest first, 1 to 250. The portal itself caps a facet at 250. You are charged per row returned.

## `language` (type: `string`):

Which language to collapse the multilingual facet labels to. Falls back to English, then to whatever the publisher provided.

## Actor input object example

```json
{
  "query": "air quality",
  "breakdown_by": [
    "country",
    "categories",
    "format",
    "license"
  ],
  "country": [],
  "catalogue": [],
  "categories": [],
  "formats": [],
  "licenses": [],
  "min_count": 0,
  "max_values_per_facet": 25,
  "language": "en"
}
```

# Actor output Schema

## `counts` (type: `string`):

One row per facet value: the value, its label, how many datasets carry it, its rank inside the facet and its share of the slice.

## `summary` (type: `string`):

The filters echoed back, how big the slice was, which facets the portal had no value for, and the licence notice. It carries no rows, so a stored result explains itself without being paid for twice.

# 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 = {
    "query": "air quality",
    "breakdown_by": [
        "country",
        "categories",
        "format",
        "license"
    ],
    "country": [],
    "catalogue": [],
    "categories": [],
    "formats": [],
    "licenses": [],
    "min_count": 0,
    "max_values_per_facet": 25,
    "language": "en"
};

// Run the Actor and wait for it to finish
const run = await client.actor("alka-labs/eu-open-data-landscape").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 = {
    "query": "air quality",
    "breakdown_by": [
        "country",
        "categories",
        "format",
        "license",
    ],
    "country": [],
    "catalogue": [],
    "categories": [],
    "formats": [],
    "licenses": [],
    "min_count": 0,
    "max_values_per_facet": 25,
    "language": "en",
}

# Run the Actor and wait for it to finish
run = client.actor("alka-labs/eu-open-data-landscape").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 '{
  "query": "air quality",
  "breakdown_by": [
    "country",
    "categories",
    "format",
    "license"
  ],
  "country": [],
  "catalogue": [],
  "categories": [],
  "formats": [],
  "licenses": [],
  "min_count": 0,
  "max_values_per_facet": 25,
  "language": "en"
}' |
apify call alka-labs/eu-open-data-landscape --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alka-labs/eu-open-data-landscape"
        }
    }
}
```

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/pdlfEhoOd22OtQBIJ/builds/KYI3eRs6GzmbzcEtx/openapi.json