Tomtom Routing

Name: Routing API
Brand: Routing
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationRouting DirectionsapiKey4 EndpointsREST

For Agents

Programmatically reachable range, reachable range. Covers 4 operations with apiKey authentication.

Use for: I need to reachable range, I want to reachable range, Search for calculate route, Find all calculate route

Install Jentic One Beta

Connect the Routing to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Routing, 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.

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 | sh

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 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 Routing API.

Reachable Range

Calculate Route

Integrate Routing into automated workflows

Query and filter Routing records by parameters

GET STARTED

Start building with Routing API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Routing API for, with concrete tasks.

★ Maps and Geolocation Operations

Use the Routing to perform maps geolocation operations programmatically. The API provides 4 endpoints covering core functionality including reachable range, reachable range, calculate route.

Call POST /routing/{versionNumber}/calculateReachableRange/{origin}/{contentType} to reachable range

Automated Routing Management

Automate routing operations by combining multiple Routing endpoints. Agents can reachable range and then calculate route in a single workflow.

Call GET /routing/{versionNumber}/calculateReachableRange/{origin}/{contentType} to reachable range, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Routing 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 'reachable range', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — routing consists of the following service: <b>calculate route</b> calculates a route between an origin and a destination, passing through waypoints (if specified).

METHOD

PATH

DESCRIPTION

POST

/routing/{versionNumber}/calculateReachableRange/{origin}/{contentType}

Reachable Range

GET

/routing/{versionNumber}/calculateReachableRange/{origin}/{contentType}

Reachable Range

POST

/routing/{versionNumber}/calculateRoute/{locations}/{contentType}

Calculate Route

GET

/routing/{versionNumber}/calculateRoute/{locations}/{contentType}

Calculate Route

POST

/routing/{versionNumber}/calculateReachableRange/{origin}/{contentType}

Reachable Range

GET

/routing/{versionNumber}/calculateReachableRange/{origin}/{contentType}

Reachable Range

POST

/routing/{versionNumber}/calculateRoute/{locations}/{contentType}

Calculate Route

GET

/routing/{versionNumber}/calculateRoute/{locations}/{contentType}

Calculate Route

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Routing 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., 'reachable range') and Jentic returns the matching Routing operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Routing integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Routing API through Jentic.

What authentication does the Routing use?

The Routing 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 reachable range with the Routing?

Yes. Use the POST /routing/{versionNumber}/calculateReachableRange/{origin}/{contentType} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Routing?

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 reachable range through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'reachable range'. Jentic returns the matching Routing operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Routing have?

The Routing exposes 4 endpoints covering routing operations.

Tomtom Routing

Connect the Routing to your agent

Capabilities

Start building with Routing API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs