# France Tenders Monitor: BOAMP Marchés Publics Alerts (MCP) (`amygraphics/france-tenders-monitor`) Actor

USE THIS ACTOR for French public procurement: official BOAMP / DILA notices (buyer, CPV, departement, deadline, winners) - search keyword+window or monitor keywords with new-tender and new-award alerts. No key. MCP-ready.

- **URL**: https://apify.com/amygraphics/france-tenders-monitor.md
- **Developed by:** [Zakaria el bouami](https://apify.com/amygraphics) (community)
- **Categories:** Lead generation, Automation, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 french tender notice (boamp)s

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

## France Tenders Monitor: BOAMP Marchés Publics Alerts (MCP)

**Use this actor when you need French public procurement notices** — official BOAMP (Bulletin officiel des annonces de marchés publics) open-data feed, keyless, typed, with buyer, CPV code, département, deadlines and **award winners**. Search now, or monitor keywords and get `new-tender` / `new-award` alerts the day a notice publishes. MCP-ready.

### Why French tenders

\~2,000 public buyers publish on BOAMP every week (MAPA, appels d'offres, attributions, concessions). Paid platforms (Marchés Online, AWS-Avis…) repackage exactly this data for €50–500/mo. The DILA publishes it free as open XML — raw, one file per notice, **no search**. This actor adds the missing layer: keyword search + fresh daily alerts, for ~$0.005/notice.

### What you get per row

Official BOAMP **IDWEB**, publication day, family (MAPA/AAPC/FNS/DSP), nature (**APPEL_OFFRE / ATTRIBUTION**), title, **buyer**, city + **département**, contract type (services/travaux/fournitures), **CPV code**, descriptors, **deadline**, duration, estimated/awarded value (EUR), **winner name** on attribution notices, buyer profile URL, official boamp.fr link, and DILA source XML.

### Two modes

#### `search` — query now

```json
{ "mode": "search", "keyword": "informatique", "dateFrom": "2026-10-20", "maxResults": 10 }
```

#### `monitor` — daily new-notice radar

```json
{ "mode": "monitor", "watchQueries": ["sécurité", "bâtiment"] }
```

- Run 1 = **free baseline** (7-day window); later runs emit only `new-tender` / `new-award` rows.
- Silence costs $0.001. Schedule 1/day.

### Recipes

1. **Bid-team Slack feed** — new-tender rows → channel message with buyer + deadline.
2. **Département targeting** — filter `buyerDept` ("75", "69"…) for local-market focus.
3. **Competitor watch** — ATTRIBUTION rows reveal who wins what (`winnerName` + value).
4. **Sales intelligence (agents/MCP)** — "any new IT tenders in France this week?" answered from the official stream.

### Data honesty

Official DILA BOAMP XML files at run time; fields as published. Values may be blank when buyers don't publish them (kept blank, never invented).

### Pricing

| event | price |
|---|---|
| Actor start | $0.001 |
| French tender notice | $0.005 / row |

Typical: 10-notice search ≈ **$0.051** · daily monitor ≈ **$0.001–0.06**.

### MCP / AI-agent usage

```
https://api.apify.com/v2/acts/YOUR_HANDLE~france-tenders-monitor/run-sync-get-dataset-items?token=YOUR_TOKEN
```

# Actor input Schema

## `mode` (type: `string`):

search = query a date window now; monitor = daily new-notice alerts for watchQueries.

## `keyword` (type: `string`):

Words to match (AND) in title/descriptors/buyer/city. French works best: 'informatique', 'sécurité', 'bâtiment'.

## `dateFrom` (type: `string`):

Start of publication window. Default: 7 days back.

## `dateTo` (type: `string`):

End of publication window. Default: today.

## `watchQueries` (type: `array`):

Monitor mode: keywords to watch daily (first run = free baseline, then new-tender/new-award alerts).

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

Cap on notice rows returned (charged per row).

## `maxFilesScan` (type: `integer`):

Safety cap on XML files fetched from the DILA feed (~200/day).

## `requestDelaySecs` (type: `number`):

Politeness delay between DILA requests.

## `parallel` (type: `integer`):

Concurrent XML fetches (DILA feed).

## Actor input object example

```json
{
  "mode": "search",
  "maxResults": 10,
  "maxFilesScan": 1200,
  "requestDelaySecs": 0.03,
  "parallel": 8
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("amygraphics/france-tenders-monitor").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("amygraphics/france-tenders-monitor").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 '{}' |
apify call amygraphics/france-tenders-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,amygraphics/france-tenders-monitor"
        }
    }
}
```

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/v5w9gElbX7fyIEJUf/builds/QnDmnqw1fDqvqZHL7/openapi.json