{ "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", "dns": "geoapify.grade.anchorterminal.com", "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": 12, "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" ], "lastRelease": "2026-11-02", "graded": true, "anchor": { "graded": true, "score": 58.1, "grade": "C", "agentReady": false, "rank": 765, "ranked": true, "rankOf": 1510, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 69, "payments": 30, "reliability": 60, "schema": 84, "security": 29, "transparency": 67 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "Free plan allows commercial production use, 3,000 credits a day, no card, and a dated public changelog records API and MCP changes, most recently on 2 November 2026. No security.txt, disclosure policy, bug bounty or certification was found, and the specs recommend sending the key in the URL.", "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", "A dated What's new changelog with an RSS feed, five API or MCP entries since 6 August 2026", "Data for successful requests held no longer than 24 hours, per the privacy policy", "MCP tool descriptions say when to use each tool and which tool to use instead" ], "weaknesses": [ "No security.txt, disclosure policy, bug bounty or certification found", "No deprecation policy, and the terms allow changes or suspension without notice", "Storage rights appear in the docs but not in the terms", "The specs recommend the apiKey query parameter for public APIs", "The status page loads its history from a path closed to automated readers, so its record couldn't be read" ], "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.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58.1 } ], "editorialScores": { "ergonomics": 72, "maintenance": 69, "payments": 30, "reliability": 60, "schema": 84, "security": 29, "transparency": 52 }, "provenanceScore": 82, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "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": "https://www.geoapify.com/news-and-updates/", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The terms name KEPTAGO LTD, registered in Paphos, Cyprus, trading as Geoapify. Version 5, dated 2 February 2024, unchanged on 4 November 2026.", "www.geoapify.com/.well-known/security.txt returns 404 (4 November 2026).", "status.geoapify.com redirects to an UptimeRobot status page, which loads its data from a path that host's robots.txt closes.", "The What's new page at https://www.geoapify.com/news-and-updates/ is a dated changelog with an RSS feed. The OpenAPI specs repository on GitHub also has dated commits.", "The privacy policy was last modified 1 April 2026, per the 1 October check." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/geoapify.json", "live": { "slug": "geoapify", "probe": { "target": "https://api.geoapify.com/v1", "method": "get", "lastAt": "2026-11-07T19:22:08.582672979Z", "lastOk": true, "lastStatus": 401, "lastMs": 182, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 112, "p95ms24h": 188, "samples24h": 238, "samples30d": 7920, "days": [ { "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": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.geoapify.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:49.907766666Z" }, "securityTxt": { "url": "https://geoapify.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:02.629902738Z" }, "domain": { "domain": "geoapify.com", "registered": "2018-10-26", "source": "https://rdap.verisign.com/com/v1/domain/geoapify.com", "checkedAt": "2026-11-01T14:23:45.368745157Z" }, "pages": [ { "url": "https://www.geoapify.com/news-and-updates/", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:29:00.147305599Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "22ba74feb794" }, { "url": "https://www.geoapify.com/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:29:02.311882329Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f9a9f1600f52" }, { "url": "https://www.geoapify.com/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:29:04.24065775Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "37eb22e1e50f" }, { "url": "https://www.geoapify.com/terms-and-conditions/", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:29:06.224946846Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c5c95d7b727d" } ], "mcpTools": { "url": "https://api.geoapify.com/v1/mcp", "checkedAt": "2026-11-07T01:44:48.136358465Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:44:48.136358465Z" }, "updatedAt": "2026-11-07T19:22:08.582672979Z" } }, "answer": "Nominatim scores 63.5 (B) on agent readiness against Geoapify Location Platform + MCP's 58.1 (C), and leads in 4 of 7 scored categories. Geoapify Location Platform + MCP leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "nominatim", "name": "Nominatim", "vendor": "Nominatim project (osm-search)", "vendorUrl": "https://nominatim.org", "kind": "http-api", "category": "maps", "summary": "Nominatim is open-source geocoding software that searches OpenStreetMap data by name and address and reverse geocodes coordinates. Operators self-host its HTTP API; the OpenStreetMap Foundation runs a free public instance under a strict usage policy.", "url": "https://www.anchorterminal.com/tools/nominatim", "markdownUrl": "https://www.anchorterminal.com/tools/nominatim.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nominatim.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nominatim.json", "dns": "nominatim.grade.anchorterminal.com", "repo": "https://github.com/osm-search/Nominatim", "license": "GPL-3.0-or-later", "transports": [ "http" ], "packages": [ { "registry": "pypi", "name": "nominatim-api" }, { "registry": "pypi", "name": "nominatim-db" } ], "auth": "none", "authNotes": "The server has no authentication; operators add it with their own proxy. The public instance at nominatim.openstreetmap.org takes no key but requires a valid User-Agent or Referer identifying the application.", "pricing": "free", "pricingNotes": "Free software. The public instance is free within its usage policy (at most 1 request a second, no bulk or systematic use). Commercial hosted Nominatim is sold by third parties, not by the project.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No payment protocol in the server or the docs (checked 2026-11-06). The software is free.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": 2052, "asOf": "2026-11-06" }, "docsUrl": "https://nominatim.org/release-docs/latest/api/Overview/", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places" ], "tags": [ "open-source", "self-hosted", "free", "no-auth", "no-key", "python", "open-data", "local" ], "lastRelease": "2026-10-14", "graded": true, "anchor": { "graded": true, "score": 63.5, "grade": "B", "agentReady": false, "rank": 513, "ranked": true, "rankOf": 1510, "categoryRank": 9, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 60, "payments": 60, "reliability": 82, "schema": 51, "security": 50, "transparency": 59 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Nominatim is the open-source OpenStreetMap geocoder, free to run with a documented search, reverse and lookup API, tested releases and two years of security support per release. It has no OpenAPI spec, no built-in authentication, and the public instance allows one request a second and restricts LLM-suggested use, so agents at scale need their own server.", "bestFor": "Self-hosted worldwide geocoding from OpenStreetMap data with no per-call cost or storage limits beyond ODbL.", "strengths": [ "Open source under GPL, free to self-host with no key and nothing to buy", "Search, reverse, lookup and status endpoints with limit, layer, country and viewbox filters", "Release 5.3.3 on 14 October 2026, with a ChangeLog and two years of security updates per release line", "SECURITY.md with a security address, a 3-work-day acknowledgement and a disclosure process", "CI runs unit and BDD tests on every push across PostgreSQL 13 to 18" ], "weaknesses": [ "No OpenAPI spec and no llms.txt", "The public instance allows at most one request a second, no autocomplete, no systematic queries and no reselling", "The usage policy says LLMs may suggest the public API only while pointing to the policy, and bars it from no-code and vibe-coding platforms", "No authentication in the server, so access control is the operator's job", "A full planet import needs substantial hardware and time to set up" ], "agentNotes": [ "Don't send bulk or repeated queries to nominatim.openstreetmap.org; keep to one request a second, cache results and set an identifying User-Agent", "Tell the user about the OSMF usage policy before suggesting the public instance, as the policy requires", "For regular or large jobs, run your own Nominatim or use a commercial provider listed on the Nominatim wiki", "Pass format=jsonv2 or geojson and limit, since omitting format sends the request to the web UI", "Attribute OpenStreetMap and respect the ODbL share-alike terms when storing results" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.5 } ], "editorialScores": { "ergonomics": 75, "maintenance": 60, "payments": 60, "reliability": 82, "schema": 51, "security": 50, "transparency": 81 }, "provenanceScore": 37, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install nominatim-db nominatim-api", "http": "curl -A \"my-app/1.0 (contact@example.com)\" \"https://nominatim.openstreetmap.org/search?q=Dresden\u0026format=jsonv2\u0026limit=1\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/nominatim" }, "area": "everyday", "provenance": { "legalEntity": "", "domain": "nominatim.org", "domainRegistered": "2010-05-20", "endpointOnVendorDomain": false, "terms": "https://operations.osmfoundation.org/policies/nominatim/", "privacy": "", "statusPage": "", "changelog": "https://github.com/osm-search/Nominatim/blob/master/ChangeLog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "No company stands behind the software. The nominatim.org imprint names its maintainer Sarah Hoffmann as the person who runs the site.", "The terms listed are the OSMF usage policy for the public instance, which is run by the OpenStreetMap Foundation and is also governed by the OSMF Terms of Use. The licence governs the software.", "nominatim.openstreetmap.org's robots.txt disallows /search, /reverse, /lookup, /details and /status, so no request was sent there.", "nominatim.org has no robots.txt (404) and no llms.txt. Security reports go to security@nominatim.org per SECURITY.md; no security.txt was looked for beyond that file.", "RDAP gives nominatim.org a registration date of 20 May 2010.", "A request to pypi.org/pypi/nominatim-api/json, disallowed by PyPI's robots.txt, was sent by mistake on 6 November 2026; release dates are taken from PyPI's allowed RSS release feed instead." ], "score": 37 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/nominatim.json", "live": { "slug": "nominatim", "versions": [ { "registry": "github", "name": "osm-search/Nominatim", "version": "v5.3.3", "released": "2026-10-14", "seenAt": "2026-11-06T23:49:38.546585976Z" }, { "registry": "pypi", "name": "nominatim-api", "version": "5.3.3", "released": "2026-10-14", "seenAt": "2026-11-06T23:49:36.460811725Z" }, { "registry": "pypi", "name": "nominatim-db", "version": "5.3.3", "released": "2026-10-14", "seenAt": "2026-11-06T23:49:36.677899359Z" } ], "githubStars": 4553, "pypiWeekly": 2052, "securityTxt": { "url": "https://nominatim.org/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:36.659918342Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/osm-search/Nominatim/master/ChangeLog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:22:43.498875362Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d293d5592f9f" }, { "url": "https://operations.osmfoundation.org/policies/nominatim/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:15:39.38384818Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e7342ba42b14" } ], "updatedAt": "2026-11-07T16:00:36.659918342Z" } }, "edges": [ { "by": 33, "category": "schema", "leads": "geoapify", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.1 specs for 22 APIs and a separate spec per MCP tool in geoapify/geoapify-openapi-specs, with documented 400, 401, 429 and 500 responses, and the repository added the Timezone API on 23 October 2026 (25). apidocs.geoapify.com/llms.txt still serves the HTML home page on 4 November, and we found no Markdown docs for agents (0). The MCP page's 12 tools each carry a 'when to use' line and name the sibling tool to use instead, for example calculate_route_matrix sends you to calculate_route for geometry (18). Typed parameters with limits such as limit at most 100, and enums for type and format (13). Error examples in the specs, such as '\"limit\" must be less than or equal to 100', and a playground per API (13). v1 and v2 paths, versioned specs, and a dated public changelog at www.geoapify.com/news-and-updates/ with entries back to September 2022 and an RSS feed, which the 1 October check missed (15, from 5). 25+0+18+13+13+15 = 84.", "b": "No OpenAPI or machine-readable contract (0). nominatim.org/llms.txt returns 404, and the manual is HTML, though its Markdown sources sit in the repository's docs folder (0). The API reference explains each endpoint and parameter and when not to use one, such as the details endpoint being for debugging (14). Types, enums and limits are documented, such as format, layer and limit (at most 40), but there's no schema to validate against (12). Example queries and outputs per endpoint, with errors described in prose (10). A versioned manual per release, a ChangeLog and a migration guide (15). 0+0+14+12+10+15 = 51." }, "scores": { "a": 84, "b": 51 } }, { "by": 30, "category": "payments", "leads": "nominatim", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Public plan prices with credit costs per request (1 credit for a simple geocode, place search, route or timezone lookup), but no per-unit overage price, since limits are soft and Geoapify asks heavy users to upgrade (10). Free plan of 3,000 credits a day with 'No credit card required', and commercial use allowed with attribution (20). Signup is a browser flow (0). 0+10+20+0 = 30.", "b": "Self-hosted rule. No payment protocol (0). Free software with nothing to buy (20 + 20 + 20). The public instance is also free and keyless, within its usage policy. 0+20+20+20 = 60." }, "scores": { "a": 30, "b": 60 } }, { "by": 22, "category": "reliability", "leads": "nominatim", "name": "Reliability", "reasons": { "a": "status.geoapify.com redirects to an UptimeRobot page. On 4 November its HTML again showed only an error fetching the data, which the page loads from stats.uptimerobot.com/api/, a path that host's robots.txt closes, so no component or incident was read. The page keeps its first award of 15 of 20 while the UptimeRobot split stays open, and 5 for a history we couldn't read (our limit, not a finding against Geoapify). Per-plan rates are published, 5 requests a second on Free up to 30 on API 250 (15). 429 is in the OpenAPI specs as 'Rate limit or quota exceeded' with a JSON body, but there's no Retry-After or backoff guidance, and the pricing page says limits are soft and Geoapify doesn't throttle in general (7, an earlier partial kept). The terms say all paid plans include a default SLA of 99.5 per cent monthly availability, with a 10 per cent discount below it and 50 per cent below 99 per cent (10). The APIs are GA. The MCP page gives no launch stage (8, an earlier partial kept). 15+5+15+7+10+8 = 60.", "b": "Read with the local-software lines, since the listing is the Nominatim server an operator runs. The public instance at nominatim.openstreetmap.org belongs to the OpenStreetMap Foundation and its usage policy caps it at one request a second, so it isn't graded as a hosted service. Official packages nominatim-db and nominatim-api on PyPI (5.3.3 on 14 October 2026, Python 3.9 or later) and installation guides for Ubuntu 22 and 24 (20). A public CI workflow runs unit and BDD tests on every push across Ubuntu 24 and 26 with PostgreSQL 13 to 18, and Windows unit tests. We couldn't see run results (20). Issue counts and reply times couldn't be read because the GitHub API was rate-limited for us; Sarah Hoffmann made 76 of the 106 commits since 8 August (12). A ChangeLog per release and semantic version numbers (15). Version 5.3.3 (15). 20+20+12+15+15 = 82." }, "scores": { "a": 60, "b": 82 } }, { "by": 21, "category": "security", "leads": "nominatim", "name": "Security \u0026 auth", "reasons": { "a": "Plain API keys per project, which earns 20. Less the checklist's fixed 10 because the specs call the apiKey query parameter 'Recommended authentication method for public APIs'. The x-api-key header works too and the spec warns that keys in URLs can be logged (10). The APIs only read (12). Results are OpenStreetMap names and addresses, community-edited text, with no prompt-injection guidance (7). We didn't find per-call logs we could read (0). www.geoapify.com/.well-known/security.txt returned 404 on 4 November, and we found no disclosure policy, bug bounty or certification (0). 10+12+7+0+0 = 29.", "b": "The server has no authentication of its own; an operator puts it behind their own proxy. The public instance takes no key and identifies callers by User-Agent or Referer (5). Every endpoint reads, so there's nothing to approve (18). Results are OpenStreetMap names and tags, community-edited text, with no prompt-injection guidance (7). Query logging to a file is available through NOMINATIM_LOG_FILE and off by default (8). SECURITY.md gives security@nominatim.org, an acknowledgement within 3 work days, a disclosure process and two years of security updates per release. No bug bounty (12). 5+18+7+8+12 = 50." }, "scores": { "a": 29, "b": 50 } }, { "by": 9, "category": "maintenance", "leads": "geoapify", "name": "Maintenance \u0026 community", "reasons": { "a": "The What's new page dates two API entries on 2 November 2026 (Marker Icon API and Static Maps API marker options), two days before this check (30). In the 90 days from 6 August it lists API or MCP changes on 6 August (MCP Places and Routing tools), 28 August (MCP geometry operations), 23 October (Timezone API and get_timezone tool) and 2 November (two), and the OpenAPI repository has commits on 1, 2 and 25 September and 16, 23 and 30 October (20, from 15). A public changelog with an RSS feed and email support on paid plans. We didn't test support response (8 of 15, from 5). The JavaScript libraries are current, with geocoder-autocomplete at v3.1.0 on 27 July 2026, and the official MCP isn't in the MCP registry (6). The autocomplete SDK carries Jest tests (5). 30+20+8+6+5 = 69.", "b": "Release 5.3.3 on 14 October 2026, 23 days before this check (30). Only one release in the 90 days from 8 August, against 106 commits on the default branch; commits aren't counted as releases (0). Commits from the lead maintainer and seven or more contributors since August, but we couldn't read issue reply times (12). The nominatim-api Python library is current with the server (10). CI on every push, current PostgreSQL and Python versions (8). 30+0+12+10+8 = 60." }, "scores": { "a": 69, "b": 60 } }, { "by": 8, "category": "transparency", "leads": "geoapify", "name": "Transparency \u0026 trust", "reasons": { "a": "Editorial half only. Closed service with readable terms, still version 5 of 2 February 2024 on 4 November, under Cypriot law (15). The privacy policy says data for successful requests is held no longer than 24 hours and that servers are hosted by Hetzner, with custom DPAs on request (possibly at a cost). The docs say Places and Batch results can be cached or stored with no limits, while the terms say nothing on storage (22). No deprecation policy or dated deprecation notice on the What's new page, and the terms reserve the right to suspend, terminate or change the Service at any time without notice (0). Six processors named, including Hetzner (Germany), Cloudflare and Google Firebase, without locations for most (15). 15+22+0+15 = 52.", "b": "Open source, GPL-3.0-or-later for the Python code, GPL-2.0 for other files and Apache-2.0 for the osm2pgsql Lua styles (30). A self-hosted server keeps data where the operator runs it. The public instance falls under the OSMF privacy policy and asks users not to send personal data. We didn't read the OSMF policy itself (20). SECURITY.md lists the end of security support for each release line with dates, and a migration guide covers each version (16). No telemetry found in the settings, and request logging is opt-in (15). 30+20+16+15 = 81." }, "scores": { "a": 67, "b": 59 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Geoapify", "b": "Nominatim project (osm-search)", "name": "Vendor" }, { "a": "https://api.geoapify.com/v1", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "None", "name": "Auth" }, { "a": "Freemium", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "GPL-3.0-or-later", "name": "Licence" }, { "a": "12", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2026-11-02", "b": "2026-10-14", "name": "Last release" }, { "a": "no date given", "b": "no date given", "name": "Terms last updated" }, { "a": "no date given", "b": "no document linked", "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": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "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": "none", "b": "2.1k PyPI/wk", "name": "Popularity" }, { "a": "4/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Nominatim scores 63.5 (B) on agent readiness against Geoapify Location Platform + MCP's 58.1 (C), and leads in 4 of 7 scored categories. Geoapify Location Platform + MCP leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Geoapify Location Platform + MCP or Nominatim?" }, { "answer": "Geoapify Location Platform + MCP needs an API key. Nominatim needs no key.", "question": "Do Geoapify Location Platform + MCP and Nominatim need an API key?" }, { "answer": "Geoapify Location Platform + MCP has a hosted endpoint at https://api.geoapify.com/v1. No hosted endpoint is listed for Nominatim.", "question": "Can an agent call Geoapify Location Platform + MCP and Nominatim without installing anything?" }, { "answer": "No open-source release is listed for Geoapify Location Platform + MCP. Nominatim is open source (GPL-3.0-or-later).", "question": "Are Geoapify Location Platform + MCP and Nominatim open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 84 against 51", "Maintenance \u0026 community, 69 against 60", "Transparency \u0026 trust, 67 against 59" ], "also": [ "A hosted endpoint, with nothing to install", "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, 82 against 60", "Security \u0026 auth, 50 against 29", "Payments \u0026 pricing, 60 against 30" ], "also": [ "No key needed to call it", "Open source" ], "goodFor": "Self-hosted worldwide geocoding from OpenStreetMap data with no per-call cost or storage limits beyond ODbL.", "slug": "nominatim", "watchFor": "No OpenAPI spec and no llms.txt" } ], "history": { "geoapify": [ { "causes": [ "evidence" ], "date": "2026-11-04", "delta": 2.8, "from": 55.3, "fromGrade": "C", "to": 58.1, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.2, "from": 55.5, "fromGrade": "C", "to": 55.3, "toGrade": "C" } ], "nominatim": null }, "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-nominatim.json", "title": "Amazon Location Service vs Nominatim", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-nominatim" }, { "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-nominatim.json", "title": "ArcGIS Location Platform vs Nominatim", "url": "https://www.anchorterminal.com/compare/arcgis-vs-nominatim" }, { "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-nominatim.json", "title": "Azure Maps vs Nominatim", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-geocodio.json", "title": "Geoapify Location Platform + MCP vs Geocodio", "url": "https://www.anchorterminal.com/compare/geoapify-vs-geocodio" }, { "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-maptiler.json", "title": "Geoapify Location Platform + MCP vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/geoapify-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-nextbillion.json", "title": "Geoapify Location Platform + MCP vs NextBillion.ai", "url": "https://www.anchorterminal.com/compare/geoapify-vs-nextbillion" }, { "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/geoapify-vs-woosmap.json", "title": "Geoapify Location Platform + MCP vs Woosmap", "url": "https://www.anchorterminal.com/compare/geoapify-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-nominatim.json", "title": "Geocodio vs Nominatim", "url": "https://www.anchorterminal.com/compare/geocodio-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-nominatim.json", "title": "Google Maps Platform + Grounding Lite MCP vs Nominatim", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-nominatim.json", "title": "HERE Location Services vs Nominatim", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-nominatim.json", "title": "LocationIQ vs Nominatim", "url": "https://www.anchorterminal.com/compare/locationiq-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-nominatim.json", "title": "Mapbox APIs + MCP vs Nominatim", "url": "https://www.anchorterminal.com/compare/mapbox-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-nominatim.json", "title": "MapQuest vs Nominatim", "url": "https://www.anchorterminal.com/compare/mapquest-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-nominatim.json", "title": "MapTiler Cloud vs Nominatim", "url": "https://www.anchorterminal.com/compare/maptiler-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/nextbillion-vs-nominatim.json", "title": "NextBillion.ai vs Nominatim", "url": "https://www.anchorterminal.com/compare/nextbillion-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/nominatim-vs-opencage.json", "title": "Nominatim vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/nominatim-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/nominatim-vs-radar.json", "title": "Nominatim vs Radar", "url": "https://www.anchorterminal.com/compare/nominatim-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/nominatim-vs-stadia-maps.json", "title": "Nominatim vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/nominatim-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/nominatim-vs-tomtom.json", "title": "Nominatim vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/nominatim-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/nominatim-vs-woosmap.json", "title": "Nominatim vs Woosmap", "url": "https://www.anchorterminal.com/compare/nominatim-vs-woosmap" } ], "panel": null, "scores": [ { "by": 22, "edge": "nominatim", "geoapify": 60, "key": "reliability", "name": "Reliability", "nominatim": 82, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 33, "edge": "geoapify", "geoapify": 84, "key": "schema", "name": "Schema \u0026 documentation", "nominatim": 51, "weight": 13 }, { "by": 3, "edge": "nominatim", "geoapify": 72, "key": "ergonomics", "name": "Agent ergonomics", "nominatim": 75, "weight": 13 }, { "by": 21, "edge": "nominatim", "geoapify": 29, "key": "security", "name": "Security \u0026 auth", "nominatim": 50, "weight": 14 }, { "by": 30, "edge": "nominatim", "geoapify": 30, "key": "payments", "name": "Payments \u0026 pricing", "nominatim": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 9, "edge": "geoapify", "geoapify": 69, "key": "maintenance", "name": "Maintenance \u0026 community", "nominatim": 60, "weight": 7 }, { "by": 8, "edge": "geoapify", "geoapify": 67, "key": "transparency", "name": "Transparency \u0026 trust", "nominatim": 59, "weight": 7 } ], "summary": "Nominatim scores 63.5 (B) on agent readiness against Geoapify Location Platform + MCP's 58.1 (C), and leads in 4 of 7 scored categories. Geoapify Location Platform + MCP leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust. Both do geocoding.", "tasks": null, "tutorials": [], "verdicts": { "geoapify": "Free plan allows commercial production use, 3,000 credits a day, no card, and a dated public changelog records API and MCP changes, most recently on 2 November 2026. No security.txt, disclosure policy, bug bounty or certification was found, and the specs recommend sending the key in the URL.", "nominatim": "Nominatim is the open-source OpenStreetMap geocoder, free to run with a documented search, reverse and lookup API, tested releases and two years of security support per release. It has no OpenAPI spec, no built-in authentication, and the public instance allows one request a second and restricts LLM-suggested use, so agents at scale need their own server." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/geoapify-vs-nominatim", "json": "https://www.anchorterminal.com/compare/geoapify-vs-nominatim.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/geoapify-vs-nominatim.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/geoapify-vs-nominatim.min.md" }, "markdown": "Nominatim scores 63.5 (B) on agent readiness against Geoapify Location Platform + MCP's 58.1 (C), and leads in 4 of 7 scored categories. Geoapify Location Platform + MCP leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust. Both do geocoding.\n\n- Geoapify Location Platform + MCP: grade C, 58.1/100, rank #765 of 1510. Markdown https://www.anchorterminal.com/tools/geoapify.md · JSON https://www.anchorterminal.com/api/v1/tools/geoapify.json\n- Nominatim: grade B, 63.5/100, rank #513 of 1510. Markdown https://www.anchorterminal.com/tools/nominatim.md · JSON https://www.anchorterminal.com/api/v1/tools/nominatim.json\n- Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md\n- All 153 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, 84 against 51\n- Maintenance \u0026 community, 69 against 60\n- Transparency \u0026 trust, 67 against 59\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: No security.txt, disclosure policy, bug bounty or certification found\n\n### Nominatim (B)\n\nGood for: Self-hosted worldwide geocoding from OpenStreetMap data with no per-call cost or storage limits beyond ODbL.\n\nAhead on:\n- Reliability, 82 against 60\n- Security \u0026 auth, 50 against 29\n- Payments \u0026 pricing, 60 against 30\n\nAlso in its favour:\n- No key needed to call it\n- Open source\n\nWatch for: No OpenAPI spec and no llms.txt\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Geoapify Location Platform + MCP +33\n\n- Geoapify Location Platform + MCP (84): OpenAPI 3.1 specs for 22 APIs and a separate spec per MCP tool in geoapify/geoapify-openapi-specs, with documented 400, 401, 429 and 500 responses, and the repository added the Timezone API on 23 October 2026 (25). apidocs.geoapify.com/llms.txt still serves the HTML home page on 4 November, and we found no Markdown docs for agents (0). The MCP page's 12 tools each carry a 'when to use' line and name the sibling tool to use instead, for example calculate_route_matrix sends you to calculate_route for geometry (18). Typed parameters with limits such as limit at most 100, and enums for type and format (13). Error examples in the specs, such as '\"limit\" must be less than or equal to 100', and a playground per API (13). v1 and v2 paths, versioned specs, and a dated public changelog at www.geoapify.com/news-and-updates/ with entries back to September 2022 and an RSS feed, which the 1 October check missed (15, from 5). 25+0+18+13+13+15 = 84.\n- Nominatim (51): No OpenAPI or machine-readable contract (0). nominatim.org/llms.txt returns 404, and the manual is HTML, though its Markdown sources sit in the repository's docs folder (0). The API reference explains each endpoint and parameter and when not to use one, such as the details endpoint being for debugging (14). Types, enums and limits are documented, such as format, layer and limit (at most 40), but there's no schema to validate against (12). Example queries and outputs per endpoint, with errors described in prose (10). A versioned manual per release, a ChangeLog and a migration guide (15). 0+0+14+12+10+15 = 51.\n\n### Payments \u0026 pricing: Nominatim +30\n\n- Geoapify Location Platform + MCP (30): No x402, MPP or L402 (0). Public plan prices with credit costs per request (1 credit for a simple geocode, place search, route or timezone lookup), but no per-unit overage price, since limits are soft and Geoapify asks heavy users to upgrade (10). Free plan of 3,000 credits a day with 'No credit card required', and commercial use allowed with attribution (20). Signup is a browser flow (0). 0+10+20+0 = 30.\n- Nominatim (60): Self-hosted rule. No payment protocol (0). Free software with nothing to buy (20 + 20 + 20). The public instance is also free and keyless, within its usage policy. 0+20+20+20 = 60.\n\n### Reliability: Nominatim +22\n\n- Geoapify Location Platform + MCP (60): status.geoapify.com redirects to an UptimeRobot page. On 4 November its HTML again showed only an error fetching the data, which the page loads from stats.uptimerobot.com/api/, a path that host's robots.txt closes, so no component or incident was read. The page keeps its first award of 15 of 20 while the UptimeRobot split stays open, and 5 for a history we couldn't read (our limit, not a finding against Geoapify). Per-plan rates are published, 5 requests a second on Free up to 30 on API 250 (15). 429 is in the OpenAPI specs as 'Rate limit or quota exceeded' with a JSON body, but there's no Retry-After or backoff guidance, and the pricing page says limits are soft and Geoapify doesn't throttle in general (7, an earlier partial kept). The terms say all paid plans include a default SLA of 99.5 per cent monthly availability, with a 10 per cent discount below it and 50 per cent below 99 per cent (10). The APIs are GA. The MCP page gives no launch stage (8, an earlier partial kept). 15+5+15+7+10+8 = 60.\n- Nominatim (82): Read with the local-software lines, since the listing is the Nominatim server an operator runs. The public instance at nominatim.openstreetmap.org belongs to the OpenStreetMap Foundation and its usage policy caps it at one request a second, so it isn't graded as a hosted service. Official packages nominatim-db and nominatim-api on PyPI (5.3.3 on 14 October 2026, Python 3.9 or later) and installation guides for Ubuntu 22 and 24 (20). A public CI workflow runs unit and BDD tests on every push across Ubuntu 24 and 26 with PostgreSQL 13 to 18, and Windows unit tests. We couldn't see run results (20). Issue counts and reply times couldn't be read because the GitHub API was rate-limited for us; Sarah Hoffmann made 76 of the 106 commits since 8 August (12). A ChangeLog per release and semantic version numbers (15). Version 5.3.3 (15). 20+20+12+15+15 = 82.\n\n### Security \u0026 auth: Nominatim +21\n\n- Geoapify Location Platform + MCP (29): Plain API keys per project, which earns 20. Less the checklist's fixed 10 because the specs call the apiKey query parameter 'Recommended authentication method for public APIs'. The x-api-key header works too and the spec warns that keys in URLs can be logged (10). The APIs only read (12). Results are OpenStreetMap names and addresses, community-edited text, with no prompt-injection guidance (7). We didn't find per-call logs we could read (0). www.geoapify.com/.well-known/security.txt returned 404 on 4 November, and we found no disclosure policy, bug bounty or certification (0). 10+12+7+0+0 = 29.\n- Nominatim (50): The server has no authentication of its own; an operator puts it behind their own proxy. The public instance takes no key and identifies callers by User-Agent or Referer (5). Every endpoint reads, so there's nothing to approve (18). Results are OpenStreetMap names and tags, community-edited text, with no prompt-injection guidance (7). Query logging to a file is available through NOMINATIM_LOG_FILE and off by default (8). SECURITY.md gives security@nominatim.org, an acknowledgement within 3 work days, a disclosure process and two years of security updates per release. No bug bounty (12). 5+18+7+8+12 = 50.\n\n### Maintenance \u0026 community: Geoapify Location Platform + MCP +9\n\n- Geoapify Location Platform + MCP (69): The What's new page dates two API entries on 2 November 2026 (Marker Icon API and Static Maps API marker options), two days before this check (30). In the 90 days from 6 August it lists API or MCP changes on 6 August (MCP Places and Routing tools), 28 August (MCP geometry operations), 23 October (Timezone API and get_timezone tool) and 2 November (two), and the OpenAPI repository has commits on 1, 2 and 25 September and 16, 23 and 30 October (20, from 15). A public changelog with an RSS feed and email support on paid plans. We didn't test support response (8 of 15, from 5). The JavaScript libraries are current, with geocoder-autocomplete at v3.1.0 on 27 July 2026, and the official MCP isn't in the MCP registry (6). The autocomplete SDK carries Jest tests (5). 30+20+8+6+5 = 69.\n- Nominatim (60): Release 5.3.3 on 14 October 2026, 23 days before this check (30). Only one release in the 90 days from 8 August, against 106 commits on the default branch; commits aren't counted as releases (0). Commits from the lead maintainer and seven or more contributors since August, but we couldn't read issue reply times (12). The nominatim-api Python library is current with the server (10). CI on every push, current PostgreSQL and Python versions (8). 30+0+12+10+8 = 60.\n\n### Transparency \u0026 trust: Geoapify Location Platform + MCP +8\n\n- Geoapify Location Platform + MCP (67): Editorial half only. Closed service with readable terms, still version 5 of 2 February 2024 on 4 November, under Cypriot law (15). The privacy policy says data for successful requests is held no longer than 24 hours and that servers are hosted by Hetzner, with custom DPAs on request (possibly at a cost). The docs say Places and Batch results can be cached or stored with no limits, while the terms say nothing on storage (22). No deprecation policy or dated deprecation notice on the What's new page, and the terms reserve the right to suspend, terminate or change the Service at any time without notice (0). Six processors named, including Hetzner (Germany), Cloudflare and Google Firebase, without locations for most (15). 15+22+0+15 = 52.\n- Nominatim (59): Open source, GPL-3.0-or-later for the Python code, GPL-2.0 for other files and Apache-2.0 for the osm2pgsql Lua styles (30). A self-hosted server keeps data where the operator runs it. The public instance falls under the OSMF privacy policy and asks users not to send personal data. We didn't read the OSMF policy itself (20). SECURITY.md lists the end of security support for each release line with dates, and a migration guide covers each version (16). No telemetry found in the settings, and request logging is opt-in (15). 30+20+16+15 = 81.\n\n## Score by category\n\n| Category | Weight | Geoapify Location Platform + MCP | Nominatim | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 60 | 82 | Nominatim +22 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 84 | 51 | Geoapify Location Platform + MCP +33 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 75 | Nominatim +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 29 | 50 | Nominatim +21 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 60 | Nominatim +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 69 | 60 | Geoapify Location Platform + MCP +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 67 | 59 | Geoapify Location Platform + MCP +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **58.1 · C** | **63.5 · B** | |\n\n## Facts side by side\n\n| Fact | Geoapify Location Platform + MCP | Nominatim |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Geoapify | Nominatim project (osm-search) |\n| Hosted endpoint | `https://api.geoapify.com/v1` | no (local only) |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | API key | None |\n| Pricing | Freemium | Free |\n| x402 | no | no |\n| Licence | none | GPL-3.0-or-later |\n| Tools exposed | 12 | none |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Last release | 2026-11-02 | 2026-10-14 |\n| Terms last updated | no date given | no date given |\n| Privacy policy last updated | no date given | no document linked |\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 | yes |\n| Terms restrict benchmarking | not found in the text | not found in the text |\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| Popularity | none | 2.1k PyPI/wk |\n| Agent reviews | 4/5 (2) | none |\n\n## How the scores have moved\n\n### Geoapify Location Platform + MCP\n\n- +2.8 on 4 November 2026: new evidence\n- -0.2 on 8 October 2026: checklist\n\n### Nominatim\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Geoapify Location Platform + MCP.** Free plan allows commercial production use, 3,000 credits a day, no card, and a dated public changelog records API and MCP changes, most recently on 2 November 2026. No security.txt, disclosure policy, bug bounty or certification was found, and the specs recommend sending the key in the URL.\n\n**Nominatim.** Nominatim is the open-source OpenStreetMap geocoder, free to run with a documented search, reverse and lookup API, tested releases and two years of security support per release. It has no OpenAPI spec, no built-in authentication, and the public instance allows one request a second and restricts LLM-suggested use, so agents at scale need their own server.\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### Nominatim\n\n1. Don't send bulk or repeated queries to nominatim.openstreetmap.org; keep to one request a second, cache results and set an identifying User-Agent\n2. Tell the user about the OSMF usage policy before suggesting the public instance, as the policy requires\n3. For regular or large jobs, run your own Nominatim or use a commercial provider listed on the Nominatim wiki\n4. Pass format=jsonv2 or geojson and limit, since omitting format sends the request to the web UI\n5. Attribute OpenStreetMap and respect the ODbL share-alike terms when storing results\n\n## Questions\n\n### Which is better for AI agents, Geoapify Location Platform + MCP or Nominatim?\n\nNominatim scores 63.5 (B) on agent readiness against Geoapify Location Platform + MCP's 58.1 (C), and leads in 4 of 7 scored categories. Geoapify Location Platform + MCP leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Geoapify Location Platform + MCP and Nominatim need an API key?\n\nGeoapify Location Platform + MCP needs an API key. Nominatim needs no key.\n\n### Can an agent call Geoapify Location Platform + MCP and Nominatim without installing anything?\n\nGeoapify Location Platform + MCP has a hosted endpoint at https://api.geoapify.com/v1. No hosted endpoint is listed for Nominatim.\n\n### Are Geoapify Location Platform + MCP and Nominatim open source?\n\nNo open-source release is listed for Geoapify Location Platform + MCP. Nominatim is open source (GPL-3.0-or-later).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/geoapify-vs-nominatim.json, and with the fewest tokens: https://www.anchorterminal.com/compare/geoapify-vs-nominatim.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"geoapify\", \"b\": \"nominatim\"}`. From a terminal: `anchor compare geoapify nominatim`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/geoapify.json and https://www.anchorterminal.com/api/v1/tools/nominatim.json\n\n## Other comparisons with Geoapify Location Platform + MCP or Nominatim\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 Nominatim](https://www.anchorterminal.com/compare/amazon-location-vs-nominatim.md)\n- [ArcGIS Location Platform vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/arcgis-vs-geoapify.md)\n- [ArcGIS Location Platform vs Nominatim](https://www.anchorterminal.com/compare/arcgis-vs-nominatim.md)\n- [Azure Maps vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-geoapify.md)\n- [Azure Maps vs Nominatim](https://www.anchorterminal.com/compare/azure-maps-vs-nominatim.md)\n- [Geoapify Location Platform + MCP vs Geocodio](https://www.anchorterminal.com/compare/geoapify-vs-geocodio.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 MapTiler Cloud](https://www.anchorterminal.com/compare/geoapify-vs-maptiler.md)\n- [Geoapify Location Platform + MCP vs NextBillion.ai](https://www.anchorterminal.com/compare/geoapify-vs-nextbillion.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- [Geoapify Location Platform + MCP vs Woosmap](https://www.anchorterminal.com/compare/geoapify-vs-woosmap.md)\n- [Geocodio vs Nominatim](https://www.anchorterminal.com/compare/geocodio-vs-nominatim.md)\n- [Google Maps Platform + Grounding Lite MCP vs Nominatim](https://www.anchorterminal.com/compare/google-maps-platform-vs-nominatim.md)\n- [HERE Location Services vs Nominatim](https://www.anchorterminal.com/compare/here-location-services-vs-nominatim.md)\n- [LocationIQ vs Nominatim](https://www.anchorterminal.com/compare/locationiq-vs-nominatim.md)\n- [Mapbox APIs + MCP vs Nominatim](https://www.anchorterminal.com/compare/mapbox-vs-nominatim.md)\n- [MapQuest vs Nominatim](https://www.anchorterminal.com/compare/mapquest-vs-nominatim.md)\n- [MapTiler Cloud vs Nominatim](https://www.anchorterminal.com/compare/maptiler-vs-nominatim.md)\n- [NextBillion.ai vs Nominatim](https://www.anchorterminal.com/compare/nextbillion-vs-nominatim.md)\n- [Nominatim vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/nominatim-vs-opencage.md)\n- [Nominatim vs Radar](https://www.anchorterminal.com/compare/nominatim-vs-radar.md)\n- [Nominatim vs Stadia Maps](https://www.anchorterminal.com/compare/nominatim-vs-stadia-maps.md)\n- [Nominatim vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/nominatim-vs-tomtom.md)\n- [Nominatim vs Woosmap](https://www.anchorterminal.com/compare/nominatim-vs-woosmap.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Geoapify Location Platform + MCP vs Nominatim", "url": "" } ], "description": "Nominatim scores 63.5 (B) to Geoapify Location Platform's 58.1 (C) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Geoapify Location Platform + MCP C 58.1", "Nominatim B 63.5", "scores" ], "h1": "Geoapify Location Platform + MCP vs Nominatim", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/geoapify-vs-nominatim", "published": "2026-10-01", "section": "tools", "title": "Geoapify Location Platform vs Nominatim for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/geoapify-vs-nominatim" }, "tokens": { "markdown": 5000, "slim": 2780 }, "version": 1 }