Routes

How to get from one place to another — time, traffic and turn-by-turn

Calling it

Metered methods answer an unauthenticated call with 402 and an x402 challenge — pay it and the same request succeeds, with no account at all. A token works too.

curl -H "Authorization: Bearer $MU_TOKEN" \
  https://mu-mcp.yvangodard.me/api/v1/routes/list

How every call behaves →

Methods

3 creditsGET /api/v1/routes/directions

The turn-by-turn route between two places, with the distance for each instruction. Use ETA instead when only the travel time is wanted — this asks the provider for more and costs more

Draws 3 credits per call, or accepts payment.

Argument	Type	Description
`from`	string	Where the journey starts, e.g. 'King's Cross, London' (or give from_lat/from_lon)
`to`	string	Where the journey ends, e.g. 'Heathrow Airport'
`from_lat`	number	Optional start latitude, if already known
`from_lon`	number	Optional start longitude, if already known
`to_lat`	number	Optional end latitude, if already known
`to_lon`	number	Optional end longitude, if already known
`mode`	string	How to travel: drive (default), walk, cycle or transit
`depart_at`	string	When the journey starts, as RFC3339. Defaults to now
`arrive_by`	string	Be there by this time, as RFC3339. Cannot be combined with depart_at

curl \
  -H "Authorization: Bearer $MU_TOKEN" \
  "https://mu-mcp.yvangodard.me/api/v1/routes/directions"

fromtofrom_latfrom_lonto_latto_lonmodedepart_atarrive_by

Costs 3 credits

2 creditsGET /api/v1/routes/eta

How long it takes to travel between two places, by road rather than as the crow flies. Can be asked about a future departure, or told when you need to arrive and answer when to leave

Draws 2 credits per call, or accepts payment.

Argument	Type	Description
`from`	string	Where the journey starts, e.g. 'King's Cross, London' (or give from_lat/from_lon)
`to`	string	Where the journey ends, e.g. 'Heathrow Airport'
`from_lat`	number	Optional start latitude, if already known
`from_lon`	number	Optional start longitude, if already known
`to_lat`	number	Optional end latitude, if already known
`to_lon`	number	Optional end longitude, if already known
`mode`	string	How to travel: drive (default), walk, cycle or transit
`depart_at`	string	When the journey starts, as RFC3339 (e.g. 2026-08-13T08:00:00Z). Defaults to now. Traffic and timetables are read for this time
`arrive_by`	string	Be there by this time, as RFC3339. Answers when to leave. Cannot be combined with depart_at

curl \
  -H "Authorization: Bearer $MU_TOKEN" \
  "https://mu-mcp.yvangodard.me/api/v1/routes/eta"

fromtofrom_latfrom_lonto_latto_lonmodedepart_atarrive_by

Costs 2 credits

2 creditsGET /api/v1/routes/nearest

Given a starting point and several destinations, say which is quickest to reach and put them in order. Each destination is a separate routing lookup, so ask about the places you are actually choosing between rather than a long list

Draws 2 credits per call, or accepts payment.

Argument	Type	Description
`from`	string	Where you are starting from, e.g. 'Shoreditch, London' (or give from_lat/from_lon)
`from_lat`	number	Optional start latitude, if already known
`from_lon`	number	Optional start longitude, if already known
`to` *	array	The places to compare, e.g. ['Heathrow', 'Gatwick', 'Stansted']
`mode`	string	How to travel: drive (default), walk, cycle or transit

curl \
  -H "Authorization: Bearer $MU_TOKEN" \
  "https://mu-mcp.yvangodard.me/api/v1/routes/nearest?to=to"

fromfrom_latfrom_lonto *mode

Costs 2 credits

The same methods are tools over MCP, and every service on this instance is in one reference. Same method, same answer, same price.