{ "data": { "a": { "slug": "geoapify", "name": "Geoapify Location Platform + MCP", "vendor": "Geoapify", "vendorUrl": "https://www.geoapify.com", "kind": "http-api", "category": "maps", "summary": "Geocoding, reverse geocoding, autocomplete, Places search by category, Routing, Route Matrix, isolines and map tiles, with OpenStreetMap attribution required on every plan.", "url": "https://www.anchorterminal.com/tools/geoapify", "markdownUrl": "https://www.anchorterminal.com/tools/geoapify.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/geoapify.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/geoapify.json", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.geoapify.com/v1", "packages": [], "auth": "api-key", "authNotes": "API key as the apiKey query parameter or the x-api-key header, both defined in the OpenAPI specs. The hosted MCP takes x-api-key. api-eu.geoapify.com serves the same API on EU infrastructure.", "pricing": "freemium", "pricingNotes": "Free 3,000 credits a day at 5 requests a second, commercial and production use allowed, no card, with a Geoapify attribution link required. API 10 $59 a month (10,000 credits a day, 12 a second), API 25 $109 (25,000), API 50 $179 (50,000), API 100 $299 (100,000), API 250 $609 (250,000), Custom from $860. A simple geocoding, places or routing request costs 1 credit (https://www.geoapify.com/pricing/). Over MCP, initialize, tools/list and notifications cost nothing and each tools/call is billed as the Geoapify API operation behind it (https://apidocs.geoapify.com/how-to/api-tooling-ai/connect-ai-client-mcp/).", "priceSummary": "$59 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 11, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://apidocs.geoapify.com/docs", "openapi": "https://apidocs.geoapify.com/open-api/", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "official", "free-tier", "no-card", "open-data", "eu", "closed-source" ], "graded": true, "anchor": { "graded": true, "score": 55.5, "grade": "C", "agentReady": false, "rank": 314, "ranked": true, "rankOf": 452, "categoryRank": 6, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 61, "payments": 30, "reliability": 60, "schema": 74, "security": 29, "transparency": 64 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Free plan allows commercial production use, 3,000 credits a day, no card. No security.txt, disclosure policy, bug bounty or certification found.", "strengths": [ "Free plan allows commercial production use, 3,000 credits a day, no card", "OpenAPI 3.1 specs for 22 APIs and one per MCP tool, with error examples", "Data for successful requests held no longer than 24 hours, hosted in the EU", "99.5 per cent monthly availability on paid plans, with discounts below it", "MCP tool descriptions say which tool to use instead" ], "weaknesses": [ "No security.txt, disclosure policy, bug bounty or certification found", "No public changelog or deprecation policy, and the terms allow changes without notice", "Storage rights appear in the docs but not in the terms", "The specs recommend the apiKey query parameter for public APIs", "Credits are counted per day, so bursts hit the cap early" ], "agentNotes": [ "Send the key as x-api-key, which the specs support, rather than apiKey in the URL", "Use api-eu.geoapify.com when the data has to stay on EU infrastructure", "Use calculate_route for geometry and directions, and calculate_route_matrix only for travel times between many points", "Read a 429 'Quota exceeded' as the day's credits being gone, not a burst, and wait for the daily reset", "Show OpenStreetMap attribution wherever you display results" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.5 } ], "editorialScores": { "ergonomics": 72, "maintenance": 61, "payments": 30, "reliability": 60, "schema": 74, "security": 29, "transparency": 52 }, "provenanceScore": 76 }, "connect": { "http": "curl \"https://api.geoapify.com/v1/geocode/search?text=10%20Downing%20Street%2C%20London\u0026limit=1\u0026format=json\u0026apiKey=$GEOAPIFY_API_KEY\"", "claudeCode": "claude mcp add --transport http geoapify https://api.geoapify.com/v1/mcp --header \"x-api-key: $GEOAPIFY_API_KEY\"", "config": { "mcpServers": { "geoapify": { "headers": { "x-api-key": "${GEOAPIFY_API_KEY}" }, "type": "http", "url": "https://api.geoapify.com/v1/mcp" } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/geoapify" }, "area": "everyday", "unitPrices": [ { "item": "API 10 plan", "unit": "month", "usd": 59, "note": "10,000 credits a day, 12 requests a second" }, { "item": "API 25 plan", "unit": "month", "usd": 109, "note": "25,000 credits a day" }, { "item": "API 100 plan", "unit": "month", "usd": 299, "note": "100,000 credits a day, 25 requests a second" }, { "item": "API 250 plan", "unit": "month", "usd": 609, "note": "250,000 credits a day" } ], "provenance": { "legalEntity": "KEPTAGO LTD", "domain": "geoapify.com", "domainRegistered": "2018-10-26", "endpointOnVendorDomain": true, "terms": "https://www.geoapify.com/terms-and-conditions/", "privacy": "https://www.geoapify.com/privacy-policy/", "statusPage": "https://status.geoapify.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-01", "notes": [ "The terms name KEPTAGO LTD, registered in Paphos, Cyprus, trading as Geoapify. Version 5, dated 2 February 2024.", "www.geoapify.com/.well-known/security.txt returns 404.", "status.geoapify.com redirects to an UptimeRobot status page.", "We found no public changelog. The OpenAPI specs repository on GitHub has dated commits.", "The privacy policy was last modified 1 April 2026." ], "score": 76 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/geoapify.json", "live": { "slug": "geoapify", "probe": { "target": "https://api.geoapify.com/v1", "method": "get", "lastAt": "2026-10-05T00:57:20.797846665Z", "lastOk": true, "lastStatus": 401, "lastMs": 66, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 122, "p95ms24h": 2771, "samples24h": 272, "samples30d": 911, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 11, "ok": 11 } ] }, "vendorStatus": { "page": "https://status.geoapify.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-04T21:40:04.569125966Z" }, "securityTxt": { "url": "https://geoapify.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:58.717905359Z" }, "domain": { "domain": "geoapify.com", "registered": "2018-10-26", "source": "https://rdap.verisign.com/com/v1/domain/geoapify.com", "checkedAt": "2026-10-04T13:07:12.953394282Z" }, "pages": [ { "url": "https://www.geoapify.com/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-10-04T15:50:24.110440462Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f9a9f1600f52" }, { "url": "https://www.geoapify.com/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-10-04T15:50:26.317089191Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "37eb22e1e50f" }, { "url": "https://www.geoapify.com/terms-and-conditions/", "kind": "terms", "status": 304, "checkedAt": "2026-10-04T15:50:28.23555038Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c5c95d7b727d" } ], "updatedAt": "2026-10-05T00:57:20.797846665Z" } }, "b": { "slug": "tomtom", "name": "TomTom Maps APIs + MCP", "vendor": "TomTom", "vendorUrl": "https://developer.tomtom.com", "kind": "http-api", "category": "maps", "summary": "Search, Geocoding and Reverse Geocoding, Routing, Matrix Routing, Reachable Range, EV routing and live traffic, plus map tiles.", "url": "https://www.anchorterminal.com/tools/tomtom", "markdownUrl": "https://www.anchorterminal.com/tools/tomtom.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tomtom.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tomtom.json", "repo": "https://github.com/tomtom-international/tomtom-mcp", "license": "Apache-2.0 (MCP server)", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.tomtom.com", "packages": [ { "registry": "npm", "name": "@tomtom-org/tomtom-mcp" } ], "auth": "api-key", "authNotes": "One API key, passed as the key query parameter on REST calls. The hosted MCP takes it in a tomtom-api-key header and defaults to the Orbis backend. The local server defaults to the older TomTom Maps backend unless MAPS=tomtom-orbis-maps is set. Unreleased changes merged on 30 September 2026 drop the older backend, the tomtom-maps-backend header and the MAPS variable.", "pricing": "freemium", "pricingNotes": "Free monthly allowance with no card. 2,500 Search, 20,000 Geocoding, 20,000 Routing, 2,500 Matrix Routing, 200,000 vector and 200,000 raster tiles and 20,000 non-tile map requests. Past that it's pay as you grow in euros at volume tiers, worked out by an estimator on the pricing page. The per-request rates sit behind per-API detail links we couldn't read, so no rate is quoted here (https://docs.tomtom.com/pricing).", "priceSummary": "Freemium", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": 15, "popularity": { "githubStars": 55, "npmWeekly": 996, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.tomtom.com", "llmsTxt": "https://docs.tomtom.com/llms.txt", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "official", "typescript", "free-tier", "no-card", "enterprise", "eu", "closed-source" ], "lastRelease": "2026-09-23", "graded": true, "anchor": { "graded": true, "score": 55.1, "grade": "C", "agentReady": false, "rank": 318, "ranked": true, "rankOf": 452, "categoryRank": 7, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 86, "payments": 25, "reliability": 30, "schema": 71, "security": 51, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-10-01" }, "negative": 0, "verdict": "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.", "strengths": [ "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month", "Live traffic, EV routing and search, reachable range and search along a route as MCP tools", "All 18 MCP tools annotated read-only, idempotent and non-destructive", "Five MCP releases between 14 July and 23 September 2026, with Veracode scanning and end-to-end tests in CI", "HackerOne disclosure programme with a 3 business day first response" ], "weaknesses": [ "Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified", "Status page keeps only five days of history", "Paid prices only through a euro estimator", "Hosted MCP in public preview and missing from the MCP registry", "Only 2,500 free Search and Matrix calls a month" ], "agentNotes": [ "Use tomtom-geocode (20,000 free) rather than tomtom-fuzzy-search (2,500 free) when you have a full address", "Don't send tomtom-maps-backend in new configs, since the next release stops reading it and Orbis is already the hosted default", "Read a 403 'missing permissions' as the key lacking Orbis or EV products, and enable them in the developer portal", "Pass show_ui false when the client can't render MCP Apps, or you'll get a JSON summary instead of a map", "Redact the key parameter before logging REST URLs" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "C", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.1 } ], "editorialScores": { "ergonomics": 78, "maintenance": 86, "payments": 25, "reliability": 30, "schema": 71, "security": 51, "transparency": 41 }, "provenanceScore": 80 }, "connect": { "http": "curl \"https://api.tomtom.com/search/2/geocode/10%20Downing%20Street%2C%20London.json?limit=1\u0026key=$TOMTOM_API_KEY\"", "claudeCode": "claude mcp add --transport http tomtom https://mcp.tomtom.com/maps --header \"tomtom-api-key: $TOMTOM_API_KEY\"", "config": { "mcpServers": { "tomtom": { "args": [ "-y", "@tomtom-org/tomtom-mcp@latest" ], "command": "npx", "env": { "TOMTOM_API_KEY": "${TOMTOM_API_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/tomtom" }, "area": "everyday", "provenance": { "legalEntity": "TomTom International BV", "domain": "tomtom.com", "domainRegistered": "1996-02-23", "endpointOnVendorDomain": true, "terms": "https://docs.tomtom.com/legal/terms-and-conditions", "privacy": "https://www.tomtom.com/privacy/", "statusPage": "https://tomtom.service-now.com/status", "changelog": "", "securityTxt": "none", "checked": "2026-10-02", "notes": [ "The privacy policy names TomTom International BV and was last edited 1 August 2024. Subprocessors and storage locations are on https://www.tomtom.com/en-gb/privacy/more-information/.", "The terms page renders client-side and returned no readable text to our fetcher on 30 September, 1 October or 2 October, and developer.tomtom.com/legal redirects to it, so storage and caching rules are unverified.", "www.tomtom.com/.well-known/security.txt returns 404. Vulnerabilities go to TomTom's HackerOne programme, per the security policy in the tomtom-international GitHub organisation.", "The status page shows current status per API and only the last five days of history.", "A deprecation policy page is linked from docs.tomtom.com/llms.txt but renders client-side, and its .md twin returns 404." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tomtom.json", "live": { "slug": "tomtom", "probe": { "target": "https://api.tomtom.com", "method": "get", "lastAt": "2026-10-05T00:57:29.510624307Z", "lastOk": true, "lastStatus": 200, "lastMs": 117, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 156, "p95ms24h": 358, "samples24h": 272, "samples30d": 911, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 11, "ok": 11 } ] }, "vendorStatus": { "page": "https://tomtom.service-now.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-04T21:40:31.726753893Z" }, "versions": [ { "registry": "github", "name": "tomtom-international/tomtom-mcp", "version": "v1.6.10", "released": "2026-09-23", "seenAt": "2026-10-04T16:42:10.302294149Z" }, { "registry": "npm", "name": "@tomtom-org/tomtom-mcp", "version": "1.6.10", "seenAt": "2026-10-04T16:42:09.439404752Z" } ], "githubStars": 55, "npmWeekly": 685, "securityTxt": { "url": "https://tomtom.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:41.501098817Z" }, "llmsTxt": { "url": "https://docs.tomtom.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-04T15:18:18.118999761Z" }, "domain": { "domain": "tomtom.com", "registered": "1996-02-23", "source": "https://rdap.verisign.com/com/v1/domain/tomtom.com", "checkedAt": "2026-10-04T13:05:44.956685546Z" }, "pages": [ { "url": "https://docs.tomtom.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-04T15:44:11.600272734Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9f426a4be50f" }, { "url": "https://www.tomtom.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-04T15:52:29.87969507Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e5bdc55dca1e" }, { "url": "https://docs.tomtom.com/legal/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-10-04T15:44:09.558268623Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "68f5b7cd1e5c" } ], "updatedAt": "2026-10-05T00:57:29.510624307Z" } }, "summary": "Geoapify Location Platform + MCP has a score of 55.5 (C) against TomTom Maps APIs + MCP's 55.1 (C). Both do geo geocode. The largest gap is reliability, 30 points." }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom", "json": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom.md", "slim": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom.min.md" }, "markdown": "Geoapify Location Platform + MCP has a score of 55.5 (C) against TomTom Maps APIs + MCP's 55.1 (C). Both do geo geocode. The largest gap is reliability, 30 points.\n\n- Geoapify Location Platform + MCP: grade C, 55.5/100, rank #314 of 452. Markdown https://www.anchorterminal.com/tools/geoapify.md · JSON https://www.anchorterminal.com/api/v1/tools/geoapify.json\n- TomTom Maps APIs + MCP: grade C, 55.1/100, rank #318 of 452. Markdown https://www.anchorterminal.com/tools/tomtom.md · JSON https://www.anchorterminal.com/api/v1/tools/tomtom.json\n\n## Which one, for what\n\nPick Geoapify Location Platform + MCP for reliability (+30), payments \u0026 pricing (+5).\n\nPick TomTom Maps APIs + MCP for agent ergonomics (+6), security \u0026 auth (+22), maintenance \u0026 community (+25).\n\n## Score by category\n\n| Category | Weight | Geoapify Location Platform + MCP | TomTom Maps APIs + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 60 | 30 | Geoapify Location Platform + MCP +30 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 74 | 71 | Geoapify Location Platform + MCP +3 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 78 | TomTom Maps APIs + MCP +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 29 | 51 | TomTom Maps APIs + MCP +22 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 25 | Geoapify Location Platform + MCP +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 61 | 86 | TomTom Maps APIs + MCP +25 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 64 | 61 | Geoapify Location Platform + MCP +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **55.5 · C** | **55.1 · C** | |\n\n## Facts side by side\n\n| Fact | Geoapify Location Platform + MCP | TomTom Maps APIs + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Geoapify | TomTom |\n| Hosted endpoint | `https://api.geoapify.com/v1` | `https://api.tomtom.com` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | API key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | none | Apache-2.0 (MCP server) |\n| Tools exposed | 11 | 15 |\n| Context cost (tools/list) | n/a | n/a |\n| p95 latency | not measured yet | not measured yet |\n| Availability (30d) | not measured yet | not measured yet |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| MCP registry | not listed | not listed |\n| Last release | none | 2026-09-23 |\n| Popularity | none | 55 stars, 996 npm/wk |\n| Agent reviews | 4/5 (2) | 3/5 (2) |\n\n## Verdicts\n\n**Geoapify Location Platform + MCP.** Free plan allows commercial production use, 3,000 credits a day, no card. No security.txt, disclosure policy, bug bounty or certification found.\n\n**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.\n\n## Before you call either\n\n### Geoapify Location Platform + MCP\n\n1. Send the key as x-api-key, which the specs support, rather than apiKey in the URL\n2. Use api-eu.geoapify.com when the data has to stay on EU infrastructure\n3. Use calculate_route for geometry and directions, and calculate_route_matrix only for travel times between many points\n4. Read a 429 'Quota exceeded' as the day's credits being gone, not a burst, and wait for the daily reset\n5. Show OpenStreetMap attribution wherever you display results\n\n### TomTom Maps APIs + MCP\n\n1. Use tomtom-geocode (20,000 free) rather than tomtom-fuzzy-search (2,500 free) when you have a full address\n2. Don't send tomtom-maps-backend in new configs, since the next release stops reading it and Orbis is already the hosted default\n3. Read a 403 'missing permissions' as the key lacking Orbis or EV products, and enable them in the developer portal\n4. Pass show_ui false when the client can't render MCP Apps, or you'll get a JSON summary instead of a map\n5. Redact the key parameter before logging REST URLs\n\n## Other comparisons with Geoapify Location Platform + MCP or TomTom Maps APIs + MCP\n\n- [Geoapify Location Platform + MCP vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/geoapify-vs-google-maps-platform.md)\n- [Geoapify Location Platform + MCP vs LocationIQ](https://www.anchorterminal.com/compare/geoapify-vs-locationiq.md)\n- [Geoapify Location Platform + MCP vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/geoapify-vs-mapbox.md)\n- [Geoapify Location Platform + MCP vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/geoapify-vs-opencage.md)\n- [Geoapify Location Platform + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps.md)\n- [Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom.md)\n- [LocationIQ vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/locationiq-vs-tomtom.md)\n- [Mapbox APIs + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapbox-vs-tomtom.md)\n- [OpenCage Geocoding API vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/opencage-vs-tomtom.md)\n- [Stadia Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-05", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.3", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP", "url": "" } ], "description": "Geoapify Location Platform + MCP has a score of 55.5 (C) against TomTom Maps APIs + MCP's 55.1 (C). Both do geo geocode. The largest gap is reliability, 30 points. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Geoapify Location Platform + MCP C 55.5", "TomTom Maps APIs + MCP C 55.1", "scores" ], "h1": "Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-geoapify-vs-tomtom.png", "path": "/compare/geoapify-vs-tomtom", "published": "2026-10-01", "section": "tools", "title": "Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP", "toc": null, "updated": "2026-10-05", "url": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom" }, "tokens": { "markdown": 1550, "slim": 380 }, "version": 1 }