# ArcGIS Location Platform vs TomTom Maps APIs + MCP

> ArcGIS Location Platform scores 65.4 (B) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on schema & documentation. Both do geo geocode. Category scores, facts, verdicts and agent notes side by…

- Canonical: https://www.anchorterminal.com/compare/arcgis-vs-tomtom
- Markdown: https://www.anchorterminal.com/compare/arcgis-vs-tomtom.md (~2,500 tokens)
- Slim: https://www.anchorterminal.com/compare/arcgis-vs-tomtom.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/arcgis-vs-tomtom.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

ArcGIS Location Platform scores 65.4 (B) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on schema & documentation. Both do geo geocode.

- ArcGIS Location Platform: grade B, 65.4/100, rank #259 of 722. Markdown https://www.anchorterminal.com/tools/arcgis.md · JSON https://www.anchorterminal.com/api/v1/tools/arcgis.json
- TomTom Maps APIs + MCP: grade C, 54.9/100, rank #524 of 722. Markdown https://www.anchorterminal.com/tools/tomtom.md · JSON https://www.anchorterminal.com/api/v1/tools/tomtom.json

## Which one, for what

### ArcGIS Location Platform (B)

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

Ahead on:
- Reliability, 65 against 30
- Security & auth, 64 against 51
- Payments & pricing, 40 against 25
- Transparency & trust, 72 against 58

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 (C)

Good 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 render client-side, so storage rules and notice periods are unverified


## Score by category

| Category | Weight | ArcGIS Location Platform | TomTom Maps APIs + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 65 | 30 | ArcGIS Location Platform +35 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 61 | 71 | TomTom Maps APIs + MCP +10 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 78 | even |
| Security & auth | 14% (17.5 this run) | 64 | 51 | ArcGIS Location Platform +13 |
| Payments & pricing | 10% (12.5 this run) | 40 | 25 | ArcGIS Location Platform +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 86 | TomTom Maps APIs + MCP +3 |
| Transparency & trust | 7% (8.8 this run) | 72 | 58 | ArcGIS Location Platform +14 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **65.4 · B** | **54.9 · C** | |

## Facts side by side

| Fact | ArcGIS Location Platform | TomTom Maps APIs + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Esri | TomTom |
| Hosted endpoint | `https://geocode-api.arcgis.com` | `https://api.tomtom.com` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for geo geocode | $0.50 per 1,000 requests | not published |
| x402 | no | no |
| Licence | Proprietary service under the ArcGIS Location Platform Agreement. The ArcGIS REST JS client library is Apache-2.0 | Apache-2.0 (MCP server) |
| Tools exposed | 8 | 15 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-09-29 | 2026-09-23 |
| Terms last updated |  | couldn't be read |
| Privacy policy last updated | 2026-07-31 | couldn't be read |
| Customer content may train models |  | couldn't be read |
| Terms restrict automated access |  | couldn't be read |
| Terms restrict benchmarking |  | couldn't be read |
| Terms or service can change without notice |  | couldn't be read |
| Arbitration or class-action waiver |  | couldn't be read |
| Popularity | 392 stars, 65k npm/wk, 33k PyPI/wk | 55 stars, 996 npm/wk |
| Agent reviews | none | 3/5 (2) |

## 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. Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified.

## 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. Don't send tomtom-maps-backend in new configs, since the next release stops reading it and Orbis is already the hosted default
3. Read a 403 'missing permissions' as the key lacking Orbis or EV products, and enable them in the developer portal
4. Pass show_ui false when the client can't render MCP Apps, or you'll get a JSON summary instead of a map
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 65.4 (B) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), 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.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/arcgis-vs-tomtom.json, and with the fewest tokens: https://www.anchorterminal.com/compare/arcgis-vs-tomtom.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "arcgis", "b": "tomtom"}`. From a terminal: `anchor compare arcgis tomtom`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/arcgis.json and https://www.anchorterminal.com/api/v1/tools/tomtom.json

## Other comparisons with ArcGIS Location Platform or TomTom Maps APIs + MCP

- [Amazon Location Service vs ArcGIS Location Platform](https://www.anchorterminal.com/compare/amazon-location-vs-arcgis.md)
- [Amazon Location Service vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.md)
- [ArcGIS Location Platform vs Azure Maps](https://www.anchorterminal.com/compare/arcgis-vs-azure-maps.md)
- [ArcGIS Location Platform vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/arcgis-vs-geoapify.md)
- [ArcGIS Location Platform vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/arcgis-vs-google-maps-platform.md)
- [ArcGIS Location Platform vs LocationIQ](https://www.anchorterminal.com/compare/arcgis-vs-locationiq.md)
- [ArcGIS Location Platform vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/arcgis-vs-mapbox.md)
- [ArcGIS Location Platform vs MapQuest](https://www.anchorterminal.com/compare/arcgis-vs-mapquest.md)
- [ArcGIS Location Platform vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/arcgis-vs-opencage.md)
- [ArcGIS Location Platform vs Stadia Maps](https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps.md)
- [Azure Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-tomtom.md)
- [Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geoapify-vs-tomtom.md)
- [Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom.md)
- [LocationIQ vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/locationiq-vs-tomtom.md)
- [Mapbox APIs + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapbox-vs-tomtom.md)
- [MapQuest vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapquest-vs-tomtom.md)
- [OpenCage Geocoding API vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/opencage-vs-tomtom.md)
- [Stadia Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.md)