TomTom APIs for AI Agents
Maps GeolocationSource ControlPlaces SearchMixed ProvenanceAPI keyAgent Ready
For Agents
APIs4 in catalogue
Endpoints47 indexed
AuthAPI key — 1 credential for all 4 APIs
ProvenanceMixed provenance
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 retrieve map tiles, static images, and copyright information across TomTom's location APIs.
TomTom pairs a global location database for search and geocoding with routing and map-imagery services, so one API-key credential covers the full path from resolving a place to calculating a route to rendering it on a map.
Use for: Location search, geocoding, reverse geocoding, route and reachable-range calculation, and map tile and image retrieval using TomTom location data
Not supported: payments, messaging, crm, real-time traffic streaming, fleet tracking, on-prem deployment
Credentials: All TomTom APIs use the same API key passed as the key query parameter, so one credential covers search, routing, and maps access.
Across 4 TomTom APIs: 3 vendor-official, 1 Jentic-generated, all indexed by Jentic and kept validated and agent-ready.
TomTom provides location APIs covering search and geocoding, route and reachable-range calculation, and map imagery. Across its APIs an agent can resolve addresses and points of interest, convert coordinates to street-level addresses, calculate routes between waypoints, and fetch map tiles, static images, and copyright data, all secured with an API key.
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 |
|---|---|
| Search addresses, POIs, and places, with fuzzy, category, geometry, or along-route queries plus geocoding and reverse geocoding | TomTom Search API |
| General TomTom access spanning search, geocoding, routing, and traffic flow from a single API | TomTom API |
| Calculate a route between waypoints or a reachable range from an origin | Routing |
| Fetch map tiles, static images, or copyright and caption data | Maps |
Install Jentic One Beta
Connect the TomTom APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TomTom APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftomtom.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftomtom.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “geocode an address and calculate a route to it”.
What AI Agents Can Do with TomTom
Each workflow spans multiple TomTom APIs. Jentic routes each operation to the right API automatically.
Resolve a place then route to it
An agent geocodes a user's destination with the Search API to get coordinates, then passes those coordinates to the Routing API to calculate a route and travel time from the origin. This turns an ambiguous address string into a full driving route in one workflow.
Example prompt:
Geocode '4 North 2nd Street, San Jose' via tomtom-search-api, then call calculateRoute on tomtom-routing-api from the user's origin to those coordinates
APIs used
TomTom Search API + Routing
Find POIs along a route and calculate the detour
An agent calculates a route with the Routing API, uses the Search API to find fuel stations or restaurants along that route within a maximum detour time, and returns the reachable stops. This combines route geometry with along-route POI discovery.
Example prompt:
Call calculateRoute on tomtom-routing-api, then pass the route geometry to searchAlongRoute on tomtom-search-api with a 600 second max detour time
APIs used
Routing + TomTom Search API
Search a location and render it on a map
An agent resolves a query to coordinates with the Search API and then fetches a static map image or map tile for those coordinates with the Maps API, producing a visual result for the user. Copyright data can be retrieved alongside the imagery.
Example prompt:
Fuzzy search a place via tomtom-search-api, then request a static image at the returned coordinates from tomtom-maps-api
APIs used
TomTom Search API + Maps
Broad location workflow from one API plus dedicated maps
An agent uses the general TomTom API for combined search, geocoding, and routing, then supplements it with the Maps API to render tiles or static images for the resolved locations. This suits agents that prefer a single search-and-route surface with imagery added on top.
Example prompt:
Run fuzzy search and routing through tomtom-api, then fetch matching map tiles from tomtom-maps-api
APIs used
TomTom API + Maps
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.
Intent-based discovery
Agents search the Jentic directory by intent such as 'geocode an address', 'calculate a route', or 'fetch a static map image', and Jentic returns the matching TomTom operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
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.
Can TomTom render maps, not just data?
Yes. The Maps API returns raster and vector map tiles, static images, and WMS/WMTS layers, along with copyright and caption data. An agent can resolve a location with search and then fetch imagery for it from the Maps API.
Are all four TomTom APIs read-only?
Yes. Search, geocoding, routing, reachable-range, and map retrieval are all read operations, so an agent can be scoped to just the operations it needs without any write access to TomTom data.
If you need a different Maps Geolocation vendor
All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.
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.