The fastest order to visit your stops.

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

POST /v1/routing/optimize

Why you need it

The problem this solves.

Field service, delivery, and home healthcare dispatch all hit the same wall: 8 to 30 stops in the wrong order costs time, fuel, and SLA breaches. optimize_stops solves the TSP in milliseconds and returns the full tour breakdown for billing, ETA quotes, and route audit.

What it does for you

What comes back in the response.

Optimised stop order plus the absolute savings versus the input order.
Per-leg distance and duration for the full tour.
Cost surface respects road network and travel mode. Reflects real driving time.
Pair with get_matrix when assigning many drivers to many drops.
Standard POST + JSON. Drops straight into any dispatch backend.

Built for

For integrators For AI developers

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/optimize

curl -X POST https://api.footstep.ai/v1/routing/optimize \
  -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.

find_and_route

Geocode both ends and compute the route in one call. The agent says 'how do I get from Kings Cross to Tower Bridge'. The tool handles the rest.

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 key See the MCP tool