{ "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-10T03:53:28.453679826Z", "lastOk": true, "lastStatus": 401, "lastMs": 205, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 126, "p95ms24h": 239, "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.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-10T03:53:28.453679826Z" } }, "answer": "Geoapify Location Platform + MCP scores 55.3 (C) on agent readiness against Radar's 53.3 (D), and leads in 4 of 7 scored categories. Radar leads on reliability, security \u0026 auth and maintenance \u0026 community.", "b": { "slug": "radar", "name": "Radar", "vendor": "Radar Labs", "vendorUrl": "https://radar.com", "kind": "http-api", "category": "maps", "summary": "Radar is a location platform from Radar Labs with REST APIs for forward, reverse and IP geocoding, address autocomplete and validation, places search, distance, matrix, directions and route optimisation, plus geofencing, trip tracking and base maps.", "url": "https://www.anchorterminal.com/tools/radar", "markdownUrl": "https://www.anchorterminal.com/tools/radar.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/radar.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/radar.json", "repo": "https://github.com/radarlabs/radar-sdk-js", "license": "Proprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://api.radar.io/v1", "packages": [ { "registry": "npm", "name": "radar-sdk-js" } ], "auth": "api-key", "authNotes": "API key in the `Authorization` header, with no query-string option documented. Each project has four keys, test and live, publishable and secret. Publishable keys reach 16 of the 36 documented operations, including all geocoding, search and routing calls, and can be restricted by website domain or mobile app identifier. Secret keys reach the rest and can read or write any data. Keys come from the dashboard. Whether sign-up is self-serve was not established, because dashboard.radar.com's robots.txt closes every path.", "pricing": "paid", "pricingNotes": "Core Maps (forward, reverse and IP geocoding, autocomplete, static maps, distance, directions, matrix) starts at $0.50 per 1,000 API calls and Premium Maps (address validation, places search, route matching, route optimisation, satellite maps) at $2.00. Matrix bills per element. Every plan is an annual commitment with a monthly quota, at a rate Radar sets by quote. The pricing page says there is no free tier, and that teams can start with a technical validation period arranged with sales (https://radar.com/pricing).", "priceSummary": "$0.50 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, the docs index or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.radar.com/api", "llmsTxt": "https://docs.radar.com/llms.txt", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "api-key", "llms-txt", "status-page", "sales-led", "annual-contract", "soc2", "closed-source" ], "lastRelease": "2026-09-14", "graded": true, "anchor": { "graded": true, "score": 53.3, "grade": "D", "agentReady": false, "rank": 713, "ranked": true, "rankOf": 950, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 77, "payments": 10, "reliability": 70, "schema": 50, "security": 56, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -2, "negativeNotes": [ "9 October 2026. The Maps product page says the geocoding APIs come with 'the right to store, reuse, and export results freely' (https://radar.com/product/maps), while section 2(d) of the Terms of Use forbids storing address or point-of-interest data from the geocoding, autocomplete or place search APIs for more than 30 days (https://radar.com/terms) and the geocoding docs repeat the 30-day limit (https://docs.radar.com/maps/geocoding.md). 2 points for a claim the published terms contradict. A quoted enterprise agreement may differ and is not published." ], "verdict": "Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found.", "bestFor": "A company that already has a Radar contract, or wants geofencing and trip tracking with geocoding and routing on one key.", "strengths": [ "Each of the 36 documented operations states its key level and a default rate limit, from 10 to 100 requests a second", "docs.radar.com publishes llms.txt and a Markdown twin of every page, including the whole API reference in one file", "Statuspage history lists two API incidents in the 90 days to 9 October 2026, of 3 minutes and about an hour", "Publishable keys are limited to 16 client-safe operations and can be restricted by website domain or mobile app identifier", "The DPA names two sub-processors (AWS and MongoDB) and the FAQ states default retention periods" ], "weaknesses": [ "The pricing page says Radar has no free tier and every plan is an annual commitment set by quote", "No OpenAPI description and no API changelog were found in the docs index", "The terms cap storage of geocoding, autocomplete and place results at 30 days, while the Maps product page claims a right to store results freely", "The terms of 24 May 2023 let Radar change or stop the services without notice, and still describe a free version", "A secret key can read or write any project data, with no scopes found", "The terms forbid using the services to develop or test other geocoding, autocomplete or place search APIs, which matters before any probe is run" ], "agentNotes": [ "Send the key in the `Authorization` header with no `Bearer` prefix, and call `https://api.radar.io/v1`, not radar.com", "Use a publishable key for geocoding, search and routing. Keep the secret key for users, trips, geofences and beacons", "Call `/v1/search/autocomplete` for partial addresses and place names. `/v1/geocode/forward` is documented as best for complete addresses", "Set `units=metric` on routing calls. The default is imperial, with distances in feet", "Treat 429 as one of three things (rate limit, no state change or selective throttling) and 402 as usage exceeded. No Retry-After header is documented", "Do not keep geocoding, autocomplete or place results for more than 30 days" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.3 } ], "editorialScores": { "ergonomics": 65, "maintenance": 77, "payments": 10, "reliability": 70, "schema": 50, "security": 56, "transparency": 51 }, "provenanceScore": 58 }, "connect": { "install": "npm install radar-sdk-js", "http": "curl \"https://api.radar.io/v1/geocode/forward?query=20+jay+st+brooklyn+ny\" -H \"Authorization: $RADAR_PUBLISHABLE_KEY\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/radar" }, "area": "everyday", "unitPrices": [ { "item": "Core Maps API calls, starting price", "unit": "1k-requests", "usd": 0.5, "note": "Geocoding, autocomplete, static maps, distance, directions, matrix (per element). Annual commitment, rate set by quote" }, { "item": "Premium Maps API calls, starting price", "unit": "1k-requests", "usd": 2, "note": "Address validation, places search, route matching, route optimisation, satellite maps. Annual commitment, rate set by quote" } ], "provenance": { "legalEntity": "Radar Labs, Inc.", "domain": "radar.com", "domainRegistered": "1994-12-16", "endpointOnVendorDomain": false, "terms": "https://radar.com/terms", "privacy": "https://radar.com/privacy", "statusPage": "https://status.radar.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The privacy notice (last updated 13 May 2025) names Radar Labs, Inc., a Delaware corporation at 111 5th Ave, 12th Floor, New York, NY 10003.", "The Terms of Use (last updated 24 May 2023) cover the SDK and Radar's APIs and incorporate the DPA at radar.com/dpa. They describe a free version, which the pricing page says Radar does not have. Paid plans are by quote, and no enterprise agreement is published.", "The API answers at api.radar.io, a second domain. Nothing was sent to it, and its registrant was not checked.", "radar.com/.well-known/security.txt answers 404. The FAQ gives security@radar.com for reports.", "No API changelog was found in the docs index. The web SDK repository has dated release tags.", "RDAP gives 16 December 1994 as the registration date of radar.com.", "robots.txt answers on the day. radar.com 200 with a sitemap line only. docs.radar.com 200 with ai-input=yes. status.radar.com 200 disallowing /api/ and /embed/. dashboard.radar.com 200 disallowing every path. trust.radar.com answers the request with its page shell." ], "score": 58 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/radar.json", "live": { "slug": "radar", "probe": { "target": "https://api.radar.io/v1", "method": "get", "lastAt": "2026-10-10T03:53:39.730180732Z", "lastOk": true, "lastStatus": 404, "lastMs": 113, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 122, "p95ms24h": 233, "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.radar.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T03:58:44.779248416Z" }, "versions": [ { "registry": "github", "name": "radarlabs/radar-sdk-js", "version": "autocomplete-v1.1.1", "released": "2026-09-14", "seenAt": "2026-10-09T17:15:51.370576682Z" }, { "registry": "npm", "name": "radar-sdk-js", "version": "5.2.0", "seenAt": "2026-10-09T17:15:50.510226325Z" } ], "githubStars": 52, "npmWeekly": 62814, "pages": [ { "url": "https://radar.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:44:14.0723216Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "22ff53a04e1c" }, { "url": "https://radar.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:44:16.223416673Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "12f29204b40d" }, { "url": "https://radar.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:44:18.136602575Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "411754a84910" } ], "updatedAt": "2026-10-10T03:58:44.779248416Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Geoapify", "b": "Radar Labs", "name": "Vendor" }, { "a": "https://api.geoapify.com/v1", "b": "https://api.radar.io/v1", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0", "name": "Licence" }, { "a": "11", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-09-14", "name": "Last release" }, { "a": "no date given", "b": "2023-05-24", "name": "Terms last updated" }, { "a": "no date given", "b": "2025-05-13", "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": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "4/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Geoapify Location Platform + MCP scores 55.3 (C) on agent readiness against Radar's 53.3 (D), and leads in 4 of 7 scored categories. Radar leads on reliability, security \u0026 auth and maintenance \u0026 community.", "question": "Which is better for AI agents, Geoapify Location Platform + MCP or Radar?" }, { "answer": "Both need an API key.", "question": "Do Geoapify Location Platform + MCP and Radar need an API key?" }, { "answer": "Yes. Geoapify Location Platform + MCP has a hosted endpoint at https://api.geoapify.com/v1 and Radar at https://api.radar.io/v1.", "question": "Can an agent call Geoapify Location Platform + MCP and Radar without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 74 against 50", "Agent ergonomics, 72 against 65", "Payments \u0026 pricing, 30 against 10", "Transparency \u0026 trust, 62 against 55" ], "also": [ "Free to start without a card" ], "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": [ "Reliability, 70 against 60", "Security \u0026 auth, 56 against 29", "Maintenance \u0026 community, 77 against 61" ], "also": null, "goodFor": "A company that already has a Radar contract, or wants geofencing and trip tracking with geocoding and routing on one key.", "slug": "radar", "watchFor": "The pricing page says Radar has no free tier and every plan is an annual commitment set by quote" } ], "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-radar.json", "title": "Amazon Location Service vs Radar", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-radar" }, { "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-radar.json", "title": "ArcGIS Location Platform vs Radar", "url": "https://www.anchorterminal.com/compare/arcgis-vs-radar" }, { "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-radar.json", "title": "Azure Maps vs Radar", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-radar" }, { "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-here-location-services.json", "title": "Geoapify Location Platform + MCP vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/geoapify-vs-here-location-services" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-locationiq.json", "title": "Geoapify Location Platform + MCP vs LocationIQ", "url": "https://www.anchorterminal.com/compare/geoapify-vs-locationiq" }, { "json": "https://www.anchorterminal.com/compare/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-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-radar.json", "title": "Google Maps Platform + Grounding Lite MCP vs Radar", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-radar" }, { "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/locationiq-vs-radar.json", "title": "LocationIQ vs Radar", "url": "https://www.anchorterminal.com/compare/locationiq-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-radar.json", "title": "Mapbox APIs + MCP vs Radar", "url": "https://www.anchorterminal.com/compare/mapbox-vs-radar" }, { "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/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/radar-vs-stadia-maps.json", "title": "Radar vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/radar-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/radar-vs-tomtom.json", "title": "Radar vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/radar-vs-tomtom" } ], "scores": [ { "by": 10, "edge": "radar", "geoapify": 60, "key": "reliability", "name": "Reliability", "radar": 70, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 24, "edge": "geoapify", "geoapify": 74, "key": "schema", "name": "Schema \u0026 documentation", "radar": 50, "weight": 13 }, { "by": 7, "edge": "geoapify", "geoapify": 72, "key": "ergonomics", "name": "Agent ergonomics", "radar": 65, "weight": 13 }, { "by": 27, "edge": "radar", "geoapify": 29, "key": "security", "name": "Security \u0026 auth", "radar": 56, "weight": 14 }, { "by": 20, "edge": "geoapify", "geoapify": 30, "key": "payments", "name": "Payments \u0026 pricing", "radar": 10, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 16, "edge": "radar", "geoapify": 61, "key": "maintenance", "name": "Maintenance \u0026 community", "radar": 77, "weight": 7 }, { "by": 7, "edge": "geoapify", "geoapify": 62, "key": "transparency", "name": "Transparency \u0026 trust", "radar": 55, "weight": 7 } ], "summary": "Geoapify Location Platform + MCP scores 55.3 (C) on agent readiness against Radar's 53.3 (D), and leads in 4 of 7 scored categories. Radar leads on reliability, security \u0026 auth and maintenance \u0026 community. 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.", "radar": "Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/geoapify-vs-radar", "json": "https://www.anchorterminal.com/compare/geoapify-vs-radar.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/geoapify-vs-radar.md", "slim": "https://www.anchorterminal.com/compare/geoapify-vs-radar.min.md" }, "markdown": "Geoapify Location Platform + MCP scores 55.3 (C) on agent readiness against Radar's 53.3 (D), and leads in 4 of 7 scored categories. Radar leads on reliability, security \u0026 auth and maintenance \u0026 community. 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- Radar: grade D, 53.3/100, rank #713 of 950. Markdown https://www.anchorterminal.com/tools/radar.md · JSON https://www.anchorterminal.com/api/v1/tools/radar.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- Schema \u0026 documentation, 74 against 50\n- Agent ergonomics, 72 against 65\n- Payments \u0026 pricing, 30 against 10\n- Transparency \u0026 trust, 62 against 55\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No security.txt, disclosure policy, bug bounty or certification found\n\n### Radar (D)\n\nGood for: A company that already has a Radar contract, or wants geofencing and trip tracking with geocoding and routing on one key.\n\nAhead on:\n- Reliability, 70 against 60\n- Security \u0026 auth, 56 against 29\n- Maintenance \u0026 community, 77 against 61\n\nWatch for: The pricing page says Radar has no free tier and every plan is an annual commitment set by quote\n\n\n## Score by category\n\n| Category | Weight | Geoapify Location Platform + MCP | Radar | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 60 | 70 | Radar +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 74 | 50 | Geoapify Location Platform + MCP +24 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 65 | Geoapify Location Platform + MCP +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 29 | 56 | Radar +27 |\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 | 77 | Radar +16 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 62 | 55 | Geoapify Location Platform + MCP +7 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **55.3 · C** | **53.3 · D** | |\n\n## Facts side by side\n\n| Fact | Geoapify Location Platform + MCP | Radar |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Geoapify | Radar Labs |\n| Hosted endpoint | `https://api.geoapify.com/v1` | `https://api.radar.io/v1` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | none | Proprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0 |\n| Tools exposed | 11 | none |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | none | 2026-09-14 |\n| Terms last updated | no date given | 2023-05-24 |\n| Privacy policy last updated | no date given | 2025-05-13 |\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 | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\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**Radar.** Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found.\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### Radar\n\n1. Send the key in the `Authorization` header with no `Bearer` prefix, and call `https://api.radar.io/v1`, not radar.com\n2. Use a publishable key for geocoding, search and routing. Keep the secret key for users, trips, geofences and beacons\n3. Call `/v1/search/autocomplete` for partial addresses and place names. `/v1/geocode/forward` is documented as best for complete addresses\n4. Set `units=metric` on routing calls. The default is imperial, with distances in feet\n5. Treat 429 as one of three things (rate limit, no state change or selective throttling) and 402 as usage exceeded. No Retry-After header is documented\n6. Do not keep geocoding, autocomplete or place results for more than 30 days\n\n## Questions\n\n### Which is better for AI agents, Geoapify Location Platform + MCP or Radar?\n\nGeoapify Location Platform + MCP scores 55.3 (C) on agent readiness against Radar's 53.3 (D), and leads in 4 of 7 scored categories. Radar leads on reliability, security \u0026 auth and maintenance \u0026 community.\n\n### Do Geoapify Location Platform + MCP and Radar need an API key?\n\nBoth need an API key.\n\n### Can an agent call Geoapify Location Platform + MCP and Radar without installing anything?\n\nYes. Geoapify Location Platform + MCP has a hosted endpoint at https://api.geoapify.com/v1 and Radar at https://api.radar.io/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/geoapify-vs-radar.json, and with the fewest tokens: https://www.anchorterminal.com/compare/geoapify-vs-radar.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"geoapify\", \"b\": \"radar\"}`. From a terminal: `anchor compare geoapify radar`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/geoapify.json and https://www.anchorterminal.com/api/v1/tools/radar.json\n\n## Other comparisons with Geoapify Location Platform + MCP or Radar\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 Radar](https://www.anchorterminal.com/compare/amazon-location-vs-radar.md)\n- [ArcGIS Location Platform vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/arcgis-vs-geoapify.md)\n- [ArcGIS Location Platform vs Radar](https://www.anchorterminal.com/compare/arcgis-vs-radar.md)\n- [Azure Maps vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-geoapify.md)\n- [Azure Maps vs Radar](https://www.anchorterminal.com/compare/azure-maps-vs-radar.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 HERE Location Services](https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.md)\n- [Geoapify Location Platform + MCP vs LocationIQ](https://www.anchorterminal.com/compare/geoapify-vs-locationiq.md)\n- [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 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 Radar](https://www.anchorterminal.com/compare/google-maps-platform-vs-radar.md)\n- [HERE Location Services vs Radar](https://www.anchorterminal.com/compare/here-location-services-vs-radar.md)\n- [LocationIQ vs Radar](https://www.anchorterminal.com/compare/locationiq-vs-radar.md)\n- [Mapbox APIs + MCP vs Radar](https://www.anchorterminal.com/compare/mapbox-vs-radar.md)\n- [MapQuest vs Radar](https://www.anchorterminal.com/compare/mapquest-vs-radar.md)\n- [OpenCage Geocoding API vs Radar](https://www.anchorterminal.com/compare/opencage-vs-radar.md)\n- [Radar vs Stadia Maps](https://www.anchorterminal.com/compare/radar-vs-stadia-maps.md)\n- [Radar vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/radar-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 Radar", "url": "" } ], "description": "Geoapify Location Platform scores 55.3 (C) to Radar's 53.3 (D) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Geoapify Location Platform + MCP C 55.3", "Radar D 53.3", "scores" ], "h1": "Geoapify Location Platform + MCP vs Radar", "image": "https://www.anchorterminal.com/assets/og/compare-geoapify-vs-radar.png", "path": "/compare/geoapify-vs-radar", "published": "2026-10-01", "section": "tools", "title": "Geoapify Location Platform vs Radar for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/geoapify-vs-radar" }, "tokens": { "markdown": 2450, "slim": 680 }, "version": 1 }