TomTom APIs for AI Agents
Maps GeolocationSource ControlPlaces SearchMixed ProvenanceAPI keyAgent Ready
TomTom API Catalog
4 APIs across 3 product groups. All share one credential.
Maps Geolocation2
Which TomTom API should I use?
| I want to... | Use | Why |
|---|---|---|
| Search addresses, POIs, and places, with fuzzy, category, geometry, or along-route queries plus geocoding and reverse geocoding | TomTom Search API | Dedicated search surface with 16 endpoints covering fuzzy search, forward and structured geocoding, reverse geocoding with cross-street lookup, and geometry and along-route filtering |
| General TomTom access spanning search, geocoding, routing, and traffic flow from a single API | TomTom API | Broad 17-endpoint API that bundles fuzzy search, POI and category search, autocomplete, and place lookup alongside geocoding and routing |
| Calculate a route between waypoints or a reachable range from an origin | Routing | Focused routing API for calculateRoute and calculateReachableRange with traffic and avoidance parameters |
| Fetch map tiles, static images, or copyright and caption data | Maps | Maps imagery API for raster and vector tiles, static images, WMS/WMTS, and copyright retrieval |
Install Jentic One Beta
Connect the TomTom APIs to your agent
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring TomTom by hand means appending the key query parameter to every call and tracking the api.tomtom.com host across search, routing, and maps paths. With Jentic One installed you import each TomTom API from the Jentic directory, store the key once, and your agent calls any of them.
Permission scoping
Every TomTom API here is read-only, so you scope the agent to only the operations it needs, such as geocoding an address, calculating a route, or fetching a map tile. Your own rules in your Jentic One instance decide which operations and credentials the agent may use, and only those you include are callable.
Credential isolation
Your single TomTom API key is stored encrypted by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, and the same key covers all four APIs.
FAQs
Specific to using TomTom APIs through Jentic.
What can an AI agent do across TomTom's APIs?
An agent can search for addresses and points of interest, geocode and reverse geocode coordinates, find POIs along a driving route, calculate routes and reachable ranges between locations, and fetch map tiles, static images, and copyright data. Together these APIs cover resolving a place, routing to it, and rendering it on a map.
Do I need separate credentials for each TomTom API?
No. All TomTom APIs use the same API key passed as the key query parameter, so a single credential covers search, geocoding, routing, and maps access.
Which TomTom API should I use for location search?
Use the TomTom Search API for dedicated address, POI, and place search with fuzzy, category, geometry, and along-route queries plus geocoding and reverse geocoding. The general TomTom API also includes search if you want one surface that spans search, geocoding, and routing.
How do the search and routing APIs work together?
The Search API resolves an address or place into coordinates, and the Routing API calculates a route or reachable range from those coordinates. The Search API can also find POIs along a route that the Routing API has calculated, within a maximum detour time.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
