← REST APIREST endpoint

Directions from A to B, by name.

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 an API keySee the MCP tool
POST /v1/routing/find-and-route
Why you need it

The problem this solves.

Backend code that builds routes from free-text input ends up writing the same orchestration: geocode origin, geocode destination, route between, handle disambiguation. find_and_route is one POST that does all of that, with up to three alternate matches per end so your code can offer choices instead of guessing.

This endpoint bundles Geocoding + Routing in a single call.

What it does for you

What comes back in the response.

  • Origin and destination accept coordinates OR free-text addresses.
  • Single POST replaces 3 to 4 orchestrated calls.
  • Returns the route as a LineString plus the matched origin and destination points with confidence scores.
  • Same terrain analytics as get_directions.
  • Use from any backend stack. Standard HTTP, JSON in, JSON out.
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/find-and-route
curl -X POST https://api.footstep.ai/v1/routing/find-and-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.

geocode

Turn an address, landmark, or place name into coordinates. Returns ranked candidates with confidence scores.

compare_routes

Run multiple travel modes through the same A to B and get a side-by-side comparison plus a natural-language summary.

Ready to call it?

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

Get an API keySee the MCP tool