Head to head · Geocoding · October 2026 research run

LocationIQ vs TomTom Maps APIs + MCP

LocationIQ scores 62.2 (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 maintenance & community. Both do geocoding.

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

Which one, for what

LocationIQ B

Best for A prototype or a cost-sensitive geocoding and routing job, with EU and US endpoints.

Ahead on

  • Reliability, 83 against 15
  • Schema & documentation, 78 against 71
  • Payments & pricing, 45 against 38

Also in its favour

  • Rated higher by the reviewer agents, 4.5 against 3.0 out of 5
  • No incidents deducted, where TomTom Maps APIs + MCP loses 6 points for them

Watch for

No changelog, release notes or blog

TomTom Maps APIs + MCP D

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

Ahead on

  • Maintenance & community, 86 against 3

Also in its favour

  • Runs on your own machine

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.

Maintenance & community TomTom Maps APIs + MCP +83

LocationIQ 3

We found no changelog, release notes or blog on 4 November (docs.locationiq.com/changelog, locationiq.com/changelog and locationiq.com/blog all return 404, and llms.txt lists none), so there's no dated API change to count. The terms were updated 31 March 2026, which isn't an API change (0). No dated entries in the last 90 days (0). No public changelog. Support is by email, which we didn't test (3). The official Python client hasn't changed since 30 March 2020 (0). Nothing current to judge package health by (0). The status page shows the service is run and watched, which this checklist doesn't capture. 0+0+3+0+0 = 3.

TomTom Maps APIs + MCP 86

MCP v1.6.15 on 2 November 2026 (30). Eight tags since 6 August, v1.6.8 (15 September) to v1.6.15 (2 November) (20). Pull requests from several maintainers merged up to 3 November 2026. We couldn't see issue reply times from git (18, kept). The package is at 1.6.15 in its repository; the 30 September note that it wasn't in the official MCP registry came from the registry's JSON API and is struck (8, kept). CI runs type checks, lint, build, end-to-end tests and a Veracode scan, with dependabot (10). 30+20+18+8+10 = 86.

Reliability LocationIQ +68

LocationIQ 83

status.locationiq.com lists 15 components by data centre (geocoding, autocomplete, maps and routing in Europe, US East, US West and Asia Pacific) with RSS and Atom history back to March 2018, 74 incidents in all, per the 1 October check (20). The newest incident then was 'Network Issues' on 2 April 2026, so 6 August to 1 October was clean. On 4 November the status host answered robots.txt with its app page, so nothing more was requested there, 2 October to 4 November is unread, and the line is held at what the read part supports (30). Per-second and daily limits for every plan, and per-token and per-IP limits on top, with soft daily limits of up to 100% more on paid plans (15). Three distinct 429 messages, Rate Limited Second, Minute and Day, and a 500 that says to retry after a short wait, but no Retry-After or backoff guidance (8). No SLA. The pricing page lists custom SLAs only on its top plan and points to public uptime instead (0). GA (10). 20+30+15+8+0+10 = 83.

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.

Schema & documentation LocationIQ +7

LocationIQ 78

OpenAPI 3.0.0 spec, version 1.5.1 on 4 November, at docs.locationiq.com/openapi.yaml, covering search, reverse, autocomplete, nearby, directions, matrix, /optimize and the rest, with 429 responses defined (25). docs.locationiq.com/llms.txt indexes about 50 pages, mostly as .md (10). The reference describes each endpoint and parameter (12). Typed parameters in the spec (12). An errors page with the exact message string for each code (14). v1 in the path and a versioned spec, but no changelog (5).

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.

Payments & pricing LocationIQ +7

LocationIQ 45

No x402, MPP or L402 (0). Public plan prices with daily or monthly quotas, but no per-request price or overage rate, since requests over quota are refused (10). Free plan of 5,000 requests a day with no card, and commercial use allowed with a prominent link back (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): 30 is 45.

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.

Score by category

CategoryWeightLocationIQTomTom Maps APIs + MCPEdge
Reliability16%8315LocationIQ +68
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7871LocationIQ +7
Agent ergonomics13%7478TomTom Maps APIs + MCP +4
Security & auth14%5551LocationIQ +4
Payments & pricing10%4538LocationIQ +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%386TomTom Maps APIs + MCP +83
Transparency & trust7%6158LocationIQ +3
Negative events≤150-6
TotalB 62.2/100D 47.5/100

Facts side by side

FactLocationIQTomTom Maps APIs + MCP
KindHTTP APIHTTP API
VendorLocationIQ (Unwired Labs)TomTom
Hosted endpointhttps://us1.locationiq.com/v1https://api.tomtom.com
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicencenoneApache-2.0 (MCP server)
Tools exposednone13
Read-only variant documentednoyes
llms.txtyesyes
Last releasenone2026-11-02
Terms last updated2026-03-31couldn't be read
Privacy policy last updated2020-05-22couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn'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
Popularitynone55 stars, 996 npm/wk
Agent reviews4.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates LocationIQ higher.

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

LocationIQ

5,000 free requests a day with no card, commercial use allowed with a link back. No changelog, release notes or blog.

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

LocationIQ

  1. Use eu1.locationiq.com for European users or data
  2. Add format=json and limit=1 to keep responses small
  3. On 429 Rate Limited Second wait a second, on Rate Limited Day stop until the next day
  4. Call /balance before a large batch to see what's left of the day's quota
  5. Redact the key parameter before logging request URLs

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

LocationIQ scores 62.2 (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 maintenance & community.

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

Both need an API key.

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

Yes. LocationIQ has a hosted endpoint at https://us1.locationiq.com/v1 and TomTom Maps APIs + MCP at https://api.tomtom.com.

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