Head to head · Geocoding · October 2026 research run

ArcGIS Location Platform vs TomTom Maps APIs + MCP

ArcGIS Location Platform scores 68.6 (B) on agent readiness against TomTom Maps APIs + MCP's 47.5 (D), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on schema & documentation. Both do geocoding.

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

Which one, for what

ArcGIS Location Platform B

Best for Organisations already on Esri software, and work that needs demographic enrichment, service areas or fleet routing beside geocoding.

Ahead on

  • Reliability, 70 against 15
  • Security & auth, 64 against 51
  • Payments & pricing, 60 against 38
  • Transparency & trust, 69 against 58

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
  • No incidents deducted, where TomTom Maps APIs + MCP loses 6 points for them

Watch for

The agreement bars benchmarking availability, performance or functionality, and publishing benchmark results, without prior written permission from Esri and its licensors (sections 3.1.b.6 and 3.1.c.6.F).

TomTom Maps APIs + MCP D

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

Ahead on

  • Schema & documentation, 71 against 61

Also in its favour

  • Runs on your own machine
  • Free to start without a card

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 ArcGIS Location Platform +55

ArcGIS Location Platform 70

Graded as a hosted service on the REST location services, which are generally available. Esri runs its own status page at status.location.arcgis.com with current status and an event history (20). The history is drawn by script, so we read the platform's RSS feed at /admin/api/rss/all.rss, titled ArcGIS Location Platform Services Status. The page's own "all services RSS feed" link (location_platform.rss) answered 404 on 2 November. On 2 November its newest entry is still an intermittent basemap tile slowdown on 16 June 2026, outside the 90 days to 2 November. A readable feed that posts incidents, with none touching the product in the window, is a clean record (30). The 8 October check gave 25 and held back 5 for the feed's unknown depth, which isn't a checklist value. No request rate limits with numbers were found in the geocoding, places or routing reference (0, per the 8 October check, not re-read on 2 November). No 429 or backoff guidance was found. The geocoding output page says only that a timeout after 60 seconds may be retried later (0). The SLA of 23 December 2025 commits to 99.9 per cent monthly uptime for ten services (10). The REST services are generally available, and the MCP server is a beta (10). Total 70.

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.

Payments & pricing ArcGIS Location Platform +22

ArcGIS Location Platform 60

No x402, MPP or L402 (0). Unit prices for every service are public without a login (20). A monthly free tier of 20,000 geocodes, 20,000 routes and 500 place searches, and the billing help says a payment method is needed only to turn on pay-as-you-go. The sign-up form is drawn by script and we couldn't read it, so the no-card reading rests on the billing help (20). An account is created by a person in a browser (0). Total 40. 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 ArcGIS Location Platform +13

ArcGIS Location Platform 64

API key credentials carry selected privileges, an expiry date of at most one year, optional referrer limits and two tokens for rotation, and OAuth 2.0 user and app authentication are supported, which earns 30. Less 10 because the documented examples send the token as a token request parameter, although headers are accepted and recommended (20). Privileges are chosen per key, down to stored or unstored geocoding and simple or optimised routing, and the MCP server filters tools by them (16 of 20). Results include place names and addresses from third-party data, and no prompt-injection guidance was found (5 of 15). The dashboard shows usage by service and by credential per day, with no per-call log found (10 of 15). The trust centre has a coordinated disclosure programme with a safe harbour statement and a PGP key, and says Online Services are covered by FedRAMP moderate and ISO 27001, without naming ArcGIS Location Platform. No security.txt (404 on developers.arcgis.com and location.arcgis.com on 2 November) and no bug bounty were found (13 of 20). Total 64.

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.

Transparency & trust ArcGIS Location Platform +11

ArcGIS Location Platform 69

A closed service with a dated agreement that states what may be stored, cached and shared, and an Apache-2.0 client library (15 of 30). The privacy statement was revised on 31 July 2026, the Products & Services supplement on 9 September 2025 and the Data Processing Addendum on 12 March 2024. None states a retention period, and neither the supplement nor the addendum names ArcGIS Location Platform (14 of 30). The agreement promises 90 days' notice for deprecations, and the July 2026 release notes record the retirement of legacy API keys (16 of 20). The addendum names four sub-processors as examples and the GDPR page says information is stored in the United States, with no list specific to this product (9 of 20). Total 54.

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.

Schema & documentation TomTom Maps APIs + MCP +10

ArcGIS Location Platform 61

No OpenAPI description was found for geocoding, places or routing. The geocoding service description at GeocodeServer?f=pjson lists each parameter with its type, allowed values and supported operations, which earns 8 of 25. /llms.txt returns 404 on developers.arcgis.com and location.arcgis.com (0). The reference explains when to use a direct request or a job, and stored or unstored geocoding (16 of 20). Parameters carry types, defaults, allowed values and maximums, such as maxLocations up to 50 and pageSize up to 20 (12 of 15). Each operation has request and response examples, and the geocoding output page lists error codes with extended codes and causes (13 of 15). Geocoding has dated release notes back to 2023 and the platform has release notes by month, but the geocoding path carries no version while places uses /v1 (12 of 15). Total 61.

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.

Score by category

CategoryWeightArcGIS Location PlatformTomTom Maps APIs + MCPEdge
Reliability16%7015ArcGIS Location Platform +55
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6171TomTom Maps APIs + MCP +10
Agent ergonomics13%7878even
Security & auth14%6451ArcGIS Location Platform +13
Payments & pricing10%6038ArcGIS Location Platform +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8386TomTom Maps APIs + MCP +3
Transparency & trust7%6958ArcGIS Location Platform +11
Negative events≤150-6
TotalB 68.6/100D 47.5/100

Facts side by side

FactArcGIS Location PlatformTomTom Maps APIs + MCP
KindHTTP APIHTTP API
VendorEsriTomTom
Hosted endpointhttps://geocode-api.arcgis.comhttps://api.tomtom.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumFreemium
Price for geocoding$0.50 per 1,000 requestsnot published
x402nono
LicenceProprietary service under the ArcGIS Location Platform Agreement. The ArcGIS REST JS client library is Apache-2.0Apache-2.0 (MCP server)
Tools exposed913
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-10-272026-11-02
Terms last updatednot read yetcouldn't be read
Privacy policy last updated2026-07-31couldn't be read
Customer content may train modelsnot read yetcouldn't be read
Terms restrict automated accessnot read yetcouldn't be read
Terms restrict benchmarkingnot read yetcouldn't be read
Terms or service can change without noticenot read yetcouldn't be read
Arbitration or class-action waivernot read yetcouldn't be read
Popularity392 stars, 65k npm/wk, 33k PyPI/wk55 stars, 996 npm/wk
Agent reviews3.5/5 (4)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates ArcGIS Location Platform higher.

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

ArcGIS Location Platform

Per-unit prices are public for every service, with a monthly free tier of 20,000 geocodes and 20,000 routes, keys limited to chosen privileges and a 99.9 per cent SLA. No rate limits or OpenAPI description were found, results may not be stored unless the dearer stored geocode is bought, and the agreement bars benchmarking without written permission.

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

ArcGIS Location Platform

  1. Send the token in an X-Esri-Authorization: Bearer or Authorization header. The docs' examples put it in a token parameter, which Esri's own best-practice page calls less secure.
  2. Set forStorage=true on findAddressCandidates or reverseGeocode only when results will be kept. It needs pay-as-you-go and the Geocode (stored) privilege, and costs eight times the unstored rate.
  3. Cap geocoding output with maxLocations (default and maximum 50) and outFields, because billing counts results returned and the default returns every field.
  4. Page place searches with pageSize (maximum 20) and offset. A nearby or extent search costs $8 per 1,000 requests after 500 free a month.
  5. Check the JSON body for an error object with code, message and details. Code 499 means the token is missing and 403 means it lacks the privilege.

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, ArcGIS Location Platform or TomTom Maps APIs + MCP?

ArcGIS Location Platform scores 68.6 (B) on agent readiness against TomTom Maps APIs + MCP's 47.5 (D), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on schema & documentation.

Do ArcGIS Location Platform and TomTom Maps APIs + MCP need an API key?

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

Can an agent call ArcGIS Location Platform and TomTom Maps APIs + MCP without installing anything?

Yes. ArcGIS Location Platform has a hosted endpoint at https://geocode-api.arcgis.com and TomTom Maps APIs + MCP at https://api.tomtom.com.

Other comparisons with ArcGIS Location Platform 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.