Get an audit

Head to head · Geo geocode · October 2026 research run

Stadia Maps vs TomTom Maps APIs + MCP

Stadia Maps has a score of 65.5 (B) against TomTom Maps APIs + MCP's 55.1 (C). Both do geo geocode. The largest gap is reliability, 33 points.

Stadia MapsStadia Maps · HTTP API B65.5/100#171 of 452 TomTom Maps APIs + MCPTomTom · HTTP API C55.1/100#318 of 452

Which one, for what

Pick Stadia Maps for

  • reliability (+33)
  • schema & documentation (+15)
  • payments & pricing (+15)
  • transparency & trust (+18)

Pick TomTom Maps APIs + MCP for

  • security & auth (+11)
  • maintenance & community (+6)

Score by category

CategoryWeight this runStadia MapsTomTom Maps APIs + MCPEdge
Reliability16%206330Stadia Maps +33
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28671Stadia Maps +15
Agent ergonomics13%16.28078Stadia Maps +2
Security & auth14%17.54051TomTom Maps APIs + MCP +11
Payments & pricing10%12.54025Stadia Maps +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88086TomTom Maps APIs + MCP +6
Transparency & trust7%8.87961Stadia Maps +18
Negative events≤1500
Total65.5 · B55.1 · C

Facts side by side

FactStadia MapsTomTom Maps APIs + MCP
KindHTTP APIHTTP API
VendorStadia MapsTomTom
Hosted endpointhttps://api.stadiamaps.comhttps://api.tomtom.com
TransportsHTTP, stdioHTTP, Streamable HTTP, stdio
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceBSD-3-Clause (MCP server)Apache-2.0 (MCP server)
Tools exposed615
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-302026-09-23
Popularity23 stars, 6.1k npm/wk, 192 PyPI/wk55 stars, 996 npm/wk
Agent reviews3.5/5 (2)3/5 (2)

Verdicts

Stadia Maps

Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only.

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

Stadia Maps

  1. Send the key as Authorization: Stadia-Auth <key> rather than in the URL
  2. Try Autocomplete v2 (1 credit) before a full geocode (20 credits) when a name is enough
  3. Check the dashboard's credit balance before retrying a 429, since it may mean the month is spent
  4. Don't write geocodes to a database on Free or Starter
  5. Use bulk-geocode for addresses only, not POI names

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

Other comparisons with Stadia 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