# Italian Procurement Monitor (ANAC, by CPV/CIG) (`chosen_loafer/italian-procurement`) Actor

Monitors Italian public tenders from ANAC's open data (dati.anticorruzione.it), filtered by CPV code or CIG code, with deadline and contracting-authority tracking. No personal data is collected.

- **URL**: https://apify.com/chosen_loafer/italian-procurement.md
- **Developed by:** [Pavel Staurouski](https://apify.com/chosen_loafer) (community)
- **Stats:** 2 total users, 1 monthly users, 91.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 checked tenders

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

## Italian Procurement Monitor (ANAC, by CPV/CIG)

Monitors Italian public tenders from ANAC's (Autorita Nazionale Anticorruzione) open data,
filtered by CPV code, CIG code, or both, with deadline and contracting-authority tracking.

### What you get

One record per matching tender/lot: CIG (Codice Identificativo Gara, Italy's national
tender identifier), title, CPV code and description, contract type (supplies/services/
works), procedure type, status, submission deadline, publication date, the contracting
authority's name and fiscal code, province, and the lot amount in EUR. Nothing about
named individuals.

### Sample output

One real ANAC record (captured during testing), run through this Actor's own field
mapping (amounts in EUR, dates in ISO 8601; this particular tender's deadline has long
since passed, a live run only ever returns tenders inside your own date window):

```json
{
  "cig": "8188396E21",
  "title": "POLIZZA RCT/O",
  "cpvCodes": ["66516000"],
  "cpvDescription": "SERVIZI DI ASSICURAZIONE DI RESPONSABILITA CIVILE",
  "contractType": "SERVIZI",
  "procedureType": "PROCEDURA APERTA",
  "status": "ATTIVO",
  "deadline": "2020-03-12T00:00:00.000Z",
  "publicationDate": "2020-02-12T00:00:00.000Z",
  "contractingAuthority": "PROVINCIA DI LIVORNO",
  "contractingAuthorityTaxId": "80011010495",
  "province": "LIVORNO",
  "amount": 1365000,
  "sourceUrl": "https://dati.anticorruzione.it/opendata/dataset/cig",
  "country": "IT"
}
```

### What it does not do

No contact-person data of any kind. No attached documents, no full notice text. ANAC's
own dataset used here does not carry any personal-name fields at all (checked against a
20,000-record live sample), and personal-data-shaped fields are stripped defensively at
ingestion regardless, before any other processing, in case a future dataset revision adds
one. There is also no stable, verified per-tender public web page to deep-link to (see
"What's not done yet" below); output includes the CIG code so you can look a specific
tender up yourself.

### Why you might need this

Italy publishes well over a million active tenders through ANAC's CIG registry, far more
than ever reach TED (the EU-wide portal), since most Italian public contracts are below
the EU publication threshold. A procurement consultant or sales team watching a specific
CPV category, or tracking a specific known CIG through to its deadline, has no ready-made
feed for this otherwise.

### Input

A list of CPV codes to watch, and/or a list of specific CIG codes to look up directly.

```json
{
  "cpvCodes": ["30000000"],
  "cigCodes": [],
  "publishedFrom": "2026-09-01",
  "publishedTo": "2026-10-07",
  "maxResults": 100,
  "maxChecked": 300
}
```

If both `cpvCodes` and `cigCodes` are given, a record matches if either one matches
(e.g. "any tender under CPV 30000000, OR this specific CIG I'm already tracking").

CPV matching uses hierarchy prefixes: a filter of `30000000` (IT/office equipment,
division 30) matches a tender tagged `30213100` (laptops) and vice versa.

`maxChecked` is a safety cap on how many candidate tender records get read from ANAC's
bulk dataset before giving up, independent of how many match. ANAC's underlying dataset
has well over a million active records; without this cap, a narrow CPV/CIG filter could
read the entire multi-gigabyte file every single run. The default is kept small so a
first run finishes quickly over the residential proxy this Actor uses; raise it if your
filter is narrow and legitimately needs to scan deeper.

### Pricing

Pay per run started, plus per tender record checked against your CPV/CIG filter (not
just per match: checking, not matching, is the real cost driver here, since the dataset
has to be read and parsed regardless of how many records end up matching). See the
Pricing tab for exact rates.

### What's not done yet

This Actor has been built and tested locally (46 automated tests, plus a live run
against production ANAC data) but has not been published. No Apify pricing has been set,
no icon chosen, and it has not been pushed to the Apify platform. Those are the project
owner's call.

***

### Monitor degli appalti pubblici italiani (ANAC, per CPV/CIG)

Monitora gli appalti pubblici italiani a partire dai dati aperti dell'ANAC (Autorita
Nazionale Anticorruzione), filtrati per codice CPV, codice CIG, o entrambi, con
tracciamento della scadenza e della stazione appaltante.

Cosa ottieni: un record per ogni gara/lotto corrispondente, con CIG (Codice
Identificativo Gara), oggetto, codice e descrizione CPV, tipo di contratto (forniture/
servizi/lavori), tipo di procedura, stato, scadenza per la presentazione delle offerte,
data di pubblicazione, denominazione e codice fiscale della stazione appaltante,
provincia e importo del lotto in euro. Nessun dato personale.

Il filtro CPV funziona per gerarchia: un filtro `30000000` (apparecchiature per ufficio e
informatica) corrisponde anche a un appalto con codice `30213100` (computer portatili), e
viceversa. I codici CPV e CIG possono essere usati insieme: un record corrisponde se
soddisfa almeno uno dei due filtri.

Prezzo: una tariffa per ogni esecuzione avviata, piu una tariffa per ogni gara verificata
rispetto al filtro CPV/CIG, non solo per ogni corrispondenza trovata, poiche il dataset
va letto e analizzato comunque, indipendentemente da quante gare risultino corrispondenti.

# Actor input Schema

## `cpvCodes` (type: `array`):

CPV codes to filter by, e.g. \["72000000"]. Matches by hierarchy (a filter like "72000000" also matches "72260000"). Required if cigCodes is empty.

## `cigCodes` (type: `array`):

Specific CIG (Codice Identificativo Gara) codes to look up directly, e.g. \["B890613958"]. OR'd with cpvCodes if both are given. Required if cpvCodes is empty.

## `publishedFrom` (type: `string`):

ISO date (YYYY-MM-DD). Filters on the tender's publication date. Defaults to 30 days ago.

## `publishedTo` (type: `string`):

ISO date (YYYY-MM-DD). Defaults to today.

## `maxResults` (type: `integer`):

Maximum number of matching records to output. Caps buyer-visible output.

## `maxChecked` (type: `integer`):

Maximum number of candidate records read from ANAC's bulk dataset before giving up, independent of how many match. ANAC's "cig" dataset has well over a million active records; without this cap a narrow filter could read the entire file every run. Lower this for a cheaper, faster run; raise it if your filter is narrow and legitimately needs to scan deeper. The default is kept small so a first run (including Apify's own automated platform check) finishes quickly over the residential proxy; raise it for real monitoring use.

## Actor input object example

```json
{
  "cpvCodes": [
    "72000000"
  ],
  "cigCodes": [],
  "maxResults": 100,
  "maxChecked": 300
}
```

# Actor output Schema

## `matchedTenders` (type: `string`):

Per-tender 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 = {
    "cpvCodes": [
        "72000000"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("chosen_loafer/italian-procurement").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 = { "cpvCodes": ["72000000"] }

# Run the Actor and wait for it to finish
run = client.actor("chosen_loafer/italian-procurement").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 '{
  "cpvCodes": [
    "72000000"
  ]
}' |
apify call chosen_loafer/italian-procurement --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,chosen_loafer/italian-procurement"
        }
    }
}
```

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/8o0a2bhB6x8d8505S/builds/c2kXL53mqel9oJ8Ox/openapi.json