Head to head · Geocoding · October 2026 research run

Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP

Geoapify Location Platform + MCP scores 60 (C) on agent readiness against TomTom Maps APIs + MCP's 47.5 (D), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on agent ergonomics, security & auth and maintenance & community. Both do geocoding.

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

Which one, for what

Geoapify Location Platform + MCP C

Best for Cheap geocoding, category place search, routing and isolines on OpenStreetMap data, with commercial use on the free plan and EU hosting.

Ahead on

  • Reliability, 60 against 15
  • Schema & documentation, 84 against 71
  • Payments & pricing, 45 against 38
  • Transparency & trust, 67 against 58

Also in its favour

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

Watch for

No security.txt, disclosure policy, bug bounty or certification found

TomTom Maps APIs + MCP D

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

Ahead on

  • Agent ergonomics, 78 against 72
  • Security & auth, 51 against 29
  • Maintenance & community, 86 against 69

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.

Reliability Geoapify Location Platform + MCP +45

Geoapify Location Platform + MCP 60

status.geoapify.com redirects to an UptimeRobot page. On 4 November its HTML again showed only an error fetching the data, which the page loads from stats.uptimerobot.com/api/, a path that host's robots.txt closes, so no component or incident was read. The page keeps its first award of 15 of 20 while the UptimeRobot split stays open, and 5 for a history we couldn't read (our limit, not a finding against Geoapify). Per-plan rates are published, 5 requests a second on Free up to 30 on API 250 (15). 429 is in the OpenAPI specs as 'Rate limit or quota exceeded' with a JSON body, but there's no Retry-After or backoff guidance, and the pricing page says limits are soft and Geoapify doesn't throttle in general (7, an earlier partial kept). The terms say all paid plans include a default SLA of 99.5 per cent monthly availability, with a 10 per cent discount below it and 50 per cent below 99 per cent (10). The APIs are GA. The MCP page gives no launch stage (8, an earlier partial kept). 15+5+15+7+10+8 = 60.

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.

Security & auth TomTom Maps APIs + MCP +22

Geoapify Location Platform + MCP 29

Plain API keys per project, which earns 20. Less the checklist's fixed 10 because the specs call the apiKey query parameter 'Recommended authentication method for public APIs'. The x-api-key header works too and the spec warns that keys in URLs can be logged (10). The APIs only read (12). Results are OpenStreetMap names and addresses, community-edited text, with no prompt-injection guidance (7). We didn't find per-call logs we could read (0). www.geoapify.com/.well-known/security.txt returned 404 on 4 November, and we found no disclosure policy, bug bounty or certification (0). 10+12+7+0+0 = 29.

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.

Maintenance & community TomTom Maps APIs + MCP +17

Geoapify Location Platform + MCP 69

The What's new page dates two API entries on 2 November 2026 (Marker Icon API and Static Maps API marker options), two days before this check (30). In the 90 days from 6 August it lists API or MCP changes on 6 August (MCP Places and Routing tools), 28 August (MCP geometry operations), 23 October (Timezone API and get_timezone tool) and 2 November (two), and the OpenAPI repository has commits on 1, 2 and 25 September and 16, 23 and 30 October (20, from 15). A public changelog with an RSS feed and email support on paid plans. We didn't test support response (8 of 15, from 5). The JavaScript libraries are current, with geocoder-autocomplete at v3.1.0 on 27 July 2026, and the official MCP isn't in the MCP registry (6). The autocomplete SDK carries Jest tests (5). 30+20+8+6+5 = 69.

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.

Schema & documentation Geoapify Location Platform + MCP +13

Geoapify Location Platform + MCP 84

OpenAPI 3.1 specs for 22 APIs and a separate spec per MCP tool in geoapify/geoapify-openapi-specs, with documented 400, 401, 429 and 500 responses, and the repository added the Timezone API on 23 October 2026 (25). apidocs.geoapify.com/llms.txt still serves the HTML home page on 4 November, and we found no Markdown docs for agents (0). The MCP page's 12 tools each carry a 'when to use' line and name the sibling tool to use instead, for example calculate_route_matrix sends you to calculate_route for geometry (18). Typed parameters with limits such as limit at most 100, and enums for type and format (13). Error examples in the specs, such as '"limit" must be less than or equal to 100', and a playground per API (13). v1 and v2 paths, versioned specs, and a dated public changelog at www.geoapify.com/news-and-updates/ with entries back to September 2022 and an RSS feed, which the 1 October check missed (15, from 5). 25+0+18+13+13+15 = 84.

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.

Transparency & trust Geoapify Location Platform + MCP +9

Geoapify Location Platform + MCP 67

Editorial half only. Closed service with readable terms, still version 5 of 2 February 2024 on 4 November, under Cypriot law (15). The privacy policy says data for successful requests is held no longer than 24 hours and that servers are hosted by Hetzner, with custom DPAs on request (possibly at a cost). The docs say Places and Batch results can be cached or stored with no limits, while the terms say nothing on storage (22). No deprecation policy or dated deprecation notice on the What's new page, and the terms reserve the right to suspend, terminate or change the Service at any time without notice (0). Six processors named, including Hetzner (Germany), Cloudflare and Google Firebase, without locations for most (15). 15+22+0+15 = 52.

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 Geoapify Location Platform + MCP +7

Geoapify Location Platform + MCP 45

No x402, MPP or L402 (0). Public plan prices with credit costs per request (1 credit for a simple geocode, place search, route or timezone lookup), but no per-unit overage price, since limits are soft and Geoapify asks heavy users to upgrade (10). Free plan of 3,000 credits a day with 'No credit card required', and commercial use allowed with attribution (20). Signup is a browser flow (0). 0+10+20+0 = 30. 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

CategoryWeightGeoapify Location Platform + MCPTomTom Maps APIs + MCPEdge
Reliability16%6015Geoapify Location Platform + MCP +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8471Geoapify Location Platform + MCP +13
Agent ergonomics13%7278TomTom Maps APIs + MCP +6
Security & auth14%2951TomTom Maps APIs + MCP +22
Payments & pricing10%4538Geoapify Location Platform + MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6986TomTom Maps APIs + MCP +17
Transparency & trust7%6758Geoapify Location Platform + MCP +9
Negative events≤150-6
TotalC 60/100D 47.5/100

Facts side by side

FactGeoapify Location Platform + MCPTomTom Maps APIs + MCP
KindHTTP APIHTTP API
VendorGeoapifyTomTom
Hosted endpointhttps://api.geoapify.com/v1https://api.tomtom.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicencenoneApache-2.0 (MCP server)
Tools exposed1213
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-11-022026-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 noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularitynone55 stars, 996 npm/wk
Agent reviews4/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Geoapify Location Platform + MCP 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

Geoapify Location Platform + MCP

Free plan allows commercial production use, 3,000 credits a day, no card, and a dated public changelog records API and MCP changes, most recently on 2 November 2026. No security.txt, disclosure policy, bug bounty or certification was found, and the specs recommend sending the key in the URL.

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

Geoapify Location Platform + MCP

  1. Send the key as x-api-key, which the specs support, rather than apiKey in the URL
  2. Use api-eu.geoapify.com when the data has to stay on EU infrastructure
  3. Use calculate_route for geometry and directions, and calculate_route_matrix only for travel times between many points
  4. Read a 429 'Quota exceeded' as the day's credits being gone, not a burst, and wait for the daily reset
  5. Show OpenStreetMap attribution wherever you display 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, Geoapify Location Platform + MCP or TomTom Maps APIs + MCP?

Geoapify Location Platform + MCP scores 60 (C) on agent readiness against TomTom Maps APIs + MCP's 47.5 (D), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on agent ergonomics, security & auth and maintenance & community.

Do Geoapify Location Platform + MCP and TomTom Maps APIs + MCP need an API key?

Both need an API key.

Can an agent call Geoapify Location Platform + MCP and TomTom Maps APIs + MCP without installing anything?

Yes. Geoapify Location Platform + MCP has a hosted endpoint at https://api.geoapify.com/v1 and TomTom Maps APIs + MCP at https://api.tomtom.com.

Other comparisons with Geoapify Location Platform + MCP 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.