Obtain a complete route polyline from your mapping service (Google, Bing, HERE, Mapbox, or similar); the full encoded polyline is required for accurate toll data.
Authenticate using HTTP Basic Auth with your TollGuru API key as the username.
POST to https://apis.tollguru.com/toll/v2/complete-polyline-from-mapping-service with a JSON body specifying the polyline or shape, the source mapping service name, and vehicle parameters (type, axle count, weight/height for trucks).
Parse the response for per-toll-plaza costs broken down by payment method (transponder, cash, license-plate billing).
Sum returned toll values for the total route cost and surface currency and transponder type to the end user.
Known gotchas
The current endpoint family is /toll/v2/…; any reference to a /v1/calc/route path is outdated and should not be used.
You must supply the *complete* route polyline, not just origin/destination waypoints — partial polylines produce inaccurate toll results.
Vehicle parameters (axle count, weight, height) materially affect returned tolls for trucks; omitting them defaults to a passenger-car profile.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp