← REST APIREST endpoint

Where can you reach in 30 minutes?

Reachability polygons by time or distance from any starting point. Walking, cycling, or driving.

Get an API keySee the MCP tool
POST /v1/routing/isochrone
Why you need it

The problem this solves.

Reach matters for response staging, retail catchment, real-estate evaluation, and rescue planning. get_isochrone returns the polygon: where can you reach in N minutes, on which mode, given the real road network. Drop the GeoJSON straight into ArcGIS, QGIS, deck.gl, or any GIS without massaging it first.

This endpoint bundles Geocoding + Reach analysis in a single call.

What it does for you

What comes back in the response.

  • One polygon per contour. Multiple contours per call.
  • Walking, cycling, or driving modes.
  • Terrain-aware. Reflects real road reach, not great-circle radius.
  • GeoJSON-shaped response. Drops directly into ArcGIS, QGIS, deck.gl, kepler.gl.
  • Standard POST. Use from any backend.
Built for
For public-safety GISFor SAR teamsFor integrators
Try it

Call it from your backend.

Predictable HTTP. JSON in, JSON out. One auth header. Use it from any backend, edge function, or script.

Read the full reference
POST /v1/routing/isochrone
curl -X POST https://api.footstep.ai/v1/routing/isochrone \
  -H "x-api-key: sk_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ ... }'

Related capabilities.

get_matrix

An N-by-M travel-time matrix between sources and destinations. The basis for assignment, dispatch, and ETA quotes.

get_directions

Point-to-point or multi-stop routes with terrain analytics. Answer 'is this walkable?' without a second call.

search_places

Points of interest near a location, by category or by venue name. Sorted by distance.

Ready to call it?

£5 free credit on signup. One auth header, every major runtime.

Get an API keySee the MCP tool