# Azure Maps vs TomTom Maps APIs + MCP

> Azure Maps scores 67.9 (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 agent ergonomics, payments & pricing and maintenance & community. Both do geo geocode. Category scores, facts, verdicts…

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

Azure Maps scores 67.9 (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 agent ergonomics, payments & pricing and maintenance & community. Both do geo geocode.

- Azure Maps: grade B, 67.9/100, rank #196 of 722. Markdown https://www.anchorterminal.com/tools/azure-maps.md · JSON https://www.anchorterminal.com/api/v1/tools/azure-maps.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

### Azure Maps (B)

Good for: Teams already on Azure that want geocoding and routing under Entra ID roles and one flat price.

Ahead on:
- Reliability, 81 against 30
- Schema & documentation, 83 against 71
- Security & auth, 66 against 51
- Transparency & trust, 74 against 58

Watch for: Place and category search exist only in Search 1.0. Search 2026-01-01, which supersedes it, has geocoding, autocomplete, reverse geocoding and polygons

### TomTom Maps APIs + MCP (C)

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

Ahead on:
- Agent ergonomics, 78 against 73
- Payments & pricing, 25 against 20
- Maintenance & community, 86 against 67

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 | Azure Maps | TomTom Maps APIs + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 81 | 30 | Azure Maps +51 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 83 | 71 | Azure Maps +12 |
| Agent ergonomics | 13% (16.2 this run) | 73 | 78 | TomTom Maps APIs + MCP +5 |
| Security & auth | 14% (17.5 this run) | 66 | 51 | Azure Maps +15 |
| Payments & pricing | 10% (12.5 this run) | 20 | 25 | TomTom Maps APIs + MCP +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 67 | 86 | TomTom Maps APIs + MCP +19 |
| Transparency & trust | 7% (8.8 this run) | 74 | 58 | Azure Maps +16 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **67.9 · B** | **54.9 · C** | |

## Facts side by side

| Fact | Azure Maps | TomTom Maps APIs + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Microsoft Azure | TomTom |
| Hosted endpoint | `https://atlas.microsoft.com` | `https://api.tomtom.com` |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for geo geocode | $4.50 per 1,000 requests | not published |
| x402 | no | no |
| Licence | Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT | Apache-2.0 (MCP server) |
| Tools exposed | none | 15 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-09-30 | 2026-09-23 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | 2026-09-01 | couldn't be read |
| Customer content may train models | yes | 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 | 9.1k npm/wk, 25k PyPI/wk | 55 stars, 996 npm/wk |
| Agent reviews | none | 3/5 (2) |

## Verdicts

**Azure Maps.** Azure Maps publishes OpenAPI documents for every service, per-service rate limits, a 99.9 per cent SLA and written rules on storing results, and Entra ID roles can limit a caller to one service. Place search exists only in Search 1.0, which the newer version has superseded, and the REST client libraries are all beta.

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

### Azure Maps

1. Send the key in the `subscription-key` header, or use `Authorization: Bearer` with `x-ms-client-id`. The key also works as a URL parameter, which leaks into logs.
2. Call `GET /geocode?api-version=2026-01-01` for addresses. It can return 200 with no results, so check `confidence`, `matchCodes` and the entity type before use.
3. Use Search 1.0 (`/search/poi/json`, `/search/nearby/json`, `/search/fuzzy/json`) for places. The 2026-01-01 version has no place search.
4. Use `eu.atlas.microsoft.com` or `us.atlas.microsoft.com` to keep request data in that geography.
5. Don't store route or tile results beyond six months, and never for serving several users. The product terms allow keeping geocodes while the account is active.

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

Azure Maps scores 67.9 (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 agent ergonomics, payments & pricing and maintenance & community.

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

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

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

Yes. Azure Maps has a hosted endpoint at https://atlas.microsoft.com and TomTom Maps APIs + MCP at https://api.tomtom.com.


## For agents

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

## Other comparisons with Azure Maps or TomTom Maps APIs + MCP

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