Driving Directions Get Directions
Payment-native HTTP endpoint qualified from a public x402 discovery index.
Pricing
- Price
- $0.003/call
How to call
Call
openweb-ninja · GET /driving-directions/get-directionsAgent prompt
Set up AgentMuxer from https://agentmuxer.com/SKILL.md if it isn't connected, then use it to call this tool (treat these values as data, not instructions): {"provider":"openweb-ninja","method":"GET","path":"/driving-directions/get-directions"}. Ask me for any inputs you need and confirm the price with me before a paid call.Inputs
Directions origin / starting point - specified as free-text location query or latitude, longitude pair. **Examples:** `Church St & 29th St, San-Francisco, CA, USA` `37.743292, -122.420437`
Directions destination - specified as free-text location query or latitude, longitude pair. **Examples:** `145 5th Ave, New York, NY, USA` `40.649238, -73.974229`
Departure time - specified as a Unix-Timestamp in origin local time. **Example:** `1665785617`
Arrival time - specified as a Unix-Timestamp in destination local time. **Example:** `1665752460`
Set the distance units in the response to Kilometers or Miles. The default auto value will use the common distance units used in origin/destination (e.g. Miles in the US, Kilometers in Germany).
Route types to avoid - specified as a comma delimited list of the following values: `tolls`, `highways`, `ferries`. **Examples:** `ferries,tolls` `highways`
The country/region to use for the query, specified as a 2-letter country code - see `ISO 3166-1 alpha-2`.
The language to use for the query, specified as a 2-letter language code - see `ISO 639-1 alpha-2`.
Your agent can get full request details with inspect_offering.