{ "data": { "a": { "slug": "here-location-services", "name": "HERE Location Services", "vendor": "HERE Technologies", "vendorUrl": "https://www.here.com", "kind": "http-api", "category": "maps", "summary": "HERE Technologies' REST APIs for geocoding, place search, routing, matrix and isoline routing, traffic, transit and map tiles, called with an API key or OAuth token. A hosted MCP server, HERE Location Reasoning, exposes 13 of these operations as tools.", "url": "https://www.anchorterminal.com/tools/here-location-services", "markdownUrl": "https://www.anchorterminal.com/tools/here-location-services.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/here-location-services.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/here-location-services.json", "license": "Proprietary service under the HERE Platform Terms", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://geocode.search.hereapi.com/v1", "packages": [], "auth": "mixed", "authNotes": "Self-serve. A HERE platform account, created in a browser with email verification, lets a person register an app and create up to two API keys, OAuth 2.0 credentials or OAuth 2.1 `private_key_jwt` credentials. REST calls take the key as the `apiKey` query parameter or a bearer token from https://account.api.here.com/oauth2/token. Location Reasoning needs a bearer token on `tools/call` and an account entitlement, and returns 403 without one.", "pricing": "freemium", "pricingNotes": "HERE's docs say a new organisation can get started for free on the Base Plan. The price table at here.com/get-started/pricing is drawn by script and was not read, so no allowance or per-request price is quoted. Support plans run from $50 a month (Developer). Location Reasoning is also sold through AWS Marketplace (checked 2026-10-09).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the Location Reasoning guides or the Platform Terms (checked 2026-10-09).", "endpoints": [] }, "toolCount": 13, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.here.com", "llmsTxt": "https://docs.here.com/llms.txt", "openapi": "https://docs.here.com/geocoding-and-search/reference/get_geocode.md", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "official", "openapi", "llms-txt", "oauth", "free-tier", "enterprise", "eu", "sla", "closed-source" ], "lastRelease": "2026-09-09", "graded": true, "anchor": { "graded": true, "score": 58, "grade": "C", "agentReady": false, "rank": 591, "ranked": true, "rankOf": 950, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 60, "payments": 10, "reliability": 57, "schema": 87, "security": 65, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -3, "negativeNotes": [ "10 July 2026. The Routing v8 changelog marks `mlDuration` as Deprecated and says `return=mlDuration` is still accepted but no longer returns a value. HERE's lifecycle policy says a deprecated feature continues to operate for 6 to 12 months after notice. Three points (https://docs.here.com/routing/docs/routing-v8-changelog.md)" ], "verdict": "Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. The Platform Terms of September 2023 forbid using HERE Materials in connection with a machine learning or AI system, and the price table could not be read.", "bestFor": "Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.", "strengths": [ "Every endpoint page has a Markdown twin holding its OpenAPI 3.0 definition, indexed from `llms.txt` files per product", "99.9 per cent monthly availability targets published for Geocoding and Search v7 and Routing v8", "Lifecycle policy promises six months' notice before a product is discontinued and 6 to 12 months for a deprecated feature", "OAuth 2.1 `private_key_jwt` credentials alongside API keys, with two keys an app for rotation and trusted-domain limits", "ISO 27001, 27701, 27017, 27018 and 42001 certificates, TISAX AL3, and SOC 2 Type 2 for Platform Foundation and Workspace" ], "weaknesses": [ "Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run", "The Base Plan price table is drawn by script, so per-request prices, free allowances and rate limits were not read", "API keys travel in the `apiKey` query parameter", "Results may be cached or stored outside the platform for 30 days at most, and only as HTTP caching headers allow", "Location Reasoning returns 403 unless the account is entitled, and the docs send the reader to an account representative or AWS Marketplace", "The acceptable use policy of January 2022 lists benchmarking and scraping among prohibited activities" ], "agentNotes": [ "Send `Authorization: Bearer` with an OAuth token where logs are kept. The `apiKey` query parameter puts the secret in every URL", "Do not store results for more than 30 days, and follow the HTTP caching headers on each response", "Treat 429 and 503 as throttling. HERE says a traffic surge can be throttled for about 10 minutes below the account's quota", "Read `code`, `cause` and `action` in the error body, and quote `correlationId` to support", "For Location Reasoning, send `initialize`, keep the `Mcp-Session-Id` header on later calls, and send a bearer token on `tools/call`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58 } ], "editorialScores": { "ergonomics": 74, "maintenance": 60, "payments": 10, "reliability": 57, "schema": 87, "security": 65, "transparency": 52 }, "provenanceScore": 73 }, "connect": { "http": "curl \"https://geocode.search.hereapi.com/v1/geocode?q=240+Washington+St.%2C+Boston\u0026limit=4\u0026apiKey=$HERE_API_KEY\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/here-location-services" }, "area": "everyday", "provenance": { "legalEntity": "HERE Europe B.V.", "domain": "here.com", "domainRegistered": "1995-06-11", "endpointOnVendorDomain": false, "terms": "https://www.here.com/en-gb/terms/here-platform-terms-september-2023", "privacy": "https://www.here.com/en-gb/privacy", "statusPage": "https://status.here.com/status", "changelog": "https://docs.here.com/routing/docs/routing-v8-changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The HERE Platform Terms, effective 18 September 2023, name HERE Europe B.V., Kennedyplein 222-226, 5611 ZT Eindhoven, as contracting party, and HERE North America, LLC, Chicago, for customers in the Americas.", "The privacy policy, effective 29 August 2024, names HERE Global B.V. as controller and says it does not apply to personal data processed on behalf of customers. The Platform Terms incorporate it and a Data Processing Agreement published as a PDF.", "The APIs answer on hereapi.com (for example geocode.search.hereapi.com and router.hereapi.com) and the MCP server on hlr.here.ai, both second domains of the vendor.", "www.here.com/.well-known/security.txt returned the site's error page. The security page gives security@here.com and a 90-day disclosure window.", "RDAP for here.com gives a registration date of 1995-06-11.", "legal.here.com/en-gb/terms/here-platform redirects to the September 2023 terms on www.here.com." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/here-location-services.json", "live": { "slug": "here-location-services", "probe": { "target": "https://geocode.search.hereapi.com/v1", "method": "get", "lastAt": "2026-10-10T03:53:29.802604157Z", "lastOk": true, "lastStatus": 404, "lastMs": 47, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 55, "p95ms24h": 97, "samples24h": 125, "samples30d": 125, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.here.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:40.516930569Z" }, "pages": [ { "url": "https://docs.here.com/routing/docs/routing-v8-changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:37:28.07952108Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c940c6209b7e" }, { "url": "https://www.here.com/en-gb/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:50:53.049981302Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bbe0eed0a23e" }, { "url": "https://www.here.com/en-gb/terms/here-platform-terms-september-2023", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:50:55.117836401Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "466d77d5e000" } ], "updatedAt": "2026-10-10T03:53:29.802604157Z" } }, "answer": "OpenCage Geocoding API scores 69.2 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation and security \u0026 auth.", "b": { "slug": "opencage", "name": "OpenCage Geocoding API", "vendor": "OpenCage", "vendorUrl": "https://opencagedata.com", "kind": "http-api", "category": "maps", "summary": "Forward and reverse geocoding on one endpoint, built on OpenStreetMap and other open data, with optional annotations and JSON, GeoJSON, XML or Google-compatible output.", "url": "https://www.anchorterminal.com/tools/opencage", "markdownUrl": "https://www.anchorterminal.com/tools/opencage.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/opencage.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/opencage.json", "repo": "https://github.com/OpenCageData/opencage-geocoding-mcp", "license": "MIT (MCP server)", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.opencagedata.com/geocode/v1/json", "packages": [ { "registry": "npm", "name": "@opencage/mcp-opencage-server" }, { "registry": "npm", "name": "opencage-api-client" }, { "registry": "pypi", "name": "opencage" } ], "auth": "api-key", "authNotes": "A 32-character key passed as the key query parameter. No headers are needed. The MCP server reads OPENCAGE_API_KEY.", "pricing": "paid", "pricingNotes": "Free trial of 2,500 requests a day at 1 a second, for testing only, no card. Monthly subscriptions by daily volume. X-Small $50 (10,000 a day, 15 a second), Small $125 (30,000 a day), Medium $500 (125,000 a day), Large $1,000 (300,000 a day), Enterprise from $2,000. Also priced in GBP (£40 to £800) and eleven other currencies. One-time plans are usable for up to a year. Subscriptions have no hard limits (https://opencagedata.com/pricing, https://opencagedata.com/api.md).", "priceSummary": "$50 / mo", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": 19, "npmWeekly": 5501, "pypiWeekly": 137628, "asOf": "2026-09-30" }, "docsUrl": "https://opencagedata.com/api", "llmsTxt": "https://opencagedata.com/llms.txt", "registryName": "io.github.OpenCageData/opencage-geocoding-mcp", "capabilities": [ "geo.geocode", "geo.reverse" ], "tags": [ "hosted", "llms-txt", "mcp", "official", "python", "typescript", "open-data", "no-card", "eu" ], "lastRelease": "2026-06-25", "graded": true, "anchor": { "graded": true, "score": 69.2, "grade": "B", "agentReady": false, "rank": 193, "ranked": true, "rankOf": 950, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 86, "maintenance": 66, "payments": 35, "reliability": 85, "schema": 77, "security": 47, "transparency": 84 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-10-01" }, "negative": 0, "verdict": "Permanent storage of results on every plan, including after you cancel. Geocoding only, no place search or routing.", "bestFor": "Bulk or repeated geocoding where results go into a database, and for EU data residency.", "strengths": [ "Permanent storage of results on every plan, including after you cancel", "Separate 402 (quota spent) and 429 (too fast) responses", "llms.txt with 70 or more Markdown pages, and agent skills on GitHub", "EU hosting, logs deleted after six months and a no_record option", "Subscriptions don't cut off or bill overage when you go over" ], "weaknesses": [ "Geocoding only, no place search or routing", "The key can only be sent as a query parameter", "The free trial isn't for production use", "MCP server is stdio-only, has no tool annotations, and npm still serves 1.0.3 from September 2025", "No SOC 2 or ISO 27001 of its own" ], "agentNotes": [ "Add no_annotations=1 and limit=1 when you only need coordinates", "Stop on 402, which means the day's quota is gone, and back off on 429", "Add no_record=1 when the query holds personal data", "Redact the key parameter before logging request URLs", "Credit OpenStreetMap wherever you show results" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 69.2 } ], "editorialScores": { "ergonomics": 86, "maintenance": 66, "payments": 35, "reliability": 85, "schema": 77, "security": 47, "transparency": 84 }, "provenanceScore": 84 }, "connect": { "http": "curl \"https://api.opencagedata.com/geocode/v1/json?q=10%20Downing%20Street%2C%20London\u0026limit=1\u0026no_annotations=1\u0026key=$OPENCAGE_API_KEY\"", "claudeCode": "claude mcp add opencage -e OPENCAGE_API_KEY=$OPENCAGE_API_KEY -- npx -y @opencage/mcp-opencage-server", "config": { "mcpServers": { "opencage": { "args": [ "-y", "@opencage/mcp-opencage-server" ], "command": "npx", "env": { "OPENCAGE_API_KEY": "${OPENCAGE_API_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/opencage" }, "area": "everyday", "unitPrices": [ { "item": "X-Small plan", "unit": "month", "usd": 50, "note": "10,000 requests a day, 15 a second" }, { "item": "Small plan", "unit": "month", "usd": 125, "note": "30,000 requests a day, 20 a second" }, { "item": "Medium plan", "unit": "month", "usd": 500, "note": "125,000 requests a day, 25 a second" }, { "item": "Large plan", "unit": "month", "usd": 1000, "note": "300,000 requests a day, 40 a second" } ], "provenance": { "legalEntity": "OpenCage GmbH", "domain": "opencagedata.com", "domainRegistered": "2013-05-16", "endpointOnVendorDomain": true, "terms": "https://opencagedata.com/terms", "privacy": "https://opencagedata.com/gdpr", "statusPage": "https://status.opencagedata.com", "changelog": "https://github.com/OpenCageData/opencagedata-misc-docs/blob/master/CHANGES.md", "securityTxt": "unknown", "checked": "2026-10-01", "notes": [ "The terms give a Berlin address, commercial register HRB 272249 and VAT ID DE323788688.", "Cancelling doesn't refund fees already paid. If OpenCage ends the service it refunds the rest of the billing period pro rata.", "robots.txt blocked our fetch of /.well-known/security.txt. A separate security policy page exists at opencagedata.com/security-policy.", "The API docs point to the dated changelog in OpenCageData/opencagedata-misc-docs (CHANGES.md). Changes are also announced on blog.opencagedata.com.", "The GDPR page was last updated 22 July 2026." ], "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/opencage.json", "live": { "slug": "opencage", "probe": { "target": "https://api.opencagedata.com/geocode/v1/json", "method": "get", "lastAt": "2026-10-10T03:53:36.86571922Z", "lastOk": true, "lastStatus": 401, "lastMs": 303, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 168, "p95ms24h": 272, "samples24h": 249, "samples30d": 2274, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.opencagedata.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:51:06.062037777Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.github.OpenCageData/opencage-geocoding-mcp", "version": "1.0.3", "seenAt": "2026-10-10T03:11:32.438759038Z" }, { "registry": "npm", "name": "@opencage/mcp-opencage-server", "version": "1.0.3", "seenAt": "2026-10-09T17:10:35.723950228Z" }, { "registry": "npm", "name": "opencage-api-client", "version": "2.2.0", "seenAt": "2026-10-09T17:10:36.555646148Z" }, { "registry": "pypi", "name": "opencage", "version": "3.4.0", "released": "2026-06-08", "seenAt": "2026-10-09T17:10:38.018982568Z" } ], "githubStars": 19, "npmWeekly": 30, "pypiWeekly": 252522, "securityTxt": { "url": "https://opencagedata.com/.well-known/security.txt", "state": "valid", "expires": "2027-01-31T00:00:00z", "checkedAt": "2026-10-09T15:40:03.042100041Z" }, "llmsTxt": { "url": "https://opencagedata.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:31.118394032Z" }, "domain": { "domain": "opencagedata.com", "registered": "2013-05-16", "source": "https://rdap.verisign.com/com/v1/domain/opencagedata.com", "checkedAt": "2026-10-04T13:05:30.747621602Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/OpenCageData/opencagedata-misc-docs/master/CHANGES.md", "kind": "changelog", "status": 304, "checkedAt": "2026-10-09T18:44:39.13790752Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "cd00a99974a7" }, { "url": "https://opencagedata.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:42:44.523571679Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "2a4d55e4f714" }, { "url": "https://opencagedata.com/gdpr", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:42:42.451451282Z", "changedAt": "2026-10-07T18:07:57.615589937Z", "fingerprint": "a8a426817cc3" }, { "url": "https://opencagedata.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:42:46.524331898Z", "changedAt": "2026-10-07T18:08:01.691588303Z", "fingerprint": "30104a7082ce" } ], "updatedAt": "2026-10-10T03:53:36.86571922Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "HERE Technologies", "b": "OpenCage", "name": "Vendor" }, { "a": "https://geocode.search.hereapi.com/v1", "b": "https://api.opencagedata.com/geocode/v1/json", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the HERE Platform Terms", "b": "MIT (MCP server)", "name": "Licence" }, { "a": "13", "b": "3", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.OpenCageData/opencage-geocoding-mcp", "name": "MCP registry" }, { "a": "2026-09-09", "b": "2026-06-25", "name": "Last release" }, { "a": "2023-09-18", "b": "no date given", "name": "Terms last updated" }, { "a": "2024-08-29", "b": "no date given", "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": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "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": "19 stars, 5.5k npm/wk, 138k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "OpenCage Geocoding API scores 69.2 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation and security \u0026 auth.", "question": "Which is better for AI agents, HERE Location Services or OpenCage Geocoding API?" }, { "answer": "HERE Location Services takes an API key or an OAuth sign-in. OpenCage Geocoding API needs an API key.", "question": "Do HERE Location Services and OpenCage Geocoding API need an API key?" }, { "answer": "Yes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and OpenCage Geocoding API at https://api.opencagedata.com/geocode/v1/json.", "question": "Can an agent call HERE Location Services and OpenCage Geocoding API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 87 against 77", "Security \u0026 auth, 65 against 47" ], "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, 85 against 57", "Agent ergonomics, 86 against 74", "Payments \u0026 pricing, 35 against 10", "Maintenance \u0026 community, 66 against 60", "Transparency \u0026 trust, 84 against 63" ], "also": [ "Runs on your own machine", "Free to start without a card", "No incidents deducted, where HERE Location Services loses 3 points for them" ], "goodFor": "Bulk or repeated geocoding where results go into a database, and for EU data residency.", "slug": "opencage", "watchFor": "Geocoding only, no place search or routing" } ], "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-opencage.json", "title": "Amazon Location Service vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-opencage" }, { "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-opencage.json", "title": "ArcGIS Location Platform vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/arcgis-vs-opencage" }, { "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-opencage.json", "title": "Azure Maps vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-opencage" }, { "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-opencage.json", "title": "Geoapify Location Platform + MCP vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/geoapify-vs-opencage" }, { "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-opencage.json", "title": "Google Maps Platform + Grounding Lite MCP vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.json", "title": "HERE Location Services vs LocationIQ", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.json", "title": "HERE Location Services vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapbox" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.json", "title": "HERE Location Services vs MapQuest", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-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-opencage.json", "title": "LocationIQ vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/locationiq-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-opencage.json", "title": "Mapbox APIs + MCP vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/mapbox-vs-opencage" }, { "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/opencage-vs-radar.json", "title": "OpenCage Geocoding API vs Radar", "url": "https://www.anchorterminal.com/compare/opencage-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/opencage-vs-stadia-maps.json", "title": "OpenCage Geocoding API vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/opencage-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/opencage-vs-tomtom.json", "title": "OpenCage Geocoding API vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/opencage-vs-tomtom" } ], "scores": [ { "by": 28, "edge": "opencage", "here-location-services": 57, "key": "reliability", "name": "Reliability", "opencage": 85, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 10, "edge": "here-location-services", "here-location-services": 87, "key": "schema", "name": "Schema \u0026 documentation", "opencage": 77, "weight": 13 }, { "by": 12, "edge": "opencage", "here-location-services": 74, "key": "ergonomics", "name": "Agent ergonomics", "opencage": 86, "weight": 13 }, { "by": 18, "edge": "here-location-services", "here-location-services": 65, "key": "security", "name": "Security \u0026 auth", "opencage": 47, "weight": 14 }, { "by": 25, "edge": "opencage", "here-location-services": 10, "key": "payments", "name": "Payments \u0026 pricing", "opencage": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 6, "edge": "opencage", "here-location-services": 60, "key": "maintenance", "name": "Maintenance \u0026 community", "opencage": 66, "weight": 7 }, { "by": 21, "edge": "opencage", "here-location-services": 63, "key": "transparency", "name": "Transparency \u0026 trust", "opencage": 84, "weight": 7 } ], "summary": "OpenCage Geocoding API scores 69.2 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation and security \u0026 auth. 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.", "opencage": "Permanent storage of results on every plan, including after you cancel. Geocoding only, no place search or routing." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage", "json": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage.md", "slim": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage.min.md" }, "markdown": "OpenCage Geocoding API scores 69.2 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation and security \u0026 auth. 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- OpenCage Geocoding API: grade B, 69.2/100, rank #193 of 950. Markdown https://www.anchorterminal.com/tools/opencage.md · JSON https://www.anchorterminal.com/api/v1/tools/opencage.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 77\n- Security \u0026 auth, 65 against 47\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### OpenCage Geocoding API (B)\n\nGood for: Bulk or repeated geocoding where results go into a database, and for EU data residency.\n\nAhead on:\n- Reliability, 85 against 57\n- Agent ergonomics, 86 against 74\n- Payments \u0026 pricing, 35 against 10\n- Maintenance \u0026 community, 66 against 60\n- Transparency \u0026 trust, 84 against 63\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n- No incidents deducted, where HERE Location Services loses 3 points for them\n\nWatch for: Geocoding only, no place search or routing\n\n\n## Score by category\n\n| Category | Weight | HERE Location Services | OpenCage Geocoding API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 57 | 85 | OpenCage Geocoding API +28 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 77 | HERE Location Services +10 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 86 | OpenCage Geocoding API +12 |\n| Security \u0026 auth | 14% (17.5 this run) | 65 | 47 | HERE Location Services +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 35 | OpenCage Geocoding API +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 66 | OpenCage Geocoding API +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 84 | OpenCage Geocoding API +21 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **58 · C** | **69.2 · B** | |\n\n## Facts side by side\n\n| Fact | HERE Location Services | OpenCage Geocoding API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | HERE Technologies | OpenCage |\n| Hosted endpoint | `https://geocode.search.hereapi.com/v1` | `https://api.opencagedata.com/geocode/v1/json` |\n| Transports | HTTP, Streamable HTTP | HTTP, stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under the HERE Platform Terms | MIT (MCP server) |\n| Tools exposed | 13 | 3 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.OpenCageData/opencage-geocoding-mcp` |\n| Last release | 2026-09-09 | 2026-06-25 |\n| Terms last updated | 2023-09-18 | no date given |\n| Privacy policy last updated | 2024-08-29 | no date given |\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 | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\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| Popularity | none | 19 stars, 5.5k npm/wk, 138k PyPI/wk |\n| Agent reviews | none | 3.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**OpenCage Geocoding API.** Permanent storage of results on every plan, including after you cancel. Geocoding only, no place search or routing.\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### OpenCage Geocoding API\n\n1. Add no_annotations=1 and limit=1 when you only need coordinates\n2. Stop on 402, which means the day's quota is gone, and back off on 429\n3. Add no_record=1 when the query holds personal data\n4. Redact the key parameter before logging request URLs\n5. Credit OpenStreetMap wherever you show results\n\n## Questions\n\n### Which is better for AI agents, HERE Location Services or OpenCage Geocoding API?\n\nOpenCage Geocoding API scores 69.2 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation and security \u0026 auth.\n\n### Do HERE Location Services and OpenCage Geocoding API need an API key?\n\nHERE Location Services takes an API key or an OAuth sign-in. OpenCage Geocoding API needs an API key.\n\n### Can an agent call HERE Location Services and OpenCage Geocoding API without installing anything?\n\nYes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and OpenCage Geocoding API at https://api.opencagedata.com/geocode/v1/json.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/here-location-services-vs-opencage.json, and with the fewest tokens: https://www.anchorterminal.com/compare/here-location-services-vs-opencage.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"here-location-services\", \"b\": \"opencage\"}`. From a terminal: `anchor compare here-location-services opencage`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/here-location-services.json and https://www.anchorterminal.com/api/v1/tools/opencage.json\n\n## Other comparisons with HERE Location Services or OpenCage Geocoding API\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 OpenCage Geocoding API](https://www.anchorterminal.com/compare/amazon-location-vs-opencage.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 OpenCage Geocoding API](https://www.anchorterminal.com/compare/arcgis-vs-opencage.md)\n- [Azure Maps vs HERE Location Services](https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.md)\n- [Azure Maps vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/azure-maps-vs-opencage.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 OpenCage Geocoding API](https://www.anchorterminal.com/compare/geoapify-vs-opencage.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 OpenCage Geocoding API](https://www.anchorterminal.com/compare/google-maps-platform-vs-opencage.md)\n- [HERE Location Services vs LocationIQ](https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.md)\n- [HERE Location Services vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.md)\n- [HERE Location Services vs MapQuest](https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.md)\n- [HERE Location Services vs 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 OpenCage Geocoding API](https://www.anchorterminal.com/compare/locationiq-vs-opencage.md)\n- [Mapbox APIs + MCP vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/mapbox-vs-opencage.md)\n- [MapQuest vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/mapquest-vs-opencage.md)\n- [OpenCage Geocoding API vs Radar](https://www.anchorterminal.com/compare/opencage-vs-radar.md)\n- [OpenCage Geocoding API vs Stadia Maps](https://www.anchorterminal.com/compare/opencage-vs-stadia-maps.md)\n- [OpenCage Geocoding API vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/opencage-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 OpenCage Geocoding API", "url": "" } ], "description": "OpenCage Geocoding scores 69.2 (B) 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", "OpenCage Geocoding API B 69.2", "scores" ], "h1": "HERE Location Services vs OpenCage Geocoding API", "image": "https://www.anchorterminal.com/assets/og/compare-here-location-services-vs-opencage.png", "path": "/compare/here-location-services-vs-opencage", "published": "2026-10-01", "section": "tools", "title": "HERE Location Services vs OpenCage Geocoding for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage" }, "tokens": { "markdown": 2600, "slim": 730 }, "version": 1 }