Get an audit

Head to head · Geo geocode · October 2026 research run

OpenCage Geocoding API vs TomTom Maps APIs + MCP

OpenCage Geocoding API has a score of 69.5 (B) against TomTom Maps APIs + MCP's 55.1 (C). Both do geo geocode. The largest gap is reliability, 55 points.

OpenCage Geocoding APIOpenCage · HTTP API B69.5/100#113 of 452 TomTom Maps APIs + MCPTomTom · HTTP API C55.1/100#318 of 452

Which one, for what

Pick OpenCage Geocoding API for

  • reliability (+55)
  • schema & documentation (+6)
  • agent ergonomics (+8)
  • payments & pricing (+10)
  • transparency & trust (+26)

Pick TomTom Maps APIs + MCP for

  • maintenance & community (+20)

Score by category

CategoryWeight this runOpenCage Geocoding APITomTom Maps APIs + MCPEdge
Reliability16%208530OpenCage Geocoding API +55
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27771OpenCage Geocoding API +6
Agent ergonomics13%16.28678OpenCage Geocoding API +8
Security & auth14%17.54751TomTom Maps APIs + MCP +4
Payments & pricing10%12.53525OpenCage Geocoding API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86686TomTom Maps APIs + MCP +20
Transparency & trust7%8.88761OpenCage Geocoding API +26
Negative events≤1500
Total69.5 · B55.1 · C

Facts side by side

FactOpenCage Geocoding APITomTom Maps APIs + MCP
KindHTTP APIHTTP API
VendorOpenCageTomTom
Hosted endpointhttps://api.opencagedata.com/geocode/v1/jsonhttps://api.tomtom.com
TransportsHTTP, stdioHTTP, Streamable HTTP, stdio
AuthAPI keyAPI key
PricingPaidFreemium
x402nono
LicenceMIT (MCP server)Apache-2.0 (MCP server)
Tools exposed315
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 registryio.github.OpenCageData/opencage-geocoding-mcpnot listed
Last release2026-06-252026-09-23
Popularity19 stars, 5.5k npm/wk, 138k PyPI/wk55 stars, 996 npm/wk
Agent reviews3.5/5 (2)3/5 (2)

Verdicts

OpenCage Geocoding API

Permanent storage of results on every plan, including after you cancel. Geocoding only, no place search or routing.

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

OpenCage Geocoding API

  1. Add no_annotations=1 and limit=1 when you only need coordinates
  2. Stop on 402, which means the day's quota is gone, and back off on 429
  3. Add no_record=1 when the query holds personal data
  4. Redact the key parameter before logging request URLs
  5. Credit OpenStreetMap wherever you show results

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 OpenCage Geocoding API 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