DistanceMatrix.ai API

Name: DistanceMatrix.ai API
Brand: DistanceMatrix.ai API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationRouting DirectionsapiKey2 EndpointsREST

For Agents

Install Jentic One Beta

Connect the DistanceMatrix.ai API to your agent

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

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%2Fdistancematrix-ai%2Fdistancematrix-ai" | sh

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%2Fdistancematrix-ai%2Fdistancematrix-ai" | 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 DistanceMatrix.ai API.

Calculate distances and travel times between origin/destination pairs via /maps/api/distancematrix/json

Apply real-time traffic predictions to driving distance results when departure_time is supplied

Switch routing mode between driving, walking, bicycling, and transit on each request

GET STARTED

Start building with DistanceMatrix.ai API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for DistanceMatrix.ai API, keeping it validated and agent-ready. DistanceMatrix.ai provides distance, travel-time, and geocoding services worldwide with support for driving, walking, bicycling, and transit modes, including real-time traffic. The two operations cover bulk distance/duration calculations between origin/destination pairs and forward geocoding of free-form addresses to coordinates. It is positioned as a lower-cost alternative to Google's Distance Matrix and Geocoding APIs.

Use Cases

Patterns agents use DistanceMatrix.ai API for, with concrete tasks.

★ Delivery and Field-Service Routing

Logistics, food delivery, and field-service businesses can compute distance and ETA between dispatch locations and many destinations using a single /maps/api/distancematrix/json call. Supplying a departure_time returns traffic-aware durations for accurate ETAs. The bulk request format reduces network overhead compared to per-pair calls and is well suited to dispatch-time route assignment.

Call /maps/api/distancematrix/json with one origin (depot) and 10 destinations, mode='driving', and departure_time='now' to get traffic-aware ETAs.

Address Cleansing and Geocoding for CRM Systems

CRM and ops teams can run customer or supplier address strings through /maps/api/geocode/json to obtain validated coordinates and standardised address components. This improves map rendering, territory assignment, and downstream routing accuracy. Geocoding at import time avoids per-display latency in dashboards and customer apps.

POST address strings to /maps/api/geocode/json one at a time and store the returned latitude/longitude on the customer record for map display.

Multi-Modal Travel Time Comparison

Travel apps, real estate platforms, and commute tools can compare travel times across driving, walking, cycling, and transit by issuing parallel requests with different mode parameters. This is the core data behind 'how long does it take to get to work' style features and rental search filters that enforce a maximum commute. The lower per-request cost compared with Google Maps makes it attractive for high-volume consumer apps.

For origin/destination pair, call /maps/api/distancematrix/json once per mode in [driving, walking, bicycling, transit] and return the durations in a single response object.

AI Agent Logistics Assistant

AI agents handling logistics or travel planning can ask DistanceMatrix.ai for distances and ETAs through Jentic without managing API keys directly. The two operations are exposed as named tools, and the apiKey is held in your Jentic One instance so it never enters the agent's context. Agents typically chain a /maps/api/geocode/json call with /maps/api/distancematrix/json to convert addresses into a routing answer.

Search Jentic for 'calculate driving time between addresses', load the /maps/api/distancematrix/json operation, and execute it with origins, destinations, and departure_time='now'.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for distancematrix.

METHOD

PATH

DESCRIPTION

GET

/maps/api/distancematrix/json

Compute distances and durations between origin/destination pairs

GET

/maps/api/geocode/json

Forward geocode an address into coordinates

GET

/maps/api/distancematrix/json

Compute distances and durations between origin/destination pairs

GET

/maps/api/geocode/json

Forward geocode an address into coordinates

Why Jentic?

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

Setup

Wiring DistanceMatrix.ai by hand means placing its key in the 'key' query parameter and formatting distance and geocode requests yourself. Through Jentic you install once, import the DistanceMatrix.ai API from the API Directory, store the key once, and your agent calls it.

Permission scoping

DistanceMatrix.ai passes its inputs as query parameters, so scope your agent to the operations it needs, such as distance-matrix calculations or forward geocoding. You choose the operations it may call, so geocoding is not included if you only grant distance calculations.

Credential isolation

Your DistanceMatrix.ai API 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 'calculate driving time' or 'geocode an address', and Jentic returns the matching DistanceMatrix.ai operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using DistanceMatrix.ai API through Jentic.

Why is there no official OpenAPI spec for DistanceMatrix.ai API?

DistanceMatrix.ai does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DistanceMatrix.ai API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the DistanceMatrix.ai API use?

It uses an API key passed via the 'key' query parameter on every request. Keys are issued from the DistanceMatrix.ai dashboard. Through Jentic, the key is stored encrypted in your Jentic One instance and injected at execution, so the agent never sees the raw key.

Can I get traffic-aware travel times with the DistanceMatrix.ai API?

Yes, supply departure_time on the /maps/api/distancematrix/json call (e.g. 'now' or a future Unix timestamp) and DistanceMatrix.ai returns traffic-adjusted durations for the driving mode. Without departure_time, durations are returned without traffic.

What are the rate limits for the DistanceMatrix.ai API?

Rate limits are tier-dependent: free plans cap at a low daily volume, while paid plans publish per-second and per-day caps from the DistanceMatrix.ai dashboard. The OpenAPI spec does not encode plan-specific limits. Check your dashboard for the exact figures applied to your key.

How do I geocode an address with DistanceMatrix.ai through Jentic?

Search Jentic for 'geocode an address', load the schema for /maps/api/geocode/json, and execute it with the address string. Jentic returns the geocoded result with latitude, longitude, and standardised address components.

How does the DistanceMatrix.ai API compare with Google Maps?

DistanceMatrix.ai positions itself as a lower-cost alternative to Google's Distance Matrix and Geocoding APIs with a similar request shape. Pricing per call is significantly lower, but coverage and traffic-data quality vary by region. Test your specific cities before migrating high-value workloads.