# Give the route and travel time between two places

> Give the route and travel time between two places: 1 companies fully do it, 13 with a limit, 15 carry the tag. Every listing in Maps, geocoding & places with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/maps.travel-time-route/
- Markdown: https://www.anchorterminal.com/niches/maps.travel-time-route/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/maps.travel-time-route/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/maps.travel-time-route/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 13 | 15 | 12 | 6 |

## What counts as done

Distance, duration and steps for the requested mode, with transit legs naming the line, stops and scheduled times, and driving times reflecting the departure time when one is given; an impossible route says why.

Measured, for our own tests: one call per route and a response within 5 seconds.

How agents ask for it: how long to drive from the lodge to the lake; train from Tokyo to Nagoya tomorrow at 9; walking route to the pub; commute time from this flat to the office

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Woosmap (WOOSMAP SAS)**: /distance/route takes a mode and a departure_time that adds traffic, and /transit/route takes departure_time and transit modes (train, bus, subway, ferry and more) and returns legs.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Amazon Location Service (Amazon Web Services, Inc.)**: CalculateRoutes takes Car, Truck, Scooter, Pedestrian, Transit and Intermodal, with transit coverage published per city. A departure-time field was not shown on the pages read, and transit mode drops the Traffic option.
- **ArcGIS Location Platform (Environmental Systems Research Institute, Inc.)**: /solve takes travelMode and startTime, using historical or live speeds for the time given, but the travel modes are road and walking modes with no public transit routing.
- **Azure Maps (Microsoft Corporation)**: Post Route Directions takes departAt or arriveAt and uses current and typical traffic, for driving, truck and walking only; there is no public transit mode.
- **Geoapify Location Platform + MCP (KEPTAGO LTD)**: Routing covers drive, truck, bus, bicycle and walk modes with steps, but there is no public transit routing and traffic is a free_flow or approximated model with no departure time.
- **Google Maps Platform + Grounding Lite MCP (Google LLC or a regional Google entity, by billing country)**: computeRoutes takes departureTime or arrivalTime and TRANSIT with transitDetails per step, but transit details come back only if the field mask asks, and a first-hand report got No route found for transit in Japan.
- **HERE Location Services (HERE Europe B.V.)**: The docs index describes traffic-aware Routing v8 and a Public Transit API v8 with stations and departure times, but the route and transit references were not read, so departure-time and leg fields are unconfirmed.
- **LocationIQ (Unwired Labs (India) Pvt Ltd)**: /directions supports driving and walking only, with steps, but no transit, no departure time and no traffic input.
- **Mapbox APIs + MCP (Mapbox, Inc.)**: Directions returns distance, duration and steps for driving, driving-traffic, walking and cycling, with depart_at and arrive_by for traffic profiles, but there is no public transit profile.
- **MapQuest (Mapquest Holdings LLC)**: Directions covers routes, narrative, truck routing and date/time routing, but no public transit routing is listed.
- **NextBillion.ai (NextBillion.ai Pte. Ltd.)**: Directions uses live and historical traffic with a departure_time UNIX timestamp, for car, truck, motorcycle, bike and walk, with up to 50 waypoints, but there is no public transit mode.
- **Radar (Radar Labs, Inc.)**: Directions and Distance take car, truck, foot or bike with departureTime, but there is no public transit mode.
- **Stadia Maps (Stadia Maps, Inc.)**: Valhalla routing covers automobile, bus, truck, taxi, motorcycle, bicycle and pedestrian with up to 50 locations, but no public transit routing is listed and departure-time traffic was not confirmed on the pages read.
- **TomTom Maps APIs + MCP (TomTom International BV)**: Routing API calculates routes with traffic, vehicle settings and waypoints, but no public transit routing is offered; a first-hand job-search agent planned TomTom for traffic and a separate service for transit.

- not this job: Geocodio (Dotsquare LLC): Distance endpoints return driving distance and duration or straight-line distance only, with no steps, no transit and no departure time.
- not this job: MapTiler Cloud (MapTiler AG): No routing or directions API in MapTiler Cloud.
- not this job: Nominatim (Nominatim project (osm-search)): Geocoding only; no routing.
- not this job: OpenCage Geocoding API (OpenCage GmbH): No routing; roadinfo annotates the nearest road only.

## What stops agents finishing

- no transit data for the country
- transit details dropped unless the field mask asks for them
- no departure-time or traffic input, so the time is a free-flow guess

## Around it

Before: maps.address-to-coordinates, maps.find-places-nearby. After: scheduling.add-event, travel.plan-itinerary, maps.show-map.

## Where this comes from

Weight 12 of 100 in Maps, geocoding & places: 6 of 53 accounts (transit gaps in Japan and in bus details, MCP schema failure, commute scoring)

As data: https://www.anchorterminal.com/api/v1/use-cases/maps.travel-time-route.json, or the MCP tool get_use_case with id maps.travel-time-route. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
