How do I calculate a route with the GraphHopper Directions API?

Call GET /route with your waypoints and a vehicle profile, or POST /route to send a larger request body. The response includes the path, distance, duration, and turn-by-turn instructions. Through Jentic you search for the intent 'calculate a route' and the agent gets the operation and its input schema.

Is the GraphHopper vehicle routing solver synchronous?

No. POST /vrp submits a vehicle routing problem as a job and returns a job id, then you poll GET /vrp/solution/{jobId} until the optimized plan is ready. This lets the solver work on large fleets and many stops without blocking the request.

Can the GraphHopper Directions API build a travel-time matrix?

Yes. GET /matrix returns travel times and distances between many origins and destinations in one call, and POST /matrix accepts a larger request body. This is the efficient way to compare many point-to-point costs without a route call for each pair.

What are the rate limits for the GraphHopper Directions API?

The OpenAPI spec does not define numeric rate limits; they depend on your GraphHopper plan and its credit allowance. Cache stable results like geocodes and check https://graphhopper.com for current plan limits.

Can I limit what my agent is allowed to do with the GraphHopper Directions API?

Yes. Most operations are read-only, so you allow only the ones a task needs, such as GET /route and GET /geocode, and leave the vehicle routing solver out of the allowed set if the agent should not submit jobs. Through Jentic these rules run on your own instance and every call is logged.

Is there a GraphHopper MCP server?

You don't need a separate MCP server to give your agent the GraphHopper Directions API. Jentic connects it directly from the API Directory: import the API and your agent calculates routes and matrices on demand without loading another server's tool definitions into its context.