← REST APIREST endpoint

Driving, walking, and cycling directions.

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

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

The problem this solves.

Every dispatch tool, field-service app, and outdoor app needs routing that does more than return a line. get_directions returns the route plus turn-by-turn legs, terrain analytics, and a difficulty classification in one POST. No second call for terrain. No SDK lock-in.

What it does for you

What comes back in the response.

  • Single POST returns distance, duration, turn-by-turn legs, and a terrain block.
  • Driving, walking, cycling, bus, or truck modes.
  • Geometry as encoded polyline (compact) or GeoJSON LineString (renderable).
  • Real road network costing. Not great-circle distance.
  • Call from any backend stack. Standard HTTP, JSON in, JSON out.
Built for
For integratorsFor 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/route
curl -X POST https://api.footstep.ai/v1/routing/route \
  -H "x-api-key: sk_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ ... }'

Related capabilities.

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.

compare_routes

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

search_along_route

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

Ready to call it?

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

Get an API keySee the MCP tool