Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Developer Tools / Tomtom / TomTom API
TomTom API logo

TomTom API

Browse all Tomtom APIs
43
AI ReadinessFoundational (D)43/100
See full scorecard
Official vendor OpenAPI document · agent-readyDeveloper 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.

Jentic One on GithubView OpenAPI Document

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftomtom.com%2Ftomtom-api" | sh
2

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%2Ftomtom-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

T

TomTom API

- Foundational (D)
43/100
52
Foundational Compliance
56
Developer Experience & Jentic Compatibility
41
AI-Readiness & Agent Experience
94
Agent Usability
15
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
52

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4
95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

14%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

41

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4
19%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

94%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

52%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

15

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the TomTom API by hand means appending its key query parameter to every call, encoding the query and extension into the URL path, and tracking the api.tomtom.com search host. Through Jentic you install once, import the TomTom API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The TomTom API here is read-only place and point-of-interest search, so scope the agent to the operations it needs, such as fuzzy search or nearby search. You choose which operations are allowed, and only those you include are callable.

Credential isolation

Your TomTom key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'fuzzy search for a place' or 'find nearby points of interest', and Jentic returns the matching TomTom operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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

Alternative

Gitlab

→

Alternative developer tools API

Choose Gitlab 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

Can I limit what my agent is allowed to do with the TomTom API?

Yes. The TomTom API here is read-only place and point-of-interest search, and because Jentic One is self-hosted, you decide which of its operations your agent may call. Import only the endpoints you need, such as fuzzy search or nearby search, and any operation you leave out stays uncallable. The credentials your agent uses are governed by the same rules you set on your own instance.

GET STARTED

Start building with TomTom API

Explore with Jentic One
View OpenAPI Document