Head to head · Geocoding · October 2026 research run

OpenCage Geocoding API vs TomTom Maps APIs + MCP

OpenCage Geocoding API scores 69.8 (B) on agent readiness against TomTom Maps APIs + MCP's 47.5 (D), and leads in 5 of 7 scored categories. TomTom Maps APIs + MCP leads on security & auth. Both do geocoding.

Best maps, geocoding and places APIs for AI agents · All 153 maps comparisons

Which one, for what

OpenCage Geocoding API B

Best for Bulk or repeated geocoding where results go into a database, and for EU data residency.

Ahead on

  • Reliability, 85 against 15
  • Schema & documentation, 77 against 71
  • Agent ergonomics, 86 against 78
  • Payments & pricing, 53 against 38
  • Transparency & trust, 85 against 58

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

Geocoding only, no place search or routing

TomTom Maps APIs + MCP D

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

Ahead on

  • Security & auth, 51 against 44

Watch for

Terms, rate limits and deprecation policy couldn't be read, so storage rules and notice periods are unverified

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability OpenCage Geocoding API +70

OpenCage Geocoding API 85

Instatus page at status.opencagedata.com, measured by StatusCake, with forward geocoding, reverse geocoding, geosearch, the website and email sending as components (20). The incident history feed, read on 1 November 2026, lists nothing since the 26 June 2026 email outage, so the last 90 days are clean (30). Free trial limits of 2,500 a day and 1 a second, and per-second rates for each paid plan (15). 402 for a spent quota and 429 for going too fast are separate codes, and free and one-time plans get X-RateLimit-Limit, -Remaining and -Reset. There's no backoff guidance beyond '408 means try again' (10). No SLA found (0). GA (10).

TomTom Maps APIs + MCP 15

TomTom's API status page sits on tomtom.service-now.com, whose robots.txt disallows every path on 4 November, so the earlier status readings are struck (0). With no history we may read, the record scores 5. No published QPS limits or 429 guidance were found on the docs pages we read on 1 October; TomTom's acceptable use policy now bars robots from its websites, so they weren't re-read (0). The MCP maps a 429 to a typed rate-limit error with a message, and we found nothing on Retry-After (5, the earlier partial kept). No SLA found (0). Orbis APIs went GA on 8 July 2026, but the remote MCP server is in public preview and the README says some Orbis and EV services may not be enabled on every account (5, kept). 0+5+0+5+0+5 = 15.

Transparency & trust OpenCage Geocoding API +27

OpenCage Geocoding API 85

Closed service with clear terms, an MIT MCP server and open-source SDKs (20). Results may be stored permanently, even after cancelling. Query logs are deleted after six months and never used to train AI, no_record turns query logging off, and the DPA is public on GitHub. The GDPR page was updated 22 July 2026 with its change history (30). A dated API changelog that announces deprecations, such as the jsonp parameter on 11 May 2026, which keeps working for existing customers. No written deprecation policy (14). Seven subprocessors with locations, and hosting at Hetzner in Germany and Finland with backups in Switzerland (20).

TomTom Maps APIs + MCP 58

Closed APIs with an Apache-2.0 MCP server. The developer terms page still renders client-side on 4 November, and TomTom's acceptable use policy (linked from its Terms of Use of 1 September 2025) bars data mining, robots and scraping on all TomTom websites, so the privacy and deprecation pages weren't re-read. Licence clarity 10, data handling 11 of 30, deprecation 8 and subprocessors 12 of 20 stand per the 2 October check, not re-read on 4 November. 10+11+8+12 = 41.

Payments & pricing OpenCage Geocoding API +15

OpenCage Geocoding API 53

No x402, MPP or L402 (0). Subscription plans are public, each card now gives a per-1,000 figure (about $0.17 on X-Small to $0.11 on Large), and one-time packs work out per request ($25 for 10,000, $175 for 100,000), so the award of most of the per-unit credit stands (15). A 2,500-a-day free trial with no card, for testing only (20). Signup is a browser flow (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

TomTom Maps APIs + MCP 38

No x402, MPP or L402 (0). Free allowances are public, but the pricing page re-read on 2 October showed no paid rate as a number, only a euro estimator and a contact-sales link (5 of 20, kept). A no-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with Search and Matrix at 2,500 (20). Signup is a browser flow (0). The pricing page is on a host whose acceptable use policy now bars robots, so it wasn't re-read on 4 November. 0+5+20+0 = 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Agent ergonomics OpenCage Geocoding API +8

OpenCage Geocoding API 86

Three compact MCP tools, and the API sizes its output with limit, no_annotations, abbrv and address_only (25). countrycode, bounds, proximity and min_confidence narrow results. No pagination, which a geocoder rarely needs (18). Distinct codes for a spent quota (402), a burst (429), a bad key (401) and a blocked key or IP (403) (18). Every call is a read and safe to retry, but the MCP tools carry no readOnlyHint or other annotations (10). One required parameter, sensible defaults, and official Python (3.5.0) and JavaScript (2.2.0) clients (15).

TomTom Maps APIs + MCP 78

13 model-visible tools on the Orbis backend plus four app-only helpers; since 1.6.12 clients known to render no MCP Apps don't get the map tools or app helpers (15). limit, countries, boundingBox, poiCategories and cursor paging on the search tools (16). Typed MCP errors for 400, 401, 403 and 429 with messages, and the 403 error says retrying won't help (15). The tools carry readOnlyHint true, destructiveHint false and idempotentHint true (20). Official map SDKs for web, Android and iOS but no Python client we found. show_ui defaults to true, which needs an MCP Apps client to render (12). 15+16+15+20+12 = 78.

Security & auth TomTom Maps APIs + MCP +7

OpenCage Geocoding API 44

Plain revocable keys that can be disabled or tied to IP addresses, which earns 20 with 2 back for the IP rules. Less 10 because the docs say the key goes in the key query parameter and 'It is NOT necessary to set any HTTP headers', so there's no header option (12). The API only reads, so there's nothing to approve (15). Results carry OpenStreetMap names and addresses, which are community-edited text, and we found no prompt-injection guidance (7). The MCP's get-opencage-info tool reports usage and rate state. We didn't check the dashboard's per-call visibility (3). A security policy page, a security@opencagedata.com contact and a SECURITY.md on GitHub. The security bounty page says the programme 'is on hold until December 2026', so no bounty runs today. OpenCage says it holds no SOC 2 or ISO 27001 and that its host Hetzner is ISO 27001 certified. security.txt couldn't be checked because robots.txt blocks it. That is below contactsplus (8, discretionary bounties running) (7).

TomTom Maps APIs + MCP 51

API keys from the developer portal, limited to the products selected for them, which earns 25. Less 10 because REST calls take the key as the key query parameter. The hosted MCP takes a tomtom-api-key header, and the source carries OAuth with an audience check that 1.6.13 made mandatory for OAuth deployments (15). Keys can be limited by product and every tool reads (16). Results include POI names and traffic incident text with no prompt-injection guidance. An app-only tool, tomtom-get-api-key, returns the raw key to the map app; since 1.6.12 clients that render no apps don't receive it (6, kept). We didn't find per-call logs or usage reporting we could read (0). HackerOne disclosure programme with a 3 business day first response in the organisation's SECURITY.md, Veracode scanning in CI, and no security.txt per the 30 September check (14, kept). 15+16+6+0+14 = 51.

Schema & documentation OpenCage Geocoding API +6

OpenCage Geocoding API 77

No OpenAPI. The MCP's three tools have JSON Schema inputs, and the REST API is one endpoint described parameter by parameter (15). llms.txt with 70 or more Markdown pages, including the API reference, pricing, terms and the MCP tutorial (10). The API reference explains each parameter and when to use it, but the MCP descriptions are one line each with no when-not-to-use (12). min and max on latitude, longitude and limit, but countrycode and bounds are free strings (10). A status code table and 23 tutorials across languages (15). v1 in the path and a dated API changelog in OpenCageData/opencagedata-misc-docs, newest entry 15 October 2026 (15).

TomTom Maps APIs + MCP 71

No public OpenAPI that we found. The MCP's tools have Zod schemas with described fields (22). docs.tomtom.com/llms.txt indexes about 180 pages, many as .md, per the 2 October check, not re-read on 4 November (10). Tool descriptions are mostly one line, with little on when not to use a tool (12). Typed fields with constraints, and since 1.6.12 the search, routing and EV tools list their valid values from the maps-sdk (11, kept). We couldn't read the REST error reference. The MCP returns typed errors per status code, and since 1.6.13 tells a 401 from a 403 (8). Versioned REST paths; the MCP CHANGELOG.md has dated entries from 1.6.11 (5 October 2026) to 1.6.14 and says 1.1.1 to 1.6.10 have none (8, kept). 22+10+12+11+8+8 = 71.

Score by category

CategoryWeightOpenCage Geocoding APITomTom Maps APIs + MCPEdge
Reliability16%8515OpenCage Geocoding API +70
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7771OpenCage Geocoding API +6
Agent ergonomics13%8678OpenCage Geocoding API +8
Security & auth14%4451TomTom Maps APIs + MCP +7
Payments & pricing10%5338OpenCage Geocoding API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8686even
Transparency & trust7%8558OpenCage Geocoding API +27
Negative events≤15-3-6
TotalB 69.8/100D 47.5/100

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 exposed313
Read-only variant documentednoyes
llms.txtyesyes
MCP registryio.github.OpenCageData/opencage-geocoding-mcpnot listed
Last release2026-10-282026-11-02
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn'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
Popularity19 stars, 5.5k npm/wk, 138k PyPI/wk55 stars, 996 npm/wk
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

OpenCage Geocoding API

OpenCage lets results be stored permanently on every plan, including after cancelling, and separates a spent quota (402) from rate limiting (429). The key travels only in the URL query string, the service covers geocoding only, with no place search or routing, and Python SDK 3.5.0 changed its exception types in a minor release.

TomTom Maps APIs + MCP

No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with an official MCP server released about weekly. Terms, rate limits and the deprecation policy couldn't be read, the status page bars our reader, and MCP patch releases in October removed tools and inputs without notice.

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, and redact the key parameter before logging request URLs
  4. On Python SDK 3.5.0 or later, catch NetworkError and NetworkTimeoutError instead of requests or aiohttp exceptions
  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. Pin @tomtom-org/tomtom-mcp to a version, since patch releases have removed tools and changed inputs
  3. Page search results with cursor and the previous response's nextCursor, not ofs, from 1.6.12
  4. Read a 403 as the account or key not covering the API, and don't retry it; a 401 means a missing or unknown key
  5. Redact the key parameter before logging REST URLs

Questions

Which is better for AI agents, OpenCage Geocoding API or TomTom Maps APIs + MCP?

OpenCage Geocoding API scores 69.8 (B) on agent readiness against TomTom Maps APIs + MCP's 47.5 (D), and leads in 5 of 7 scored categories. TomTom Maps APIs + MCP leads on security & auth.

Do OpenCage Geocoding API and TomTom Maps APIs + MCP need an API key?

Both need an API key.

Can an agent call OpenCage Geocoding API and TomTom Maps APIs + MCP without installing anything?

Yes. OpenCage Geocoding API has a hosted endpoint at https://api.opencagedata.com/geocode/v1/json and TomTom Maps APIs + MCP at https://api.tomtom.com.

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.