Travel Time
How long to get there, door to door
On it. Running Travel Time now and I'll bring the results straight back here.
Try asking
About
Travel Time tells you exactly how long it will take to get from one place to another — by car, on foot, or by bike — with live or predicted traffic.
Connect a traffic API key and it shows the actual current delay alongside the no-traffic baseline: "28 min without traffic, 41 min with current congestion." Without a key it still works, using road-speed estimates from the OpenStreetMap routing engine. Works anywhere in the world and understands plain addresses, landmarks, city names, UK postcodes, and raw "lat,lon" coordinate pairs.
What you can do
- get_travel_time — get door-to-door journey time with live traffic delay for driving, walking, or cycling
- get_travel_time_batch — score one origin against many destinations in a single call (dispatcher / "who's closest" workflows)
- get_route — get the full route as decoded coordinates, ready to plot on any map
- See the no-traffic baseline vs current traffic side by side
- Plan any future departure — "tomorrow 8:30am", "in 2 weeks", "June 20" — and see the traffic typically expected at that time
- Compare modes by calling it once per mode
Who it's for
Anyone planning a journey and wanting a realistic time — not just the optimistic GPS default. Commuters, meeting schedulers, dispatchers, delivery planners, developers building map-based features, or anyone deciding whether to drive or take a different route.
How to use it
- Call get_travel_time with your origin, destination, and travel mode for a quick journey summary
- Call get_travel_time_batch when you have one origin and several candidate destinations — returns all results in a single response
- Call get_route when you need the actual route geometry — returns all coordinates decoded and ready for Mapbox, Google Maps, Leaflet, or any mapping library
- Optionally pass a departure time — e.g. "tomorrow 8:30am" or "Friday 5pm"
Tips
- Pass coordinates as
"lat,lon"(e.g."51.5074,-0.1278") when you already have them — skips the geocoding step entirely - A returned
duration_minutes: 0is a valid result for same-location requests (origin = destination). Test for success witherror == null, never with the duration value - UK postcodes that have been retired by Royal Mail return a
LOCATION_TERMINATEDerror — ask the user for the current postcode rather than using the historic coordinates
Getting started
Works immediately with no setup. Connect a traffic API key for live traffic data.
Door-to-door journey time and distance between two locations
Compare one origin against many destinations in a single call — for…
Get the full route geometry between two locations as decoded lat/lon…
Door-to-door journey time and distance between two locations. Driving, walking, or cycling anywhere in the world. Accepts addresses, landmarks, UK postcodes, or "lat,lon" pairs (coordinates skip geocoding). duration_minutes of 0 is valid for same-location requests — test success with error == null.
Compare one origin against many destinations in a single call — for dispatcher / "who's closest" workflows. Returns one entry per destination, keyed by a client-supplied `key`. Per-destination failures go in results[].error and do not fail the batch. Up to 50 destinations.
Get the full route geometry between two locations as decoded lat/lon coordinates, plus journey time and distance. Use when you need to plot the route on a map. Driving, walking, or cycling anywhere in the world. Accepts addresses, landmarks, UK postcodes, or "lat,lon" pairs.
- Future departure times now return the traffic you'll actually face at that time, not current traffic — say "tomorrow 8:30am", "next Friday 9am", or "this Saturday 5pm" and get that day's typical congestion
- Plan much further ahead — now accepts "in 2 weeks", "in 1 month", calendar dates like "June 20", and full date-and-time values; longer-range trips use typical day-of-week and time-of-day patterns
- Every result now says whether the time is based on live traffic right now or a prediction for your chosen departure time
- Accept "lat,lon" strings as origin or destination — skips geocoding when you already have coordinates
- UK postcodes resolve via Royal Mail authoritative data — terminated postcodes are now flagged instead of silently routing to historic coordinates
- Added get_travel_time_batch — one origin to many destinations in a single call, with per-destination errors surfaced individually
- Transparent retry on transient upstream failures
- Added get_route skill — returns the full route as decoded coordinates for plotting on a map
- Live traffic via TomTom and HERE APIs — shows real traffic delay vs no-traffic baseline when a key is configured
- Initial release — driving, walking, cycling with time-of-day traffic estimates
Related
