← REST APIREST endpoint

Find stops along the way.

Coffee, charging, fuel, food. Ranked by how little detour they add to the existing route.

Get an API keySee the MCP tool
POST /v1/routing/search-along-route
Why you need it

The problem this solves.

Corridor search is the right primitive for navigation, delivery, and EV apps. The user's already moving; 'closest' is the wrong heuristic. search_along_route returns candidates ranked by how little they add to the existing route, with detour time, distance, and where along the route they sit.

What it does for you

What comes back in the response.

  • Ranked results sorted by added detour time.
  • Tunable detour budget (max_detour_seconds).
  • Filter by category or specific venue.
  • Returns the route plus the candidates as standard GeoJSON.
  • Standard POST. Best paired with an existing get_directions response.
Built for
For AI developersFor 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/search-along-route
curl -X POST https://api.footstep.ai/v1/routing/search-along-route \
  -H "x-api-key: sk_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ ... }'

Related capabilities.

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.

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.

Ready to call it?

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

Get an API keySee the MCP tool