The GraphHopper Directions API is a routing toolkit for moving people and goods. Calculate a route between waypoints for cars, bikes, or on foot with turn-by-turn instructions, compute travel-time and distance matrices between many origins and destinations, and generate isochrones that show how far you can travel in a given time. It also geocodes place names to coordinates and back, matches noisy GPS traces to the road network, and solves vehicle routing problems that assign and sequence stops across a fleet. The vehicle routing solver runs as an asynchronous job you submit and then poll for the solution.
Jentic publishes the only available OpenAPI specification for GraphHopper Directions API, keeping it validated and agent-ready. This spec covers the full Directions API surface - Routing, Route Optimization, Isochrone, Map Matching, Matrix, Geocoding, and Cluster - across 16 endpoints, with both synchronous and async job-style calls. Authentication is a single API key passed as a query parameter, and OpenStreetMap is the default data layer with optional TomTom traffic add-ons available for the Route Optimization API.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgraphhopper.com" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgraphhopper.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.