> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to TomTom

The TomTom connector lets your AI agent act in each user's TomTom account. Each user connects their own TomTom API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 19 tools.

**Authentication:** API Key
**Categories:** Search, Analytics
**Tools:** 19: 19 read, 0 write, 0 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=TOMTOM)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the TomTom connection

   In **AgentKit > Connections**, create a TomTom connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'tomtom'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize TomTom:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'tomtom_poi_categories_list',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "tomtom"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize TomTom:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="tomtom_poi_categories_list",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their TomTom credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'tomtom_additional_data_get',
  toolInput: {
    geometries: '<geometries>',
  },
  connector: 'tomtom',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="tomtom_additional_data_get",
    tool_input={
        "geometries": "<geometries>",
    },
    connection_name="tomtom",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `tomtom_additional_data_get`

Get Area Geometry · Read-only

Get the outline geometry (GeoJSON polygons) of geographic areas such as cities or countries, using the geometry IDs returned in search results' dataSources. Returns a GeoJSON geometry per ID. Use this to draw or test against an area's boundary.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `geometries` (`string`, required): Comma-separated geometry IDs from a search result's dataSources.geometry.id (up to 20). Example: 00004631-3400-3c00-0000-0000673c4d2e.
- `geometries_zoom` (`integer`, optional): Zoom level (0 to 22) that sets the geometry precision. One of: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22. Example: 10.

Example input: `{"geometries":"<geometries>"}`

### `tomtom_autocomplete`

Autocomplete Search Query · Read-only

Recognise what a partial search query means: which parts are a brand, a category or plain text, with suggested categories and brands. Returns segments with their type, matched value and IDs. Use this to build search-as-you-type experiences before calling tomtom_category_search or tomtom_poi_search.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `language` (`string`, required): IETF language tag of the query, e.g. en-US. Example: en-US.
- `query` (`string`, required): Partial query typed by the user, e.g. piz. Do not include slashes. Example: pizza.
- `country_set` (`string`, optional): Comma-separated ISO country codes to restrict results to. Example: NL,BE.
- `lat` (`number`, optional): Latitude to bias results to; use with lon. Example: 52.3759.
- `limit` (`integer`, optional): Maximum number of results (default 5, max 10). Example: 5.
- `lon` (`number`, optional): Longitude to bias results to; use with lat. Example: 4.8975.
- `radius` (`integer`, optional): Radius in meters around lat/lon (up to 5000000). Example: 5000.
- `result_set` (`string`, optional): Segment types to return: category, brand or category,brand. Example: category,brand.

Example input: `{"language":"<language>","query":"<query>"}`

### `tomtom_calculate_reachable_range`

Calculate Reachable Range · Read-only

Calculate the area reachable from an origin within a time, distance, fuel or energy budget (an isochrone or isodistance). Returns the center and the boundary polygon points. Use this for coverage or delivery-area questions. Set exactly one budget.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `origin` (`string`, required): Origin as lat,lon, e.g. 52.3759,4.8975. Example: 52.3759,4.8975.
- `avoid` (`string`, optional): Things to avoid: tollRoads, motorways, ferries, unpavedRoads, carpools, alreadyUsedRoads or borderCrossings. Example: tollRoads.
- `depart_at` (`string`, optional): Departure time: now or an ISO 8601 date-time (e.g. 2026-07-01T08:00:00). Cannot be used with arrive_at. Defaults to now. Example: now.
- `energy_budget_ink_wh` (`number`, optional): Energy budget in kWh (electric vehicles). Example: 20.
- `fuel_budget_in_liters` (`number`, optional): Fuel budget in liters (combustion vehicles). Example: 10.
- `hilliness` (`string`, optional): Degree of hilliness for calculating a thrilling route. One of: low, normal, high. Defaults to normal. Example: low. One of: `low`, `normal`, `high`.
- `route_type` (`string`, optional): The type of route requested. One of: fastest, shortest, eco, thrilling. Defaults to fastest. Example: fastest. One of: `fastest`, `shortest`, `eco`, `thrilling`.
- `time_budget_in_sec` (`number`, optional): Time budget in seconds. Example: 1800.
- `traffic` (`boolean`, optional): Set to false to ignore live traffic. Defaults to true. Example: true.
- `travel_mode` (`string`, optional): The mode of travel for the requested route. One of: car, truck, taxi, bus, van, motorcycle, bicycle, pedestrian. Defaults to car. Example: car. One of: `car`, `truck`, `taxi`, `bus`, `van`, `motorcycle`, `bicycle`, `pedestrian`.
- `vehicle_engine_type` (`string`, optional): Engine type of the vehicle. One of: combustion, electric. Defaults to combustion. Example: combustion. One of: `combustion`, `electric`.
- `vehicle_max_speed` (`integer`, optional): Maximum speed of the vehicle in km/hour. Defaults to 0. Example: 90.
- `vehicle_weight` (`integer`, optional): Weight of the vehicle in kilograms. Defaults to 0. Example: 3500.
- `windingness` (`string`, optional): Amount that a thrilling route should wind. One of: low, normal, high. Defaults to normal. Example: low. One of: `low`, `normal`, `high`.

Example input: `{"origin":"<origin>"}`

### `tomtom_calculate_route`

Calculate Route · Read-only

Calculate a route between two or more locations for a car, truck, bike, pedestrian or other travel mode, with live traffic, departure or arrival time, things to avoid and vehicle dimensions. Returns per route the length, travel time, traffic delay, arrival time, legs with points (the polyline), sections and optional turn-by-turn guidance. Use this for directions and ETAs. Use tomtom_matrix_calculate for many origin-destination pairs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `locations` (`string`, required): Colon-separated lat,lon points from origin through waypoints to destination, e.g. 52.3759,4.8975:52.0907,5.1214. Example: 52.3759,4.8975:52.0907,5.1214.
- `arrive_at` (`string`, optional): Arrival time as an ISO 8601 date-time. Cannot be used with depart_at. Example: 2026-07-01T09:00:00.
- `avoid` (`string`, optional): Things to avoid: tollRoads, motorways, ferries, unpavedRoads, carpools, alreadyUsedRoads or borderCrossings. Example: tollRoads.
- `compute_best_order` (`boolean`, optional): Re-order the route waypoints to reduce the route length. Defaults to false. Example: true.
- `compute_travel_time_for` (`string`, optional): Specifies whether to return additional travel times using different types of traffic information (none, historic, live) as well as the default best-estimate travel time. One of: none, all. Example: none. One of: `none`, `all`.
- `depart_at` (`string`, optional): Departure time: now or an ISO 8601 date-time (e.g. 2026-07-01T08:00:00). Cannot be used with arrive_at. Defaults to now. Example: now.
- `hilliness` (`string`, optional): Degree of hilliness for calculating a thrilling route. One of: low, normal, high. Defaults to normal. Example: low. One of: `low`, `normal`, `high`.
- `instructions_type` (`string`, optional): If specified, guidance instructions will be returned (if available). One of: coded, text, tagged. Example: coded. One of: `coded`, `text`, `tagged`.
- `language` (`string`, optional): IETF language tag for the results, e.g. en-US. Defaults to en-GB. Example: en-US.
- `max_alternatives` (`integer`, optional): Number of alternative routes to be calculated. Defaults to 0. Example: 1.
- `route_representation` (`string`, optional): Specifies the representation of the set of routes provided as a response. One of: polyline, none. Defaults to polyline. Example: polyline. One of: `polyline`, `none`.
- `route_type` (`string`, optional): The type of route requested. One of: fastest, shortest, eco, thrilling. Defaults to fastest. Example: fastest. One of: `fastest`, `shortest`, `eco`, `thrilling`.
- `section_type` (`string`, optional): Section types to report, e.g. traffic, toll, tunnel, motorway, pedestrian. Defaults to travelMode. Example: traffic.
- `traffic` (`boolean`, optional): Set to false to ignore live traffic. Defaults to true. Example: true.
- `travel_mode` (`string`, optional): The mode of travel for the requested route. One of: car, truck, taxi, bus, van, motorcycle, bicycle, pedestrian. Defaults to car. Example: car. One of: `car`, `truck`, `taxi`, `bus`, `van`, `motorcycle`, `bicycle`, `pedestrian`.
- `vehicle_axle_weight` (`integer`, optional): Weight per axle of the vehicle in kg. Defaults to 0. Example: 1500.
- `vehicle_commercial` (`boolean`, optional): Indicates that the vehicle is used for commercial purposes. This means it may not be allowed on certain roads. Defaults to false. Example: true.
- `vehicle_engine_type` (`string`, optional): Engine type of the vehicle. One of: combustion, electric. Defaults to combustion. Example: combustion. One of: `combustion`, `electric`.
- `vehicle_height` (`number`, optional): Height of the vehicle in meters. Defaults to 0. Example: 3.1.
- `vehicle_length` (`number`, optional): Length of the vehicle in meters. Defaults to 0. Example: 6.5.
- `vehicle_load_type` (`string`, optional): Indicates what kinds of hazardous materials the vehicle is carrying (if any). This means it may not be allowed on certain roads. Use these for routing in the US: - <i>USHazmatClass1</i> Explosives - <i>USHazmatClass2</i> Compressed gas - <i>USHazmatClass3</i> Flammable liquids - <i>USHazmatClass4</i> Flammable solids - <i>USHazmatClass5</i> Oxidizers - <i>USHazmatClass6</i> Poisons - <i>USHazmatClass7</i> Radioactive - <i>USHazmatClass8</i> Corrosives - <i>USHazmatClass9</i> Miscellaneous Use these for routing in all other countries: - <i>otherHazmatExplosive</i> Explosives - <i>otherHazmatGeneral</i> Miscellaneous - <i>otherHazmatHarmfulToWater</i> Harmful to water vehicleLoadType can be specified multiple times. This parameter is currently only considered for <b>travelMode</b>=<i>truck</i>. Example: otherHazmatGeneral.
- `vehicle_max_speed` (`integer`, optional): Maximum speed of the vehicle in km/hour. Defaults to 0. Example: 90.
- `vehicle_weight` (`integer`, optional): Weight of the vehicle in kilograms. Defaults to 0. Example: 3500.
- `vehicle_width` (`number`, optional): Width of the vehicle in meters. Defaults to 0. Example: 2.2.
- `windingness` (`string`, optional): Amount that a thrilling route should wind. One of: low, normal, high. Defaults to normal. Example: low. One of: `low`, `normal`, `high`.

Example input: `{"locations":"<locations>"}`

### `tomtom_category_search`

Search POIs by Category · Read-only

Search points of interest of a category such as restaurant, parking or petrol station, optionally near a position or in an area. Returns POIs with name, categories, address, position and distance. Use tomtom_poi_categories_list for the category names.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): Category name, e.g. restaurant, parking garage or electric vehicle station. Example: restaurant.
- `btm_right` (`string`, optional): Bottom-right corner of the bounding box, as lat,lon. Example: 52.33,4.95.
- `country_set` (`string`, optional): Comma-separated ISO 3166 country codes to restrict results to. Example: NL,BE.
- `extended_postal_codes_for` (`string`, optional): Indexes for which extended postal codes should be included in the results. Available indexes are: - <b>Addr</b> = Address ranges - <b>Geo</b> = Geographies - <b>PAD</b> = Point Addresses - <b>POI</b> = Points of Interest - <b>Str</b> = Streets - <b>XStr</b> = Cross Streets (intersections). Example: PAD,Addr.
- `language` (`string`, optional): IETF language tag for the results, e.g. en-US. Example: en-US.
- `lat` (`number`, optional): Latitude of the point to bias or center results on, in decimal degrees; use with lon. Example: 52.3759.
- `limit` (`integer`, optional): Maximum number of results to return (up to 100). Defaults to 10. Example: 10.
- `lon` (`number`, optional): Longitude of the point to bias or center results on, in decimal degrees; use with lat. Example: 4.8975.
- `ofs` (`integer`, optional): Offset of the first result, for paging. Defaults to 0. Example: 0.
- `radius` (`integer`, optional): Radius in meters around lat/lon to restrict results to. Example: 5000.
- `top_left` (`string`, optional): Top-left corner of a bounding box to restrict results to, as lat,lon. Example: 52.41,4.84.
- `typeahead` (`boolean`, optional): Set to true to treat the query as a partial input (search-as-you-type). Defaults to false. Example: false.
- `view` (`string`, optional): Geopolitical view for disputed areas. One of: Unified, IN, PK, IL, MA. Defaults to Unified. Example: Unified. One of: `Unified`, `IN`, `PK`, `IL`, `MA`.

Example input: `{"query":"<query>"}`

### `tomtom_cross_street_lookup`

Find Nearest Cross Street · Read-only

Find the nearest intersection (cross street) to a coordinate. Returns the crossing street names and the intersection position. Use this to describe a location by its nearest intersection.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `lat` (`number`, required): Latitude of the position, in decimal degrees. Example: 52.3759.
- `lon` (`number`, required): Longitude of the position, in decimal degrees. Example: 4.8975.
- `heading` (`number`, optional): Direction of travel in degrees (0 = north). Example: 90.
- `language` (`string`, optional): IETF language tag for the results, e.g. en-US. Example: en-US.
- `limit` (`integer`, optional): Maximum number of results to return (up to 100). Defaults to 1. Example: 10.
- `radius` (`integer`, optional): Maximum distance in meters to look for an intersection. Defaults to 10000. Example: 5000.
- `spatial_keys` (`boolean`, optional): If the "spatialKeys" flag is set, the response will also contain a proprietary geospatial keys for a specified location. Defaults to false. Example: false.

Example input: `{"lat":52.3759,"lon":4.8975}`

### `tomtom_fuzzy_search`

Search Places and Addresses · Read-only

Search for addresses, places and points of interest with one free-text query that tolerates typos and partial input, optionally biased to a position or limited to a radius, bounding box or countries. Returns ranked results with type, name, address, position, categories, phone and URL for POIs, and a match score. Use this when the query could be anything. Use tomtom_geocode for addresses only and tomtom_poi_search for businesses only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): Free-text query, such as a place name, address or POI type. Do not include slashes (/), ? or #. Example: pizza.
- `btm_right` (`string`, optional): Bottom-right corner of the bounding box, as lat,lon. Example: 52.33,4.95.
- `country_set` (`string`, optional): Comma-separated ISO 3166 country codes to restrict results to. Example: NL,BE.
- `extended_postal_codes_for` (`string`, optional): Indexes for which extended postal codes should be included in the results. Available indexes are: - <b>Addr</b> = Address ranges - <b>Geo</b> = Geographies - <b>PAD</b> = Point Addresses - <b>POI</b> = Points of Interest - <b>Str</b> = Streets - <b>XStr</b> = Cross Streets (intersections). Example: PAD,Addr.
- `idx_set` (`string`, optional): Comma-separated indexes to search: Geo, PAD (point addresses), Addr, Str, XStr, POI. Example: POI,PAD.
- `language` (`string`, optional): IETF language tag for the results, e.g. en-US. Example: en-US.
- `lat` (`number`, optional): Latitude of the point to bias or center results on, in decimal degrees; use with lon. Example: 52.3759.
- `limit` (`integer`, optional): Maximum number of results to return (up to 100). Defaults to 10. Example: 10.
- `lon` (`number`, optional): Longitude of the point to bias or center results on, in decimal degrees; use with lat. Example: 4.8975.
- `max_fuzzy_level` (`integer`, optional): Maximum fuzziness level to be used. Defaults to 2. Example: 2.
- `min_fuzzy_level` (`integer`, optional): Minimum fuzziness level to be used. Defaults to 1. Example: 1.
- `ofs` (`integer`, optional): Offset of the first result, for paging. Defaults to 0. Example: 0.
- `radius` (`integer`, optional): Radius in meters around lat/lon to restrict results to. Example: 5000.
- `top_left` (`string`, optional): Top-left corner of a bounding box to restrict results to, as lat,lon. Example: 52.41,4.84.
- `typeahead` (`boolean`, optional): Set to true to treat the query as a partial input (search-as-you-type). Defaults to false. Example: false.
- `view` (`string`, optional): Geopolitical view for disputed areas. One of: Unified, IN, PK, IL, MA. Defaults to Unified. Example: Unified. One of: `Unified`, `IN`, `PK`, `IL`, `MA`.

Example input: `{"query":"<query>"}`

### `tomtom_geocode`

Geocode Address · Read-only

Convert a free-text address or place name into coordinates. Returns matches with the full address, position, entry points, bounding box and score. Use this when you have a written address. Use tomtom_structured_geocode when the address is already split into fields.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): Address or place to geocode, e.g. Damrak 1 Amsterdam. Do not include slashes. Example: Damrak 1 Amsterdam.
- `btm_right` (`string`, optional): Bottom-right corner of the bounding box, as lat,lon. Example: 52.33,4.95.
- `country_set` (`string`, optional): Comma-separated ISO 3166 country codes to restrict results to. Example: NL,BE.
- `extended_postal_codes_for` (`string`, optional): Indexes for which extended postal codes should be included in the results. Available indexes are: - <b>Addr</b> = Address ranges - <b>Geo</b> = Geographies - <b>PAD</b> = Point Addresses - <b>POI</b> = Points of Interest - <b>Str</b> = Streets - <b>XStr</b> = Cross Streets (intersections). Example: PAD,Addr.
- `language` (`string`, optional): IETF language tag for the results, e.g. en-US. Example: en-US.
- `lat` (`number`, optional): Latitude of the point to bias or center results on, in decimal degrees; use with lon. Example: 52.3759.
- `limit` (`integer`, optional): Maximum number of results to return (up to 100). Defaults to 10. Example: 10.
- `lon` (`number`, optional): Longitude of the point to bias or center results on, in decimal degrees; use with lat. Example: 4.8975.
- `ofs` (`integer`, optional): Offset of the first result, for paging. Defaults to 0. Example: 0.
- `radius` (`integer`, optional): Radius in meters around lat/lon to restrict results to. Example: 5000.
- `top_left` (`string`, optional): Top-left corner of a bounding box to restrict results to, as lat,lon. Example: 52.41,4.84.
- `typeahead` (`boolean`, optional): Set to true to treat the query as a partial input (search-as-you-type). Defaults to false. Example: false.
- `view` (`string`, optional): Geopolitical view for disputed areas. One of: Unified, IN, PK, IL, MA. Defaults to Unified. Example: Unified. One of: `Unified`, `IN`, `PK`, `IL`, `MA`.

Example input: `{"query":"<query>"}`

### `tomtom_geometry_search`

Search Within Geometry · Read-only

Search places and POIs inside one or more circles or polygons you define. Returns results with name, address, position and categories. Use this for searches inside a custom area such as a delivery zone.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): Free-text query, such as a place name, address or POI type. Do not include slashes (/), ? or #. Example: pizza.
- `extended_postal_codes_for` (`string`, optional): Indexes for which extended postal codes should be included in the results. Available indexes are: - <b>Addr</b> = Address ranges - <b>Geo</b> = Geographies - <b>PAD</b> = Point Addresses - <b>POI</b> = Points of Interest - <b>Str</b> = Streets - <b>XStr</b> = Cross Streets (intersections). Example: PAD,Addr.
- `geometry_list` (`array`, optional): Shapes to search inside: circles {"type": "CIRCLE", "position": "lat, lon", "radius": meters} or polygons {"type": "POLYGON", "vertices": ["lat, lon", ...]}. Example: [{"type":"CIRCLE","position":"52.3759, 4.8975","radius":1000}]
- `idx_set` (`string`, optional): Comma-separated indexes to search: Geo, PAD (point addresses), Addr, Str, XStr, POI. Example: POI,PAD.
- `language` (`string`, optional): IETF language tag for the results, e.g. en-US. Example: en-US.
- `limit` (`integer`, optional): Maximum number of results to return (up to 100). Defaults to 10. Example: 10.

Example input: `{"query":"<query>"}`

### `tomtom_matrix_calculate`

Calculate Route Matrix · Read-only

Calculate travel times and distances between every origin and every destination (up to 100 x 100 cells, within a 400 km box unless the options allow unlimited) in one synchronous call. Returns a cell per origin-destination pair with travel time, length, traffic delay and departure and arrival times. Use this to compare many pairs, e.g. nearest driver. Use tomtom_calculate_route for the route itself.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `destinations` (`array`, required): Destinations, each {"point": {"latitude": ..., "longitude": ...}}. Example: [{"point":{"latitude":52.0907,"longitude":5.1214}},{"point":{"latitude":51.9244,"longitude":4.4777}}]
- `origins` (`array`, required): Origins, each {"point": {"latitude": ..., "longitude": ...}}. Example: [{"point":{"latitude":52.3759,"longitude":4.8975}}]
- `arrive_at` (`string`, optional): Arrival: any or a future ISO 8601 date-time. Cannot be used with depart_at. Example: 2026-07-01T09:00:00Z.
- `avoid` (`array`, optional): Things to avoid: tollRoads, unpavedRoads. Example: ["tollRoads"]
- `depart_at` (`string`, optional): Departure: any, now or a future ISO 8601 date-time. Cannot be used with arrive_at. Example: now.
- `traffic` (`string`, optional): historical (default) or live traffic. Example: live. One of: `historical`, `live`.
- `travel_mode` (`string`, optional): car (default), truck or pedestrian. Example: car. One of: `car`, `truck`, `pedestrian`.
- `vehicle_commercial` (`boolean`, optional): Set to true for a commercial vehicle. Example: false.

Example input: `{"destinations":[{"point":{"latitude":52.0907,"longitude":5.1214}},{"point":{"latitude":51.9244,"longitude":4.4777}}],"origins":[{"point":{"latitude":52.3759,"longitude":4.8975}}]}`

### `tomtom_nearby_search`

Search Nearby POIs · Read-only

List points of interest around a position, nearest first, within an optional radius. Returns POIs with name, categories, address, position and distance. Use this for what is around a location. Use tomtom_category_search to restrict to one category.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `lat` (`number`, required): Latitude of the center point. Example: 52.3759.
- `lon` (`number`, required): Longitude of the center point. Example: 4.8975.
- `btm_right` (`string`, optional): Bottom-right corner of the bounding box, as lat,lon. Example: 52.33,4.95.
- `country_set` (`string`, optional): Comma-separated ISO 3166 country codes to restrict results to. Example: NL,BE.
- `extended_postal_codes_for` (`string`, optional): Indexes for which extended postal codes should be included in the results. Available indexes are: - <b>Addr</b> = Address ranges - <b>Geo</b> = Geographies - <b>PAD</b> = Point Addresses - <b>POI</b> = Points of Interest - <b>Str</b> = Streets - <b>XStr</b> = Cross Streets (intersections). Example: PAD,Addr.
- `idx_set` (`string`, optional): Comma-separated indexes to search: Geo, PAD (point addresses), Addr, Str, XStr, POI. Example: POI,PAD.
- `language` (`string`, optional): IETF language tag for the results, e.g. en-US. Example: en-US.
- `limit` (`integer`, optional): Maximum number of results to return (up to 100). Defaults to 10. Example: 10.
- `max_fuzzy_level` (`integer`, optional): Maximum fuzziness level to be used. Defaults to 2. Example: 2.
- `min_fuzzy_level` (`integer`, optional): Minimum fuzziness level to be used. Defaults to 1. Example: 1.
- `ofs` (`integer`, optional): Offset of the first result, for paging. Defaults to 0. Example: 0.
- `radius` (`integer`, optional): Search radius in meters (default 10000). Example: 5000.
- `top_left` (`string`, optional): Top-left corner of a bounding box to restrict results to, as lat,lon. Example: 52.41,4.84.
- `view` (`string`, optional): Geopolitical view for disputed areas. One of: Unified, IN, PK, IL, MA. Defaults to Unified. Example: Unified. One of: `Unified`, `IN`, `PK`, `IL`, `MA`.

Example input: `{"lat":52.3759,"lon":4.8975}`

### `tomtom_place_get`

Get Place by ID · Read-only

Get the full details of a place by its ID from an earlier search result. Returns name, address, position, categories, phone, URL, opening hours, time zone and related POIs. Use this to refresh or expand one search result.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `entity_id` (`string`, required): ID of the place (the id of a search result). Example: 528009004256119.
- `language` (`string`, optional): IETF language tag for the result, e.g. en-US. Example: en-US.
- `opening_hours` (`string`, optional): Set to nextSevenDays to include opening hours. Example: nextSevenDays. One of: `nextSevenDays`.
- `related_pois` (`string`, optional): Related POIs to include: off, child, parent or all. Example: all. One of: `off`, `child`, `parent`, `all`.
- `time_zone` (`string`, optional): Set to iana to include the place's time zone. Example: iana. One of: `iana`.
- `view` (`string`, optional): Geopolitical view for disputed areas. Example: Unified.

Example input: `{"entity_id":"<entity_id>"}`

### `tomtom_poi_categories_list`

List POI Categories · Read-only

List the full tree of point-of-interest categories with their IDs, names, synonyms and child categories. Use this to find category names or IDs for tomtom_category_search.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `language` (`string`, optional): IETF language tag for category names, e.g. en-US. Example: en-US.

Example input: `{}`

### `tomtom_poi_search`

Search Points of Interest · Read-only

Search points of interest (businesses and landmarks) by name, brand or type, optionally near a position or in an area. Returns POIs with name, categories, brand, address, position, phone, URL and distance. Use this for businesses. Use tomtom_category_search to search by category name and tomtom_nearby_search for everything around a point.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): POI name or type to search for, e.g. Starbucks or museum. Do not include slashes. Example: pizza.
- `btm_right` (`string`, optional): Bottom-right corner of the bounding box, as lat,lon. Example: 52.33,4.95.
- `country_set` (`string`, optional): Comma-separated ISO 3166 country codes to restrict results to. Example: NL,BE.
- `extended_postal_codes_for` (`string`, optional): Indexes for which extended postal codes should be included in the results. Available indexes are: - <b>Addr</b> = Address ranges - <b>Geo</b> = Geographies - <b>PAD</b> = Point Addresses - <b>POI</b> = Points of Interest - <b>Str</b> = Streets - <b>XStr</b> = Cross Streets (intersections). Example: PAD,Addr.
- `language` (`string`, optional): IETF language tag for the results, e.g. en-US. Example: en-US.
- `lat` (`number`, optional): Latitude of the point to bias or center results on, in decimal degrees; use with lon. Example: 52.3759.
- `limit` (`integer`, optional): Maximum number of results to return (up to 100). Defaults to 10. Example: 10.
- `lon` (`number`, optional): Longitude of the point to bias or center results on, in decimal degrees; use with lat. Example: 4.8975.
- `ofs` (`integer`, optional): Offset of the first result, for paging. Defaults to 0. Example: 0.
- `radius` (`integer`, optional): Radius in meters around lat/lon to restrict results to. Example: 5000.
- `top_left` (`string`, optional): Top-left corner of a bounding box to restrict results to, as lat,lon. Example: 52.41,4.84.
- `typeahead` (`boolean`, optional): Set to true to treat the query as a partial input (search-as-you-type). Defaults to false. Example: false.
- `view` (`string`, optional): Geopolitical view for disputed areas. One of: Unified, IN, PK, IL, MA. Defaults to Unified. Example: Unified. One of: `Unified`, `IN`, `PK`, `IL`, `MA`.

Example input: `{"query":"<query>"}`

### `tomtom_reverse_geocode`

Reverse Geocode · Read-only

Convert coordinates into the nearest address, optionally with the street's speed limit and road use. Returns the address (street, number, postal code, city, country) and the matched position. Use this to describe where a coordinate is. Use tomtom_cross_street_lookup for the nearest intersection.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `lat` (`number`, required): Latitude of the position, in decimal degrees. Example: 52.3759.
- `lon` (`number`, required): Longitude of the position, in decimal degrees. Example: 4.8975.
- `heading` (`number`, optional): Direction of travel in degrees (0 = north), to pick the right side of the road. Example: 90.
- `number` (`string`, optional): House number to look for on the matched street. Example: 1.
- `radius` (`integer`, optional): Maximum distance in meters from the position to look for an address. Defaults to 10000. Example: 5000.
- `return_road_use` (`boolean`, optional): Enables return of the road use array for reverse geocodes at street level. Defaults to false. Example: true.
- `return_speed_limit` (`boolean`, optional): To enable return of the posted speed limit (where available). Defaults to false. Example: true.
- `road_use` (`string`, optional): Road uses to restrict the match to, e.g. LocalStreet, Arterial, Ramp, Rotary. Example: LocalStreet.
- `spatial_keys` (`boolean`, optional): If the "spatialKeys" flag is set, the response will also contain a proprietary geospatial keys for a specified location. Defaults to false. Example: false.

Example input: `{"lat":52.3759,"lon":4.8975}`

### `tomtom_search_along_route`

Search Along Route · Read-only

Search POIs along a route given as a list of points, within a maximum detour time. Returns POIs with name, address, position and the detour time and distance. Use this to find fuel, charging or food stops on a trip; get the route points from tomtom_calculate_route.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `max_detour_time` (`integer`, required): Maximum detour in seconds for a stop (up to 3600). Example: 600.
- `query` (`string`, required): POI name or type, e.g. petrol station. Do not include slashes. Example: petrol station.
- `limit` (`integer`, optional): Maximum number of results to return (up to 100). Defaults to 10. Example: 10.
- `route` (`object`, optional): Route as {"points": [{"lat": ..., "lon": ...}, ...]} with at least 2 points. Example: {"points":[{"lat":52.3759,"lon":4.8975},{"lat":52.0907,"lon":5.1214}]}

Example input: `{"max_detour_time":600,"query":"<query>"}`

### `tomtom_structured_geocode`

Geocode Structured Address · Read-only

Convert an address given as separate fields (country code, street, number, postal code, city and so on) into coordinates. Returns matches with the full address, position and score. Use this when your address data is already structured.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `country_code` (`string`, required): 2 or 3 letter country code (e.g.: FR, ES). Example: NL.
- `country_secondary_subdivision` (`string`, optional): The county for the structured address. Example: Amsterdam.
- `country_subdivision` (`string`, optional): The state or province for the structured address. Example: Noord-Holland.
- `country_tertiary_subdivision` (`string`, optional): The named area for the structured address. Example: Amsterdam.
- `cross_street` (`string`, optional): The cross street name for the structured address. Example: Nieuwendijk.
- `extended_postal_codes_for` (`string`, optional): Indexes for which extended postal codes should be included in the results. Available indexes are: - <b>Addr</b> = Address ranges - <b>Geo</b> = Geographies - <b>PAD</b> = Point Addresses - <b>POI</b> = Points of Interest - <b>Str</b> = Streets - <b>XStr</b> = Cross Streets (intersections). Example: PAD,Addr.
- `language` (`string`, optional): IETF language tag for the results, e.g. en-US. Example: en-US.
- `limit` (`integer`, optional): Maximum number of results to return (up to 100). Defaults to 10. Example: 10.
- `municipality` (`string`, optional): The municipality (city/town) for the structured address. Example: Amsterdam.
- `municipality_subdivision` (`string`, optional): The municipality subdivision (sub/super city) for the structured address. Example: Centrum.
- `ofs` (`integer`, optional): Offset of the first result, for paging. Defaults to 0. Example: 0.
- `postal_code` (`string`, optional): The zip code or postal code for the structured address. Example: 1012.
- `street_name` (`string`, optional): The street name for the structured address. Example: Damrak.
- `street_number` (`string`, optional): The street number for the structured address. Example: 1.

Example input: `{"country_code":"<country_code>"}`

### `tomtom_traffic_flow_segment_get`

Get Traffic Flow · Read-only

Get live traffic on the road segment closest to a point. Returns current and free-flow speed and travel time, confidence, whether the road is closed, and the segment's coordinates. Use this to check congestion at a location.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `point` (`string`, required): Point as lat,lon, e.g. 52.3759,4.8975. Example: 52.3759,4.8975.
- `style` (`string`, required): Flow style that sets how speeds are classified: absolute, relative, relative0, relative0-dark, relative-delay or reduced-sensitivity. Example: relative0. One of: `absolute`, `relative`, `relative0`, `relative0-dark`, `relative-delay`, `reduced-sensitivity`.
- `zoom` (`integer`, required): Map zoom level (0 to 22) that sets how coarse the road network is. Example: 10.
- `open_lr` (`boolean`, optional): Set to true to include the OpenLR location code. Example: false.
- `thickness` (`integer`, optional): Segment line thickness 1 to 20 (affects which segment is matched). Example: 10.
- `unit` (`string`, optional): Speed unit: KMPH (default) or MPH. Example: KMPH. One of: `KMPH`, `MPH`.

Example input: `{"point":"<point>","style":"absolute","zoom":10}`

### `tomtom_traffic_incidents_get`

Get Traffic Incidents · Read-only

Get live traffic incidents (accidents, jams, road works, closures, weather) inside a bounding box of up to 10,000 km², or by incident IDs. Returns incidents as GeoJSON features with type, location, delay, length, start and end time and description, depending on the fields selection. Use this to see what is disrupting traffic in an area.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `bbox` (`string`, optional): Bounding box minLon,minLat,maxLon,maxLat (up to 10,000 km²). Give this or ids. Example: 4.80,52.30,5.00,52.42.
- `category_filter` (`string`, optional): Comma-separated categories: 0 Unknown, 1 Accident, 2 Fog, 3 DangerousConditions, 4 Rain, 5 Ice, 6 Jam, 7 LaneClosed, 8 RoadClosed, 9 RoadWorks, 10 Wind, 11 Flooding, 14 BrokenDownVehicle. Example: 1,6,8,9.
- `fields` (`string`, optional): Fields to return, in TomTom's nested selection syntax. Example: {incidents{type,geometry{type,coordinates},properties{id,iconCategory,magnitudeOfDelay,events{description,code},startTime,endTime,from,to,length,delay}}}
- `ids` (`string`, optional): Comma-separated incident IDs (up to 5). Give this or bbox. Example: 4819f7d0a1ed3a4b4e3c4e8f7f8c3b2a.
- `language` (`string`, optional): Language of descriptions, e.g. en-GB (default) or nl-NL. Example: en-GB.
- `time_validity_filter` (`string`, optional): present (default), future, or present,future. Example: present.

Example input: `{}`

## Related

Other Search connectors ([all 89](/agentkit/connectors/?category=search)):

- [Supadata](/agentkit/connectors/supadata/): Scalekit connector, API key, 21 tools
- [Exa](/agentkit/connectors/exa/): Scalekit connector, API key, 21 tools
- [Brave Search](/agentkit/connectors/brave/): Scalekit connector, API key, 18 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
