Graphhopper
for LuumenAI
Routing, geocoding, and fleet optimization from the terminal
Connect GraphHopper and Luumen can answer routing questions while you work. Geocode addresses, compute distance and time matrices, draw isochrones around a site, and check which custom profiles your account has. When a job needs to run — a matrix batch or a vehicle routing optimization — Luumen shows the plan first and submits it after you approve. Authentication is by API key.
The Graphhopper toolbox
13 tools: 11 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadCapacity ClusteringSolve capacity-constrained clustering problems by assigning customers to clusters while minimizing total travel distance.
- ReadGraphHopper GeocodingPerform forward or reverse geocoding.
- ReadGet Cluster SolutionRetrieve the solution of an asynchronous clustering job.
- ReadGet MatrixCompute a distance and/or time matrix using GET request with query parameters.
- ReadGet Matrix SolutionRetrieve the result of an asynchronous matrix computation job.
- ReadGET RouteCalculate the best path connecting two or more points using simple GET request.
- ReadGet IsochroneCompute isochrone polygons for a given point.
- ReadCalculate MatrixCalculate distance, time, or weight matrices via POST.
- ReadGet Custom ProfilesRetrieve all custom routing profiles for your GraphHopper account.
- ReadPOST RouteCalculate complex routes via POST /route.
- ReadMap Match GPX TrackMap-match a GPX track using GraphHopper's Map Matching API.
- WriteSubmit Matrix JobSubmit a matrix computation job for asynchronous processing. Approval by default
- WriteGraphHopper VRP POSTInitiate VRP optimization. Approval by default
One prompt, start to finish
What a governed Graphhopper run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as submit matrix job, graphhopper vrp post. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Graphhopper — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Graphhopper to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.