{ "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-10T02:54:57.537414358Z", "lastOk": true, "lastStatus": 404, "lastMs": 60, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 55, "p95ms24h": 124, "samples24h": 115, "samples30d": 115, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 30, "ok": 30 } ] }, "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-10T02:54:57.537414358Z" } }, "answer": "LocationIQ scores 60.3 (C) on agent readiness against HERE Location Services's 58 (C), and leads in 2 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community.", "b": { "slug": "locationiq", "name": "LocationIQ", "vendor": "LocationIQ (Unwired Labs)", "vendorUrl": "https://locationiq.com", "kind": "http-api", "category": "maps", "summary": "Forward and reverse geocoding, autocomplete, nearby places, directions, matrix and map tiles, from US and EU endpoints.", "url": "https://www.anchorterminal.com/tools/locationiq", "markdownUrl": "https://www.anchorterminal.com/tools/locationiq.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/locationiq.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/locationiq.json", "transports": [ "http" ], "remoteUrl": "https://us1.locationiq.com/v1", "packages": [], "auth": "api-key", "authNotes": "Access token passed as the key query parameter. Same API on us1.locationiq.com and eu1.locationiq.com.", "pricing": "freemium", "pricingNotes": "Free 5,000 requests a day at 2 a second, no card, with a prominent link back required. Maps Lite $45 a month (10,000 a day, maps only), Developer $100 (25,000 a day, all APIs), Startup $200 (60,000 a day), Growth Plus $500 (7.5 million a month), Business Plus $950 (30 million a month), Enterprise custom. Paid plans need a card (https://locationiq.com/pricing).", "priceSummary": "$100 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.locationiq.com", "llmsTxt": "https://docs.locationiq.com/llms.txt", "openapi": "https://docs.locationiq.com/openapi.yaml", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "llms-txt", "free-tier", "no-card", "eu", "closed-source" ], "graded": true, "anchor": { "graded": true, "score": 60.3, "grade": "C", "agentReady": false, "rank": 518, "ranked": true, "rankOf": 950, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 3, "payments": 30, "reliability": 83, "schema": 78, "security": 55, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "5,000 free requests a day with no card, commercial use allowed with a link back. No changelog, release notes or blog.", "bestFor": "A prototype or a cost-sensitive geocoding and routing job, with EU and US endpoints.", "strengths": [ "5,000 free requests a day with no card, commercial use allowed with a link back", "Public OpenAPI 3.0 spec and an llms.txt with Markdown pages", "Scoped tokens with referrer or IP restrictions and per-token rate limits", "No incidents posted between 2 April and 1 October 2026, with history back to 2018", "Error messages that separate per-second, per-minute and per-day limits" ], "weaknesses": [ "No changelog, release notes or blog", "Official SDKs untouched since 2020", "No MCP server", "Key only in the query string", "Free plan must delete cached results after 48 hours and gets a single token" ], "agentNotes": [ "Use eu1.locationiq.com for European users or data", "Add format=json and limit=1 to keep responses small", "On 429 Rate Limited Second wait a second, on Rate Limited Day stop until the next day", "Call /balance before a large batch to see what's left of the day's quota", "Redact the key parameter before logging request URLs" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.3 } ], "editorialScores": { "ergonomics": 74, "maintenance": 3, "payments": 30, "reliability": 83, "schema": 78, "security": 55, "transparency": 40 }, "provenanceScore": 82 }, "connect": { "http": "curl \"https://eu1.locationiq.com/v1/search?key=$LOCATIONIQ_API_KEY\u0026q=10%20Downing%20Street%2C%20London\u0026format=json\u0026limit=1\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/locationiq" }, "area": "everyday", "unitPrices": [ { "item": "Developer plan", "unit": "month", "usd": 100, "note": "25,000 requests a day, 20 a second, all APIs" }, { "item": "Startup plan", "unit": "month", "usd": 200, "note": "60,000 requests a day, 22 a second" }, { "item": "Growth Plus plan", "unit": "month", "usd": 500, "note": "7.5 million requests a month, 30 a second" }, { "item": "Business Plus plan", "unit": "month", "usd": 950, "note": "30 million requests a month, 40 a second" } ], "provenance": { "legalEntity": "Unwired Labs (India) Pvt Ltd", "domain": "locationiq.com", "domainRegistered": "2005-09-20", "endpointOnVendorDomain": true, "terms": "https://locationiq.com/tos", "privacy": "https://locationiq.com/privacy", "statusPage": "https://status.locationiq.com", "changelog": "", "securityTxt": "valid", "checked": "2026-10-01", "notes": [ "The terms were last updated 31 March 2026.", "security.txt lists hello@locationiq.com and expires 2028-01-01.", "LocationIQ's own privacy policy is at locationiq.com/privacy, last updated 22 May 2020. The parent's page at unwiredlabs.com/privacy embeds a Google Doc our reader couldn't see.", "The status page's RSS feed holds 74 incidents from March 2018 to 2 April 2026.", "We found no changelog or blog." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/locationiq.json", "live": { "slug": "locationiq", "probe": { "target": "https://us1.locationiq.com/v1", "method": "get", "lastAt": "2026-10-10T02:55:00.661186911Z", "lastOk": true, "lastStatus": 403, "lastMs": 273, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 237, "p95ms24h": 384, "samples24h": 249, "samples30d": 2264, "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": 30, "ok": 30 } ] }, "vendorStatus": { "page": "https://status.locationiq.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:46.391834711Z" }, "securityTxt": { "url": "https://locationiq.com/.well-known/security.txt", "state": "valid", "expires": "2028-01-01T00:00:00Z", "checkedAt": "2026-10-09T15:39:37.271745968Z" }, "llmsTxt": { "url": "https://docs.locationiq.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:14.551061706Z" }, "domain": { "domain": "locationiq.com", "registered": "2005-09-20", "source": "https://rdap.verisign.com/com/v1/domain/locationiq.com", "checkedAt": "2026-10-04T13:04:09.085884687Z" }, "pages": [ { "url": "https://locationiq.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:41:31.224260276Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8ef406b8d494" }, { "url": "https://locationiq.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:41:33.34856973Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f99922f73f1e" }, { "url": "https://locationiq.com/tos", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:41:35.978330542Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "13f087788a40" } ], "updatedAt": "2026-10-10T02:55:00.661186911Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "HERE Technologies", "b": "LocationIQ (Unwired Labs)", "name": "Vendor" }, { "a": "https://geocode.search.hereapi.com/v1", "b": "https://us1.locationiq.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "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": "none", "name": "Licence" }, { "a": "13", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-09", "b": "none", "name": "Last release" }, { "a": "2023-09-18", "b": "2026-03-31", "name": "Terms last updated" }, { "a": "2024-08-29", "b": "2020-05-22", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "4.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "LocationIQ scores 60.3 (C) on agent readiness against HERE Location Services's 58 (C), and leads in 2 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community.", "question": "Which is better for AI agents, HERE Location Services or LocationIQ?" }, { "answer": "HERE Location Services takes an API key or an OAuth sign-in. LocationIQ needs an API key.", "question": "Do HERE Location Services and LocationIQ need an API key?" }, { "answer": "Yes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and LocationIQ at https://us1.locationiq.com/v1.", "question": "Can an agent call HERE Location Services and LocationIQ without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 87 against 78", "Security \u0026 auth, 65 against 55", "Maintenance \u0026 community, 60 against 3" ], "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": [ "Reliability, 83 against 57", "Payments \u0026 pricing, 30 against 10" ], "also": [ "Free to start without a card", "No incidents deducted, where HERE Location Services loses 3 points for them" ], "goodFor": "A prototype or a cost-sensitive geocoding and routing job, with EU and US endpoints.", "slug": "locationiq", "watchFor": "No changelog, release notes or blog" } ], "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-locationiq.json", "title": "Amazon Location Service vs LocationIQ", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-locationiq" }, { "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-locationiq.json", "title": "ArcGIS Location Platform vs LocationIQ", "url": "https://www.anchorterminal.com/compare/arcgis-vs-locationiq" }, { "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-locationiq.json", "title": "Azure Maps vs LocationIQ", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-locationiq" }, { "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-locationiq.json", "title": "Geoapify Location Platform + MCP vs LocationIQ", "url": "https://www.anchorterminal.com/compare/geoapify-vs-locationiq" }, { "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-locationiq.json", "title": "Google Maps Platform + Grounding Lite MCP vs LocationIQ", "url": "https://www.anchorterminal.com/compare/google-maps-platform-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/here-location-services-vs-tomtom.json", "title": "HERE Location Services vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-mapbox.json", "title": "LocationIQ vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/locationiq-vs-mapbox" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-mapquest.json", "title": "LocationIQ vs MapQuest", "url": "https://www.anchorterminal.com/compare/locationiq-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-opencage.json", "title": "LocationIQ vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/locationiq-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-radar.json", "title": "LocationIQ vs Radar", "url": "https://www.anchorterminal.com/compare/locationiq-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps.json", "title": "LocationIQ vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/locationiq-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" } ], "scores": [ { "by": 26, "edge": "locationiq", "here-location-services": 57, "key": "reliability", "locationiq": 83, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 9, "edge": "here-location-services", "here-location-services": 87, "key": "schema", "locationiq": 78, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 0, "edge": "", "here-location-services": 74, "key": "ergonomics", "locationiq": 74, "name": "Agent ergonomics", "weight": 13 }, { "by": 10, "edge": "here-location-services", "here-location-services": 65, "key": "security", "locationiq": 55, "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "edge": "locationiq", "here-location-services": 10, "key": "payments", "locationiq": 30, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 57, "edge": "here-location-services", "here-location-services": 60, "key": "maintenance", "locationiq": 3, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 2, "edge": "here-location-services", "here-location-services": 63, "key": "transparency", "locationiq": 61, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "LocationIQ scores 60.3 (C) on agent readiness against HERE Location Services's 58 (C), and leads in 2 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation, security \u0026 auth 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.", "locationiq": "5,000 free requests a day with no card, commercial use allowed with a link back. No changelog, release notes or blog." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq", "json": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.md", "slim": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.min.md" }, "markdown": "LocationIQ scores 60.3 (C) on agent readiness against HERE Location Services's 58 (C), and leads in 2 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation, security \u0026 auth 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- LocationIQ: grade C, 60.3/100, rank #518 of 950. Markdown https://www.anchorterminal.com/tools/locationiq.md · JSON https://www.anchorterminal.com/api/v1/tools/locationiq.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- Schema \u0026 documentation, 87 against 78\n- Security \u0026 auth, 65 against 55\n- Maintenance \u0026 community, 60 against 3\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### LocationIQ (C)\n\nGood for: A prototype or a cost-sensitive geocoding and routing job, with EU and US endpoints.\n\nAhead on:\n- Reliability, 83 against 57\n- Payments \u0026 pricing, 30 against 10\n\nAlso in its favour:\n- Free to start without a card\n- No incidents deducted, where HERE Location Services loses 3 points for them\n\nWatch for: No changelog, release notes or blog\n\n\n## Score by category\n\n| Category | Weight | HERE Location Services | LocationIQ | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 57 | 83 | LocationIQ +26 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 78 | HERE Location Services +9 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 74 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 65 | 55 | HERE Location Services +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 30 | LocationIQ +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 3 | HERE Location Services +57 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 61 | HERE Location Services +2 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **58 · C** | **60.3 · C** | |\n\n## Facts side by side\n\n| Fact | HERE Location Services | LocationIQ |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | HERE Technologies | LocationIQ (Unwired Labs) |\n| Hosted endpoint | `https://geocode.search.hereapi.com/v1` | `https://us1.locationiq.com/v1` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under the HERE Platform Terms | none |\n| Tools exposed | 13 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-09 | none |\n| Terms last updated | 2023-09-18 | 2026-03-31 |\n| Privacy policy last updated | 2024-08-29 | 2020-05-22 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Agent reviews | none | 4.5/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**LocationIQ.** 5,000 free requests a day with no card, commercial use allowed with a link back. No changelog, release notes or blog.\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### LocationIQ\n\n1. Use eu1.locationiq.com for European users or data\n2. Add format=json and limit=1 to keep responses small\n3. On 429 Rate Limited Second wait a second, on Rate Limited Day stop until the next day\n4. Call /balance before a large batch to see what's left of the day's quota\n5. Redact the key parameter before logging request URLs\n\n## Questions\n\n### Which is better for AI agents, HERE Location Services or LocationIQ?\n\nLocationIQ scores 60.3 (C) on agent readiness against HERE Location Services's 58 (C), and leads in 2 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community.\n\n### Do HERE Location Services and LocationIQ need an API key?\n\nHERE Location Services takes an API key or an OAuth sign-in. LocationIQ needs an API key.\n\n### Can an agent call HERE Location Services and LocationIQ without installing anything?\n\nYes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and LocationIQ at https://us1.locationiq.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.json, and with the fewest tokens: https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"here-location-services\", \"b\": \"locationiq\"}`. From a terminal: `anchor compare here-location-services locationiq`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/here-location-services.json and https://www.anchorterminal.com/api/v1/tools/locationiq.json\n\n## Other comparisons with HERE Location Services or LocationIQ\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 LocationIQ](https://www.anchorterminal.com/compare/amazon-location-vs-locationiq.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 LocationIQ](https://www.anchorterminal.com/compare/arcgis-vs-locationiq.md)\n- [Azure Maps vs HERE Location Services](https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.md)\n- [Azure Maps vs LocationIQ](https://www.anchorterminal.com/compare/azure-maps-vs-locationiq.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 LocationIQ](https://www.anchorterminal.com/compare/geoapify-vs-locationiq.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 LocationIQ](https://www.anchorterminal.com/compare/google-maps-platform-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- [HERE Location Services vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.md)\n- [LocationIQ vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/locationiq-vs-mapbox.md)\n- [LocationIQ vs MapQuest](https://www.anchorterminal.com/compare/locationiq-vs-mapquest.md)\n- [LocationIQ vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/locationiq-vs-opencage.md)\n- [LocationIQ vs Radar](https://www.anchorterminal.com/compare/locationiq-vs-radar.md)\n- [LocationIQ vs Stadia Maps](https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps.md)\n- [LocationIQ vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/locationiq-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 LocationIQ", "url": "" } ], "description": "LocationIQ scores 60.3 (C) to HERE Location Services's 58 (C) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "HERE Location Services C 58", "LocationIQ C 60.3", "scores" ], "h1": "HERE Location Services vs LocationIQ", "image": "https://www.anchorterminal.com/assets/og/compare-here-location-services-vs-locationiq.png", "path": "/compare/here-location-services-vs-locationiq", "published": "2026-10-01", "section": "tools", "title": "HERE Location Services vs LocationIQ for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq" }, "tokens": { "markdown": 2450, "slim": 630 }, "version": 1 }