EN · 中文← all APIs
When an accident, a closure or fresh congestion appears, your vehicle should not stall to recompute the whole route. We absorb the change as a tiny update and hand back the new route in milliseconds, on board, beside your own planner. You keep your map.
A routing companion that runs next to your autonomy stack, it does not replace your perception, control or HD map.
A reported closure, crash or jam becomes a cost change on a handful of road segments. We re-route by updating only those, not the whole map.
Light enough for the vehicle's own compute, so re-routing keeps working with no connection, and your route data never leaves the car.
Bring your own road graph or HD map. We are the speed layer on top of it, not a map-data provider, important for licensing in regulated markets.
Feed events from one vehicle, the cloud or roadside units; re-route every affected vehicle in the fleet at once.
REST over HTTPS, or link the engine as an on-board library. Same endpoints as the live service.
# Plan the route on your road graph POST /v1/route { "from": [-26.10,28.05], "to": [-26.20,27.86] } # An event appears, re-route by sending only what changed POST /v1/reroute { "from": [...], "to": [...], "prev_geometry": [...], "incident_index": 42 } # → returns the new route + the minimal delta (only the changed points)
| Capability | Status | Notes |
|---|---|---|
| Route planning on your graph / HD map | ● Live | Bring your own map; we route on it. |
| Millisecond event re-route (minimal delta) | ● Live | The core advantage for fast vehicles. |
| On-board / edge deployment | ● Live | Runs offline on the vehicle's compute. |
| Live-event & V2X ingestion | ◆ Rolling out | Closures, incidents, congestion as cost updates. |
| Functional-safety integration package | ◆ Partner | Delivered with your safety case (see scope below). |