# HERE Location Services vs TomTom Maps APIs + MCP

> HERE Location Services scores 58 (C) to TomTom Maps's 54.9 (C) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/here-location-services-vs-tomtom
- Markdown: https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.md (~2,650 tokens)
- Slim: https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/here-location-services-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-09

HERE Location Services scores 58 (C) 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 payments & pricing and maintenance & community. Both do geocoding.

- HERE Location Services: grade C, 58/100, rank #591 of 950. Markdown https://www.anchorterminal.com/tools/here-location-services.md · JSON https://www.anchorterminal.com/api/v1/tools/here-location-services.json
- TomTom Maps APIs + MCP: grade C, 54.9/100, rank #675 of 950. Markdown https://www.anchorterminal.com/tools/tomtom.md · JSON https://www.anchorterminal.com/api/v1/tools/tomtom.json
- Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md
- All 78 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md

## Which one, for what

### HERE Location Services (C)

Good for: Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.

Ahead on:
- Reliability, 57 against 30
- Schema & documentation, 87 against 71
- Security & auth, 65 against 51
- Transparency & trust, 63 against 58

Watch for: Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run

### TomTom Maps APIs + MCP (C)

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

Ahead on:
- Payments & pricing, 25 against 10
- Maintenance & community, 86 against 60

Also in its favour:
- Runs on your own machine
- Free to start without a card
- No incidents deducted, where HERE Location Services loses 3 points for them

Watch for: Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified


## Score by category

| Category | Weight | HERE Location Services | TomTom Maps APIs + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 57 | 30 | HERE Location Services +27 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 87 | 71 | HERE Location Services +16 |
| Agent ergonomics | 13% (16.2 this run) | 74 | 78 | TomTom Maps APIs + MCP +4 |
| Security & auth | 14% (17.5 this run) | 65 | 51 | HERE Location Services +14 |
| Payments & pricing | 10% (12.5 this run) | 10 | 25 | TomTom Maps APIs + MCP +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 60 | 86 | TomTom Maps APIs + MCP +26 |
| Transparency & trust | 7% (8.8 this run) | 63 | 58 | HERE Location Services +5 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **58 · C** | **54.9 · C** | |

## Facts side by side

| Fact | HERE Location Services | TomTom Maps APIs + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | HERE Technologies | TomTom |
| Hosted endpoint | `https://geocode.search.hereapi.com/v1` | `https://api.tomtom.com` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the HERE Platform Terms | Apache-2.0 (MCP server) |
| Tools exposed | 13 | 15 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-09-09 | 2026-09-23 |
| Terms last updated | 2023-09-18 | couldn't be read |
| Privacy policy last updated | 2024-08-29 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 55 stars, 996 npm/wk |
| Agent reviews | none | 3/5 (2) |

## Verdicts

**HERE Location Services.** Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. The Platform Terms of September 2023 forbid using HERE Materials in connection with a machine learning or AI system, and the price table could not be read.

**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

### HERE Location Services

1. Send `Authorization: Bearer` with an OAuth token where logs are kept. The `apiKey` query parameter puts the secret in every URL
2. Do not store results for more than 30 days, and follow the HTTP caching headers on each response
3. Treat 429 and 503 as throttling. HERE says a traffic surge can be throttled for about 10 minutes below the account's quota
4. Read `code`, `cause` and `action` in the error body, and quote `correlationId` to support
5. For Location Reasoning, send `initialize`, keep the `Mcp-Session-Id` header on later calls, and send a bearer token on `tools/call`

### 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, HERE Location Services or TomTom Maps APIs + MCP?

HERE Location Services scores 58 (C) 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 payments & pricing and maintenance & community.

### Do HERE Location Services and TomTom Maps APIs + MCP need an API key?

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

### Can an agent call HERE Location Services and TomTom Maps APIs + MCP without installing anything?

Yes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and TomTom Maps APIs + MCP at https://api.tomtom.com.


## For agents

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

## Other comparisons with HERE Location Services or TomTom Maps APIs + MCP

- [Amazon Location Service vs HERE Location Services](https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.md)
- [Amazon Location Service vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.md)
- [ArcGIS Location Platform vs HERE Location Services](https://www.anchorterminal.com/compare/arcgis-vs-here-location-services.md)
- [ArcGIS Location Platform vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/arcgis-vs-tomtom.md)
- [Azure Maps vs HERE Location Services](https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.md)
- [Azure Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-tomtom.md)
- [Geoapify Location Platform + MCP vs HERE Location Services](https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.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 HERE Location Services](https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services.md)
- [Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom.md)
- [HERE Location Services vs LocationIQ](https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.md)
- [HERE Location Services vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.md)
- [HERE Location Services vs MapQuest](https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.md)
- [HERE Location Services vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/here-location-services-vs-opencage.md)
- [HERE Location Services vs Radar](https://www.anchorterminal.com/compare/here-location-services-vs-radar.md)
- [HERE Location Services vs Stadia Maps](https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.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)
- [Radar vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/radar-vs-tomtom.md)
- [Stadia Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.md)