TomTom API
Browse all Tomtom APIs✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey17 EndpointsREST
For Agents
Programmatically fuzzy search, points of interest search. Covers 17 operations with apiKey authentication.
Use for: I need to fuzzy search, I want to points of interest search, Search for category search, Find all nearby search
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
TomTom APIs for search, routing, geocoding, reverse geocoding, and traffic flow data. The API exposes 17 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the TomTom API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TomTom API, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.
Capabilities
What an agent can do with TomTom API.
Fuzzy Search
Points of Interest Search
Category Search
Nearby Search
Geometry Search
Autocomplete
Place by ID
Use Cases
Patterns agents use TomTom API for, with concrete tasks.
★ Developer Tools Operations
Use the TomTom API to perform developer tools operations programmatically. The API provides 17 endpoints covering core functionality including fuzzy search, points of interest search, category search.
Call GET /search/2/search/{query}.{ext} to fuzzy search
Automated Search Management
Automate search operations by combining multiple TomTom API endpoints. Agents can points of interest search and then category search in a single workflow.
Call GET /search/2/poiSearch/{query}.{ext} to points of interest search, then verify the result
AI Agent Integration via Jentic
AI agents discover and call TomTom API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'fuzzy search', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
17 endpoints — tomtom apis for search, routing, geocoding, reverse geocoding, and traffic flow data.
METHOD
PATH
DESCRIPTION
GET
/search/2/search/{query}.{ext}
Fuzzy Search
GET
/search/2/poiSearch/{query}.{ext}
Points of Interest Search
GET
/search/2/categorySearch/{query}.{ext}
Category Search
GET
/search/2/nearbySearch/.{ext}
Nearby Search
GET
/search/2/geometrySearch/{query}.{ext}
Geometry Search
GET
/search/2/autocomplete/{query}.{ext}
Autocomplete
GET
/search/2/place.{ext}
Place by ID
GET
/search/2/poiCategories.{ext}
POI Categories
GET
/search/2/search/{query}.{ext}
Fuzzy Search
GET
/search/2/poiSearch/{query}.{ext}
Points of Interest Search
GET
/search/2/categorySearch/{query}.{ext}
Category Search
GET
/search/2/nearbySearch/.{ext}
Nearby Search
GET
/search/2/geometrySearch/{query}.{ext}
Geometry Search
GET
/search/2/autocomplete/{query}.{ext}
Autocomplete
GET
/search/2/place.{ext}
Place by ID
GET
/search/2/poiCategories.{ext}
POI Categories
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
TomTom API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'fuzzy search') and Jentic returns the matching TomTom API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct TomTom API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using TomTom API through Jentic.
What authentication does the TomTom API use?
The TomTom API uses an API key passed in the `key` query. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I fuzzy search with the TomTom API?
Yes. Use the GET /search/2/search/{query}.{ext} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the TomTom API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I fuzzy search through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'fuzzy search'. Jentic returns the matching TomTom API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the TomTom API have?
The TomTom API exposes 17 endpoints covering search, geocoding, routing operations.
GET STARTED