# Show the area reachable within a time or distance

> Show the area reachable within a time or distance: 5 companies fully do it, 5 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.reachable-area/
- Markdown: https://www.anchorterminal.com/niches/maps.reachable-area/index.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/niches/maps.reachable-area/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/maps.reachable-area/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

Four or more companies' docs show a full fit.

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

## What counts as done

A polygon or set of polygons as GeoJSON for each limit and mode, in one call, that the agent can pass to a point-in-polygon check or a map.

How agents ask for it: where can I live within 30 minutes of the office; what's within a 15 minute walk; delivery zone for 20 minutes' drive

## Does the job

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

- **Azure Maps (Microsoft Corporation)**: Post Route Range returns a polygon of the area reachable within a time or distance budget, with a batch version for up to 100 queries.
- **Geoapify Location Platform + MCP (KEPTAGO LTD)**: Isoline API takes type=time or distance, a range and a routing mode, and returns a GeoJSON FeatureCollection (or 202 with an id to poll).
- **Mapbox APIs + MCP (Mapbox, Inc.)**: Isochrone API returns up to four contours by minutes or metres per profile as GeoJSON polygons or lines in one call.
- **NextBillion.ai (NextBillion.ai Pte. Ltd.)**: Isochrone API takes contours_minutes or contours_meters and a mode and returns contours as polygons or lines in one call.
- **Stadia Maps (Stadia Maps, Inc.)**: Isochrone API takes contours by time or distance per costing model and returns polygons when polygons=true, ready for a map or point-in-polygon check.

## 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.)**: CalculateIsolines takes time or distance ranges, but the pages read did not confirm the geometry comes back as GeoJSON polygons rather than an encoded format.
- **ArcGIS Location Platform (Environmental Systems Research Institute, Inc.)**: solveServiceArea exists, but whether polygons can be returned as GeoJSON was not read.
- **HERE Location Services (HERE Europe B.V.)**: Isoline Routing API v8 exists for time and distance ranges, but its reference was not read, so whether polygons come back as GeoJSON is unconfirmed.
- **TomTom Maps APIs + MCP (TomTom International BV)**: Reachable range is part of the Routing API per the listing, but its reference was not read, so the polygon format (GeoJSON or a list of points) is unconfirmed.
- **Woosmap (WOOSMAP SAS)**: /distance/isochrone exists in GET and POST, but its reference was not read for the polygon format.

- not this job: Geocodio (Dotsquare LLC): No isochrone or reachable-range endpoint.
- not this job: Google Maps Platform + Grounding Lite MCP (Google LLC or a regional Google entity, by billing country): No isochrone or reachable-area endpoint in Routes or elsewhere in the platform docs read.
- not this job: LocationIQ (Unwired Labs (India) Pvt Ltd): No isochrone or isoline endpoint in the spec or docs index.
- not this job: MapQuest (Mapquest Holdings LLC): No isochrone or reachable-range endpoint in the API index.
- not this job: MapTiler Cloud (MapTiler AG): No isochrone API.
- not this job: Nominatim (Nominatim project (osm-search)): No isochrone.
- not this job: OpenCage Geocoding API (OpenCage GmbH): No isochrone.
- not this job: Radar (Radar Labs, Inc.): No isochrone endpoint in the Routing section of the API reference.

## What stops agents finishing

- isochrones offered for driving only
- polygon too coarse to decide an address near the edge

## Around it

Before: maps.address-to-coordinates. After: data.query-table, maps.show-map.

## Where this comes from

Weight 3 of 100 in Maps, geocoding & places: 1 of 53 accounts; vendor pages (Mapbox, Stadia, Geoapify, NextBillion, TomTom reachable range) carry the rest

As data: https://www.anchorterminal.com/api/v1/use-cases/maps.reachable-area.json, or the MCP tool get_use_case with id maps.reachable-area. 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
