Official vendor OpenAPI document · agent-readyMediaImage ProcessingapiKey10 EndpointsREST
For Agents
Programmatically copyrights whole world, captions. Covers 10 operations with apiKey authentication.
Use for: I need to copyrights whole world, I want to captions, Search for copyrights bounding box, Find all copyrights tile
Not supported: Does not handle payments, communications, or crm - use for media and content only.
The Maps API web services suite offers the following APIs: - Raster The Maps Raster API renders map data that is divided into gridded sections called tiles. Tiles are square images (png or jpg format) in various sizes which are available at 19 different zoom levels, ranging from 0 to 20. For zoom level 0, the entire earth is displayed on one single tile, while at zoom level 20, the world is divide. The API exposes 10 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Maps to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Maps, 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%2Fmaps" | 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%2Fmaps" | 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 Maps API.
Copyrights whole world
Captions
Static Image
Tile
Monitor Maps operational status and events
Use Cases
Patterns agents use Maps API for, with concrete tasks.
★ Media and Content Operations
Use the Maps to perform media operations programmatically. The API provides 10 endpoints covering core functionality including copyrights whole world, captions, copyrights bounding box.
Call GET /map/{versionNumber}/copyrights.{format} to copyrights whole world
Automated Copyrights Management
Automate copyrights operations by combining multiple Maps endpoints. Agents can captions and then copyrights bounding box in a single workflow.
Call GET /map/{versionNumber}/copyrights/caption.{format} to captions, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Maps 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 'copyrights whole world', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
10 endpoints — the maps api web services suite offers the following apis: - raster the maps raster api renders map data that is divided into gridded sections called tiles.
METHOD
PATH
DESCRIPTION
GET
/map/{versionNumber}/copyrights.{format}
Copyrights whole world
GET
/map/{versionNumber}/copyrights/caption.{format}
Captions
GET
/map/{versionNumber}/copyrights/{minLon}/{minLat}/{maxLon}/{maxLat}.{format}
Copyrights bounding box
GET
/map/{versionNumber}/copyrights/{zoom}/{X}/{Y}.{format}
Copyrights tile
GET
/map/{versionNumber}/staticimage
Static Image
GET
/map/{versionNumber}/tile/{layer}/{style}/{zoom}/{X}/{Y}.pbf
Tile
GET
/map/{versionNumber}/tile/{layer}/{style}/{zoom}/{X}/{Y}.{format}
Tile
GET
/map/{versionNumber}/wms
GetMap
GET
/map/{versionNumber}/copyrights.{format}
Copyrights whole world
GET
/map/{versionNumber}/copyrights/caption.{format}
Captions
GET
/map/{versionNumber}/copyrights/{minLon}/{minLat}/{maxLon}/{maxLat}.{format}
Copyrights bounding box
GET
/map/{versionNumber}/copyrights/{zoom}/{X}/{Y}.{format}
Copyrights tile
GET
/map/{versionNumber}/staticimage
Static Image
GET
/map/{versionNumber}/tile/{layer}/{style}/{zoom}/{X}/{Y}.pbf
Tile
GET
/map/{versionNumber}/tile/{layer}/{style}/{zoom}/{X}/{Y}.{format}
Tile
GET
/map/{versionNumber}/wms
GetMap
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.
M
Maps
- Foundational (D+)48/100
74
Foundational Compliance75
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability15
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-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).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
75
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
25%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
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.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
60%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
80%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
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.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring TomTom Maps by hand means appending its key query parameter to every call, encoding tile coordinates and version into the URL path, and tracking the api.tomtom.com host. Through Jentic you install once, import Maps from the API Directory, store the key once, and your agent calls it.
Permission scoping
TomTom Maps is read-only tile, static image, and copyright retrieval, so scope the agent to the operations it needs, such as fetching copyrights or a static image. 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 'get map copyrights' or 'fetch a static map image', and Jentic returns the matching Maps 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.
FAQs
Specific to using Maps API through Jentic.
What authentication does the Maps use?
The Maps 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 copyrights whole world with the Maps?
Yes. Use the GET /map/{versionNumber}/copyrights.{format} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Maps?
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 copyrights whole world through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'copyrights whole world'. Jentic returns the matching Maps operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Maps have?
The Maps exposes 10 endpoints covering copyrights, raster, vector operations.
Can I limit what my agent is allowed to do with the TomTom Maps API?
Yes. Because you run Jentic One yourself, your own rules decide which TomTom Maps operations the agent can call and which credentials it may use. The TomTom Maps API is read-only tile, static image, and copyright retrieval, so you can scope the agent to just the operations it needs, such as fetching copyrights or a static image, and leave the rest uncallable. Only the operations you explicitly include are available to the agent.
GET STARTED