# Cab dispatch on your own drivers’ speeds

> Dispatch asks which free driver reaches a rider first. /sources-to-targets answers it, with drivers as sources, the rider as the target and live speeds that you supply.

Status: In development, not deployed: there is no routing endpoint to call yet, on geolith.app or api.geolith.app, and no routing plan, price or key.

## Traffic (/route with a date_time) against Valhalla 3.9.1, Berlin

| Set | Requests | Byte-identical |
| --- | --- | --- |
| Historical (predicted) speeds | 50 | 50/50 |
| Live speeds | 30 | 30/30 |
| Closures | 5 | 5/5 |

## Where routing fits

Your pings, your speeds, your router.

- Pings to speeds: map-match each driver’s recent pings and aggregate a speed per road (your code).
- Speeds to router: pass the live speeds and closures to the router you run, beside the .glx file.
- Dispatch: /sources-to-targets from free drivers to the rider, with a date_time so live speeds apply.
- geolith does not collect, share or sell your pings; a hosted live overlay is planned, not built.

## Sources

1. [Routing: traffic and live data](https://docs.geolith.app/routing/traffic), geolith docs (read 2026-11-08)
2. [Routing API (planned)](https://docs.geolith.app/routing/api), geolith docs (read 2026-11-08)

Routing is in development and not deployed; there is no endpoint to call yet, and no routing plan, price or key. Read the routing docs: https://docs.geolith.app/routing