{ "data": { "a": { "slug": "here-location-services", "name": "HERE Location Services", "vendor": "HERE Technologies", "vendorUrl": "https://www.here.com", "kind": "http-api", "category": "maps", "summary": "HERE Technologies' REST APIs for geocoding, place search, routing, matrix and isoline routing, traffic, transit and map tiles, called with an API key or OAuth token. A hosted MCP server, HERE Location Reasoning, exposes 13 of these operations as tools.", "url": "https://www.anchorterminal.com/tools/here-location-services", "markdownUrl": "https://www.anchorterminal.com/tools/here-location-services.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/here-location-services.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/here-location-services.json", "license": "Proprietary service under the HERE Platform Terms", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://geocode.search.hereapi.com/v1", "packages": [], "auth": "mixed", "authNotes": "Self-serve. A HERE platform account, created in a browser with email verification, lets a person register an app and create up to two API keys, OAuth 2.0 credentials or OAuth 2.1 `private_key_jwt` credentials. REST calls take the key as the `apiKey` query parameter or a bearer token from https://account.api.here.com/oauth2/token. Location Reasoning needs a bearer token on `tools/call` and an account entitlement, and returns 403 without one.", "pricing": "freemium", "pricingNotes": "HERE's docs say a new organisation can get started for free on the Base Plan. The price table at here.com/get-started/pricing is drawn by script and was not read, so no allowance or per-request price is quoted. Support plans run from $50 a month (Developer). Location Reasoning is also sold through AWS Marketplace (checked 2026-10-09).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the Location Reasoning guides or the Platform Terms (checked 2026-10-09).", "endpoints": [] }, "toolCount": 13, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.here.com", "llmsTxt": "https://docs.here.com/llms.txt", "openapi": "https://docs.here.com/geocoding-and-search/reference/get_geocode.md", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "official", "openapi", "llms-txt", "oauth", "free-tier", "enterprise", "eu", "sla", "closed-source" ], "lastRelease": "2026-09-09", "graded": true, "anchor": { "graded": true, "score": 58, "grade": "C", "agentReady": false, "rank": 591, "ranked": true, "rankOf": 950, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 60, "payments": 10, "reliability": 57, "schema": 87, "security": 65, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -3, "negativeNotes": [ "10 July 2026. The Routing v8 changelog marks `mlDuration` as Deprecated and says `return=mlDuration` is still accepted but no longer returns a value. HERE's lifecycle policy says a deprecated feature continues to operate for 6 to 12 months after notice. Three points (https://docs.here.com/routing/docs/routing-v8-changelog.md)" ], "verdict": "Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. The Platform Terms of September 2023 forbid using HERE Materials in connection with a machine learning or AI system, and the price table could not be read.", "bestFor": "Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.", "strengths": [ "Every endpoint page has a Markdown twin holding its OpenAPI 3.0 definition, indexed from `llms.txt` files per product", "99.9 per cent monthly availability targets published for Geocoding and Search v7 and Routing v8", "Lifecycle policy promises six months' notice before a product is discontinued and 6 to 12 months for a deprecated feature", "OAuth 2.1 `private_key_jwt` credentials alongside API keys, with two keys an app for rotation and trusted-domain limits", "ISO 27001, 27701, 27017, 27018 and 42001 certificates, TISAX AL3, and SOC 2 Type 2 for Platform Foundation and Workspace" ], "weaknesses": [ "Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run", "The Base Plan price table is drawn by script, so per-request prices, free allowances and rate limits were not read", "API keys travel in the `apiKey` query parameter", "Results may be cached or stored outside the platform for 30 days at most, and only as HTTP caching headers allow", "Location Reasoning returns 403 unless the account is entitled, and the docs send the reader to an account representative or AWS Marketplace", "The acceptable use policy of January 2022 lists benchmarking and scraping among prohibited activities" ], "agentNotes": [ "Send `Authorization: Bearer` with an OAuth token where logs are kept. The `apiKey` query parameter puts the secret in every URL", "Do not store results for more than 30 days, and follow the HTTP caching headers on each response", "Treat 429 and 503 as throttling. HERE says a traffic surge can be throttled for about 10 minutes below the account's quota", "Read `code`, `cause` and `action` in the error body, and quote `correlationId` to support", "For Location Reasoning, send `initialize`, keep the `Mcp-Session-Id` header on later calls, and send a bearer token on `tools/call`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58 } ], "editorialScores": { "ergonomics": 74, "maintenance": 60, "payments": 10, "reliability": 57, "schema": 87, "security": 65, "transparency": 52 }, "provenanceScore": 73 }, "connect": { "http": "curl \"https://geocode.search.hereapi.com/v1/geocode?q=240+Washington+St.%2C+Boston\u0026limit=4\u0026apiKey=$HERE_API_KEY\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/here-location-services" }, "area": "everyday", "provenance": { "legalEntity": "HERE Europe B.V.", "domain": "here.com", "domainRegistered": "1995-06-11", "endpointOnVendorDomain": false, "terms": "https://www.here.com/en-gb/terms/here-platform-terms-september-2023", "privacy": "https://www.here.com/en-gb/privacy", "statusPage": "https://status.here.com/status", "changelog": "https://docs.here.com/routing/docs/routing-v8-changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The HERE Platform Terms, effective 18 September 2023, name HERE Europe B.V., Kennedyplein 222-226, 5611 ZT Eindhoven, as contracting party, and HERE North America, LLC, Chicago, for customers in the Americas.", "The privacy policy, effective 29 August 2024, names HERE Global B.V. as controller and says it does not apply to personal data processed on behalf of customers. The Platform Terms incorporate it and a Data Processing Agreement published as a PDF.", "The APIs answer on hereapi.com (for example geocode.search.hereapi.com and router.hereapi.com) and the MCP server on hlr.here.ai, both second domains of the vendor.", "www.here.com/.well-known/security.txt returned the site's error page. The security page gives security@here.com and a 90-day disclosure window.", "RDAP for here.com gives a registration date of 1995-06-11.", "legal.here.com/en-gb/terms/here-platform redirects to the September 2023 terms on www.here.com." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/here-location-services.json", "live": { "slug": "here-location-services", "probe": { "target": "https://geocode.search.hereapi.com/v1", "method": "get", "lastAt": "2026-10-10T03:53:29.802604157Z", "lastOk": true, "lastStatus": 404, "lastMs": 47, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 55, "p95ms24h": 97, "samples24h": 125, "samples30d": 125, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.here.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:40.516930569Z" }, "pages": [ { "url": "https://docs.here.com/routing/docs/routing-v8-changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:37:28.07952108Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c940c6209b7e" }, { "url": "https://www.here.com/en-gb/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:50:53.049981302Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bbe0eed0a23e" }, { "url": "https://www.here.com/en-gb/terms/here-platform-terms-september-2023", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:50:55.117836401Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "466d77d5e000" } ], "updatedAt": "2026-10-10T03:53:29.802604157Z" } }, "answer": "HERE Location Services scores 58 (C) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on payments \u0026 pricing and maintenance \u0026 community.", "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": 54.9, "grade": "C", "agentReady": false, "rank": 675, "ranked": true, "rankOf": 950, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 86, "payments": 25, "reliability": 30, "schema": 71, "security": 51, "transparency": 58 }, "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.", "bestFor": "Drive planning with live traffic, EV charging and reachable range.", "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.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.9 } ], "editorialScores": { "ergonomics": 78, "maintenance": 86, "payments": 25, "reliability": 30, "schema": 71, "security": 51, "transparency": 41 }, "provenanceScore": 74 }, "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": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tomtom.json", "live": { "slug": "tomtom", "probe": { "target": "https://api.tomtom.com", "method": "get", "lastAt": "2026-10-10T03:53:47.22047623Z", "lastOk": true, "lastStatus": 200, "lastMs": 139, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 183, "p95ms24h": 661, "samples24h": 249, "samples30d": 2274, "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": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://tomtom.service-now.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:51:20.792064098Z" }, "versions": [ { "registry": "github", "name": "tomtom-international/tomtom-mcp", "version": "v1.6.12", "released": "2026-10-09", "seenAt": "2026-10-09T17:25:04.0205712Z" }, { "registry": "npm", "name": "@tomtom-org/tomtom-mcp", "version": "1.6.12", "seenAt": "2026-10-09T17:25:03.080630502Z" } ], "githubStars": 56, "npmWeekly": 777, "securityTxt": { "url": "https://tomtom.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:40:05.596425929Z" }, "llmsTxt": { "url": "https://docs.tomtom.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:55.11188535Z" }, "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-09T18:38:37.010050617Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9f426a4be50f" }, { "url": "https://www.tomtom.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:55:03.387246233Z", "changedAt": "2026-10-08T18:31:01.446679763Z", "fingerprint": "b77d548785dc" }, { "url": "https://docs.tomtom.com/legal/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:38:34.908266259Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "68f5b7cd1e5c" } ], "updatedAt": "2026-10-10T03:53:47.22047623Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "HERE Technologies", "b": "TomTom", "name": "Vendor" }, { "a": "https://geocode.search.hereapi.com/v1", "b": "https://api.tomtom.com", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the HERE Platform Terms", "b": "Apache-2.0 (MCP server)", "name": "Licence" }, { "a": "13", "b": "15", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-09", "b": "2026-09-23", "name": "Last release" }, { "a": "2023-09-18", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2024-08-29", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "55 stars, 996 npm/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "HERE Location Services scores 58 (C) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, HERE Location Services or TomTom Maps APIs + MCP?" }, { "answer": "HERE Location Services takes an API key or an OAuth sign-in. TomTom Maps APIs + MCP needs an API key.", "question": "Do HERE Location Services and TomTom Maps APIs + MCP need an API key?" }, { "answer": "Yes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and TomTom Maps APIs + MCP at https://api.tomtom.com.", "question": "Can an agent call HERE Location Services and TomTom Maps APIs + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 57 against 30", "Schema \u0026 documentation, 87 against 71", "Security \u0026 auth, 65 against 51", "Transparency \u0026 trust, 63 against 58" ], "also": null, "goodFor": "Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.", "slug": "here-location-services", "watchFor": "Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run" }, { "aheadOn": [ "Payments \u0026 pricing, 25 against 10", "Maintenance \u0026 community, 86 against 60" ], "also": [ "Runs on your own machine", "Free to start without a card", "No incidents deducted, where HERE Location Services loses 3 points for them" ], "goodFor": "Drive planning with live traffic, EV charging and reachable range.", "slug": "tomtom", "watchFor": "Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified" } ], "job": { "capability": "geo.geocode", "name": "Geocoding" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.json", "title": "Amazon Location Service vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.json", "title": "Amazon Location Service vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-here-location-services.json", "title": "ArcGIS Location Platform vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/arcgis-vs-here-location-services" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-tomtom.json", "title": "ArcGIS Location Platform vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/arcgis-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.json", "title": "Azure Maps vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-tomtom.json", "title": "Azure Maps vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.json", "title": "Geoapify Location Platform + MCP vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/geoapify-vs-here-location-services" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom.json", "title": "Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services.json", "title": "Google Maps Platform + Grounding Lite MCP vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom.json", "title": "Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.json", "title": "HERE Location Services vs LocationIQ", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.json", "title": "HERE Location Services vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapbox" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.json", "title": "HERE Location Services vs MapQuest", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage.json", "title": "HERE Location Services vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-radar.json", "title": "HERE Location Services vs Radar", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.json", "title": "HERE Location Services vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-tomtom.json", "title": "LocationIQ vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/locationiq-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-tomtom.json", "title": "Mapbox APIs + MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/mapbox-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-tomtom.json", "title": "MapQuest vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/mapquest-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/opencage-vs-tomtom.json", "title": "OpenCage Geocoding API vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/opencage-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/radar-vs-tomtom.json", "title": "Radar vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/radar-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.json", "title": "Stadia Maps vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom" } ], "scores": [ { "by": 27, "edge": "here-location-services", "here-location-services": 57, "key": "reliability", "name": "Reliability", "tomtom": 30, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 16, "edge": "here-location-services", "here-location-services": 87, "key": "schema", "name": "Schema \u0026 documentation", "tomtom": 71, "weight": 13 }, { "by": 4, "edge": "tomtom", "here-location-services": 74, "key": "ergonomics", "name": "Agent ergonomics", "tomtom": 78, "weight": 13 }, { "by": 14, "edge": "here-location-services", "here-location-services": 65, "key": "security", "name": "Security \u0026 auth", "tomtom": 51, "weight": 14 }, { "by": 15, "edge": "tomtom", "here-location-services": 10, "key": "payments", "name": "Payments \u0026 pricing", "tomtom": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 26, "edge": "tomtom", "here-location-services": 60, "key": "maintenance", "name": "Maintenance \u0026 community", "tomtom": 86, "weight": 7 }, { "by": 5, "edge": "here-location-services", "here-location-services": 63, "key": "transparency", "name": "Transparency \u0026 trust", "tomtom": 58, "weight": 7 } ], "summary": "HERE Location Services scores 58 (C) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on payments \u0026 pricing and maintenance \u0026 community. Both do geocoding.", "verdicts": { "here-location-services": "Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. The Platform Terms of September 2023 forbid using HERE Materials in connection with a machine learning or AI system, and the price table could not be read.", "tomtom": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/here-location-services-vs-tomtom", "json": "https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.md", "slim": "https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.min.md" }, "markdown": "HERE Location Services scores 58 (C) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on payments \u0026 pricing and maintenance \u0026 community. Both do geocoding.\n\n- HERE Location Services: grade C, 58/100, rank #591 of 950. Markdown https://www.anchorterminal.com/tools/here-location-services.md · JSON https://www.anchorterminal.com/api/v1/tools/here-location-services.json\n- TomTom Maps APIs + MCP: grade C, 54.9/100, rank #675 of 950. Markdown https://www.anchorterminal.com/tools/tomtom.md · JSON https://www.anchorterminal.com/api/v1/tools/tomtom.json\n- Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md\n- All 78 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md\n\n## Which one, for what\n\n### HERE Location Services (C)\n\nGood for: Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.\n\nAhead on:\n- Reliability, 57 against 30\n- Schema \u0026 documentation, 87 against 71\n- Security \u0026 auth, 65 against 51\n- Transparency \u0026 trust, 63 against 58\n\nWatch for: Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run\n\n### TomTom Maps APIs + MCP (C)\n\nGood for: Drive planning with live traffic, EV charging and reachable range.\n\nAhead on:\n- Payments \u0026 pricing, 25 against 10\n- Maintenance \u0026 community, 86 against 60\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n- No incidents deducted, where HERE Location Services loses 3 points for them\n\nWatch for: Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified\n\n\n## Score by category\n\n| Category | Weight | HERE Location Services | TomTom Maps APIs + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 57 | 30 | HERE Location Services +27 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 71 | HERE Location Services +16 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 78 | TomTom Maps APIs + MCP +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 65 | 51 | HERE Location Services +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 25 | TomTom Maps APIs + MCP +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 86 | TomTom Maps APIs + MCP +26 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 58 | HERE Location Services +5 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **58 · C** | **54.9 · C** | |\n\n## Facts side by side\n\n| Fact | HERE Location Services | TomTom Maps APIs + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | HERE Technologies | TomTom |\n| Hosted endpoint | `https://geocode.search.hereapi.com/v1` | `https://api.tomtom.com` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under the HERE Platform Terms | Apache-2.0 (MCP server) |\n| Tools exposed | 13 | 15 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-09-09 | 2026-09-23 |\n| Terms last updated | 2023-09-18 | couldn't be read |\n| Privacy policy last updated | 2024-08-29 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | yes | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | none | 55 stars, 996 npm/wk |\n| Agent reviews | none | 3/5 (2) |\n\n## Verdicts\n\n**HERE Location Services.** Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. The Platform Terms of September 2023 forbid using HERE Materials in connection with a machine learning or AI system, and the price table could not be read.\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### HERE Location Services\n\n1. Send `Authorization: Bearer` with an OAuth token where logs are kept. The `apiKey` query parameter puts the secret in every URL\n2. Do not store results for more than 30 days, and follow the HTTP caching headers on each response\n3. Treat 429 and 503 as throttling. HERE says a traffic surge can be throttled for about 10 minutes below the account's quota\n4. Read `code`, `cause` and `action` in the error body, and quote `correlationId` to support\n5. For Location Reasoning, send `initialize`, keep the `Mcp-Session-Id` header on later calls, and send a bearer token on `tools/call`\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## Questions\n\n### Which is better for AI agents, HERE Location Services or TomTom Maps APIs + MCP?\n\nHERE Location Services scores 58 (C) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on payments \u0026 pricing and maintenance \u0026 community.\n\n### Do HERE Location Services and TomTom Maps APIs + MCP need an API key?\n\nHERE Location Services takes an API key or an OAuth sign-in. TomTom Maps APIs + MCP needs an API key.\n\n### Can an agent call HERE Location Services and TomTom Maps APIs + MCP without installing anything?\n\nYes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and TomTom Maps APIs + MCP at https://api.tomtom.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.json, and with the fewest tokens: https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"here-location-services\", \"b\": \"tomtom\"}`. From a terminal: `anchor compare here-location-services tomtom`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/here-location-services.json and https://www.anchorterminal.com/api/v1/tools/tomtom.json\n\n## Other comparisons with HERE Location Services or TomTom Maps APIs + MCP\n\n- [Amazon Location Service vs HERE Location Services](https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.md)\n- [Amazon Location Service vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.md)\n- [ArcGIS Location Platform vs HERE Location Services](https://www.anchorterminal.com/compare/arcgis-vs-here-location-services.md)\n- [ArcGIS Location Platform vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/arcgis-vs-tomtom.md)\n- [Azure Maps vs HERE Location Services](https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.md)\n- [Azure Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-tomtom.md)\n- [Geoapify Location Platform + MCP vs HERE Location Services](https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.md)\n- [Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geoapify-vs-tomtom.md)\n- [Google Maps Platform + Grounding Lite MCP vs HERE Location Services](https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services.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- [HERE Location Services vs LocationIQ](https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.md)\n- [HERE Location Services vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.md)\n- [HERE Location Services vs MapQuest](https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.md)\n- [HERE Location Services vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/here-location-services-vs-opencage.md)\n- [HERE Location Services vs Radar](https://www.anchorterminal.com/compare/here-location-services-vs-radar.md)\n- [HERE Location Services vs Stadia Maps](https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.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- [MapQuest vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapquest-vs-tomtom.md)\n- [OpenCage Geocoding API vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/opencage-vs-tomtom.md)\n- [Radar vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/radar-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-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "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": "HERE Location Services vs TomTom Maps APIs + MCP", "url": "" } ], "description": "HERE Location Services scores 58 (C) to TomTom Maps's 54.9 (C) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "HERE Location Services C 58", "TomTom Maps APIs + MCP C 54.9", "scores" ], "h1": "HERE Location Services vs TomTom Maps APIs + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-here-location-services-vs-tomtom.png", "path": "/compare/here-location-services-vs-tomtom", "published": "2026-10-01", "section": "tools", "title": "HERE Location Services vs TomTom Maps for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-tomtom" }, "tokens": { "markdown": 2650, "slim": 780 }, "version": 1 }