# Zero-Emission Zone Fleet Plan (`eloquent_mountain/zez-fleet-plan`) Actor Which of your Dutch vans may enter zero-emission zones, until when, and what to replace first, from RDW open data. - **URL**: https://apify.com/eloquent_mountain/zez-fleet-plan.md - **Developed by:** [Paco](https://apify.com/eloquent_mountain) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing $36.00 / 1,000 van assesseds 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 ## Zero-Emission Zone Fleet Plan Which of your Dutch vans may enter zero-emission zones, until when, and what to replace first, from RDW data. ### Who it's for Fleet and operations managers of small and mid-size companies with Dutch vans (installers, wholesalers, couriers) who must decide which vans to replace before the zero-emission zones close to them. ### What you get Give up to 200 licence plates. For every van the plan lists the Euro class, first registration date, APK expiry and whether a recall is open, read from RDW open data. Each van gets a verdict: zero-emission, allowed until a date, or already not allowed. A timeline groups the fleet by the date it may no longer enter, so you see what to replace first. The rules table carries a version, a status (in force or proposed) and a source for every date. Where a proposal would change a date, the van shows the alternative date; proposals are never applied. ### Example (illustrative) 48 van plates: 7 may not enter from 2027-01-01, 31 from 2028-01-01, 10 are electric with no deadline. Each plate line can be checked against the official per-plate check. ### Limits Only vans (category N1) are assessed; trucks, buses and cars are listed as not assessed. One national rule table is applied to every zone and per-zone start dates are not modelled. Municipal exemptions, day permits and local postponements are not checked. Every date in the rules table cites its official source (letter to parliament of 22 June 2026, RDW letter to van owners); the planned extension for Euro 6 vans to 2029 is shown per van but not applied until it is in force. Plates are not stored and no owner data is read. ### How to use - **Run it** in Apify Console or through the API: choose what to do, fill in the fields for that tool and start. The result is one item in the run's dataset. - **From an AI assistant** through Apify's MCP server (mcp.apify.com), which finds and runs this Actor with the same fields. What each choice does: - `zez_rules`: Returns the versioned table of zero-emission zone rules for vans (category N1) that plan_fleet applies: cutoff dates, in_force or proposed status, source and source kind, plus what is not checked. - `plan_fleet`: For Dutch van licence plates, reads RDW open data and returns per vehicle the Euro class, first registration date, APK expiry and open recall flag, whether it may enter the zero-emission zones and from which date it may not, and a timeline of replacement deadlines. ### Pricing - Van assessed: $0.036 Failed calls are never charged. # Actor input Schema ## `tool` (type: `string`): zez_rules: Returns the versioned table of zero-emission zone rules for vans (category N1) that plan_fleet applies: cutoff dates, in_force or proposed status, source and source kind, plus what is not checked. plan_fleet: For Dutch van licence plates, reads RDW open data and returns per vehicle the Euro class, first registration date, APK expiry and open recall flag, whether it may enter the zero-emission zones and from which date it may not, and a timeline of replacement deadlines. ## `plates` (type: `array`): 1-200 Dutch licence plates, dashes optional. Used by: plan_fleet. ## Actor input object example ```json { "tool": "plan_fleet", "plates": [ "VTV69T" ] } ``` # Actor output Schema ## `results` (type: `string`): The tool result as a dataset item, shown in the overview view. # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "plates": [ "VTV69T" ] }; // Run the Actor and wait for it to finish const run = await client.actor("eloquent_mountain/zez-fleet-plan").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "plates": ["VTV69T"] } # Run the Actor and wait for it to finish run = client.actor("eloquent_mountain/zez-fleet-plan").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 '{ "plates": [ "VTV69T" ] }' | apify call eloquent_mountain/zez-fleet-plan --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,eloquent_mountain/zez-fleet-plan" } } } ``` 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 ` 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/83bTfO1JwCeFP2P6u/builds/Scq160J5p1lOO5zkG/openapi.json