# ETAs and service areas from isochrones

> An ETA is a /route time, with historical speeds for the time of week. A service area is an /isochrone: the area reachable from a store or hub within a time.

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.

## Isochrones (/isochrone) against Valhalla 3.9.1, Berlin

| Set | Requests | Byte-identical |
| --- | --- | --- |
| Isochrones | 45 | 45/45 |

## 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

Two endpoints cover both questions.

- ETA: /route with a date_time, so historical speeds apply (in development).
- Service area: /isochrone with contours such as 15 and 30 minutes, as GeoJSON polygons to draw or test against (in development).
- "Do we deliver here?": geocode the address with geolith Search (live), then test the point against the polygon in your code.

## Sources

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