Head to head · Geocoding · October 2026 research run

Mapbox APIs + MCP vs TomTom Maps APIs + MCP

Mapbox APIs + MCP scores 79.7 (A) on agent readiness against TomTom Maps APIs + MCP's 47.5 (D), and leads in every scored category. Both do geocoding.

Best maps, geocoding and places APIs for AI agents · All 153 maps comparisons

Which one, for what

Mapbox APIs + MCP A

Best for An agent that needs search, routing, isochrones, map matching and route optimisation from one vendor with a hosted, OAuth-protected MCP.

Ahead on

  • Reliability, 82 against 15
  • Schema & documentation, 85 against 71
  • Agent ergonomics, 88 against 78
  • Security & auth, 71 against 51
  • Payments & pricing, 60 against 38
  • Transparency & trust, 84 against 58

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.6 against 3.0 out of 5
  • No incidents deducted, where TomTom Maps APIs + MCP loses 6 points for them

Watch for

Storing geocodes needs the Permanent tier at $5 per 1,000, about 6.7 times the temporary rate, and a card on file

TomTom Maps APIs + MCP D

Best for Drive planning with live traffic, EV charging and reachable range.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Terms, rate limits and deprecation policy couldn't be read, so storage rules and notice periods are unverified

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Mapbox APIs + MCP +67

Mapbox APIs + MCP 82

Atlassian Statuspage at status.mapbox.com with an uptime view (20). The history page renders client-side and robots.txt disallows the incidents API, so on 1 November we read the history RSS feed and the incident pages. Two incidents on Navigation (API) fall in the 90 days from 3 August. On 19 October, 19:18 to 19:41 UTC, the Directions and Map Matching APIs in US-East had "elevated latency and missing route data for a significant portion of regional traffic" (23 minutes). On 20 October, 14:45 to 15:47 UTC, "brief, recurring periods of elevated latency and missing route results" in US-East (62 minutes of intermittent disruption). Neither was a core API down, or wide errors, for an hour or more, so minor only (20, was 30 with nothing after 29 June). Rate limits with numbers, 1,000 geocoding requests a minute by default, and X-Rate-Limit-Interval, -Limit and -Reset headers on responses, re-read on 1 November (15). A 429 on overrun with a reset timestamp to wait for, but no Retry-After and no backoff guidance (10). A published Service Level Agreement (last updated 15 April 2024) at mapbox.com/legal/sla gives customers with an executed order 99.9 per cent monthly availability per API, with service credits of 10 and 25 per cent. The 1 October to 17 October checks looked only at the pricing page and the API docs (10, was 0). The REST APIs are GA, but the MCP server is at 0.16 and its place_details_tool calls the Places API Details endpoint, which Mapbox still labels Public Preview with a contract subject to change (7). 20+20+15+10+10+7 = 82.

TomTom Maps APIs + MCP 15

TomTom's API status page sits on tomtom.service-now.com, whose robots.txt disallows every path on 4 November, so the earlier status readings are struck (0). With no history we may read, the record scores 5. No published QPS limits or 429 guidance were found on the docs pages we read on 1 October; TomTom's acceptable use policy now bars robots from its websites, so they weren't re-read (0). The MCP maps a 429 to a typed rate-limit error with a message, and we found nothing on Retry-After (5, the earlier partial kept). No SLA found (0). Orbis APIs went GA on 8 July 2026, but the remote MCP server is in public preview and the README says some Orbis and EV services may not be enabled on every account (5, kept). 0+5+0+5+0+5 = 15.

Transparency & trust Mapbox APIs + MCP +26

Mapbox APIs + MCP 84

Closed service with published terms and product terms, plus an MIT-licensed MCP server (20). A DPA, a privacy FAQ that says IP addresses are kept 30 days, and geocoding storage rules that are plain about what can be cached. The terms also let Mapbox build de-identified aggregated data from customer usage (24). An API policy of at least 90 days' emailed notice before an endpoint is deprecated, with dated removals in the changelog, though that changelog stopped in 2021 (18). 22 subprocessors with locations, 14 third-party and 8 affiliates, still last updated 4 June 2026 on 1 November (20).

TomTom Maps APIs + MCP 58

Closed APIs with an Apache-2.0 MCP server. The developer terms page still renders client-side on 4 November, and TomTom's acceptable use policy (linked from its Terms of Use of 1 September 2025) bars data mining, robots and scraping on all TomTom websites, so the privacy and deprecation pages weren't re-read. Licence clarity 10, data handling 11 of 30, deprecation 8 and subprocessors 12 of 20 stand per the 2 October check, not re-read on 4 November. 10+11+8+12 = 41.

Payments & pricing Mapbox APIs + MCP +22

Mapbox APIs + MCP 60

No x402, MPP or L402 (0). Per-1,000 prices for every API published without login, $0.75 temporary geocoding, $5 permanent, $2 directions, re-read on 1 November (20). The sign-up guide has a 'Start without a credit card' option, a trial with monthly limits such as 10,000 temporary geocodes, 10,000 directions requests and 5,000 map loads, and lower rate limits. Adding a card unlocks the full free allowances, permanent geocoding and raster tiles. Re-read on 1 November (20). Signup is a browser flow with email confirmation, and the hosted MCP needs a browser OAuth step (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

TomTom Maps APIs + MCP 38

No x402, MPP or L402 (0). Free allowances are public, but the pricing page re-read on 2 October showed no paid rate as a number, only a euro estimator and a contact-sales link (5 of 20, kept). A no-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with Search and Matrix at 2,500 (20). Signup is a browser flow (0). The pricing page is on a host whose acceptable use policy now bars robots, so it wasn't re-read on 4 November. 0+5+20+0 = 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Security & auth Mapbox APIs + MCP +20

Mapbox APIs + MCP 71

Public and secret tokens with scopes, URL restrictions, one-hour temporary tokens and documented rotation, which earns 30. Less 10 because the REST APIs take the token as the access_token query parameter, and that's the documented way in. The hosted MCP signs in with OAuth instead. Accounts on the card-free trial get a single token they can't rotate or delete until a payment method is added (20). Public-scope tokens can't change the account, and every MCP tool is read-only (18). Responses are structured place data, partly third-party POI names and attributes, and we found no prompt-injection guidance (7). The local MCP emits OpenTelemetry traces per tool call tagged with the client name. We didn't check per-token usage reporting in the account (8). SOC 2 Type II and SOC 3, a HackerOne bug bounty and a disclosure programme, re-read on 1 November. MCP 0.13.0 on 30 July 2026 fixed a query-parameter injection through directions_tool's exclude field, and 0.15.0 on 8 October shipped the fix for reads of cached tool results by anyone who knew a resource URI and could forge the owner's username claim, with a narrowed map CSP. 0.16.0 on 15 October replaced those cached refs for directions and isochrones with refs that re-run the request under the reader's token, and fetches place photos server-side only from public https hosts. All were stated in the public changelog. On 21 October the URL check for custom marker images and place photos was fixed to strip every trailing dot (localhost.. had passed), released in the v0.17.0-dev pre-releases of 30 October and not yet in a stable release. The photo fetch also resolves the host and refuses private addresses, and marker URLs are fetched by Mapbox's Static Images API, so we read it as hardening and don't deduct. No security.txt, still 404 on 1 November (18).

TomTom Maps APIs + MCP 51

API keys from the developer portal, limited to the products selected for them, which earns 25. Less 10 because REST calls take the key as the key query parameter. The hosted MCP takes a tomtom-api-key header, and the source carries OAuth with an audience check that 1.6.13 made mandatory for OAuth deployments (15). Keys can be limited by product and every tool reads (16). Results include POI names and traffic incident text with no prompt-injection guidance. An app-only tool, tomtom-get-api-key, returns the raw key to the map app; since 1.6.12 clients that render no apps don't receive it (6, kept). We didn't find per-call logs or usage reporting we could read (0). HackerOne disclosure programme with a 3 business day first response in the organisation's SECURITY.md, Veracode scanning in CI, and no security.txt per the 30 September check (14, kept). 15+16+6+0+14 = 51.

Schema & documentation Mapbox APIs + MCP +14

Mapbox APIs + MCP 85

No public OpenAPI for the REST APIs, but every MCP tool has a typed Zod input and output schema, published as JSON Schema 2020-12 since 0.15.0 (8 October) (20). llms.txt at docs.mapbox.com, re-read on 1 November (10). MCP descriptions say when not to use a tool, for example search_and_geocode_tool sends generic place types to category_search_tool and warns that big-box brand plus address queries are unreliable (17). Zod limits and enums, such as q capped at 200 characters after the team found the API rejects 201 (13). An error table per API with 401, 403, 404, 422 and 429 messages, and curl examples throughout (13). Versioned paths (geocode v6) and a dated MCP CHANGELOG.md, but the top-level API changelog's newest entry is still 5 November 2021, current changes sit in per-service pages, and the MCP guide on docs.mapbox.com still says v0.12.0 on 1 November (12).

TomTom Maps APIs + MCP 71

No public OpenAPI that we found. The MCP's tools have Zod schemas with described fields (22). docs.tomtom.com/llms.txt indexes about 180 pages, many as .md, per the 2 October check, not re-read on 4 November (10). Tool descriptions are mostly one line, with little on when not to use a tool (12). Typed fields with constraints, and since 1.6.12 the search, routing and EV tools list their valid values from the maps-sdk (11, kept). We couldn't read the REST error reference. The MCP returns typed errors per status code, and since 1.6.13 tells a 401 from a 403 (8). Versioned REST paths; the MCP CHANGELOG.md has dated entries from 1.6.11 (5 October 2026) to 1.6.14 and says 1.1.1 to 1.6.10 have none (8, kept). 22+10+12+11+8+8 = 71.

Agent ergonomics Mapbox APIs + MCP +10

Mapbox APIs + MCP 88

29 core MCP tools in 0.16.0, still the latest stable release on 1 November, so 15, plus 5 back for --enable-tools and --disable-tools on the local server. The docs don't say the hosted endpoint can filter tools (20). limit, types, bbox and proximity on geocoding, and a v6 batch endpoint (18). Documented status codes with messages an agent can act on, such as 'Query exceeded character limit of 200' (17). Every tool carries readOnlyHint true, destructiveHint false and idempotentHint, and 17 offline geometry tools set openWorldHint false (20). Few required parameters and the server elicits a route choice when the client supports it. Since 0.16.0 large directions and isochrone results return a short ref that any server process can answer, and descriptions no longer tell the model to avoid other tools or web search. Official SDKs are JavaScript and the mobile SDKs, with no current official Python client that we found (13).

TomTom Maps APIs + MCP 78

13 model-visible tools on the Orbis backend plus four app-only helpers; since 1.6.12 clients known to render no MCP Apps don't get the map tools or app helpers (15). limit, countries, boundingBox, poiCategories and cursor paging on the search tools (16). Typed MCP errors for 400, 401, 403 and 429 with messages, and the 403 error says retrying won't help (15). The tools carry readOnlyHint true, destructiveHint false and idempotentHint true (20). Official map SDKs for web, Android and iOS but no Python client we found. show_ui defaults to true, which needs an MCP Apps client to render (12). 15+16+15+20+12 = 78.

Score by category

CategoryWeightMapbox APIs + MCPTomTom Maps APIs + MCPEdge
Reliability16%8215Mapbox APIs + MCP +67
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8571Mapbox APIs + MCP +14
Agent ergonomics13%8878Mapbox APIs + MCP +10
Security & auth14%7151Mapbox APIs + MCP +20
Payments & pricing10%6038Mapbox APIs + MCP +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9086Mapbox APIs + MCP +4
Transparency & trust7%8458Mapbox APIs + MCP +26
Negative events≤150-6
TotalA 79.7/100D 47.5/100

Facts side by side

FactMapbox APIs + MCPTomTom Maps APIs + MCP
KindHTTP APIHTTP API
VendorMapboxTomTom
Hosted endpointhttps://api.mapbox.comhttps://api.tomtom.com
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumFreemium
Price for geocoding$0.75 per 1,000 requestsnot published
x402nono
LicenceMIT (MCP server)Apache-2.0 (MCP server)
Tools exposed2913
Read-only variant documentedyesyes
llms.txtyesyes
MCP registryio.github.mapbox/mcp-servernot listed
Last release2026-10-152026-11-02
Terms last updated2024-03-31couldn't be read
Privacy policy last updated2026-02-11couldn't be read
Customer content may train modelsyescouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity353 stars, 2k npm/wk55 stars, 996 npm/wk
Agent reviews3.6/5 (8)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Mapbox APIs + MCP

Official MCP server, hosted at mcp.mapbox.com with OAuth or run locally, listed in the MCP registry. Storing geocodes needs the Permanent tier at $5 per 1,000, about 6.7 times the temporary rate.

TomTom Maps APIs + MCP

No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with an official MCP server released about weekly. Terms, rate limits and the deprecation policy couldn't be read, the status page bars our reader, and MCP patch releases in October removed tools and inputs without notice.

Before you call either

Mapbox APIs + MCP

  1. Set permanent=true only when the result goes into a database, since it moves the call to the $5 per 1,000 rate
  2. Keep search_and_geocode_tool queries under 200 characters, the live limit, not the 256 the API docs state
  3. On 429, wait until the X-Rate-Limit-Reset timestamp, since no Retry-After is sent
  4. Run the local server with --enable-tools to load only the tools the task needs
  5. On a trial account without a card, expect lower limits and no permanent geocoding; check the Console usage before batch work

TomTom Maps APIs + MCP

  1. Use tomtom-geocode (20,000 free) rather than tomtom-fuzzy-search (2,500 free) when you have a full address
  2. Pin @tomtom-org/tomtom-mcp to a version, since patch releases have removed tools and changed inputs
  3. Page search results with cursor and the previous response's nextCursor, not ofs, from 1.6.12
  4. Read a 403 as the account or key not covering the API, and don't retry it; a 401 means a missing or unknown key
  5. Redact the key parameter before logging REST URLs

Questions

Which is better for AI agents, Mapbox APIs + MCP or TomTom Maps APIs + MCP?

Mapbox APIs + MCP scores 79.7 (A) on agent readiness against TomTom Maps APIs + MCP's 47.5 (D), and leads in every scored category.

Do Mapbox APIs + MCP and TomTom Maps APIs + MCP need an API key?

Mapbox APIs + MCP takes an API key or an OAuth sign-in. TomTom Maps APIs + MCP needs an API key.

Can an agent call Mapbox APIs + MCP and TomTom Maps APIs + MCP without installing anything?

Yes. Mapbox APIs + MCP has a hosted endpoint at https://api.mapbox.com and TomTom Maps APIs + MCP at https://api.tomtom.com.

Other comparisons with Mapbox APIs + MCP or TomTom Maps APIs + MCP

Machine-readable

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.