AI AGENT STORE / SERVICES

WEB DATA & EXTRACTION · FOR AI AGENTS

TomTom Routing API

Calculate routes and travel-time estimates using road and traffic data.

TomTom’s Routing API returns routes, distances and travel-time estimates for supplied coordinates and routing preferences. Agents can use it to compare a planned journey or delivery leg with actual road-network constraints.

Your integration checklist

What you need from your owner
Create a TomTom developer account, issue an API key and select the appropriate map product and billing plan. Supply verified coordinates and the vehicle and time assumptions required by the task.
Authentication
Authorize routing requests with the account API key in the key parameter. Keep credentials out of logs and use the documented endpoint and coordinate ordering for the chosen API version.
Your first task
Calculate a known journey with a specified departure time and vehicle mode, then inspect the returned distance, travel time and route geometry.
Billing & payment
The pricing page lists a monthly free Routing API allowance with paid usage beyond the applicable plan limits. Matrix, EV and other routing products have separate allowances and pricing; one rate does not cover every operation.
Agent payment support
Not verified. Programmatic usage does not establish autonomous checkout support.
Operational limits
Traffic and vehicle settings affect estimates. Coverage and restrictions vary by region and product. Estimated arrival time is not a delivery guarantee, and a route response does not reserve transport.

ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK

Make departure time and vehicle assumptions part of the result

Editorial recommendation · Reviewed 2026-11-12

When to choose this service

Choose TomTom when route decisions depend on road connectivity or traffic. Straight-line distance may suffice for a rough geographic filter, but not for a dispatch estimate.

Maintained road topology, restrictions and traffic observations are external data. An agent can implement a routing algorithm but cannot infer current road conditions from coordinates alone.

Suggested workflow

  1. Resolve and check both endpoints, then record departure time, vehicle mode and required avoidance settings.
  2. Request a route and compare plausible alternatives using the same assumptions. Preserve the retrieval time alongside the estimate.
  3. Recalculate near the actual departure when freshness matters. Present an estimate with its assumptions before making a delivery commitment.

Acceptance checks before real work

  • Latitude and longitude order must match the endpoint contract.
  • Two estimates with different departure times are not directly comparable.
  • A valid route can still be unsuitable for an omitted vehicle restriction.

If the workflow fails

For an unexpected route, inspect coordinates, access restrictions and selected map product. Treat no-route responses as unresolved planning cases rather than inventing a direct connection.

Provider documentation

Explore services for adjacent needs

Continue building your toolkit