canonical: https://jentic.com/apis/dati.gov.it/dati-gov

# Dati Open Data Portal - CKAN API

The Open Data Portal CKAN API exposes the catalog behind dati.gov.it, Italy's national open-data portal, through the standard CKAN action endpoints. You list the datasets, groups, organizations, licenses, and tags that classify the catalog, read the full metadata for a single dataset, and run keyword searches across datasets, resources, and tags. It is a discovery layer over published public-sector datasets, returning the metadata and resource links an agent needs to locate open data.

## For AI agents

List and search the datasets, organizations, and tags in Italy's dati.gov.it open-data catalog, and read a dataset's full metadata. Built on the standard CKAN action API.

## Scope

Does not host or transform the datasets themselves, and does not cover non-Italian catalogs. Use for discovering and reading open-data metadata on dati.gov.it only.

## Capabilities

- List every dataset in the Italian national open-data portal
- List current datasets together with their resources
- List the groups, organizations, licenses, and tags that classify the catalog
- Read the full metadata for a single dataset by name or id
- Search datasets, resources, and tags by keyword
- Discover which organizations publish open data and under which licenses

## Use cases

### Agent-Driven Open Data Discovery

An AI agent answers a research question by searching Italy's open-data catalog, ranking the matching datasets, and reading each one's metadata to find downloadable resources. Because the catalog is keyword-searchable, the agent can go from a plain-language topic to a shortlist of datasets and their resource links without a human browsing the portal.

Example prompt: Search the catalog for datasets matching a topic, then read the metadata of the top result and return its resource download links

### Catalog Harvesting

Mirror or index the Italian open-data catalog by listing every dataset, then reading each one's metadata and resources. This feeds a downstream data warehouse or search index that tracks what public-sector data is available and when it changes.

Example prompt: List all packages, then fetch the resources for each so a downstream index can record every available dataset

### Publisher and License Analysis

Analyse which organizations publish the most open data and under which licenses by listing organizations, licenses, and tags, then counting the datasets attached to each. This supports open-data transparency reporting over the national portal.

Example prompt: List all organizations and licenses, then report how many datasets each organization publishes

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/action/package_list` | List all datasets |
| GET | `/action/current_package_list_with_resources` | List datasets with their resources |
| GET | `/action/package_show` | Full metadata for one dataset |
| GET | `/action/package_search` | Search datasets by query |
| GET | `/action/resource_search` | Search resources |
| GET | `/action/organization_list` | List publishing organizations |
| GET | `/action/license_list` | List available licenses |
| GET | `/action/tag_search` | Search catalog tags |

## Key resources

- **Datasets** — Catalog packages, their resources, and full per-dataset metadata
- **Classification** — Groups, organizations, licenses, and tags used to organise the catalog
- **Search** — Keyword search across datasets, resources, and tags

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 45 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 51 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 24 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/dati.gov.it/dati-gov/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** By hand you obtain an API key, set the Authorization header, learn the CKAN action conventions, and page through large result sets yourself. Through Jentic you connect once from the API Directory and your agent calls the catalog actions by intent.
- **Permission scoping:** Every operation is a read-only CKAN action over a public catalog, so you choose exactly which your agent may call, such as dataset search and metadata reads while leaving out bulk listing. Each call is logged for review.
- **Credential handling:** Your API key is stored encrypted on your own Jentic One instance and injected into the Authorization header at execution time, never placed in the agent's prompt, logs, or context. You rotate it in one place.
- **Discovery method:** Agents search Jentic by intent such as 'search datasets by keyword' or 'list organizations', and Jentic returns the matching CKAN action with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Opendatasoft** — A commercial open-data platform exposing datasets through its own catalog API.
- **Data.gov** — The US government open-data catalog, also built on CKAN.
- **OpenCage Geocoding API** — Geocode place names found in a dataset's records into coordinates.

## FAQ

### What authentication does the Dati.gov.it CKAN API use?

The spec declares an apiKey scheme that passes your key in the Authorization header, so each request carries that key. When you connect it through Jentic, your own Jentic One instance stores the key encrypted and attaches it to every call for you.

### Can I search the Italian open-data catalog by keyword?

Yes. The CKAN package search endpoint takes a query and returns the matching datasets with their metadata, and separate endpoints search resources and tags. You can also list every dataset outright and read a single dataset's full metadata by its name or id.

### What are the rate limits for the Dati.gov.it CKAN API?

The OpenAPI spec does not specify rate limits. Check the official dati.gov.it documentation at https://www.dati.gov.it/ for current usage guidance before running large catalog harvests.

### How do I query Italian open data through Jentic?

Add the Dati.gov.it Open Data API from the Jentic API Directory, then have your agent search by intent such as 'search datasets by keyword' and call the matching CKAN action. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit which catalog actions my agent is allowed to call?

Yes. Every operation is a read-only CKAN action, so you grant your agent only the ones it needs, such as dataset search and metadata reads, and leave out the rest. Each call is logged, so you can see exactly which catalog actions the agent used.

### Is there a Dati.gov.it open data MCP server?

You don't need an MCP server to give your agent the Dati.gov.it catalog. Jentic connects it directly from the API Directory: import it and your agent can search datasets and read metadata right away, without another server loading tool definitions into its context.
