{
  "data": {
    "a": {
      "slug": "radar",
      "name": "Radar",
      "vendor": "Radar Labs",
      "vendorUrl": "https://radar.com",
      "kind": "http-api",
      "category": "maps",
      "summary": "Radar is a location platform from Radar Labs with REST APIs for forward, reverse and IP geocoding, address autocomplete and validation, places search, distance, matrix, directions and route optimisation, plus geofencing, trip tracking and base maps.",
      "url": "https://www.anchorterminal.com/tools/radar",
      "markdownUrl": "https://www.anchorterminal.com/tools/radar.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/radar.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/radar.json",
      "repo": "https://github.com/radarlabs/radar-sdk-js",
      "license": "Proprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.radar.io/v1",
      "packages": [
        {
          "registry": "npm",
          "name": "radar-sdk-js"
        }
      ],
      "auth": "api-key",
      "authNotes": "API key in the `Authorization` header, with no query-string option documented. Each project has four keys, test and live, publishable and secret. Publishable keys reach 16 of the 36 documented operations, including all geocoding, search and routing calls, and can be restricted by website domain or mobile app identifier. Secret keys reach the rest and can read or write any data. Keys come from the dashboard. Whether sign-up is self-serve was not established, because dashboard.radar.com's robots.txt closes every path.",
      "pricing": "paid",
      "pricingNotes": "Core Maps (forward, reverse and IP geocoding, autocomplete, static maps, distance, directions, matrix) starts at $0.50 per 1,000 API calls and Premium Maps (address validation, places search, route matching, route optimisation, satellite maps) at $2.00. Matrix bills per element. Every plan is an annual commitment with a monthly quota, at a rate Radar sets by quote. The pricing page says there is no free tier, and that teams can start with a technical validation period arranged with sales (https://radar.com/pricing).",
      "priceSummary": "$0.50 / 1k req",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the API reference, the docs index or the pricing page (checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://docs.radar.com/api",
      "llmsTxt": "https://docs.radar.com/llms.txt",
      "capabilities": [
        "geo.geocode",
        "geo.reverse",
        "geo.places",
        "geo.routing",
        "geo.tiles"
      ],
      "tags": [
        "hosted",
        "api-key",
        "llms-txt",
        "status-page",
        "sales-led",
        "annual-contract",
        "soc2",
        "closed-source"
      ],
      "lastRelease": "2026-09-14",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 53.3,
        "grade": "D",
        "agentReady": false,
        "rank": 713,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 12,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 65,
          "maintenance": 77,
          "payments": 10,
          "reliability": 70,
          "schema": 50,
          "security": 56,
          "transparency": 55
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": -2,
        "negativeNotes": [
          "9 October 2026. The Maps product page says the geocoding APIs come with 'the right to store, reuse, and export results freely' (https://radar.com/product/maps), while section 2(d) of the Terms of Use forbids storing address or point-of-interest data from the geocoding, autocomplete or place search APIs for more than 30 days (https://radar.com/terms) and the geocoding docs repeat the 30-day limit (https://docs.radar.com/maps/geocoding.md). 2 points for a claim the published terms contradict. A quoted enterprise agreement may differ and is not published."
        ],
        "verdict": "Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found.",
        "bestFor": "A company that already has a Radar contract, or wants geofencing and trip tracking with geocoding and routing on one key.",
        "strengths": [
          "Each of the 36 documented operations states its key level and a default rate limit, from 10 to 100 requests a second",
          "docs.radar.com publishes llms.txt and a Markdown twin of every page, including the whole API reference in one file",
          "Statuspage history lists two API incidents in the 90 days to 9 October 2026, of 3 minutes and about an hour",
          "Publishable keys are limited to 16 client-safe operations and can be restricted by website domain or mobile app identifier",
          "The DPA names two sub-processors (AWS and MongoDB) and the FAQ states default retention periods"
        ],
        "weaknesses": [
          "The pricing page says Radar has no free tier and every plan is an annual commitment set by quote",
          "No OpenAPI description and no API changelog were found in the docs index",
          "The terms cap storage of geocoding, autocomplete and place results at 30 days, while the Maps product page claims a right to store results freely",
          "The terms of 24 May 2023 let Radar change or stop the services without notice, and still describe a free version",
          "A secret key can read or write any project data, with no scopes found",
          "The terms forbid using the services to develop or test other geocoding, autocomplete or place search APIs, which matters before any probe is run"
        ],
        "agentNotes": [
          "Send the key in the `Authorization` header with no `Bearer` prefix, and call `https://api.radar.io/v1`, not radar.com",
          "Use a publishable key for geocoding, search and routing. Keep the secret key for users, trips, geofences and beacons",
          "Call `/v1/search/autocomplete` for partial addresses and place names. `/v1/geocode/forward` is documented as best for complete addresses",
          "Set `units=metric` on routing calls. The default is imperial, with distances in feet",
          "Treat 429 as one of three things (rate limit, no state change or selective throttling) and 402 as usage exceeded. No Retry-After header is documented",
          "Do not keep geocoding, autocomplete or place results for more than 30 days"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "D",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 53.3
          }
        ],
        "editorialScores": {
          "ergonomics": 65,
          "maintenance": 77,
          "payments": 10,
          "reliability": 70,
          "schema": 50,
          "security": 56,
          "transparency": 51
        },
        "provenanceScore": 58
      },
      "connect": {
        "install": "npm install radar-sdk-js",
        "http": "curl \"https://api.radar.io/v1/geocode/forward?query=20+jay+st+brooklyn+ny\" -H \"Authorization: $RADAR_PUBLISHABLE_KEY\""
      },
      "letme": {
        "capability": "https://letme.dev/geo.geocode",
        "tool": "https://letme.dev/radar"
      },
      "area": "everyday",
      "unitPrices": [
        {
          "item": "Core Maps API calls, starting price",
          "unit": "1k-requests",
          "usd": 0.5,
          "note": "Geocoding, autocomplete, static maps, distance, directions, matrix (per element). Annual commitment, rate set by quote"
        },
        {
          "item": "Premium Maps API calls, starting price",
          "unit": "1k-requests",
          "usd": 2,
          "note": "Address validation, places search, route matching, route optimisation, satellite maps. Annual commitment, rate set by quote"
        }
      ],
      "provenance": {
        "legalEntity": "Radar Labs, Inc.",
        "domain": "radar.com",
        "domainRegistered": "1994-12-16",
        "endpointOnVendorDomain": false,
        "terms": "https://radar.com/terms",
        "privacy": "https://radar.com/privacy",
        "statusPage": "https://status.radar.com",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-10-09",
        "notes": [
          "The privacy notice (last updated 13 May 2025) names Radar Labs, Inc., a Delaware corporation at 111 5th Ave, 12th Floor, New York, NY 10003.",
          "The Terms of Use (last updated 24 May 2023) cover the SDK and Radar's APIs and incorporate the DPA at radar.com/dpa. They describe a free version, which the pricing page says Radar does not have. Paid plans are by quote, and no enterprise agreement is published.",
          "The API answers at api.radar.io, a second domain. Nothing was sent to it, and its registrant was not checked.",
          "radar.com/.well-known/security.txt answers 404. The FAQ gives security@radar.com for reports.",
          "No API changelog was found in the docs index. The web SDK repository has dated release tags.",
          "RDAP gives 16 December 1994 as the registration date of radar.com.",
          "robots.txt answers on the day. radar.com 200 with a sitemap line only. docs.radar.com 200 with ai-input=yes. status.radar.com 200 disallowing /api/ and /embed/. dashboard.radar.com 200 disallowing every path. trust.radar.com answers the request with its page shell."
        ],
        "score": 58
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/radar.json",
      "live": {
        "slug": "radar",
        "probe": {
          "target": "https://api.radar.io/v1",
          "method": "get",
          "lastAt": "2026-10-10T01:38:03.858495583Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 119,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 124,
          "p95ms24h": 231,
          "samples24h": 102,
          "samples30d": 102,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 85,
              "ok": 85
            },
            {
              "date": "2026-10-10",
              "probes": 17,
              "ok": 17
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.radar.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-10T01:34:07.147754926Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "radarlabs/radar-sdk-js",
            "version": "autocomplete-v1.1.1",
            "released": "2026-09-14",
            "seenAt": "2026-10-09T17:15:51.370576682Z"
          },
          {
            "registry": "npm",
            "name": "radar-sdk-js",
            "version": "5.2.0",
            "seenAt": "2026-10-09T17:15:50.510226325Z"
          }
        ],
        "githubStars": 52,
        "npmWeekly": 62814,
        "pages": [
          {
            "url": "https://radar.com/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-09T18:44:14.0723216Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "22ff53a04e1c"
          },
          {
            "url": "https://radar.com/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-09T18:44:16.223416673Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "12f29204b40d"
          },
          {
            "url": "https://radar.com/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-09T18:44:18.136602575Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "411754a84910"
          }
        ],
        "updatedAt": "2026-10-10T01:38:03.858495583Z"
      }
    },
    "answer": "TomTom Maps APIs + MCP scores 54.9 (C) on agent readiness against Radar's 53.3 (D), and leads in 5 of 7 scored categories. Radar leads on reliability and security \u0026 auth.",
    "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",
      "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 defaults to the Orbis backend. The local server defaults to the older TomTom Maps backend unless MAPS=tomtom-orbis-maps is set. Unreleased changes merged on 30 September 2026 drop the older backend, the tomtom-maps-backend header and the MAPS variable.",
      "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": 15,
      "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-09-23",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 54.9,
        "grade": "C",
        "agentReady": false,
        "rank": 675,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 11,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 78,
          "maintenance": 86,
          "payments": 25,
          "reliability": 30,
          "schema": 71,
          "security": 51,
          "transparency": 58
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "low",
          "date": "2026-10-01"
        },
        "negative": 0,
        "verdict": "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month. Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified.",
        "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 routing and search, reachable range and search along a route as MCP tools",
          "All 18 MCP tools annotated read-only, idempotent and non-destructive",
          "Five MCP releases between 14 July and 23 September 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 render client-side, so storage rules and notice periods are unverified",
          "Status page keeps only five days of history",
          "Paid prices only through a euro estimator",
          "Hosted MCP in public preview and missing from the MCP registry",
          "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",
          "Don't send tomtom-maps-backend in new configs, since the next release stops reading it and Orbis is already the hosted default",
          "Read a 403 'missing permissions' as the key lacking Orbis or EV products, and enable them in the developer portal",
          "Pass show_ui false when the client can't render MCP Apps, or you'll get a JSON summary instead of a map",
          "Redact the key parameter before logging REST URLs"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "low",
            "grade": "C",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 54.9
          }
        ],
        "editorialScores": {
          "ergonomics": 78,
          "maintenance": 86,
          "payments": 25,
          "reliability": 30,
          "schema": 71,
          "security": 51,
          "transparency": 41
        },
        "provenanceScore": 74
      },
      "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-10-02",
        "notes": [
          "The privacy policy names TomTom International BV and was last edited 1 August 2024. Subprocessors and storage locations are on https://www.tomtom.com/en-gb/privacy/more-information/.",
          "The terms page renders client-side and returned no readable text to our fetcher on 30 September, 1 October or 2 October, and developer.tomtom.com/legal redirects to it, so storage and caching rules are unverified.",
          "www.tomtom.com/.well-known/security.txt returns 404. Vulnerabilities go to TomTom's HackerOne programme, per the security policy in the tomtom-international GitHub organisation.",
          "The status page shows current status per API and only the last five days of history.",
          "A deprecation policy page is linked from docs.tomtom.com/llms.txt but renders client-side, and its .md twin returns 404."
        ],
        "score": 74
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/tomtom.json",
      "live": {
        "slug": "tomtom",
        "probe": {
          "target": "https://api.tomtom.com",
          "method": "get",
          "lastAt": "2026-10-10T01:38:11.065601636Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 173,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 179,
          "p95ms24h": 661,
          "samples24h": 250,
          "samples30d": 2251,
          "days": [
            {
              "date": "2026-10-01",
              "probes": 109,
              "ok": 109
            },
            {
              "date": "2026-10-02",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-03",
              "probes": 271,
              "ok": 271
            },
            {
              "date": "2026-10-04",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-05",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-06",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-07",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-08",
              "probes": 268,
              "ok": 268
            },
            {
              "date": "2026-10-09",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-10",
              "probes": 17,
              "ok": 17
            }
          ]
        },
        "vendorStatus": {
          "page": "https://tomtom.service-now.com/status",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-10T00:51:20.792064098Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "tomtom-international/tomtom-mcp",
            "version": "v1.6.12",
            "released": "2026-10-09",
            "seenAt": "2026-10-09T17:25:04.0205712Z"
          },
          {
            "registry": "npm",
            "name": "@tomtom-org/tomtom-mcp",
            "version": "1.6.12",
            "seenAt": "2026-10-09T17:25:03.080630502Z"
          }
        ],
        "githubStars": 56,
        "npmWeekly": 777,
        "securityTxt": {
          "url": "https://tomtom.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-09T15:40:05.596425929Z"
        },
        "llmsTxt": {
          "url": "https://docs.tomtom.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-09T14:02:55.11188535Z"
        },
        "domain": {
          "domain": "tomtom.com",
          "registered": "1996-02-23",
          "source": "https://rdap.verisign.com/com/v1/domain/tomtom.com",
          "checkedAt": "2026-10-04T13:05:44.956685546Z"
        },
        "pages": [
          {
            "url": "https://docs.tomtom.com/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-09T18:38:37.010050617Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "9f426a4be50f"
          },
          {
            "url": "https://www.tomtom.com/privacy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-09T18:55:03.387246233Z",
            "changedAt": "2026-10-08T18:31:01.446679763Z",
            "fingerprint": "b77d548785dc"
          },
          {
            "url": "https://docs.tomtom.com/legal/terms-and-conditions",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-09T18:38:34.908266259Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "68f5b7cd1e5c"
          }
        ],
        "updatedAt": "2026-10-10T01:38:11.065601636Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Radar Labs",
        "b": "TomTom",
        "name": "Vendor"
      },
      {
        "a": "https://api.radar.io/v1",
        "b": "https://api.tomtom.com",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP, Streamable HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Paid",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0",
        "b": "Apache-2.0 (MCP server)",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "15",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-09-14",
        "b": "2026-09-23",
        "name": "Last release"
      },
      {
        "a": "2023-05-24",
        "b": "couldn't be read",
        "name": "Terms last updated"
      },
      {
        "a": "2025-05-13",
        "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": "not found in the text",
        "b": "couldn't be read",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "couldn't be read",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "couldn't be read",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "couldn't be read",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "55 stars, 996 npm/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3/5 (2)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "TomTom Maps APIs + MCP scores 54.9 (C) on agent readiness against Radar's 53.3 (D), and leads in 5 of 7 scored categories. Radar leads on reliability and security \u0026 auth.",
        "question": "Which is better for AI agents, Radar or TomTom Maps APIs + MCP?"
      },
      {
        "answer": "Both need an API key.",
        "question": "Do Radar and TomTom Maps APIs + MCP need an API key?"
      },
      {
        "answer": "Yes. Radar has a hosted endpoint at https://api.radar.io/v1 and TomTom Maps APIs + MCP at https://api.tomtom.com.",
        "question": "Can an agent call Radar and TomTom Maps APIs + MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 70 against 30",
          "Security \u0026 auth, 56 against 51"
        ],
        "also": null,
        "goodFor": "A company that already has a Radar contract, or wants geofencing and trip tracking with geocoding and routing on one key.",
        "slug": "radar",
        "watchFor": "The pricing page says Radar has no free tier and every plan is an annual commitment set by quote"
      },
      {
        "aheadOn": [
          "Schema \u0026 documentation, 71 against 50",
          "Agent ergonomics, 78 against 65",
          "Payments \u0026 pricing, 25 against 10",
          "Maintenance \u0026 community, 86 against 77"
        ],
        "also": [
          "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 render client-side, so storage rules and notice periods are unverified"
      }
    ],
    "job": {
      "capability": "geo.geocode",
      "name": "Geocoding"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/amazon-location-vs-radar.json",
        "title": "Amazon Location Service vs Radar",
        "url": "https://www.anchorterminal.com/compare/amazon-location-vs-radar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/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-radar.json",
        "title": "ArcGIS Location Platform vs Radar",
        "url": "https://www.anchorterminal.com/compare/arcgis-vs-radar"
      },
      {
        "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-radar.json",
        "title": "Azure Maps vs Radar",
        "url": "https://www.anchorterminal.com/compare/azure-maps-vs-radar"
      },
      {
        "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-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-tomtom.json",
        "title": "Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom"
      },
      {
        "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-radar.json",
        "title": "Google Maps Platform + Grounding Lite MCP vs Radar",
        "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-radar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/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-radar.json",
        "title": "HERE Location Services vs Radar",
        "url": "https://www.anchorterminal.com/compare/here-location-services-vs-radar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/here-location-services-vs-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-radar.json",
        "title": "LocationIQ vs Radar",
        "url": "https://www.anchorterminal.com/compare/locationiq-vs-radar"
      },
      {
        "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-radar.json",
        "title": "Mapbox APIs + MCP vs Radar",
        "url": "https://www.anchorterminal.com/compare/mapbox-vs-radar"
      },
      {
        "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-radar.json",
        "title": "MapQuest vs Radar",
        "url": "https://www.anchorterminal.com/compare/mapquest-vs-radar"
      },
      {
        "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/opencage-vs-radar.json",
        "title": "OpenCage Geocoding API vs Radar",
        "url": "https://www.anchorterminal.com/compare/opencage-vs-radar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/opencage-vs-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-stadia-maps.json",
        "title": "Radar vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/radar-vs-stadia-maps"
      },
      {
        "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"
      }
    ],
    "scores": [
      {
        "by": 40,
        "edge": "radar",
        "key": "reliability",
        "name": "Reliability",
        "radar": 70,
        "tomtom": 30,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 21,
        "edge": "tomtom",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "radar": 50,
        "tomtom": 71,
        "weight": 13
      },
      {
        "by": 13,
        "edge": "tomtom",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "radar": 65,
        "tomtom": 78,
        "weight": 13
      },
      {
        "by": 5,
        "edge": "radar",
        "key": "security",
        "name": "Security \u0026 auth",
        "radar": 56,
        "tomtom": 51,
        "weight": 14
      },
      {
        "by": 15,
        "edge": "tomtom",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "radar": 10,
        "tomtom": 25,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 9,
        "edge": "tomtom",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "radar": 77,
        "tomtom": 86,
        "weight": 7
      },
      {
        "by": 3,
        "edge": "tomtom",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "radar": 55,
        "tomtom": 58,
        "weight": 7
      }
    ],
    "summary": "TomTom Maps APIs + MCP scores 54.9 (C) on agent readiness against Radar's 53.3 (D), and leads in 5 of 7 scored categories. Radar leads on reliability and security \u0026 auth. Both do geocoding.",
    "verdicts": {
      "radar": "Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found.",
      "tomtom": "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month. Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/radar-vs-tomtom",
    "json": "https://www.anchorterminal.com/compare/radar-vs-tomtom.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/radar-vs-tomtom.md",
    "slim": "https://www.anchorterminal.com/compare/radar-vs-tomtom.min.md"
  },
  "markdown": "TomTom Maps APIs + MCP scores 54.9 (C) on agent readiness against Radar's 53.3 (D), and leads in 5 of 7 scored categories. Radar leads on reliability and security \u0026 auth. Both do geocoding.\n\n- Radar: grade D, 53.3/100, rank #713 of 950. Markdown https://www.anchorterminal.com/tools/radar.md · JSON https://www.anchorterminal.com/api/v1/tools/radar.json\n- TomTom Maps APIs + MCP: grade C, 54.9/100, rank #675 of 950. 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 78 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md\n\n## Which one, for what\n\n### Radar (D)\n\nGood for: A company that already has a Radar contract, or wants geofencing and trip tracking with geocoding and routing on one key.\n\nAhead on:\n- Reliability, 70 against 30\n- Security \u0026 auth, 56 against 51\n\nWatch for: The pricing page says Radar has no free tier and every plan is an annual commitment set by quote\n\n### TomTom Maps APIs + MCP (C)\n\nGood for: Drive planning with live traffic, EV charging and reachable range.\n\nAhead on:\n- Schema \u0026 documentation, 71 against 50\n- Agent ergonomics, 78 against 65\n- Payments \u0026 pricing, 25 against 10\n- Maintenance \u0026 community, 86 against 77\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified\n\n\n## Score by category\n\n| Category | Weight | Radar | TomTom Maps APIs + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 30 | Radar +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 50 | 71 | TomTom Maps APIs + MCP +21 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 78 | TomTom Maps APIs + MCP +13 |\n| Security \u0026 auth | 14% (17.5 this run) | 56 | 51 | Radar +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 25 | TomTom Maps APIs + MCP +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 77 | 86 | TomTom Maps APIs + MCP +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 55 | 58 | TomTom Maps APIs + MCP +3 |\n| Negative events | ≤15 | -2 | 0 | |\n| **Total** | | **53.3 · D** | **54.9 · C** | |\n\n## Facts side by side\n\n| Fact | Radar | TomTom Maps APIs + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Radar Labs | TomTom |\n| Hosted endpoint | `https://api.radar.io/v1` | `https://api.tomtom.com` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | API key | API key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0 | Apache-2.0 (MCP server) |\n| Tools exposed | none | 15 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-09-14 | 2026-09-23 |\n| Terms last updated | 2023-05-24 | couldn't be read |\n| Privacy policy last updated | 2025-05-13 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | yes | couldn't be read |\n| Terms or service can change without notice | yes | couldn't be read |\n| Arbitration or class-action waiver | yes | couldn't be read |\n| Popularity | none | 55 stars, 996 npm/wk |\n| Agent reviews | none | 3/5 (2) |\n\n## Verdicts\n\n**Radar.** Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found.\n\n**TomTom Maps APIs + MCP.** No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month. Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified.\n\n## Before you call either\n\n### Radar\n\n1. Send the key in the `Authorization` header with no `Bearer` prefix, and call `https://api.radar.io/v1`, not radar.com\n2. Use a publishable key for geocoding, search and routing. Keep the secret key for users, trips, geofences and beacons\n3. Call `/v1/search/autocomplete` for partial addresses and place names. `/v1/geocode/forward` is documented as best for complete addresses\n4. Set `units=metric` on routing calls. The default is imperial, with distances in feet\n5. Treat 429 as one of three things (rate limit, no state change or selective throttling) and 402 as usage exceeded. No Retry-After header is documented\n6. Do not keep geocoding, autocomplete or place results for more than 30 days\n\n### 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. Don't send tomtom-maps-backend in new configs, since the next release stops reading it and Orbis is already the hosted default\n3. Read a 403 'missing permissions' as the key lacking Orbis or EV products, and enable them in the developer portal\n4. Pass show_ui false when the client can't render MCP Apps, or you'll get a JSON summary instead of a map\n5. Redact the key parameter before logging REST URLs\n\n## Questions\n\n### Which is better for AI agents, Radar or TomTom Maps APIs + MCP?\n\nTomTom Maps APIs + MCP scores 54.9 (C) on agent readiness against Radar's 53.3 (D), and leads in 5 of 7 scored categories. Radar leads on reliability and security \u0026 auth.\n\n### Do Radar and TomTom Maps APIs + MCP need an API key?\n\nBoth need an API key.\n\n### Can an agent call Radar and TomTom Maps APIs + MCP without installing anything?\n\nYes. Radar has a hosted endpoint at https://api.radar.io/v1 and TomTom Maps APIs + MCP at https://api.tomtom.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/radar-vs-tomtom.json, and with the fewest tokens: https://www.anchorterminal.com/compare/radar-vs-tomtom.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"radar\", \"b\": \"tomtom\"}`. From a terminal: `anchor compare radar tomtom`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/radar.json and https://www.anchorterminal.com/api/v1/tools/tomtom.json\n\n## Other comparisons with Radar or TomTom Maps APIs + MCP\n\n- [Amazon Location Service vs Radar](https://www.anchorterminal.com/compare/amazon-location-vs-radar.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 Radar](https://www.anchorterminal.com/compare/arcgis-vs-radar.md)\n- [ArcGIS Location Platform vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/arcgis-vs-tomtom.md)\n- [Azure Maps vs Radar](https://www.anchorterminal.com/compare/azure-maps-vs-radar.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 Radar](https://www.anchorterminal.com/compare/geoapify-vs-radar.md)\n- [Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geoapify-vs-tomtom.md)\n- [Google Maps Platform + Grounding Lite MCP vs Radar](https://www.anchorterminal.com/compare/google-maps-platform-vs-radar.md)\n- [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 Radar](https://www.anchorterminal.com/compare/here-location-services-vs-radar.md)\n- [HERE Location Services vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.md)\n- [LocationIQ vs Radar](https://www.anchorterminal.com/compare/locationiq-vs-radar.md)\n- [LocationIQ vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/locationiq-vs-tomtom.md)\n- [Mapbox APIs + MCP vs Radar](https://www.anchorterminal.com/compare/mapbox-vs-radar.md)\n- [Mapbox APIs + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapbox-vs-tomtom.md)\n- [MapQuest vs Radar](https://www.anchorterminal.com/compare/mapquest-vs-radar.md)\n- [MapQuest vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapquest-vs-tomtom.md)\n- [OpenCage Geocoding API vs Radar](https://www.anchorterminal.com/compare/opencage-vs-radar.md)\n- [OpenCage Geocoding API vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/opencage-vs-tomtom.md)\n- [Radar vs Stadia Maps](https://www.anchorterminal.com/compare/radar-vs-stadia-maps.md)\n- [Stadia Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-10",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Radar vs TomTom Maps APIs + MCP",
        "url": ""
      }
    ],
    "description": "TomTom Maps scores 54.9 (C) to Radar's 53.3 (D) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Radar D 53.3",
      "TomTom Maps APIs + MCP C 54.9",
      "scores"
    ],
    "h1": "Radar vs TomTom Maps APIs + MCP",
    "image": "https://www.anchorterminal.com/assets/og/compare-radar-vs-tomtom.png",
    "path": "/compare/radar-vs-tomtom",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Radar vs TomTom Maps for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/radar-vs-tomtom"
  },
  "tokens": {
    "markdown": 2400,
    "slim": 730
  },
  "version": 1
}