{ "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:07:11.240971654Z", "lastOk": true, "lastStatus": 404, "lastMs": 69, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 55, "p95ms24h": 124, "samples24h": 107, "samples30d": 107, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 22, "ok": 22 } ] }, "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:07:11.240971654Z" } }, "answer": "HERE Location Services scores 58 (C) on agent readiness against MapQuest's 35.1 (F), and leads in 6 of 7 scored categories. MapQuest leads on payments \u0026 pricing.", "b": { "slug": "mapquest", "name": "MapQuest", "vendor": "MapQuest (System1)", "vendorUrl": "https://developer.mapquest.com", "kind": "http-api", "category": "maps", "summary": "MapQuest's location APIs cover geocoding, directions, route matrices, place search, traffic and static maps. Agents call the REST API with a key or connect to a hosted MCP server over OAuth.", "url": "https://www.anchorterminal.com/tools/mapquest", "markdownUrl": "https://www.anchorterminal.com/tools/mapquest.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mapquest.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mapquest.json", "license": "Proprietary service. No API terms were found published without a login", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://www.mapquestapi.com", "packages": [], "auth": "mixed", "authNotes": "Self-serve. A person registers at developer.mapquest.com and creates an API key. REST calls send it in the `key` query parameter. The MCP server uses OAuth through login.mapquest.com with the single scope `mcp:tools`, then picks one of the account's keys. Further keys can be created with `POST /account/v1/keys`.", "pricing": "usage", "pricingNotes": "MapQuestGO is pay-as-you-go at $0.0045 a transaction with no monthly minimum, after 50,000 one-time free transactions that expire on 1 January 2027. Monthly plans run from Basic at $119 (30,000 transactions) to Business Plus at $949 (500,000). Enterprise is by quote. An agent can start on the free credits without a contract. Whether sign-up needs a card was not established (https://developer.mapquest.com/plans, checked 2026-10-08).", "priceSummary": "$4.50 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the plans page, llms.txt or the MCP endpoint's 401 response (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developer.mapquest.com/documentation/", "llmsTxt": "https://developer.mapquest.com/llms.txt", "capabilities": [ "geo.geocode", "geo.reverse", "geo.routing", "geo.places" ], "tags": [ "hosted", "mcp", "oauth", "api-key", "llms-txt", "free-credits", "usage-priced", "closed-source" ], "lastRelease": "2026-07-16", "graded": true, "anchor": { "graded": true, "score": 35.1, "grade": "F", "agentReady": false, "rank": 936, "ranked": true, "rankOf": 950, "categoryRank": 13, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 60, "maintenance": 23, "payments": 30, "reliability": 23, "schema": 47, "security": 28, "transparency": 28 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "One account reaches geocoding, routing, place search and traffic through a REST API or a hosted MCP server with OAuth, at a published $0.0045 a transaction. No API terms, status page, changelog or product OpenAPI spec was found, and REST keys travel in the query string.", "bestFor": "An agent that needs US-centred geocoding, routing with truck profiles, traffic and place search behind one account, with an MCP server ready to connect.", "strengths": [ "Hosted MCP server at `https://www.mapquestapi.com/mcp` with OAuth and published protected-resource metadata", "Pay-as-you-go price of $0.0045 a transaction published without a login, with 50,000 one-time free transactions", "The Account API creates and lists keys and reports usage by key, service and hour", "`llms.txt` indexes every REST API, SDK and tool with a one-line purpose", "Async batch geocoding accepts up to 1 million rows, and batch calls take 100 locations" ], "weaknesses": [ "No API terms of service found. The legal link leads to System1's 2021 website terms, which allow personal, non-commercial use only", "No status page, changelog or published rate-limit numbers found", "REST keys are sent in the `key` query parameter, and no key scopes or restrictions are documented", "`openapi.json` describes the marketing site and has no paths, so the product APIs have no machine-readable contract", "Monthly plans forbid storing or caching geocodes. That needs an Enterprise account" ], "agentNotes": [ "Register an account and create an API key before connecting the MCP server. Every tool needs an active key, chosen by nickname on first use", "Send REST calls to `https://www.mapquestapi.com` with `key` in the query string, and redact it from logged URLs", "Read `info.statuscode` in geocoding and directions responses. 0 is success, and errors such as 610 (ambiguous location) arrive in the body", "Set `thumbMaps=false` and `maxResults` on geocoding, and `pageSize` (1 to 50) on place search, to keep responses small", "Do not store or cache geocodes on a monthly or pay-as-you-go plan" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 35.1 } ], "editorialScores": { "ergonomics": 60, "maintenance": 23, "payments": 30, "reliability": 23, "schema": 47, "security": 28, "transparency": 21 }, "provenanceScore": 35 }, "connect": { "http": "curl \"https://www.mapquestapi.com/geocoding/v1/address?key=$MAPQUEST_API_KEY\u0026location=Washington,DC\u0026maxResults=1\u0026thumbMaps=false\"", "claudeCode": "claude mcp add --transport http mapquest https://www.mapquestapi.com/mcp", "config": { "mcpServers": { "mapquest": { "url": "https://www.mapquestapi.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/mapquest" }, "area": "everyday", "unitPrices": [ { "item": "MapQuestGO pay-as-you-go", "unit": "1k-requests", "usd": 4.5, "note": "$0.0045 a transaction after 50,000 one-time free transactions" }, { "item": "Basic plan", "unit": "month", "usd": 119, "note": "30,000 transactions a month" }, { "item": "Plus plan", "unit": "month", "usd": 249, "note": "75,000 transactions a month" }, { "item": "Business plan", "unit": "month", "usd": 499, "note": "200,000 transactions a month" }, { "item": "Business Plus plan", "unit": "month", "usd": 949, "note": "500,000 transactions a month" } ], "provenance": { "legalEntity": "Mapquest Holdings LLC", "domain": "mapquest.com", "domainRegistered": "1996-01-10", "endpointOnVendorDomain": false, "terms": "", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The developer site's footer reads '© 2026 Mapquest Holdings LLC, A System1 Company'.", "No terms link is given. The site's Terms of Use link, and developer.mapquest.com/legal, lead to https://system1.com/terms/terms-of-use, the parent's website terms (last updated 26 February 2021), which allow personal, non-commercial use only and do not mention the APIs. We found no API or platform terms published without a login.", "No privacy link is given. The only privacy document linked is the System1 OpCo, LLC group privacy policy at https://system1.com/terms/privacy-policy (last updated 5 July 2023), a parent company's notice.", "The REST API and the MCP server answer at www.mapquestapi.com, a second domain (registered 2008-09-08 per RDAP). MapQuest's own docs name that host. OAuth runs at login.mapquest.com.", "developer.mapquest.com/.well-known/security.txt redirects to the home page, www.mapquestapi.com/.well-known/security.txt returns 404, and www.mapquest.com returned an empty 202 to our reader.", "No status page is linked from the developer site, the docs or the plans page. No changelog was found. The blog carries two product announcements dated 16 July 2026.", "RDAP for mapquest.com gives a registration date of 1996-01-10." ], "score": 35 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mapquest.json", "live": { "slug": "mapquest", "probe": { "target": "https://www.mapquestapi.com", "method": "get", "lastAt": "2026-10-10T02:07:15.371892088Z", "lastOk": true, "lastStatus": 404, "lastMs": 322, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 257, "p95ms24h": 322, "samples24h": 250, "samples30d": 322, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 22, "ok": 22 } ] }, "securityTxt": { "url": "https://mapquest.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-10-09T15:39:51.558930961Z" }, "llmsTxt": { "url": "https://developer.mapquest.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:15.566506813Z" }, "updatedAt": "2026-10-10T02:07:15.371892088Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "HERE Technologies", "b": "MapQuest (System1)", "name": "Vendor" }, { "a": "https://geocode.search.hereapi.com/v1", "b": "https://www.mapquestapi.com", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the HERE Platform Terms", "b": "Proprietary service. No API terms were found published without a login", "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": "2026-07-16", "name": "Last release" }, { "a": "2023-09-18", "b": "no document linked", "name": "Terms last updated" }, { "a": "2024-08-29", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "HERE Location Services scores 58 (C) on agent readiness against MapQuest's 35.1 (F), and leads in 6 of 7 scored categories. MapQuest leads on payments \u0026 pricing.", "question": "Which is better for AI agents, HERE Location Services or MapQuest?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do HERE Location Services and MapQuest need an API key?" }, { "answer": "Yes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and MapQuest at https://www.mapquestapi.com.", "question": "Can an agent call HERE Location Services and MapQuest without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 57 against 23", "Schema \u0026 documentation, 87 against 47", "Agent ergonomics, 74 against 60", "Security \u0026 auth, 65 against 28", "Maintenance \u0026 community, 60 against 23", "Transparency \u0026 trust, 63 against 28" ], "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, 30 against 10" ], "also": [ "No incidents deducted, where HERE Location Services loses 3 points for them" ], "goodFor": "An agent that needs US-centred geocoding, routing with truck profiles, traffic and place search behind one account, with an MCP server ready to connect.", "slug": "mapquest", "watchFor": "No API terms of service found. The legal link leads to System1's 2021 website terms, which allow personal, non-commercial use only" } ], "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-mapquest.json", "title": "Amazon Location Service vs MapQuest", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-mapquest" }, { "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-mapquest.json", "title": "ArcGIS Location Platform vs MapQuest", "url": "https://www.anchorterminal.com/compare/arcgis-vs-mapquest" }, { "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-mapquest.json", "title": "Azure Maps vs MapQuest", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-mapquest" }, { "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-mapquest.json", "title": "Geoapify Location Platform + MCP vs MapQuest", "url": "https://www.anchorterminal.com/compare/geoapify-vs-mapquest" }, { "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-mapquest.json", "title": "Google Maps Platform + Grounding Lite MCP vs MapQuest", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-mapquest" }, { "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-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-mapquest.json", "title": "LocationIQ vs MapQuest", "url": "https://www.anchorterminal.com/compare/locationiq-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-mapquest.json", "title": "Mapbox APIs + MCP vs MapQuest", "url": "https://www.anchorterminal.com/compare/mapbox-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-opencage.json", "title": "MapQuest vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/mapquest-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-radar.json", "title": "MapQuest vs Radar", "url": "https://www.anchorterminal.com/compare/mapquest-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.json", "title": "MapQuest vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps" }, { "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" } ], "scores": [ { "by": 34, "edge": "here-location-services", "here-location-services": 57, "key": "reliability", "mapquest": 23, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 40, "edge": "here-location-services", "here-location-services": 87, "key": "schema", "mapquest": 47, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 14, "edge": "here-location-services", "here-location-services": 74, "key": "ergonomics", "mapquest": 60, "name": "Agent ergonomics", "weight": 13 }, { "by": 37, "edge": "here-location-services", "here-location-services": 65, "key": "security", "mapquest": 28, "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "edge": "mapquest", "here-location-services": 10, "key": "payments", "mapquest": 30, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 37, "edge": "here-location-services", "here-location-services": 60, "key": "maintenance", "mapquest": 23, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 35, "edge": "here-location-services", "here-location-services": 63, "key": "transparency", "mapquest": 28, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "HERE Location Services scores 58 (C) on agent readiness against MapQuest's 35.1 (F), and leads in 6 of 7 scored categories. MapQuest leads on payments \u0026 pricing. 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.", "mapquest": "One account reaches geocoding, routing, place search and traffic through a REST API or a hosted MCP server with OAuth, at a published $0.0045 a transaction. No API terms, status page, changelog or product OpenAPI spec was found, and REST keys travel in the query string." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest", "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.md", "slim": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.min.md" }, "markdown": "HERE Location Services scores 58 (C) on agent readiness against MapQuest's 35.1 (F), and leads in 6 of 7 scored categories. MapQuest leads on payments \u0026 pricing. 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- MapQuest: grade F, 35.1/100, rank #936 of 950. Markdown https://www.anchorterminal.com/tools/mapquest.md · JSON https://www.anchorterminal.com/api/v1/tools/mapquest.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 23\n- Schema \u0026 documentation, 87 against 47\n- Agent ergonomics, 74 against 60\n- Security \u0026 auth, 65 against 28\n- Maintenance \u0026 community, 60 against 23\n- Transparency \u0026 trust, 63 against 28\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### MapQuest (F)\n\nGood for: An agent that needs US-centred geocoding, routing with truck profiles, traffic and place search behind one account, with an MCP server ready to connect.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 10\n\nAlso in its favour:\n- No incidents deducted, where HERE Location Services loses 3 points for them\n\nWatch for: No API terms of service found. The legal link leads to System1's 2021 website terms, which allow personal, non-commercial use only\n\n\n## Score by category\n\n| Category | Weight | HERE Location Services | MapQuest | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 57 | 23 | HERE Location Services +34 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 47 | HERE Location Services +40 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 60 | HERE Location Services +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 65 | 28 | HERE Location Services +37 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 30 | MapQuest +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 23 | HERE Location Services +37 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 28 | HERE Location Services +35 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **58 · C** | **35.1 · F** | |\n\n## Facts side by side\n\n| Fact | HERE Location Services | MapQuest |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | HERE Technologies | MapQuest (System1) |\n| Hosted endpoint | `https://geocode.search.hereapi.com/v1` | `https://www.mapquestapi.com` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under the HERE Platform Terms | Proprietary service. No API terms were found published without a login |\n| Tools exposed | 13 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-09 | 2026-07-16 |\n| Terms last updated | 2023-09-18 | no document linked |\n| Privacy policy last updated | 2024-08-29 | no document linked |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | not found in the text | |\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**MapQuest.** One account reaches geocoding, routing, place search and traffic through a REST API or a hosted MCP server with OAuth, at a published $0.0045 a transaction. No API terms, status page, changelog or product OpenAPI spec was found, and REST keys travel in the query string.\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### MapQuest\n\n1. Register an account and create an API key before connecting the MCP server. Every tool needs an active key, chosen by nickname on first use\n2. Send REST calls to `https://www.mapquestapi.com` with `key` in the query string, and redact it from logged URLs\n3. Read `info.statuscode` in geocoding and directions responses. 0 is success, and errors such as 610 (ambiguous location) arrive in the body\n4. Set `thumbMaps=false` and `maxResults` on geocoding, and `pageSize` (1 to 50) on place search, to keep responses small\n5. Do not store or cache geocodes on a monthly or pay-as-you-go plan\n\n## Questions\n\n### Which is better for AI agents, HERE Location Services or MapQuest?\n\nHERE Location Services scores 58 (C) on agent readiness against MapQuest's 35.1 (F), and leads in 6 of 7 scored categories. MapQuest leads on payments \u0026 pricing.\n\n### Do HERE Location Services and MapQuest need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call HERE Location Services and MapQuest without installing anything?\n\nYes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and MapQuest at https://www.mapquestapi.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.json, and with the fewest tokens: https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"here-location-services\", \"b\": \"mapquest\"}`. From a terminal: `anchor compare here-location-services mapquest`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/here-location-services.json and https://www.anchorterminal.com/api/v1/tools/mapquest.json\n\n## Other comparisons with HERE Location Services or MapQuest\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 MapQuest](https://www.anchorterminal.com/compare/amazon-location-vs-mapquest.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 MapQuest](https://www.anchorterminal.com/compare/arcgis-vs-mapquest.md)\n- [Azure Maps vs HERE Location Services](https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.md)\n- [Azure Maps vs MapQuest](https://www.anchorterminal.com/compare/azure-maps-vs-mapquest.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 MapQuest](https://www.anchorterminal.com/compare/geoapify-vs-mapquest.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 MapQuest](https://www.anchorterminal.com/compare/google-maps-platform-vs-mapquest.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 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 MapQuest](https://www.anchorterminal.com/compare/locationiq-vs-mapquest.md)\n- [Mapbox APIs + MCP vs MapQuest](https://www.anchorterminal.com/compare/mapbox-vs-mapquest.md)\n- [MapQuest vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/mapquest-vs-opencage.md)\n- [MapQuest vs Radar](https://www.anchorterminal.com/compare/mapquest-vs-radar.md)\n- [MapQuest vs Stadia Maps](https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.md)\n- [MapQuest vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapquest-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 MapQuest", "url": "" } ], "description": "HERE Location Services scores 58 (C) to MapQuest's 35.1 (F) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "HERE Location Services C 58", "MapQuest F 35.1", "scores" ], "h1": "HERE Location Services vs MapQuest", "image": "https://www.anchorterminal.com/assets/og/compare-here-location-services-vs-mapquest.png", "path": "/compare/here-location-services-vs-mapquest", "published": "2026-10-01", "section": "tools", "title": "HERE Location Services vs MapQuest for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest" }, "tokens": { "markdown": 2550, "slim": 730 }, "version": 1 }