{ "data": { "a": { "slug": "geoapify", "name": "Geoapify Location Platform + MCP", "vendor": "Geoapify", "vendorUrl": "https://www.geoapify.com", "kind": "http-api", "category": "maps", "summary": "Geocoding, reverse geocoding, autocomplete, Places search by category, Routing, Route Matrix, isolines and map tiles, with OpenStreetMap attribution required on every plan.", "url": "https://www.anchorterminal.com/tools/geoapify", "markdownUrl": "https://www.anchorterminal.com/tools/geoapify.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/geoapify.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/geoapify.json", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.geoapify.com/v1", "packages": [], "auth": "api-key", "authNotes": "API key as the apiKey query parameter or the x-api-key header, both defined in the OpenAPI specs. The hosted MCP takes x-api-key. api-eu.geoapify.com serves the same API on EU infrastructure.", "pricing": "freemium", "pricingNotes": "Free 3,000 credits a day at 5 requests a second, commercial and production use allowed, no card, with a Geoapify attribution link required. API 10 $59 a month (10,000 credits a day, 12 a second), API 25 $109 (25,000), API 50 $179 (50,000), API 100 $299 (100,000), API 250 $609 (250,000), Custom from $860. A simple geocoding, places or routing request costs 1 credit (https://www.geoapify.com/pricing/). Over MCP, initialize, tools/list and notifications cost nothing and each tools/call is billed as the Geoapify API operation behind it (https://apidocs.geoapify.com/how-to/api-tooling-ai/connect-ai-client-mcp/).", "priceSummary": "$59 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 11, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://apidocs.geoapify.com/docs", "openapi": "https://apidocs.geoapify.com/open-api/", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "official", "free-tier", "no-card", "open-data", "eu", "closed-source" ], "graded": true, "anchor": { "graded": true, "score": 55.3, "grade": "C", "agentReady": false, "rank": 658, "ranked": true, "rankOf": 950, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 61, "payments": 30, "reliability": 60, "schema": 74, "security": 29, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Free plan allows commercial production use, 3,000 credits a day, no card. No security.txt, disclosure policy, bug bounty or certification found.", "bestFor": "Cheap geocoding, category place search, routing and isolines on OpenStreetMap data, with commercial use on the free plan and EU hosting.", "strengths": [ "Free plan allows commercial production use, 3,000 credits a day, no card", "OpenAPI 3.1 specs for 22 APIs and one per MCP tool, with error examples", "Data for successful requests held no longer than 24 hours, hosted in the EU", "99.5 per cent monthly availability on paid plans, with discounts below it", "MCP tool descriptions say which tool to use instead" ], "weaknesses": [ "No security.txt, disclosure policy, bug bounty or certification found", "No public changelog or deprecation policy, and the terms allow changes without notice", "Storage rights appear in the docs but not in the terms", "The specs recommend the apiKey query parameter for public APIs", "Credits are counted per day, so bursts hit the cap early" ], "agentNotes": [ "Send the key as x-api-key, which the specs support, rather than apiKey in the URL", "Use api-eu.geoapify.com when the data has to stay on EU infrastructure", "Use calculate_route for geometry and directions, and calculate_route_matrix only for travel times between many points", "Read a 429 'Quota exceeded' as the day's credits being gone, not a burst, and wait for the daily reset", "Show OpenStreetMap attribution wherever you display results" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.3 } ], "editorialScores": { "ergonomics": 72, "maintenance": 61, "payments": 30, "reliability": 60, "schema": 74, "security": 29, "transparency": 52 }, "provenanceScore": 72 }, "connect": { "http": "curl \"https://api.geoapify.com/v1/geocode/search?text=10%20Downing%20Street%2C%20London\u0026limit=1\u0026format=json\u0026apiKey=$GEOAPIFY_API_KEY\"", "claudeCode": "claude mcp add --transport http geoapify https://api.geoapify.com/v1/mcp --header \"x-api-key: $GEOAPIFY_API_KEY\"", "config": { "mcpServers": { "geoapify": { "headers": { "x-api-key": "${GEOAPIFY_API_KEY}" }, "type": "http", "url": "https://api.geoapify.com/v1/mcp" } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/geoapify" }, "area": "everyday", "unitPrices": [ { "item": "API 10 plan", "unit": "month", "usd": 59, "note": "10,000 credits a day, 12 requests a second" }, { "item": "API 25 plan", "unit": "month", "usd": 109, "note": "25,000 credits a day" }, { "item": "API 100 plan", "unit": "month", "usd": 299, "note": "100,000 credits a day, 25 requests a second" }, { "item": "API 250 plan", "unit": "month", "usd": 609, "note": "250,000 credits a day" } ], "provenance": { "legalEntity": "KEPTAGO LTD", "domain": "geoapify.com", "domainRegistered": "2018-10-26", "endpointOnVendorDomain": true, "terms": "https://www.geoapify.com/terms-and-conditions/", "privacy": "https://www.geoapify.com/privacy-policy/", "statusPage": "https://status.geoapify.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-01", "notes": [ "The terms name KEPTAGO LTD, registered in Paphos, Cyprus, trading as Geoapify. Version 5, dated 2 February 2024.", "www.geoapify.com/.well-known/security.txt returns 404.", "status.geoapify.com redirects to an UptimeRobot status page.", "We found no public changelog. The OpenAPI specs repository on GitHub has dated commits.", "The privacy policy was last modified 1 April 2026." ], "score": 72 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/geoapify.json", "live": { "slug": "geoapify", "probe": { "target": "https://api.geoapify.com/v1", "method": "get", "lastAt": "2026-10-10T02:07:09.807376703Z", "lastOk": true, "lastStatus": 401, "lastMs": 82, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 129, "p95ms24h": 239, "samples24h": 250, "samples30d": 2256, "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": 22, "ok": 22 } ] }, "vendorStatus": { "page": "https://status.geoapify.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:37.1656829Z" }, "securityTxt": { "url": "https://geoapify.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:40:18.50303449Z" }, "domain": { "domain": "geoapify.com", "registered": "2018-10-26", "source": "https://rdap.verisign.com/com/v1/domain/geoapify.com", "checkedAt": "2026-10-04T13:07:12.953394282Z" }, "pages": [ { "url": "https://www.geoapify.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:50:22.903128181Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f9a9f1600f52" }, { "url": "https://www.geoapify.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:50:25.272327671Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "37eb22e1e50f" }, { "url": "https://www.geoapify.com/terms-and-conditions/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:50:27.062998727Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c5c95d7b727d" } ], "updatedAt": "2026-10-10T02:07:09.807376703Z" } }, "answer": "HERE Location Services scores 58 (C) on agent readiness against Geoapify Location Platform + MCP's 55.3 (C), and leads in 4 of 7 scored categories. Geoapify Location Platform + MCP leads on payments \u0026 pricing.", "b": { "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" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Geoapify", "b": "HERE Technologies", "name": "Vendor" }, { "a": "https://api.geoapify.com/v1", "b": "https://geocode.search.hereapi.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under the HERE Platform Terms", "name": "Licence" }, { "a": "11", "b": "13", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-09-09", "name": "Last release" }, { "a": "no date given", "b": "2023-09-18", "name": "Terms last updated" }, { "a": "no date given", "b": "2024-08-29", "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": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "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": "4/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "HERE Location Services scores 58 (C) on agent readiness against Geoapify Location Platform + MCP's 55.3 (C), and leads in 4 of 7 scored categories. Geoapify Location Platform + MCP leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Geoapify Location Platform + MCP or HERE Location Services?" }, { "answer": "Geoapify Location Platform + MCP needs an API key. HERE Location Services takes an API key or an OAuth sign-in.", "question": "Do Geoapify Location Platform + MCP and HERE Location Services need an API key?" }, { "answer": "Yes. Geoapify Location Platform + MCP has a hosted endpoint at https://api.geoapify.com/v1 and HERE Location Services at https://geocode.search.hereapi.com/v1.", "question": "Can an agent call Geoapify Location Platform + MCP and HERE Location Services without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 30 against 10" ], "also": [ "Free to start without a card", "No incidents deducted, where HERE Location Services loses 3 points for them" ], "goodFor": "Cheap geocoding, category place search, routing and isolines on OpenStreetMap data, with commercial use on the free plan and EU hosting.", "slug": "geoapify", "watchFor": "No security.txt, disclosure policy, bug bounty or certification found" }, { "aheadOn": [ "Schema \u0026 documentation, 87 against 74", "Security \u0026 auth, 65 against 29" ], "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" } ], "job": { "capability": "geo.geocode", "name": "Geocoding" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-geoapify.json", "title": "Amazon Location Service vs Geoapify Location Platform + MCP", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-geoapify" }, { "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/arcgis-vs-geoapify.json", "title": "ArcGIS Location Platform vs Geoapify Location Platform + MCP", "url": "https://www.anchorterminal.com/compare/arcgis-vs-geoapify" }, { "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/azure-maps-vs-geoapify.json", "title": "Azure Maps vs Geoapify Location Platform + MCP", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-geoapify" }, { "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/geoapify-vs-google-maps-platform.json", "title": "Geoapify Location Platform + MCP vs Google Maps Platform + Grounding Lite MCP", "url": "https://www.anchorterminal.com/compare/geoapify-vs-google-maps-platform" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-locationiq.json", "title": "Geoapify Location Platform + MCP vs LocationIQ", "url": "https://www.anchorterminal.com/compare/geoapify-vs-locationiq" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-mapbox.json", "title": "Geoapify Location Platform + MCP vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/geoapify-vs-mapbox" }, { "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/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/geoapify-vs-radar.json", "title": "Geoapify Location Platform + MCP vs Radar", "url": "https://www.anchorterminal.com/compare/geoapify-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps.json", "title": "Geoapify Location Platform + MCP vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom.json", "title": "Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services.json", "title": "Google Maps Platform + Grounding Lite MCP vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.json", "title": "HERE Location Services vs LocationIQ", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.json", "title": "HERE Location Services vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapbox" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.json", "title": "HERE Location Services vs MapQuest", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage.json", "title": "HERE Location Services vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-radar.json", "title": "HERE Location Services vs Radar", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.json", "title": "HERE Location Services vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/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" } ], "scores": [ { "by": 3, "edge": "geoapify", "geoapify": 60, "here-location-services": 57, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "edge": "here-location-services", "geoapify": 74, "here-location-services": 87, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 2, "edge": "here-location-services", "geoapify": 72, "here-location-services": 74, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 36, "edge": "here-location-services", "geoapify": 29, "here-location-services": 65, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "edge": "geoapify", "geoapify": 30, "here-location-services": 10, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 1, "edge": "geoapify", "geoapify": 61, "here-location-services": 60, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 1, "edge": "here-location-services", "geoapify": 62, "here-location-services": 63, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "HERE Location Services scores 58 (C) on agent readiness against Geoapify Location Platform + MCP's 55.3 (C), and leads in 4 of 7 scored categories. Geoapify Location Platform + MCP leads on payments \u0026 pricing. Both do geocoding.", "verdicts": { "geoapify": "Free plan allows commercial production use, 3,000 credits a day, no card. No security.txt, disclosure policy, bug bounty or certification found.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/geoapify-vs-here-location-services", "json": "https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.md", "slim": "https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.min.md" }, "markdown": "HERE Location Services scores 58 (C) on agent readiness against Geoapify Location Platform + MCP's 55.3 (C), and leads in 4 of 7 scored categories. Geoapify Location Platform + MCP leads on payments \u0026 pricing. Both do geocoding.\n\n- Geoapify Location Platform + MCP: grade C, 55.3/100, rank #658 of 950. Markdown https://www.anchorterminal.com/tools/geoapify.md · JSON https://www.anchorterminal.com/api/v1/tools/geoapify.json\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- 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### Geoapify Location Platform + MCP (C)\n\nGood for: Cheap geocoding, category place search, routing and isolines on OpenStreetMap data, with commercial use on the free plan and EU hosting.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 10\n\nAlso in its favour:\n- Free to start without a card\n- No incidents deducted, where HERE Location Services loses 3 points for them\n\nWatch for: No security.txt, disclosure policy, bug bounty or certification found\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 74\n- Security \u0026 auth, 65 against 29\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\n## Score by category\n\n| Category | Weight | Geoapify Location Platform + MCP | HERE Location Services | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 60 | 57 | Geoapify Location Platform + MCP +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 74 | 87 | HERE Location Services +13 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 74 | HERE Location Services +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 29 | 65 | HERE Location Services +36 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 10 | Geoapify Location Platform + MCP +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 61 | 60 | Geoapify Location Platform + MCP +1 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 62 | 63 | HERE Location Services +1 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **55.3 · C** | **58 · C** | |\n\n## Facts side by side\n\n| Fact | Geoapify Location Platform + MCP | HERE Location Services |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Geoapify | HERE Technologies |\n| Hosted endpoint | `https://api.geoapify.com/v1` | `https://geocode.search.hereapi.com/v1` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | none | Proprietary service under the HERE Platform Terms |\n| Tools exposed | 11 | 13 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | none | 2026-09-09 |\n| Terms last updated | no date given | 2023-09-18 |\n| Privacy policy last updated | no date given | 2024-08-29 |\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 | not found in the text | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Agent reviews | 4/5 (2) | none |\n\n## Verdicts\n\n**Geoapify Location Platform + MCP.** Free plan allows commercial production use, 3,000 credits a day, no card. No security.txt, disclosure policy, bug bounty or certification found.\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## Before you call either\n\n### Geoapify Location Platform + MCP\n\n1. Send the key as x-api-key, which the specs support, rather than apiKey in the URL\n2. Use api-eu.geoapify.com when the data has to stay on EU infrastructure\n3. Use calculate_route for geometry and directions, and calculate_route_matrix only for travel times between many points\n4. Read a 429 'Quota exceeded' as the day's credits being gone, not a burst, and wait for the daily reset\n5. Show OpenStreetMap attribution wherever you display results\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## Questions\n\n### Which is better for AI agents, Geoapify Location Platform + MCP or HERE Location Services?\n\nHERE Location Services scores 58 (C) on agent readiness against Geoapify Location Platform + MCP's 55.3 (C), and leads in 4 of 7 scored categories. Geoapify Location Platform + MCP leads on payments \u0026 pricing.\n\n### Do Geoapify Location Platform + MCP and HERE Location Services need an API key?\n\nGeoapify Location Platform + MCP needs an API key. HERE Location Services takes an API key or an OAuth sign-in.\n\n### Can an agent call Geoapify Location Platform + MCP and HERE Location Services without installing anything?\n\nYes. Geoapify Location Platform + MCP has a hosted endpoint at https://api.geoapify.com/v1 and HERE Location Services at https://geocode.search.hereapi.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.json, and with the fewest tokens: https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"geoapify\", \"b\": \"here-location-services\"}`. From a terminal: `anchor compare geoapify here-location-services`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/geoapify.json and https://www.anchorterminal.com/api/v1/tools/here-location-services.json\n\n## Other comparisons with Geoapify Location Platform + MCP or HERE Location Services\n\n- [Amazon Location Service vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-geoapify.md)\n- [Amazon Location Service vs HERE Location Services](https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.md)\n- [ArcGIS Location Platform vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/arcgis-vs-geoapify.md)\n- [ArcGIS Location Platform vs HERE Location Services](https://www.anchorterminal.com/compare/arcgis-vs-here-location-services.md)\n- [Azure Maps vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-geoapify.md)\n- [Azure Maps vs HERE Location Services](https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.md)\n- [Geoapify Location Platform + MCP vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/geoapify-vs-google-maps-platform.md)\n- [Geoapify Location Platform + MCP vs LocationIQ](https://www.anchorterminal.com/compare/geoapify-vs-locationiq.md)\n- [Geoapify Location Platform + MCP vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/geoapify-vs-mapbox.md)\n- [Geoapify Location Platform + MCP vs MapQuest](https://www.anchorterminal.com/compare/geoapify-vs-mapquest.md)\n- [Geoapify Location Platform + MCP vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/geoapify-vs-opencage.md)\n- [Geoapify Location Platform + MCP vs Radar](https://www.anchorterminal.com/compare/geoapify-vs-radar.md)\n- [Geoapify Location Platform + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps.md)\n- [Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geoapify-vs-tomtom.md)\n- [Google Maps Platform + Grounding Lite MCP vs HERE Location Services](https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services.md)\n- [HERE Location Services vs LocationIQ](https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.md)\n- [HERE Location Services vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.md)\n- [HERE Location Services vs MapQuest](https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.md)\n- [HERE Location Services vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/here-location-services-vs-opencage.md)\n- [HERE Location Services vs Radar](https://www.anchorterminal.com/compare/here-location-services-vs-radar.md)\n- [HERE Location Services vs Stadia Maps](https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.md)\n- [HERE Location Services vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-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": "Geoapify Location Platform + MCP vs HERE Location Services", "url": "" } ], "description": "HERE Location Services scores 58 (C) to Geoapify Location Platform's 55.3 (C) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Geoapify Location Platform + MCP C 55.3", "HERE Location Services C 58", "scores" ], "h1": "Geoapify Location Platform + MCP vs HERE Location Services", "image": "https://www.anchorterminal.com/assets/og/compare-geoapify-vs-here-location-services.png", "path": "/compare/geoapify-vs-here-location-services", "published": "2026-10-01", "section": "tools", "title": "Geoapify Location Platform vs HERE Location Services (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/geoapify-vs-here-location-services" }, "tokens": { "markdown": 2650, "slim": 680 }, "version": 1 }