# HERE Location Services > 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. - Canonical: https://www.anchorterminal.com/tools/here-location-services - Markdown: https://www.anchorterminal.com/tools/here-location-services.md (~8,050 tokens) - Slim: https://www.anchorterminal.com/tools/here-location-services.min.md (~1,680 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/here-location-services.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-10 ## Overview **Grade C · 58/100 · rank #591 of 950 · #9 in Maps, geocoding & places · not agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | HERE Technologies (https://www.here.com) | | Kind | HTTP API | | Category | Maps, geocoding & places (https://www.anchorterminal.com/categories/maps) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://geocode.search.hereapi.com/v1` | | Auth | OAuth or key · 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 (Freemium) · 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). | | x402 | No · No x402, MPP or L402 in the docs index, the Location Reasoning guides or the Platform Terms (checked 2026-10-09). | | Licence | Proprietary service under the HERE Platform Terms | | Tools exposed | 13 | | Docs | https://docs.here.com | | llms.txt | https://docs.here.com/llms.txt | | Last release | 2026-09-09 | | APIs | Geocoding and Search v7 (geocode, reverse geocode, autocomplete, autosuggest, discover, browse, lookup, batch), Routing v8, Matrix Routing v8, Isoline Routing v8, Waypoints Sequence, Route Matching, Traffic, Public Transit, raster and vector tiles | | MCP server | HERE Location Reasoning, hosted at https://hlr.here.ai/mcp. 13 tools in the docs, two marked experimental. Needs an account entitlement | | Credentials | API key in the `apiKey` query parameter, OAuth 2.0 client credentials, or OAuth 2.1 `private_key_jwt`. Two keys or two JWKs an app, and up to 20 trusted domains in the console | | Storage | Results may be cached or stored outside the platform for at most 30 days (24 hours for Positioning), and only as HTTP caching headers allow, per the Platform Terms | | AI clause | Platform Terms forbid using HERE Materials in connection with a machine learning or AI system, generative AI included | | Availability target | 99.9 per cent a month for Geocoding and Search v7 and Routing v8. Service credits need the Essential support plan or above | | Errors | JSON body with `status`, `title`, `code`, `cause`, `action`, `correlationId` and `requestId`. 429 or 503 when a quota is exceeded | | Deprecations | Six months' notice before a product is discontinued, 6 to 12 months for a deprecated feature | | Data use | HERE uses anonymised or aggregated findings from platform use to develop its products. Essential Data Processing domains such as `subp-router.hereapi.com` switch that off | | Certifications | ISO/IEC 27001:2022, 27701, 27017, 27018, 42001, TISAX AL3, CSA STAR Level 2, SOC 2 Type 2 for Platform Foundation and Workspace | | Support | Developer plan $50 a month with 72-hour response, Essential from $525, Advanced from $2,200 | | 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 | | JSON | https://www.anchorterminal.com/api/v1/tools/here-location-services.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 57 | 11.4 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 87 | 14.1 | | Agent ergonomics | 13% | 16.2 | 74 | 12.0 | | Security & auth | 14% | 17.5 | 65 | 11.4 | | Payments & pricing | 10% | 12.5 | 10 | 1.2 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 60 | 5.2 | | Transparency & trust (editorial 52, provenance 73) | 7% | 8.8 | 63 | 5.5 | | Negative events | up to −15 | up to −15 | 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) | -3 | | **Total** | | | | **58 → C** | ### Why each score - Reliability 57: Graded on the REST APIs (Geocoding and Search v7, Routing v8) with the hosted lines. HERE's docs describe a public status page at status.here.com/status with current status, a status history tab and scheduled maintenance (20). The page is drawn by script and showed only a loading message, so the 90-day record is unread (5). No rate limit with a number was found in the docs. A Rate Limit Rules API returns an account's own rules, and the Base Plan limits sit on the unread price page (5 of 15). The Limits and Quotas page says an exceeded quota returns 429 or 503 and that a surge can be throttled for about 10 minutes, and the OpenAPI definition lists 429. No Retry-After header or backoff guidance was found, and the calls are reads (7 of 15). Monthly availability targets of 99.9 per cent are published for Geocoding and Search v7 and Routing v8, with service credits only for the Essential support plan and above (10). Both APIs are in the Active lifecycle stage (10). Total 57. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 87: Each endpoint page has a Markdown twin holding an OpenAPI 3.0.0 definition, read for `/geocode` at version 7.157 (25). docs.here.com has a site `llms.txt` and one for each product and section (10). Endpoint descriptions state the purpose, and parameter descriptions are long, with ALPHA, BETA and RESTRICTED maturity tags. Little says when not to use an endpoint (14 of 20). Parameters are typed with 34 enums in the geocode definition, ranges such as `limit` 1 to 100 and defaults (13 of 15). 400, 405, 429 and 503 share an `ErrorResponse` schema, and the developer guide has code examples for each endpoint (12 of 15). The Routing v8 changelog is dated by entry up to 8.162.0 on 7 September 2026. The Geocoding and Search release notes are numbered by release without dates (13 of 15). The Location Reasoning tool schemas come only from `tools/list` and were not read. Total 87. - Agent ergonomics 74: `limit` sizes geocoding responses (1 to 100, default 20), and `show` and `return` parameters add optional blocks only when asked for. The MCP server lists 13 tools, two of them experimental, and passes cached route and isoline IDs between tools so geometry is not returned twice (18 of 25). Filters by country, result type, position and bounding area are documented. No offset or cursor paging was found for geocoding (15 of 20). Errors carry `status`, `title`, `code`, `cause`, `action` and `correlationId`, and the routing changelog names error codes such as `E605502` (17). Calls are reads and safe to repeat. MCP annotations were not read (14 of 20). A geocode needs only `q` and a credential. The SDKs in the docs are for maps on JavaScript, Android, iOS and Flutter, and no server-side REST client was found in the reviewed documentation (10 of 15). Total 74. - Security & auth 65: Credentials are API keys, OAuth 2.0 client credentials and OAuth 2.1 `private_key_jwt` with a registered JWK, where the private key stays with the customer. Tokens are short-lived and can be scoped to a project, and an app holds two API keys or two JWKs for rotation (30). Less 10 because the documented API key method is the `apiKey` query parameter (20). The location services only read. Trusted domains limit where a key works, and app credentials do not inherit the user's permissions (15 of 20). Results carry place names from third-party sources. The Location Reasoning examples load a `guardrails://location-reasoning-usage-policy` resource and a `hlr___secure_location_reasoning` prompt, whose text was not read (7 of 15). A Usage API reports billable usage by app and project. Per-call logs were not found (6 of 15). ISO/IEC 27001:2022, 27701, 27017, 27018 and 42001 certificates, SOC 2 Type 2 scoped to Platform Foundation and Workspace, TISAX AL3 and CSA STAR Level 2 are listed. A disclosure policy of 13 July 2023 names security@here.com with a 90-day window. No bug bounty and no security.txt were found (17 of 20). Total 65. - Payments & pricing 10: No x402, MPP or L402 was found in the docs index or the terms (0). The Base Plan price page is public, but its table is drawn by script and showed no prices to our reader, so per-request prices score as absent. This is a limit of our reading and not a finding that prices are hidden (0 of 20). HERE's docs say a new organisation can get started for free. Whether a card is asked for was not established (10 of 20). Sign-up is a browser flow with email verification (0). Support plans are priced in public, from $50 a month for the Developer plan. Total 10. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 60: The newest dated API entries are Matrix Routing 8.49.0 on 9 September 2026 and Routing 8.162.0 on 7 September 2026, 30 and 32 days before the check. The Matrix entry is a documentation change, so we scored the 90-day band (20 of 30). Routing v8 had releases 8.160.0, 8.161.0 and 8.162.0 between 16 July and 7 September (20). Changelogs are public for each API, and paid support plans state response times from 72 hours down to 4. A free community channel was not checked (10 of 15). HERE SDK and Maps API for JavaScript changelogs are indexed, but their dates were not read, and no HERE entry was found in the official MCP registry (5 of 15). Package health is not visible for a closed service (5 of 10). Total 60. - Transparency & trust 63: Closed service under public, dated terms. The HERE Platform Terms, effective 18 September 2023, name the contracting entity by region and govern the Base Plan (15 of 30). The terms say HERE analyses use of the platform and uses anonymised or aggregated findings to develop its products, and Essential Data Processing domains switch that off. The privacy policy of 29 August 2024 says it does not cover processing done on behalf of customers and gives no retention periods. The DPA is a PDF we did not read (14 of 30). The Product Lifecycle Policy gives six months' notice before discontinuation and 6 to 12 months for a deprecated feature, and changelogs mark deprecations with dates (20). No sub-processor list or data location was found on the pages read (3 of 20). Total 52. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (20 items): https://www.anchorterminal.com/fixes/here-location-services.md (JSON https://www.anchorterminal.com/fixes/here-location-services.json) ### What we couldn't check - unchecked: Base Plan prices, free monthly allowances, rate limits and whether a card is needed. https://www.here.com/get-started/pricing is drawn by script and showed only headings. - unchecked: the 90-day incident record. https://status.here.com/status is drawn by script, and robots.txt on that host disallows `/status`. - unchecked: Location Reasoning tool schemas, descriptions and annotations. They are published only through `tools/list` on https://hlr.here.ai/mcp, which we did not call. The count of 13 tools comes from the docs table. - unchecked: the HERE Platform Data Processing Agreement, a PDF, and with it any sub-processor list, data locations and retention periods. - unchecked: release dates of the HERE SDK and Maps API for JavaScript, and any GitHub repositories or server-side client libraries. - The Platform Terms forbid use of HERE Materials in connection with a machine learning or AI system, while HERE sells Location Reasoning for AI agents. Which terms govern Location Reasoning, and whether they lift that clause, was not established. This matters before any probe is run. - The acceptable use policy of 18 January 2022 lists benchmarking, scraping and data mining as prohibited. Recorded as a fact with no deduction. It matters before any probe is run. - The lead was right about the APIs and the MCP server. It did not say the MCP server runs on hlr.here.ai, needs an account entitlement and is also sold through AWS Marketplace. - The APIs answer on hereapi.com and the MCP server on here.ai, both off here.com, so `endpointOnVendorDomain` is false. ### Sources - docs index for agents: (seen 2026-10-09) - Geocode endpoint page with its OpenAPI 3.0 definition (Markdown twin): (seen 2026-10-09) - Geocoding and Search release notes, API changes: (seen 2026-10-09) - Routing API v8 changelog: (seen 2026-10-09) - Matrix Routing API v8 changelog: (seen 2026-10-09) - API key authorisation, rotation and trusted domains: (seen 2026-10-09) - OAuth 2.1 machine-to-machine guide: (seen 2026-10-09) - rate limit rules: (seen 2026-10-09) - Limits and Quotas policy: (seen 2026-10-09) - service availability targets: (seen 2026-10-09) - SLA introduction: (seen 2026-10-09) - Product Lifecycle Policy: (seen 2026-10-09) - Essential Data Processing domains: (seen 2026-10-09) - Location Reasoning overview: (seen 2026-10-09) - Location Reasoning connection and authentication: (seen 2026-10-09) - Location Reasoning tools reference: (seen 2026-10-09) - Location Reasoning integration examples: (seen 2026-10-09) - status page description: (seen 2026-10-09) - status page (drawn by script, unreadable): (seen 2026-10-09) - Base Plan pricing (table drawn by script, unreadable): (seen 2026-10-09) - support plans and prices: (seen 2026-10-09) - HERE Platform Terms, September 2023: (seen 2026-10-09) - Acceptable Use Policy, January 2022: (seen 2026-10-09) - privacy policy: (seen 2026-10-09) - security and disclosure page: (seen 2026-10-09) - certifications and attestations: (seen 2026-10-09) - MCP registry search: (seen 2026-10-09) - RDAP record for here.com: (seen 2026-10-09) ## Who's behind it (provenance 73/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | HERE Europe B.V. | 20/20 | | Domain age | here.com, registered 1995-06-11 (31 years) | 15/15 | | Endpoint on the vendor's domain | geocode.search.hereapi.com is not on here.com | 0/15 | | Terms of service | read, states 7 of the 7 things a reader expects, and has 1 clause that costs points | 8/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | status.here.com/status | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | 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. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.here.com/en-gb/terms/here-platform-terms-september-2023), read 2026-10-09, dated 2023-09-18, states 7 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "g) Use HERE Materials for: (i) benchmarking of third-party data sets, or (ii) a reference to create, enhance, or improve a product or service competitive to HERE;" - To know. Says access can be ended without notice or for any reason. "HERE may suspend or terminate your access to HERE Materials without notice if you choose not to accept the updated Terms." - To know. Has not been updated for three years or more. "Effective date: Monday, 18 September, 2023" - Gives the date it was last updated. Last updated 2023-09-18. - Names the governing law or courts. The law of the State of Illinois. - States a limit on its liability. Capped at the fees paid in the 24 months before the claim. - Says how changes to the terms are announced. Says it gives notice of a change. - Also in the text (2026-10-08). The list of things a customer may not do includes using HERE Materials in connection with a machine learning or AI system, generative AI among them. "f) Use HERE Materials in connection with a machine learning or artificial intelligence (“AI”) system, including but not limited to, models used in connection with natural language processing, algorithm optimization and training" - Also in the text (2026-10-08). Results may not be cached or stored outside the platform for more than 30 days, or 24 hours for HERE Positioning services, with stated exceptions. "j) Cache or store outside of the Platform any Results that include anything from the use of HERE Content or Location Services for more than 30 days, except HERE Positioning services which cannot be cached or stored outside the Platform for more than 24 hours" - Also in the text (2026-10-08). HERE deletes the customer's content, applications and other account materials after a subscription plan or the terms end. "HERE will delete Your Content, Applications, and other materials in your Platform account after the termination of your Subscription Plan or these Terms." **Privacy policy** (https://www.here.com/en-gb/privacy), read 2026-10-09, dated 2024-08-29, states 8 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2024-08-29. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. privacy@HERE.com. - Says where data is transferred or stored. Relies on standard contractual clauses. - Also in the text (2026-10-08). The policy does not cover personal data HERE processes on behalf of customers when supplying a service, which the terms for that service govern. "This Policy does not apply to the processing of personal data that we carry out on behalf of our customers for the purpose of service provisioning." ## Live (updated 2026-10-10 05:38 UTC) - Right now: up, HTTP 404, 54 ms, checked 2026-10-10 05:38 UTC (get on `https://geocode.search.hereapi.com/v1`) - Uptime 24h 100.0% (143 probes) · 30 days 100.0% (143 probes) · p50 55 ms · p95 92 ms - Vendor status page: unknown, no machine-readable status found - Watching changelog - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/here-location-services.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## 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 ## Before you call it (notes for agents) 1. Send `Authorization: Bearer` with an OAuth token where logs are kept. The `apiKey` query parameter puts the secret in every URL 2. Do not store results for more than 30 days, and follow the HTTP caching headers on each response 3. Treat 429 and 503 as throttling. HERE says a traffic surge can be throttled for about 10 minutes below the account's quota 4. Read `code`, `cause` and `action` in the error body, and quote `correlationId` to support 5. For Location Reasoning, send `initialize`, keep the `Mcp-Session-Id` header on later calls, and send a bearer token on `tools/call` ## Connect First request: ```bash curl "https://geocode.search.hereapi.com/v1/geocode?q=240+Washington+St.%2C+Boston&limit=4&apiKey=$HERE_API_KEY" ``` Through letme (picks today, calling later): https://letme.dev/here-location-services. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Mapbox APIs + MCP | BB | 75 | 57 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/mapbox.md | | Amazon Location Service | BB | 74.1 | 77 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/amazon-location.md | | Google Maps Platform + Grounding Lite MCP | B | 68.2 | 227 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/google-maps-platform.md | | Azure Maps | B | 67.9 | 236 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/azure-maps.md | | ArcGIS Location Platform | B | 65.4 | 320 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/arcgis.md | | Stadia Maps | B | 65.2 | 325 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/stadia-maps.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Each endpoint page has a Markdown twin holding its OpenAPI 3.0.0 definition, and the geocode definition is at version 7.157 (source: ) - HERE Location Reasoning is a hosted MCP server at https://hlr.here.ai/mcp with 13 documented tools, among them `geocode`, `calculate-route`, `matrix-routing`, `discover`, `traffic-flow` and `isoline-route` (source: ) - The Platform Terms forbid using HERE Materials in connection with a machine learning or AI system, including generative AI (source: ) - Results may be cached or stored outside the platform for at most 30 days, and only as the HTTP caching headers allow (source: ) - Monthly availability targets of 99.9 per cent are published for Geocoding and Search v7 and Routing v8 (source: ) - Routing v8 reached 8.162.0 on 7 September 2026, with dated changelog entries for each release (source: ) - #9 of 13 in Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md - All 78 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md ## Compare - [Amazon Location Service vs HERE Location Services](https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.md): BB 74.1 vs C 58 - [ArcGIS Location Platform vs HERE Location Services](https://www.anchorterminal.com/compare/arcgis-vs-here-location-services.md): B 65.4 vs C 58 - [Azure Maps vs HERE Location Services](https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.md): B 67.9 vs C 58 - [Geoapify Location Platform + MCP vs HERE Location Services](https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.md): C 55.3 vs C 58 - [Google Maps Platform + Grounding Lite MCP vs HERE Location Services](https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services.md): B 68.2 vs C 58 - [HERE Location Services vs LocationIQ](https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.md): C 58 vs C 60.3 - [HERE Location Services vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.md): C 58 vs BB 75 - [HERE Location Services vs MapQuest](https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.md): C 58 vs F 35.1 - [HERE Location Services vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/here-location-services-vs-opencage.md): C 58 vs B 69.2 - [HERE Location Services vs Radar](https://www.anchorterminal.com/compare/here-location-services-vs-radar.md): C 58 vs D 53.3 - [HERE Location Services vs Stadia Maps](https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.md): C 58 vs B 65.2 - [HERE Location Services vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.md): C 58 vs C 54.9 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on here.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "here-location-services", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html HERE Location Services on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![HERE Location Services on Anchor Terminal](https://www.anchorterminal.com/badges/here-location-services.svg)](https://www.anchorterminal.com/tools/here-location-services) ``` Plain link: ```html HERE Location Services on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say HERE Location Services is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/here-location-services-dark.png - Light: https://www.anchorterminal.com/assets/share/here-location-services-light.png