The RouteCalc route-cost API and the MCP server for AI assistants now take everything the web calculator takes: 3.5 t vans, Euro 4, the number of axles, the CO₂ emission class, and on request a price list of every toll bridge, tunnel, mountain pass and ferry on the route. Version 1.1 went live on 2 November 2026.
Nothing changes for integrations that already run. Version 1.1 only adds options. A request written for version 1.0 gets exactly the same answer as before, field for field.
What is new
| Field | New values | What it does |
|---|---|---|
vehicle.truck_type | 3.5t | Goods van up to 3.5 t: no truck distance tolls, the light-vehicle vignettes instead. |
vehicle.euro | euro4 | Euro 4 next to Euro 6, 5 and 3 (and older). |
vehicle.axles | 40 t: 3, 4, 5 · 12 t: 2, 3 · 7.5 t and 3.5 t: 2 | Optional. 5 means 5 or more. Left out: 5 on a 40 t truck, 2 on the others, as before. |
vehicle.co2_class | 1 to 5 | Optional. 5 = zero-emission. Above 1 only with Euro 6. Left out: class 1, as before. |
include | ["crossings"] | Optional. Adds each toll bridge, tunnel, mountain pass and ferry with its own price. |
Why axles and CO₂ class change the price
Germany, Austria, Hungary, Czechia and other countries charge trucks by axles and by CO₂ class. A quote for a 4-axle truck or a low-emission truck priced as a standard 5-axle diesel is simply wrong. Two examples, calculated with the API on 2 November 2026 for a 40 t Euro 6 truck on the fastest route (that country's toll only, excl. VAT):
| Munich → Hamburg (German toll) | Toll |
|---|---|
| 5 or more axles, CO₂ class 1 (the default) | €268.87 |
| 4 axles | €250.30 |
| 3 axles | €234.02 |
| CO₂ class 2 | €262.67 |
| CO₂ class 5, zero-emission | €0.00 |
| Vienna → Linz (Austrian toll) | Toll |
|---|---|
| CO₂ class 1 (the default) | €95.30 |
| CO₂ class 5, zero-emission | €19.82 |
Crossing prices, one by one
With "include": ["crossings"] the answer lists every toll bridge, tunnel, mountain pass and ferry with its price for that vehicle. Copenhagen → Malmö, for example, returns:
"crossings": [
{"type": "toll_crossing", "name": "Oresund Bridge", "country": "SE", "cost_eur": 177.48}
]
These amounts are already inside the totals and the per-country tolls; the list shows where they come from. A ferry on the route whose price is not known is listed with "cost_eur": null, so you can see that a cost is missing instead of not noticing the ferry.
Fast, Economical or Both
fast(default): the quickest truck route.economical: the cheapest route for the whole trip, counting tolls, vignettes and fuel. It may avoid toll roads and take longer.both: both answers in one call, the economical one undereconomical. It uses 2 credits per leg instead of 1.
Your integration keeps working
Nothing to do on your side. Version 1.1 only adds options, and we tested it thoroughly before release: a request written for 1.0 gets the same answer as before.
Example
curl -sS https://app.routecalc.eu/api/v1/routes/calculate \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer rc_yourkey' \
-d '{"origin": "Rotterdam, Netherlands", "destination": "Copenhagen, Denmark",
"vehicle": {"truck_type": "40t", "euro": "euro6", "cargo": "dry",
"axles": 4, "co2_class": 3},
"routing": "both", "include": ["crossings"]}'
AI assistants that support MCP (Claude, Cursor and others) can use the same options. Add the server https://app.routecalc.eu/mcp; its calculate_route tool now lists the new fields itself.
Read more
- API documentation: every field, the response, errors and the changelog
- OpenAPI 3.1 file (version 1.1.0) for code generators
- Your API keys in the app