Orchestrator API
Point nexvia.eu at Google, Mapbox, and the OSRM server you already run. Your own graph is the cheap path — we only orchestrate the hop. Paid vendors join the same contract when you need traffic, maps, or a line drawn in the client app.
Bring your own engine
Give us the URL of the OSRM server you already run. nexvia.eu sends route and matrix there first. That is the cheap way: your graph, your hardware, one small orchestrator fee. Google Maps Platform and Mapbox sit on the same key for the jobs OSRM should not do — traffic, Places, a map in the client, matching the line the driver sees.
Your OSRM host for domestic and bulk routing. Google when the job needs their graph. Mapbox when the app draws the route. One JSON body. One receipt.
Providers we merge
Geocoding, Routes, Places, Dynamic Maps when you need the Google graph.
Directions, Maps SDK loads and matching for the line drawn in the client app.
Port in the OSRM instance you already host. Same /v1/route contract. The engine line stays €0 — you only pay the cheap orchestrator hop.
OSM routing and matrices when you want an open-data engine.
Traffic-aware routing and matrices on the HERE network.
Routing and traffic as another interchangeable backend.
Self-hosted or cloud open engines, same Nexvia request shape.
Bring another key. We add the connector. The client contract stays /v1/route.
How the orchestrator works
Dispatch or the app hits api.nexvia.eu. Same JSON for route, matrix, geocode, match.
provider: auto prefers your OSRM when it can. Pin osrm, google, or mapbox when you want that engine on purpose.
Normalized geometry, duration, distance. The monthly extract lists which provider ran, under the nexvia.eu call.