{ "data": { "a": { "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" } }, "answer": "Nominatim scores 63.5 (B) on agent readiness against TomTom Maps APIs + MCP's 45.9 (E), and leads in 3 of 7 scored categories. TomTom Maps APIs + MCP leads on schema \u0026 documentation and maintenance \u0026 community.", "b": { "slug": "tomtom", "name": "TomTom Maps APIs + MCP", "vendor": "TomTom", "vendorUrl": "https://developer.tomtom.com", "kind": "http-api", "category": "maps", "summary": "Search, Geocoding and Reverse Geocoding, Routing, Matrix Routing, Reachable Range, EV routing and live traffic, plus map tiles.", "url": "https://www.anchorterminal.com/tools/tomtom", "markdownUrl": "https://www.anchorterminal.com/tools/tomtom.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tomtom.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tomtom.json", "dns": "tomtom.grade.anchorterminal.com", "repo": "https://github.com/tomtom-international/tomtom-mcp", "license": "Apache-2.0 (MCP server)", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.tomtom.com", "packages": [ { "registry": "npm", "name": "@tomtom-org/tomtom-mcp" } ], "auth": "api-key", "authNotes": "One API key, passed as the key query parameter on REST calls. The hosted MCP takes it in a tomtom-api-key header, and OAuth deployments must set OAUTH_AUDIENCE since 1.6.13. Since 1.6.11 every tool runs on the Orbis backend; the MAPS variable and the tomtom-maps-backend header are no longer read.", "pricing": "freemium", "pricingNotes": "Free monthly allowance with no card. 2,500 Search, 20,000 Geocoding, 20,000 Routing, 2,500 Matrix Routing, 200,000 vector and 200,000 raster tiles and 20,000 non-tile map requests. Past that it's pay as you grow in euros at volume tiers, worked out by an estimator on the pricing page. The per-request rates sit behind per-API detail links we couldn't read, so no rate is quoted here (https://docs.tomtom.com/pricing).", "priceSummary": "Freemium", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": 13, "popularity": { "githubStars": 55, "npmWeekly": 996, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.tomtom.com", "llmsTxt": "https://docs.tomtom.com/llms.txt", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "official", "typescript", "free-tier", "no-card", "enterprise", "eu", "closed-source" ], "lastRelease": "2026-11-02", "graded": true, "anchor": { "graded": true, "score": 45.9, "grade": "E", "agentReady": false, "rank": 1185, "ranked": true, "rankOf": 1510, "categoryRank": 17, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 86, "payments": 25, "reliability": 15, "schema": 71, "security": 51, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-04" }, "negative": -6, "negativeNotes": [ "2026-10-05 to 2026-10-22. `@tomtom-org/tomtom-mcp` 1.6.11, 1.6.12 and 1.6.13, patch releases, carry changes marked BREAKING in the changelog with no earlier dated notice found. They removed the Genesis backend, the MAPS variable and the tomtom-maps-backend header, tomtom-static-map, tomtom-waypoint-routing, tomtom-reachable-range and tomtom-ev-routing, replaced offset paging with cursors and changed 75 POI category codes. A breaking change in a minor or patch release without notice (-3). https://github.com/tomtom-international/tomtom-mcp/blob/main/CHANGELOG.md", "2026-10-05 and 2026-10-22. 1.6.11 fixes tomtom-reachable-range returning the caller's TomTom API key in full responses, and 1.6.13 stops OAuth deployments accepting tokens issued for other TomTom applications. No advisory was found for either. Released fixes of the package's own described flaws with no advisory, folded (-3). https://github.com/tomtom-international/tomtom-mcp/blob/main/CHANGELOG.md" ], "verdict": "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with an official MCP server released about weekly. Terms, rate limits and the deprecation policy couldn't be read, the status page bars our reader, and MCP patch releases in October removed tools and inputs without notice.", "bestFor": "Drive planning with live traffic, EV charging and reachable range.", "strengths": [ "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month", "Live traffic, EV charging search and search along a route as MCP tools", "MCP tools annotated read-only, idempotent and non-destructive, with typed errors that tell a missing key from a refused account", "Eight MCP releases between 15 September and 2 November 2026, with Veracode scanning and end-to-end tests in CI", "HackerOne disclosure programme with a 3 business day first response" ], "weaknesses": [ "Terms, rate limits and deprecation policy couldn't be read, so storage rules and notice periods are unverified", "The ServiceNow status page disallows every path in robots.txt, so no incident history could be read", "MCP patch releases 1.6.11 to 1.6.13 removed tools, inputs and the older backend, marked breaking with no earlier notice", "Paid prices only through a euro estimator", "Only 2,500 free Search and Matrix calls a month" ], "agentNotes": [ "Use tomtom-geocode (20,000 free) rather than tomtom-fuzzy-search (2,500 free) when you have a full address", "Pin `@tomtom-org/tomtom-mcp` to a version, since patch releases have removed tools and changed inputs", "Page search results with `cursor` and the previous response's `nextCursor`, not `ofs`, from 1.6.12", "Read a 403 as the account or key not covering the API, and don't retry it; a 401 means a missing or unknown key", "Redact the key parameter before logging REST URLs" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 45.9 } ], "editorialScores": { "ergonomics": 78, "maintenance": 86, "payments": 25, "reliability": 15, "schema": 71, "security": 51, "transparency": 41 }, "provenanceScore": 75, "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.tomtom.com/search/2/geocode/10%20Downing%20Street%2C%20London.json?limit=1\u0026key=$TOMTOM_API_KEY\"", "claudeCode": "claude mcp add --transport http tomtom https://mcp.tomtom.com/maps --header \"tomtom-api-key: $TOMTOM_API_KEY\"", "config": { "mcpServers": { "tomtom": { "args": [ "-y", "@tomtom-org/tomtom-mcp@latest" ], "command": "npx", "env": { "TOMTOM_API_KEY": "${TOMTOM_API_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/tomtom" }, "area": "everyday", "provenance": { "legalEntity": "TomTom International BV", "domain": "tomtom.com", "domainRegistered": "1996-02-23", "endpointOnVendorDomain": true, "terms": "https://docs.tomtom.com/legal/terms-and-conditions", "privacy": "https://www.tomtom.com/privacy/", "statusPage": "https://tomtom.service-now.com/status", "changelog": "", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The privacy policy names TomTom International BV and was last edited 1 August 2024, per the 2 October check. Subprocessors and storage locations are on https://www.tomtom.com/en-gb/privacy/more-information/.", "The developer terms page still renders client-side on 4 November 2026, and developer.tomtom.com/legal redirects to it, so storage and caching rules are unverified. TomTom's Terms of Use (effective 1 September 2025) and acceptable use policy cover all TomTom websites.", "www.tomtom.com/.well-known/security.txt returned 404 per the 30 September check. Vulnerabilities go to TomTom's HackerOne programme, per the security policy in the tomtom-international GitHub organisation.", "The status page is a ServiceNow page at tomtom.service-now.com, whose robots.txt disallows every path on 4 November 2026.", "A deprecation policy page is linked from docs.tomtom.com/llms.txt but rendered client-side, and its .md twin returned 404, per the 1 October check." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tomtom.json", "live": { "slug": "tomtom", "probe": { "target": "https://api.tomtom.com", "method": "get", "lastAt": "2026-11-07T19:22:41.075542175Z", "lastOk": true, "lastStatus": 200, "lastMs": 286, "authRequired": false, "uptime24h": 100, "uptime30d": 99.96, "p50ms24h": 202, "p95ms24h": 498, "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": 251 }, { "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": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 247 }, { "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://tomtom.service-now.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:53.259050511Z" }, "versions": [ { "registry": "github", "name": "tomtom-international/tomtom-mcp", "version": "v1.6.15", "released": "2026-11-02", "seenAt": "2026-11-07T00:12:31.820004932Z" }, { "registry": "npm", "name": "@tomtom-org/tomtom-mcp", "version": "1.6.15", "seenAt": "2026-11-07T00:12:30.983981983Z" } ], "githubStars": 59, "npmWeekly": 533, "securityTxt": { "url": "https://tomtom.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:35.80240856Z" }, "llmsTxt": { "url": "https://docs.tomtom.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:10.63321814Z" }, "domain": { "domain": "tomtom.com", "registered": "1996-02-23", "source": "https://rdap.verisign.com/com/v1/domain/tomtom.com", "checkedAt": "2026-11-01T14:08:40.010831658Z" }, "pages": [ { "url": "https://docs.tomtom.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:08:24.436245345Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9f426a4be50f" }, { "url": "https://www.tomtom.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:35:50.482210619Z", "changedAt": "2026-10-08T18:31:01.446679763Z", "fingerprint": "b77d548785dc" }, { "url": "https://docs.tomtom.com/legal/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:08:22.338954308Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "68f5b7cd1e5c" } ], "mcpTools": { "url": "https://mcp.tomtom.com/maps", "checkedAt": "2026-11-07T01:48:48.000289783Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:48:48.000289783Z" }, "github": { "repo": "tomtom-international/tomtom-mcp", "checkedAt": "2026-11-02T09:32:23.866567335Z", "stars": 59, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T09:12:05Z", "openIssues": 6, "openPRs": 9, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-11-02T08:40:13Z" }, "replies": { "sampled": 10, "unanswered": 6, "medianDays": 10.4 } }, "updatedAt": "2026-11-07T19:22:41.075542175Z" } }, "edges": [ { "by": 67, "category": "reliability", "leads": "nominatim", "name": "Reliability", "reasons": { "a": "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.", "b": "TomTom's API status page sits on tomtom.service-now.com, whose robots.txt disallows every path on 4 November, so the earlier status readings are struck (0). With no history we may read, the record scores 5. No published QPS limits or 429 guidance were found on the docs pages we read on 1 October; TomTom's acceptable use policy now bars robots from its websites, so they weren't re-read (0). The MCP maps a 429 to a typed rate-limit error with a message, and we found nothing on Retry-After (5, the earlier partial kept). No SLA found (0). Orbis APIs went GA on 8 July 2026, but the remote MCP server is in public preview and the README says some Orbis and EV services may not be enabled on every account (5, kept). 0+5+0+5+0+5 = 15." }, "scores": { "a": 82, "b": 15 } }, { "by": 35, "category": "payments", "leads": "nominatim", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "No x402, MPP or L402 (0). Free allowances are public, but the pricing page re-read on 2 October showed no paid rate as a number, only a euro estimator and a contact-sales link (5 of 20, kept). A no-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with Search and Matrix at 2,500 (20). Signup is a browser flow (0). The pricing page is on a host whose acceptable use policy now bars robots, so it wasn't re-read on 4 November. 0+5+20+0 = 25." }, "scores": { "a": 60, "b": 25 } }, { "by": 26, "category": "maintenance", "leads": "tomtom", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "MCP v1.6.15 on 2 November 2026 (30). Eight tags since 6 August, v1.6.8 (15 September) to v1.6.15 (2 November) (20). Pull requests from several maintainers merged up to 3 November 2026. We couldn't see issue reply times from git (18, kept). The package is at 1.6.15 in its repository; the 30 September note that it wasn't in the official MCP registry came from the registry's JSON API and is struck (8, kept). CI runs type checks, lint, build, end-to-end tests and a Veracode scan, with dependabot (10). 30+20+18+8+10 = 86." }, "scores": { "a": 60, "b": 86 } }, { "by": 20, "category": "schema", "leads": "tomtom", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "No public OpenAPI that we found. The MCP's tools have Zod schemas with described fields (22). docs.tomtom.com/llms.txt indexes about 180 pages, many as .md, per the 2 October check, not re-read on 4 November (10). Tool descriptions are mostly one line, with little on when not to use a tool (12). Typed fields with constraints, and since 1.6.12 the search, routing and EV tools list their valid values from the maps-sdk (11, kept). We couldn't read the REST error reference. The MCP returns typed errors per status code, and since 1.6.13 tells a 401 from a 403 (8). Versioned REST paths; the MCP CHANGELOG.md has dated entries from 1.6.11 (5 October 2026) to 1.6.14 and says 1.1.1 to 1.6.10 have none (8, kept). 22+10+12+11+8+8 = 71." }, "scores": { "a": 51, "b": 71 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Nominatim project (osm-search)", "b": "TomTom", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.tomtom.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "None", "b": "API key", "name": "Auth" }, { "a": "Free", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "GPL-3.0-or-later", "b": "Apache-2.0 (MCP server)", "name": "Licence" }, { "a": "none", "b": "13", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-14", "b": "2026-11-02", "name": "Last release" }, { "a": "no date given", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "no document linked", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "2.1k PyPI/wk", "b": "55 stars, 996 npm/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Nominatim scores 63.5 (B) on agent readiness against TomTom Maps APIs + MCP's 45.9 (E), and leads in 3 of 7 scored categories. TomTom Maps APIs + MCP leads on schema \u0026 documentation and maintenance \u0026 community.", "question": "Which is better for AI agents, Nominatim or TomTom Maps APIs + MCP?" }, { "answer": "Nominatim needs no key. TomTom Maps APIs + MCP needs an API key.", "question": "Do Nominatim and TomTom Maps APIs + MCP need an API key?" }, { "answer": "No hosted endpoint is listed for Nominatim. TomTom Maps APIs + MCP has a hosted endpoint at https://api.tomtom.com.", "question": "Can an agent call Nominatim and TomTom Maps APIs + MCP without installing anything?" }, { "answer": "Nominatim is open source (GPL-3.0-or-later). No open-source release is listed for TomTom Maps APIs + MCP.", "question": "Are Nominatim and TomTom Maps APIs + MCP open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 82 against 15", "Payments \u0026 pricing, 60 against 25" ], "also": [ "No key needed to call it", "Open source", "No incidents deducted, where TomTom Maps APIs + MCP loses 6 points for them" ], "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" }, { "aheadOn": [ "Schema \u0026 documentation, 71 against 51", "Maintenance \u0026 community, 86 against 60" ], "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine", "Free to start without a card" ], "goodFor": "Drive planning with live traffic, EV charging and reachable range.", "slug": "tomtom", "watchFor": "Terms, rate limits and deprecation policy couldn't be read, so storage rules and notice periods are unverified" } ], "history": { "nominatim": null, "tomtom": [ { "causes": [ "product", "evidence" ], "date": "2026-11-04", "delta": -9, "from": 54.9, "fromGrade": "C", "to": 45.9, "toGrade": "E" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.2, "from": 55.1, "fromGrade": "C", "to": 54.9, "toGrade": "C" } ] }, "job": { "capability": "geo.geocode", "name": "Geocoding" }, "others": [ { "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/amazon-location-vs-tomtom.json", "title": "Amazon Location Service vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-tomtom" }, { "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/arcgis-vs-tomtom.json", "title": "ArcGIS Location Platform vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/arcgis-vs-tomtom" }, { "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/azure-maps-vs-tomtom.json", "title": "Azure Maps vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-nominatim.json", "title": "Geoapify Location Platform + MCP vs Nominatim", "url": "https://www.anchorterminal.com/compare/geoapify-vs-nominatim" }, { "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/geocodio-vs-nominatim.json", "title": "Geocodio vs Nominatim", "url": "https://www.anchorterminal.com/compare/geocodio-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-tomtom.json", "title": "Geocodio vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/geocodio-vs-tomtom" }, { "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/google-maps-platform-vs-tomtom.json", "title": "Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom" }, { "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/here-location-services-vs-tomtom.json", "title": "HERE Location Services vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-nominatim.json", "title": "LocationIQ vs Nominatim", "url": "https://www.anchorterminal.com/compare/locationiq-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-tomtom.json", "title": "LocationIQ vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/locationiq-vs-tomtom" }, { "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/mapbox-vs-tomtom.json", "title": "Mapbox APIs + MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/mapbox-vs-tomtom" }, { "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/mapquest-vs-tomtom.json", "title": "MapQuest vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/mapquest-vs-tomtom" }, { "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/maptiler-vs-tomtom.json", "title": "MapTiler Cloud vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/maptiler-vs-tomtom" }, { "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-woosmap.json", "title": "Nominatim vs Woosmap", "url": "https://www.anchorterminal.com/compare/nominatim-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/opencage-vs-tomtom.json", "title": "OpenCage Geocoding API vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/opencage-vs-tomtom" }, { "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" }, { "json": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.json", "title": "Stadia Maps vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/tomtom-vs-woosmap.json", "title": "TomTom Maps APIs + MCP vs Woosmap", "url": "https://www.anchorterminal.com/compare/tomtom-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/nextbillion-vs-tomtom.json", "title": "NextBillion.ai vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/nextbillion-vs-tomtom" } ], "panel": null, "scores": [ { "by": 67, "edge": "nominatim", "key": "reliability", "name": "Reliability", "nominatim": 82, "tomtom": 15, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 20, "edge": "tomtom", "key": "schema", "name": "Schema \u0026 documentation", "nominatim": 51, "tomtom": 71, "weight": 13 }, { "by": 3, "edge": "tomtom", "key": "ergonomics", "name": "Agent ergonomics", "nominatim": 75, "tomtom": 78, "weight": 13 }, { "by": 1, "edge": "tomtom", "key": "security", "name": "Security \u0026 auth", "nominatim": 50, "tomtom": 51, "weight": 14 }, { "by": 35, "edge": "nominatim", "key": "payments", "name": "Payments \u0026 pricing", "nominatim": 60, "tomtom": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 26, "edge": "tomtom", "key": "maintenance", "name": "Maintenance \u0026 community", "nominatim": 60, "tomtom": 86, "weight": 7 }, { "by": 1, "edge": "nominatim", "key": "transparency", "name": "Transparency \u0026 trust", "nominatim": 59, "tomtom": 58, "weight": 7 } ], "summary": "Nominatim scores 63.5 (B) on agent readiness against TomTom Maps APIs + MCP's 45.9 (E), and leads in 3 of 7 scored categories. TomTom Maps APIs + MCP leads on schema \u0026 documentation and maintenance \u0026 community. Both do geocoding.", "tasks": null, "tutorials": [], "verdicts": { "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.", "tomtom": "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with an official MCP server released about weekly. Terms, rate limits and the deprecation policy couldn't be read, the status page bars our reader, and MCP patch releases in October removed tools and inputs without notice." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/nominatim-vs-tomtom", "json": "https://www.anchorterminal.com/compare/nominatim-vs-tomtom.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/nominatim-vs-tomtom.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/nominatim-vs-tomtom.min.md" }, "markdown": "Nominatim scores 63.5 (B) on agent readiness against TomTom Maps APIs + MCP's 45.9 (E), and leads in 3 of 7 scored categories. TomTom Maps APIs + MCP leads on schema \u0026 documentation and maintenance \u0026 community. Both do geocoding.\n\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- TomTom Maps APIs + MCP: grade E, 45.9/100, rank #1185 of 1510. Markdown https://www.anchorterminal.com/tools/tomtom.md · JSON https://www.anchorterminal.com/api/v1/tools/tomtom.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### 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 15\n- Payments \u0026 pricing, 60 against 25\n\nAlso in its favour:\n- No key needed to call it\n- Open source\n- No incidents deducted, where TomTom Maps APIs + MCP loses 6 points for them\n\nWatch for: No OpenAPI spec and no llms.txt\n\n### TomTom Maps APIs + MCP (E)\n\nGood for: Drive planning with live traffic, EV charging and reachable range.\n\nAhead on:\n- Schema \u0026 documentation, 71 against 51\n- Maintenance \u0026 community, 86 against 60\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Terms, rate limits and deprecation policy couldn't be read, so storage rules and notice periods are unverified\n\n\n## Why the edge\n\n### Reliability: Nominatim +67\n\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- TomTom Maps APIs + MCP (15): TomTom's API status page sits on tomtom.service-now.com, whose robots.txt disallows every path on 4 November, so the earlier status readings are struck (0). With no history we may read, the record scores 5. No published QPS limits or 429 guidance were found on the docs pages we read on 1 October; TomTom's acceptable use policy now bars robots from its websites, so they weren't re-read (0). The MCP maps a 429 to a typed rate-limit error with a message, and we found nothing on Retry-After (5, the earlier partial kept). No SLA found (0). Orbis APIs went GA on 8 July 2026, but the remote MCP server is in public preview and the README says some Orbis and EV services may not be enabled on every account (5, kept). 0+5+0+5+0+5 = 15.\n\n### Payments \u0026 pricing: Nominatim +35\n\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- TomTom Maps APIs + MCP (25): No x402, MPP or L402 (0). Free allowances are public, but the pricing page re-read on 2 October showed no paid rate as a number, only a euro estimator and a contact-sales link (5 of 20, kept). A no-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with Search and Matrix at 2,500 (20). Signup is a browser flow (0). The pricing page is on a host whose acceptable use policy now bars robots, so it wasn't re-read on 4 November. 0+5+20+0 = 25.\n\n### Maintenance \u0026 community: TomTom Maps APIs + MCP +26\n\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- TomTom Maps APIs + MCP (86): MCP v1.6.15 on 2 November 2026 (30). Eight tags since 6 August, v1.6.8 (15 September) to v1.6.15 (2 November) (20). Pull requests from several maintainers merged up to 3 November 2026. We couldn't see issue reply times from git (18, kept). The package is at 1.6.15 in its repository; the 30 September note that it wasn't in the official MCP registry came from the registry's JSON API and is struck (8, kept). CI runs type checks, lint, build, end-to-end tests and a Veracode scan, with dependabot (10). 30+20+18+8+10 = 86.\n\n### Schema \u0026 documentation: TomTom Maps APIs + MCP +20\n\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- TomTom Maps APIs + MCP (71): No public OpenAPI that we found. The MCP's tools have Zod schemas with described fields (22). docs.tomtom.com/llms.txt indexes about 180 pages, many as .md, per the 2 October check, not re-read on 4 November (10). Tool descriptions are mostly one line, with little on when not to use a tool (12). Typed fields with constraints, and since 1.6.12 the search, routing and EV tools list their valid values from the maps-sdk (11, kept). We couldn't read the REST error reference. The MCP returns typed errors per status code, and since 1.6.13 tells a 401 from a 403 (8). Versioned REST paths; the MCP CHANGELOG.md has dated entries from 1.6.11 (5 October 2026) to 1.6.14 and says 1.1.1 to 1.6.10 have none (8, kept). 22+10+12+11+8+8 = 71.\n\n## Score by category\n\n| Category | Weight | Nominatim | TomTom Maps APIs + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 82 | 15 | Nominatim +67 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 51 | 71 | TomTom Maps APIs + MCP +20 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 78 | TomTom Maps APIs + MCP +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 50 | 51 | TomTom Maps APIs + MCP +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 25 | Nominatim +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 86 | TomTom Maps APIs + MCP +26 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 59 | 58 | Nominatim +1 |\n| Negative events | ≤15 | 0 | -6 | |\n| **Total** | | **63.5 · B** | **45.9 · E** | |\n\n## Facts side by side\n\n| Fact | Nominatim | TomTom Maps APIs + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Nominatim project (osm-search) | TomTom |\n| Hosted endpoint | no (local only) | `https://api.tomtom.com` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | None | API key |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| Licence | GPL-3.0-or-later | Apache-2.0 (MCP server) |\n| Tools exposed | none | 13 |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| Last release | 2026-10-14 | 2026-11-02 |\n| Terms last updated | no date given | couldn't be read |\n| Privacy policy last updated | no document linked | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | yes | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | 2.1k PyPI/wk | 55 stars, 996 npm/wk |\n| Agent reviews | none | 3/5 (2) |\n\n## How the scores have moved\n\n### Nominatim\n\nNo score change since it was listed.\n\n### TomTom Maps APIs + MCP\n\n- -9.0 on 4 November 2026 (C to E): product, new evidence\n- -0.2 on 8 October 2026: checklist\n\n## Verdicts\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**TomTom Maps APIs + MCP.** No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with an official MCP server released about weekly. Terms, rate limits and the deprecation policy couldn't be read, the status page bars our reader, and MCP patch releases in October removed tools and inputs without notice.\n\n## Before you call either\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### TomTom Maps APIs + MCP\n\n1. Use tomtom-geocode (20,000 free) rather than tomtom-fuzzy-search (2,500 free) when you have a full address\n2. Pin `@tomtom-org/tomtom-mcp` to a version, since patch releases have removed tools and changed inputs\n3. Page search results with `cursor` and the previous response's `nextCursor`, not `ofs`, from 1.6.12\n4. Read a 403 as the account or key not covering the API, and don't retry it; a 401 means a missing or unknown key\n5. Redact the key parameter before logging REST URLs\n\n## Questions\n\n### Which is better for AI agents, Nominatim or TomTom Maps APIs + MCP?\n\nNominatim scores 63.5 (B) on agent readiness against TomTom Maps APIs + MCP's 45.9 (E), and leads in 3 of 7 scored categories. TomTom Maps APIs + MCP leads on schema \u0026 documentation and maintenance \u0026 community.\n\n### Do Nominatim and TomTom Maps APIs + MCP need an API key?\n\nNominatim needs no key. TomTom Maps APIs + MCP needs an API key.\n\n### Can an agent call Nominatim and TomTom Maps APIs + MCP without installing anything?\n\nNo hosted endpoint is listed for Nominatim. TomTom Maps APIs + MCP has a hosted endpoint at https://api.tomtom.com.\n\n### Are Nominatim and TomTom Maps APIs + MCP open source?\n\nNominatim is open source (GPL-3.0-or-later). No open-source release is listed for TomTom Maps APIs + MCP.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/nominatim-vs-tomtom.json, and with the fewest tokens: https://www.anchorterminal.com/compare/nominatim-vs-tomtom.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"nominatim\", \"b\": \"tomtom\"}`. From a terminal: `anchor compare nominatim tomtom`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/nominatim.json and https://www.anchorterminal.com/api/v1/tools/tomtom.json\n\n## Other comparisons with Nominatim or TomTom Maps APIs + MCP\n\n- [Amazon Location Service vs Nominatim](https://www.anchorterminal.com/compare/amazon-location-vs-nominatim.md)\n- [Amazon Location Service vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.md)\n- [ArcGIS Location Platform vs Nominatim](https://www.anchorterminal.com/compare/arcgis-vs-nominatim.md)\n- [ArcGIS Location Platform vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/arcgis-vs-tomtom.md)\n- [Azure Maps vs Nominatim](https://www.anchorterminal.com/compare/azure-maps-vs-nominatim.md)\n- [Azure Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-tomtom.md)\n- [Geoapify Location Platform + MCP vs Nominatim](https://www.anchorterminal.com/compare/geoapify-vs-nominatim.md)\n- [Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geoapify-vs-tomtom.md)\n- [Geocodio vs Nominatim](https://www.anchorterminal.com/compare/geocodio-vs-nominatim.md)\n- [Geocodio vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geocodio-vs-tomtom.md)\n- [Google Maps Platform + Grounding Lite MCP vs Nominatim](https://www.anchorterminal.com/compare/google-maps-platform-vs-nominatim.md)\n- [Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom.md)\n- [HERE Location Services vs Nominatim](https://www.anchorterminal.com/compare/here-location-services-vs-nominatim.md)\n- [HERE Location Services vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.md)\n- [LocationIQ vs Nominatim](https://www.anchorterminal.com/compare/locationiq-vs-nominatim.md)\n- [LocationIQ vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/locationiq-vs-tomtom.md)\n- [Mapbox APIs + MCP vs Nominatim](https://www.anchorterminal.com/compare/mapbox-vs-nominatim.md)\n- [Mapbox APIs + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapbox-vs-tomtom.md)\n- [MapQuest vs Nominatim](https://www.anchorterminal.com/compare/mapquest-vs-nominatim.md)\n- [MapQuest vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapquest-vs-tomtom.md)\n- [MapTiler Cloud vs Nominatim](https://www.anchorterminal.com/compare/maptiler-vs-nominatim.md)\n- [MapTiler Cloud vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/maptiler-vs-tomtom.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 Woosmap](https://www.anchorterminal.com/compare/nominatim-vs-woosmap.md)\n- [OpenCage Geocoding API vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/opencage-vs-tomtom.md)\n- [Radar vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/radar-vs-tomtom.md)\n- [Stadia Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.md)\n- [TomTom Maps APIs + MCP vs Woosmap](https://www.anchorterminal.com/compare/tomtom-vs-woosmap.md)\n- [NextBillion.ai vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/nextbillion-vs-tomtom.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": "Nominatim vs TomTom Maps APIs + MCP", "url": "" } ], "description": "Nominatim scores 63.5 (B) to TomTom Maps's 45.9 (E) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Nominatim B 63.5", "TomTom Maps APIs + MCP E 45.9", "scores" ], "h1": "Nominatim vs TomTom Maps APIs + MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/nominatim-vs-tomtom", "published": "2026-10-01", "section": "tools", "title": "Nominatim vs TomTom Maps for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/nominatim-vs-tomtom" }, "tokens": { "markdown": 4050, "slim": 1980 }, "version": 1 }