apify-google-maps-directions-apilisted

Get Google Maps directions as structured JSON with the Apify Google Maps Directions API Actor (johnvc/google-maps-directions-api). Give a start and end point as an address, GPS coordinates, or a Google Maps place ID, pick a travel mode (best, driving, cycling, walking, transit, flight, two-wheeler), and get route options back with formatted_distance, formatted_duration, a via summary, turn-by-turn steps, a per-mode durations summary, resolved place coordinates, and a google_maps_directions_url. Use when the user wants a google maps directions api, route data as JSON, distance and ETA between two addresses, turn-by-turn directions inside a script or agent, or directions without a Google Cloud API key. Pay-per-route billing, MCP-ready for Claude and other AI agents.
johnisanerd/claude-skill-google-maps-directions-api · ★ 0 · API & Backend · score 66

Install: claude install-skill johnisanerd/claude-skill-google-maps-directions-api

# Google Maps Directions API: Routes and ETAs as JSON One call takes an origin and a destination and returns every route option Google offers, with distance, travel time, the roads or lines used, and turn-by-turn steps. No Google Cloud project and no API key of your own. ## When to use this skill - The user wants a Google Maps directions API they can call from code or an agent. - They want distance, ETA, or travel time between two addresses as JSON. - They want turn-by-turn steps, a transit itinerary, or a shareable Google Maps link. - They ask how to get directions data without setting up Google Cloud billing. Not for: finding or geocoding the places themselves (use the Google Maps Places API Actor), local business search (use the Google Local API Actor), or multi-stop optimization, which this Actor does not do. ## What you get (one row per route lookup) Top level: `result_type`, `start`, `end`, `travel_mode`, `directions_found`, `directions_count`, `best_duration` ("8 min"), `best_distance` ("1.1 miles"), `google_maps_directions_url`, `gl`, `hl`, `fetched_at`. `places_info`: the resolved origin and destination, each with `address`, `data_id` (place ID), and `gps_coordinates` (`latitude`, `longitude`). `durations`: a compact per-mode summary of the same trip, one entry per mode with `travel_mode`, `duration` (seconds), and `formatted_duration`. A Manhattan test route returned Driving, Transit, Walking, and Cycling in a single lookup. `directions`: one entry per rout