openrouteservice
openrouteservice (HeiGIT) routing on OpenStreetMap: geocoding and reverse geocoding, directions with turn-by-turn steps for car, truck, bike, foot and wheelchair, travel time matrices, isochrones (reachable areas), multi-vehicle route optimisation and points of interest. Free API key.
7 giorni gratis · senza carta · hosting UE
Chiedi qualsiasi cosa a openrouteservice
Prova un prompt reale su openrouteservice via AnythingMCP — Claude chiama i tool e risponde. Premi Enter sul tuo messaggio per installare su Cloud.
Installa openrouteservice su CloudClaude è un'AI e può sbagliare. Verifica sempre le risposte.
Setup in 2 minuti
- 1Avvia la trial gratuita su cloud.anythingmcp.com.
- 2Clicca openrouteservice nel connector store. Incolla le credenziali quando richiesto.
- 3Genera una MCP API key e punta il client AI all'URL MCP generato.
Guide per openrouteservice
Setup passo-passo per i principali client AI.
Configurare openrouteservice
Direttamente dalla definizione del connettore: dove trovare le credenziali, quali permessi servono e con quale API parla questo adapter. Fornite in inglese dall'autore del connettore.
openrouteservice
This connector uses openrouteservice by HeiGIT (Heidelberg Institute for Geoinformation Technology), the routing and geocoding service built on OpenStreetMap, at its current address https://api.heigit.org: geocoding and reverse geocoding, routes with turn-by-turn directions for car, truck, bicycle, foot and wheelchair, travel-time matrices, reachability areas (isochrones), route optimisation for several vehicles, and points of interest.
Setup (about 2 minutes)
- Sign up for free at https://account.heigit.org and create an API key (the free plan covers testing and small production use).
- Paste the key into
OPENROUTESERVICE_API_KEY. It is sent as is in theAuthorizationheader (no Bearer). Keys made for the old api.openrouteservice.org work here too; that old address is being shut down in November 2026. - Install and run
openrouteservice_geocodeto check the key.
Coordinates are [longitude, latitude], longitude first, in every routing tool (e.g. [7.8421, 47.9990] for Freiburg). Geocoding results also return coordinates as [longitude, latitude]. Swapping them is the usual cause of "point not found" (error 2010) or of a route in the ocean.
Workflow
- Addresses to points:
openrouteservice_geocode(countrynarrows, e.g.DE),openrouteservice_autocomplete,openrouteservice_reverse_geocode. - Routes:
openrouteservice_directionsreturns distance, duration and steps; setprofile(driving-car,driving-hgvfor trucks,cycling-regular,foot-walking,wheelchair...),languagefor the instructions andoptions.avoid_featuresto avoid highways, tolls or ferries. - Many-to-many:
openrouteservice_matrix(durations in seconds, distances in the chosen unit). - Catchment areas:
openrouteservice_isochroneswithrangein seconds (or metres withrange_typedistance). - Tours for a fleet:
openrouteservice_optimize_routeswith jobs and vehicles (VROOM format; times in seconds since midnight or Unix time). - Places around:
openrouteservice_find_poiswith a point and abufferin metres.
Units: durations are seconds; distances follow units (km by default here). Convert seconds to hours and minutes before quoting.
Limits and errors: the free plan allows about 2,000 directions and 40 per minute, with smaller daily quotas for matrix, isochrones, optimisation and POIs; answers carry x-ratelimit-remaining. 403 means the daily quota is used up (or a wrong key), 429 the per-minute limit, 401 a missing key. Error 2004 means the request exceeds a limit (too many points or too long a route), 2010 a point not near a road.
La tua AI è a due click da openrouteservice.
Installa il connettore, incolla le credenziali, chiedi all'AI. 7 giorni gratis, niente carta.