# Delivery route planning from one routing file

> A delivery run needs the time and distance between every pair of stops (/sources-to-targets) and the driving route for the chosen order (/route). geolith Routing answers both in Valhalla’s bodies.

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.

## Matrix (/sources-to-targets) against Valhalla 3.9.1, Berlin

| Set | Requests | Byte-identical |
| --- | --- | --- |
| Matrices | 60 | 60/60 |

## Route (/route) against Valhalla 3.9.1, Berlin

| Set | Requests | Byte-identical |
| --- | --- | --- |
| Auto | 100 | 100/100 |
| Pedestrian | 30 | 30/30 |
| Bicycle | 30 | 30/30 |

## Where routing fits

Geocode the addresses with geolith Search (live), then route.

- Order intake: /v1/search turns each address into coordinates (geolith Search, live today).
- Planning: /sources-to-targets gives the time matrix between depot and stops (in development).
- Order: your optimizer, or an open-source solver, picks the visiting order from the matrix. geolith does not solve the order.
- Driving: /route returns the route and turn-by-turn maneuvers for that order (in development).

## Questions

### Does geolith optimize the stop order?

No. geolith Routing gives the matrix and the routes; choosing the order is your optimizer’s job.

## Sources

1. [Routing API (planned)](https://docs.geolith.app/routing/api), geolith docs (read 2026-11-08)
2. [Valhalla turn-by-turn API reference](https://valhalla.github.io/valhalla/api/turn-by-turn/api-reference/), Valhalla (open source, MIT) (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