Niches · Maps, geocoding & places

Compare travel times across many stops or plan a multi-stop run

Four or more companies' docs show a full fit.

9companies, full fit
6companies, fit with a limit
15companies carry the tag
5share of the category's work
1first-hand accounts

What counts as done

A matrix of times and distances for all pairs requested, or an ordered stop sequence with arrival times, in one call or one async job, priced per element or per job as published.

Measured, for our own tests: a 25 by 25 matrix returns within 10 seconds. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: best order to visit these 12 addresses, which depot is closest by drive time to each customer, plan today's delivery route

Does the job 9

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Amazon Location Service A
Amazon Web Services, Inc.
CalculateRouteMatrix takes up to 160,000 cells with RoutingBoundary.Geometry (100 unbounded), and Optimize waypoints takes 50 stops; limits are published per call. source
Azure Maps B
Microsoft Corporation
Post Route Matrix computes up to 2,500 cells synchronously (50 by 50 is an example), with an async endpoint for larger jobs; billing is four cells per transaction. source
Geoapify Location Platform + MCP C
KEPTAGO LTD
Route Matrix returns up to 1,000 time and distance values per call, larger matrices by combining calls, billed in published credits. source
Geocodio BB
Dotsquare LLC
Distance matrix takes up to 10,000 calculations (2,500 pairs) synchronously, with distance jobs for larger runs, driving priced at two lookups per element and billing headers on each response. source
Google Maps Platform + Grounding Lite MCP BB
Google LLC or a regional Google entity, by billing country
Compute Route Matrix takes up to 625 elements for non-transit routes (25 by 25), 100 for transit or TRAFFIC_AWARE_OPTIMAL, priced per element on the published sheet. source
HERE Location Services C
HERE Europe B.V.
Matrix Routing v8 states its limits: Flexible mode takes 15 by 100 with live traffic, and Region mode serves larger matrices within a region, both sync and async. source
Radar D
Radar Labs, Inc.
/v1/route/matrix calculates up to 625 routes per call (25 by 25), billed per element, and /route/optimize orders up to 10 stops. source
Stadia Maps B
Stadia Maps, Inc.
Time/distance matrix limits are published per plan: 625 elements on Standard and 10,000 on Professional for driving, with a distance cap; priced at 10 credits per element. source
TomTom Maps APIs + MCP D
TomTom International BV
Matrix Routing v2 publishes its limits: 2,500 cells synchronously and 100 million asynchronously with job status and download; only 2,500 free a month. source

Does the job, with a limit 6

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
ArcGIS Location Platform B
Environmental Systems Research Institute, Inc.
solveODCostMatrix and the vehicle routing problem service exist in the routing reference, but their size limits and per-element prices were not on the pages read. source
LocationIQ B
Unwired Labs (India) Pvt Ltd
Matrix and Optimize APIs exist (optimisation is a greedy heuristic), but no maximum matrix size was found in the spec or index. source
Mapbox APIs + MCP A
Mapbox, Inc.
Matrix takes at most 25 coordinates a request (10 for driving-traffic), so a 25 by 25 matrix of distinct origins and destinations needs several calls; priced per element, and a first-hand account used Optimization instead. source
MapQuest F
Mapquest Holdings LLC
Route Matrix and an async Route Matrix (submit, status, results) and Optimized Route exist, but no maximum size or per-element price was found. source
NextBillion.ai C
NextBillion.ai Pte. Ltd.
Synchronous and asynchronous Distance Matrix APIs and a Route Optimization API exist for many-to-many runs, but no maximum size or per-element price is public; pricing is by quote. source
Woosmap C
WOOSMAP SAS
Synchronous matrices are capped at 200 elements a query (15 by 100 with departure_time), so a 25 by 25 needs the async matrix endpoints, whose limits were not read. source

Doesn't do this job 3

Listings in the category that do something else, with the reason.

ListingWhy
MapTiler Cloud B
MapTiler AG
No matrix or optimisation API.
Nominatim B
Nominatim project (osm-search)
No routing or matrix.
OpenCage Geocoding API B
OpenCage GmbH
No routing or matrix.

What stops agents finishing

  • matrix priced per element so a mid-sized run costs dollars
  • matrix size per call too small for the stop count
  • optimisation sold only on an annual contract

Around it

Before: maps.batch-geocode-and-store. After: shipping.buy-label, scheduling.add-event.

Where this comes from

Weight 5 of 100 in Maps, geocoding & places: 1 of 53 accounts; held above its count because five listings (Mapbox, HERE, TomTom, NextBillion, Radar) sell it as a main use

The same as data: /api/v1/use-cases/maps.travel-time-matrix.json, or the MCP tool get_use_case with id maps.travel-time-matrix. Other jobs in this category: /api/v1/niches?category=maps.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.