Get an audit

Head to head · Geo geocode · October 2026 research run

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.

Azure MapsMicrosoft Azure · HTTP API B67.9/100#196 of 722 TomTom Maps APIs + MCPTomTom · HTTP API C54.9/100#524 of 722

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

CategoryWeight this runAzure MapsTomTom Maps APIs + MCPEdge
Reliability16%208130Azure Maps +51
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28371Azure Maps +12
Agent ergonomics13%16.27378TomTom Maps APIs + MCP +5
Security & auth14%17.56651Azure Maps +15
Payments & pricing10%12.52025TomTom Maps APIs + MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86786TomTom Maps APIs + MCP +19
Transparency & trust7%8.87458Azure Maps +16
Negative events≤1500
Total67.9 · B54.9 · C

Facts side by side

FactAzure MapsTomTom Maps APIs + MCP
KindHTTP APIHTTP API
VendorMicrosoft AzureTomTom
Hosted endpointhttps://atlas.microsoft.comhttps://api.tomtom.com
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumFreemium
Price for geo geocode$4.50 per 1,000 requestsnot published
x402nono
LicenceProprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MITApache-2.0 (MCP server)
Tools exposednone15
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-09-302026-09-23
Terms last updatedno date givencouldn't be read
Privacy policy last updated2026-09-01couldn't be read
Customer content may train modelsyescouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity9.1k npm/wk, 25k PyPI/wk55 stars, 996 npm/wk
Agent reviewsnone3/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.

Other comparisons with Azure Maps 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.

Get an auditSee a sample report