← REST APIREST endpoint

Walk, cycle, or drive. Which one fits?

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

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

The problem this solves.

Travel and outdoor apps want to recommend modes, not just pick one. compare_routes runs 2 to 4 modes through the same A to B and returns a comparison block (fastest, shortest, easiest terrain) in one POST instead of three orchestrated calls.

What it does for you

What comes back in the response.

  • 2 to 4 modes per call (driving, walking, cycling).
  • Side-by-side distance, duration, ascent, and difficulty per mode.
  • Each mode comes back as its own LineString with a recommended colour hint.
  • Per-mode terrain block for difficulty surfacing.
  • Standard POST. Use from any backend stack.
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/compare
curl -X POST https://api.footstep.ai/v1/routing/compare \
  -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.

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_elevation

Heights in metres above sea level, with summary statistics for total ascent and descent.

Ready to call it?

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

Get an API keySee the MCP tool