← REST APIREST endpoint

Travel times between every pair.

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

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

The problem this solves.

Logistics dispatch, ambulance assignment, and warehouse planning all need the same primitive: how long from each source to each destination? get_matrix returns the full grid in one call. The basis for the assignment step before optimisation, or for ranking candidates by operational time rather than straight-line distance.

What it does for you

What comes back in the response.

  • N sources × M destinations of travel-time and distance.
  • Driving, walking, or cycling modes.
  • Real road network costing per cell. Not Haversine.
  • Pair with optimize_stops for dispatch; pair with get_isochrone for reach analysis.
  • Standard POST. JSON in, JSON out. Drops into any dispatch backend.
Built for
For public-safety GISFor 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/matrix
curl -X POST https://api.footstep.ai/v1/routing/matrix \
  -H "x-api-key: sk_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ ... }'

Related capabilities.

optimize_stops

Travelling salesman in milliseconds. Returns the optimised order, the savings, and per-leg breakdowns.

get_isochrone

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

get_directions

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

Ready to call it?

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

Get an API keySee the MCP tool