# France Fuel Station Prices - roulez-eco, Per Price (`nexgensignal/fr-fuel-station-price-records`) Actor

France fuel prices (roulez-eco) as clean per-record data - one row per station and fuel, with coordinates, price in EUR/litre and update time. 9,802 stations, ~32,500 prices. Licence Ouverte 2.0. $0.05 per record.

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

## Pricing

from $33.50 / 1,000 fuel price 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

## France Fuel Station Prices - roulez-eco, Per Price

France's fuel prices from the official **roulez-eco** instantaneous feed as clean, per-price records - one row
per station and fuel, with the price in euros per litre and the update timestamp, plus the station's location.

### What one record represents

The source is the **roulez-eco** instantaneous open-data feed (`donnees.roulez-eco.fr`), the French government
fuel-price service. The Actor downloads the feed's ZIP, reads its XML, and emits **one record per station x
fuel**: the station id, coordinates, postcode, city, address and location type (road or motorway), then the
fuel name, the price in euros per litre, and the timestamp the price was last updated.

### Coverage and volume

The feed carries **9,802 stations** and about **32,500 individual fuel prices** at fetch time - a live snapshot
that updates continuously.

**Sol's Wave-4 index put this door at 32,568 prices; measured live at build time the feed carries about 32,500
prices across 9,802 stations - the count moves with the live feed, and the live figures are what this listing
quotes.**

### Licence and attribution

The data is published under the **Licence Ouverte 2.0** (Etalab). The full notice travels on every record:

> Prix des carburants (roulez-eco / data.gouv.fr), Licence Ouverte 2.0 (Etalab): free to reproduce, redistribute and adapt, including commercially, provided the source and date are acknowledged.

### Person-data policy

Stations are **business premises** - the feed carries station id, brand-free location and prices, with **no
operator or owner person field**. A per-record assertion rejects any operator/person field as a matter of form.
No natural-person data is processed.

### Interpretation caveat

One record per station x fuel price from the roulez-eco instantaneous feed (9,802 stations, ~32,500 prices): station id, coordinates, postcode, city, address, fuel name, price (EUR/litre) and update timestamp. Stations are business premises; the feed carries no operator-person field.

Values are reproduced verbatim from the feed; the Actor never rewrites a field, except that the source's integer
coordinates are converted to standard decimal degrees (dividing by 100,000) so latitude/longitude are usable
directly. The price is the station's own reported value in euros per litre.

### Provenance and compliance

Every run reads the door host's `robots.txt` at runtime; the gate result (URL, status, byte length and, where a
policy is served, its SHA-256) is written to the run's `RUN_RECEIPT`. Where the host serves no applicable
robots rule, the gate records that (flagged) and proceeds on the licence, which grants re-use. The endpoint is
keyless. The Actor never bypasses a block or fetches through a mirror.

### Data quality and freshness

Boolean columns are delivered as real booleans and numeric columns as real numbers. Delivery is keyed on a
stable id, so the dataset is safe to diff, deduplicate or upsert. Every run re-reads the live door, so the data
is as fresh as the source publishes, and each record's `observed_at` stamp dates the snapshot. The run's
`RUN_RECEIPT` records the source URL and how many records were delivered and charged, and confirms
`charge_equals_delivered`.

### Billing, delivery and joins

Pricing is per record: you are billed only for records the Actor actually delivers, with the charge raised after
each record is pushed (push-then-charge), so a failed or empty run costs nothing. The **Maximum records** cap
bounds every run, so you control spend precisely - sample cheaply, then raise it. Every record is a flat, typed
object keyed on a stable id, so the data loads without a cleaning pass, diffs cleanly between runs, and upserts
into a table you maintain over time; re-running keeps that table current without re-paying for rows you already
hold, and each receipt reconciles delivered against charged. Because the source's own identifiers are preserved
verbatim, the dataset joins cleanly onto other sources keyed on the same identifier.

### Scaling and scheduling

Set **Maximum records** low to sample the shape of the data cheaply, then raise it once the cell fits your use.
The Actor delivers incrementally and streams its source, so memory stays flat regardless of how many records you
request, and you are billed only for what is delivered. Because the source republishes on its own cadence, a
scheduled run keeps a downstream table current: new and changed records upsert over the old ones on the stable
key, and the `observed_at` stamp on every record tells you when each was last seen live. There is no
subscription and no minimum - the per-record price and the record cap together mean the spend on any run is
known in advance and matched exactly to the data you receive.

### Inputs

- **Maximum records** (`maxRecords`) - hard cap on price records delivered and billed.

### Output

Records land in the Actor's default dataset and export as JSON, CSV, Excel or via the Apify API. A tabular
overview surfaces station, city, postcode, fuel name, price and update time.

### Fields in detail

The record leads with `station_id`, `latitude`, `longitude`, `postcode`, `road_type`, `address`, `city`, then
`fuel_name`, `fuel_id`, `price_eur` and `price_updated`. The provenance block closes every record.

### Typical uses

Fuel-price monitoring teams use this cell to track pump prices across France - one row per station and fuel,
with coordinates - ready to map, to compare by region or brand, or to feed a price-comparison model. Because the
price is a real number and coordinates are decimal degrees, a filter surfaces the cheapest diesel in a
department without cleaning, and the station id lets you follow a pump over time by stacking runs. It is one of
four fuel-price cells in this fleet.

### A live snapshot

The roulez-eco feed is instantaneous - it carries the latest price each station has reported, updated
continuously - so a run is a live snapshot rather than a history. To build a price history, schedule runs and
append: each record carries the source's own `price_updated` timestamp and the run's `observed_at`, and the
station-plus-fuel key lets you follow a single pump over time. Because the feed is one compact ZIP, a run is
cheap, and a scheduled run keeps a downstream price table current.

### The four-country fuel family

This cell is one of four fuel-price cells in the fleet, one per country: France here, Spain in the companion
MINCOTUR cell, and Italy in the two MIMIT cells (a price-observation feed and a station registry). Each draws
its own national open-data source at that country's own grain, so the four do not overlap; together they give a
cross-border view of European pump prices. Where the Italian feed splits prices and stations into two cells, the
French feed carries both in one row per station-and-fuel, which is why this cell keeps the station's location on
every price row - a single join is not needed to map a French price. Run the four and align them on your own
schema for a multi-country comparison; because each keeps its source's own station identifiers and fuel names
verbatim, aligning them is a mapping exercise you control - no country's naming is imposed on another - and the
result is a genuine like-for-like European pump-price panel rather than a lossy merge, refreshed as fast as you
schedule each national run.

### Sibling Actors

It sits beside the Spain fuel-station-price cell and the two Italy fuel cells (station registry and price observations) - a four-country fuel-price family. It shares its zip/XML engineering with the fleet's other records Actors.

# Actor input Schema

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

Maximum records delivered and billed. You are billed only for records actually delivered. Raise it to pull the full set.

## Actor input object example

```json
{
  "maxRecords": 500
}
```

# Actor output Schema

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

The delivered France fuel station price record.

# 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 = {
    "maxRecords": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/fr-fuel-station-price-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 = { "maxRecords": 500 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/fr-fuel-station-price-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 '{
  "maxRecords": 500
}' |
apify call nexgensignal/fr-fuel-station-price-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/fr-fuel-station-price-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/lV8tX1wDIgrkT6MRg/builds/6kUXBWQeZmvngxCSq/openapi.json