{
  "data": {
    "a": {
      "slug": "amazon-location",
      "name": "Amazon Location Service",
      "vendor": "Amazon Web Services",
      "vendorUrl": "https://aws.amazon.com/location/",
      "kind": "http-api",
      "category": "maps",
      "summary": "Amazon Location Service is AWS's API for geocoding, place search, routing and map tiles, with geofences and device tracking. Agents call regional REST endpoints with an API key or IAM credentials, or through the AWS SDKs and CLI.",
      "url": "https://www.anchorterminal.com/tools/amazon-location",
      "markdownUrl": "https://www.anchorterminal.com/tools/amazon-location.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/amazon-location.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/amazon-location.json",
      "repo": "https://github.com/aws-geospatial/amazon-location-agent-context",
      "license": "Proprietary service under the AWS Customer Agreement and AWS Service Terms. The AWS SDK clients and the agent context package on GitHub are Apache-2.0",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://places.geo.us-east-1.amazonaws.com",
      "packages": [
        {
          "registry": "npm",
          "name": "@aws-sdk/client-geo-places"
        },
        {
          "registry": "npm",
          "name": "@aws-sdk/client-geo-routes"
        },
        {
          "registry": "npm",
          "name": "@aws-sdk/client-geo-maps"
        },
        {
          "registry": "pypi",
          "name": "boto3"
        }
      ],
      "auth": "api-key",
      "authNotes": "Access needs an AWS account. Maps, Places and Routes accept an Amazon Location API key in the `key` query parameter, created in the console, the CLI or the `CreateKey` call, limited to named actions and resources, with optional expiry and referrer or mobile app restrictions. Every API also accepts AWS Signature Version 4 with IAM credentials or a role, and Amazon Cognito identity pools for unauthenticated clients. Geofences, trackers and the Jobs API refuse API keys. API keys can't be used over AWS PrivateLink (https://docs.aws.amazon.com/location/latest/developerguide/using-apikeys.html).",
      "pricing": "usage",
      "pricingNotes": "Geocoding, reverse geocoding and place search cost $0.50 per 1,000 requests (core), $1.50 with advanced fields and $4.00 when results are stored, in US East (N. Virginia). Routes cost $0.50 per 1,000 for car, truck or pedestrian, map tiles $0.04 per 1,000. No sandbox or contract is needed, but an AWS account is. The pricing page lists monthly allowances for the first three months (20,000 core Places requests, 10,000 routes, 500,000 tiles) and up to $200 of credits for customers who joined after 15 July 2025. Volume discounts above $5,000 a month are by quote (https://aws.amazon.com/location/pricing/, checked 2026-10-08).",
      "priceSummary": "$0.50 / 1k req",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the developer guide's llms.txt, the service models or the pricing page (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 426988,
        "pypiWeekly": null,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://docs.aws.amazon.com/location/latest/developerguide/what-is.html",
      "llmsTxt": "https://docs.aws.amazon.com/location/latest/developerguide/llms.txt",
      "capabilities": [
        "geo.geocode",
        "geo.reverse",
        "geo.places",
        "geo.routing",
        "geo.tiles"
      ],
      "tags": [
        "hosted",
        "closed-source",
        "python",
        "typescript",
        "enterprise",
        "llms-txt",
        "card-required",
        "sla",
        "status-page",
        "batch"
      ],
      "lastRelease": "2026-08-17",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 74.1,
        "grade": "BB",
        "agentReady": true,
        "rank": 77,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 2,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 88,
          "maintenance": 60,
          "payments": 20,
          "reliability": 95,
          "schema": 87,
          "security": 73,
          "transparency": 70
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "high",
          "date": "2026-10-08"
        },
        "negative": 0,
        "verdict": "Places, Routes and Maps calls work over plain HTTPS with an API key limited to named actions, and every one of the 17 operations is read-only with typed inputs. Access starts with an AWS account a person opens, the key travels in the URL query string, and stored results cost eight times the single-use rate.",
        "bestFor": "Operators already on AWS who want geocoding, places and routing inside IAM, CloudTrail and one bill, with HERE data and GrabMaps for Southeast Asia.",
        "strengths": [
          "API keys are limited to named actions and resources, can expire, and can be restricted by referrer or mobile app identifier",
          "All 17 Places, Routes and Maps operations are marked read-only in the public Smithy models, with enums and numeric ranges on inputs",
          "Default rates are published per operation (100 a second for each Places call, 20 for `CalculateRoutes`) and can be doubled by self-service",
          "An SLA of 99.9 per cent monthly uptime per region, with credits of 10, 25 and 100 per cent",
          "llms.txt, a Markdown twin of every guide page and an Apache-2.0 agent context package (v1.2.0, 11 September 2026)"
        ],
        "weaknesses": [
          "The API key is sent as the `key` query parameter, the only documented way to present it",
          "Storing or caching results is barred unless `IntendedUse` is `Storage`, billed at $4.00 per 1,000 against $0.50 for single use",
          "An AWS account opened by a person in a browser is needed before any call, and no keyless or machine-payment route exists",
          "The developer guide gives no backoff or `Retry-After` guidance for `ThrottlingException` (429)",
          "The guide's document history holds one entry, dated 31 October 2024, so API changes have to be read from the SDK models"
        ],
        "agentNotes": [
          "Call the v2 endpoints (`places.geo.\u003cregion\u003e.amazonaws.com/v2/geocode`, `routes.geo`, `maps.geo`). They need no resource creation, unlike the v1 place index and route calculator calls",
          "Set `IntendedUse` to `Storage` before saving or caching any Places result. The default `SingleUse` results may not be stored under section 82.4 of the AWS Service Terms",
          "Read `PricingBucket` in each response. Requesting `Contact`, `Access`, `TimeZone` or `Phonemes` in `AdditionalFeatures` moves a Places call from $0.50 to $1.50 per 1,000",
          "Keep the API key out of logs and shared URLs, since it travels as `?key=`. Use SigV4 with an IAM role for server-side work, and for the Jobs API, which refuses API keys",
          "Back off on HTTP 429 `ThrottlingException`. The burst allowance is 80 per cent of the per-second rate within any part of a second"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "high",
            "grade": "BB",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 74.1
          }
        ],
        "editorialScores": {
          "ergonomics": 88,
          "maintenance": 60,
          "payments": 20,
          "reliability": 95,
          "schema": 87,
          "security": 73,
          "transparency": 52
        },
        "provenanceScore": 88
      },
      "connect": {
        "install": "pip install boto3   # or: npm i @aws-sdk/client-geo-places",
        "http": "curl --request POST \\\n  --url 'https://places.geo.eu-central-1.amazonaws.com/v2/geocode?key=Your_Key' \\\n  --header 'Content-Type: application/json' \\\n  --data '{\"QueryText\": \"510 W Georgia St, Vancouver, BC\"}'",
        "claudeCode": "/plugin install amazon-location-service@claude-plugins-official"
      },
      "letme": {
        "capability": "https://letme.dev/geo.geocode",
        "tool": "https://letme.dev/amazon-location"
      },
      "sameCompany": [
        "amazon-nova-embeddings",
        "amazon-bedrock-guardrails",
        "amazon-transcribe",
        "amazon-polly",
        "agentcore-memory",
        "agentcore-identity",
        "aws-secrets-manager",
        "aws-mcp-servers",
        "amazon-ses",
        "amazon-translate",
        "amazon-ads-api"
      ],
      "area": "everyday",
      "unitPrices": [
        {
          "item": "Geocode, reverse geocode, place search (core)",
          "unit": "1k-requests",
          "usd": 0.5,
          "note": "US East. `SingleUse` results, not for storage"
        },
        {
          "item": "Geocode, reverse geocode, place search (advanced)",
          "unit": "1k-requests",
          "usd": 1.5,
          "note": "With contacts, opening hours, access points or time zone"
        },
        {
          "item": "Geocode, reverse geocode, place search (stored)",
          "unit": "1k-requests",
          "usd": 4,
          "note": "`IntendedUse` set to `Storage`"
        },
        {
          "item": "Autocomplete and Suggest (label)",
          "unit": "1k-requests",
          "usd": 0.2
        },
        {
          "item": "Routes calculated (core)",
          "unit": "1k-requests",
          "usd": 0.5,
          "note": "Car, truck or pedestrian. A matrix bills origins times destinations"
        },
        {
          "item": "Routes with toll cost (premium)",
          "unit": "1k-requests",
          "usd": 4
        },
        {
          "item": "Dynamic map tiles",
          "unit": "1k-requests",
          "usd": 0.04
        },
        {
          "item": "Static map images",
          "unit": "1k-requests",
          "usd": 0.5
        }
      ],
      "provenance": {
        "legalEntity": "Amazon Web Services, Inc.",
        "domain": "amazon.com",
        "domainRegistered": "1994-11-01",
        "endpointOnVendorDomain": true,
        "terms": "https://aws.amazon.com/service-terms/",
        "privacy": "https://aws.amazon.com/privacy/",
        "statusPage": "https://health.aws.amazon.com/health/status",
        "changelog": "https://docs.aws.amazon.com/location/latest/developerguide/doc-history.html",
        "securityTxt": "expired",
        "checked": "2026-10-08",
        "notes": [
          "The AWS Service Terms (last updated 1 October 2026) govern the service, with Amazon Location Service at section 82. The AWS Customer Agreement sits above them.",
          "The AWS Privacy Notice (last updated 18 May 2026) names Amazon Web Services, Inc., 410 Terry Avenue North, Seattle, WA 98109-5210.",
          "The endpoints are on amazonaws.com and api.aws, both AWS domains.",
          "aws.amazon.com/.well-known/security.txt carries Expires 2026-09-24T16:25:03Z, which had passed on the day of the check. It points to a HackerOne disclosure programme.",
          "RDAP for amazon.com gives a registration date of 1994-11-01.",
          "The document history page has one entry, dated 31 October 2024. API changes are otherwise visible in AWS What's New posts and the SDK service models."
        ],
        "score": 88
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/amazon-location.json",
      "live": {
        "slug": "amazon-location",
        "probe": {
          "target": "https://places.geo.us-east-1.amazonaws.com",
          "method": "get",
          "lastAt": "2026-10-10T01:37:42.077900927Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 269,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 252,
          "p95ms24h": 303,
          "samples24h": 250,
          "samples30d": 317,
          "days": [
            {
              "date": "2026-10-08",
              "probes": 50,
              "ok": 50
            },
            {
              "date": "2026-10-09",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-10",
              "probes": 17,
              "ok": 17
            }
          ]
        },
        "versions": [
          {
            "registry": "github",
            "name": "aws-geospatial/amazon-location-agent-context",
            "version": "v1.2.0",
            "released": "2026-09-11",
            "seenAt": "2026-10-09T16:38:44.131233325Z"
          },
          {
            "registry": "npm",
            "name": "@aws-sdk/client-geo-maps",
            "version": "3.1148.0",
            "seenAt": "2026-10-09T16:38:41.92822938Z"
          },
          {
            "registry": "npm",
            "name": "@aws-sdk/client-geo-places",
            "version": "3.1148.0",
            "seenAt": "2026-10-09T16:38:39.617279624Z"
          },
          {
            "registry": "npm",
            "name": "@aws-sdk/client-geo-routes",
            "version": "3.1148.0",
            "seenAt": "2026-10-09T16:38:40.553611585Z"
          },
          {
            "registry": "pypi",
            "name": "boto3",
            "version": "1.43.110",
            "released": "2026-10-08",
            "seenAt": "2026-10-09T16:38:43.993994547Z"
          }
        ],
        "githubStars": 7,
        "npmWeekly": 350438,
        "pypiWeekly": 577963463,
        "securityTxt": {
          "url": "https://amazon.com/.well-known/security.txt",
          "state": "valid",
          "checkedAt": "2026-10-09T15:39:50.439024529Z"
        },
        "llmsTxt": {
          "url": "https://docs.aws.amazon.com/location/latest/developerguide/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-09T14:01:15.860395575Z"
        },
        "pages": [
          {
            "url": "https://docs.aws.amazon.com/location/latest/developerguide/doc-history.html",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-09T18:36:42.166912963Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "57dff2a88a23"
          },
          {
            "url": "https://aws.amazon.com/location/pricing/",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-09T18:33:03.946049597Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "3ad65fd82f9b"
          }
        ],
        "updatedAt": "2026-10-10T01:37:42.077900927Z"
      }
    },
    "answer": "Amazon Location Service scores 74.1 (BB) on agent readiness against Radar's 53.3 (D), and leads in 6 of 7 scored categories. Radar leads on maintenance \u0026 community.",
    "b": {
      "slug": "radar",
      "name": "Radar",
      "vendor": "Radar Labs",
      "vendorUrl": "https://radar.com",
      "kind": "http-api",
      "category": "maps",
      "summary": "Radar is a location platform from Radar Labs with REST APIs for forward, reverse and IP geocoding, address autocomplete and validation, places search, distance, matrix, directions and route optimisation, plus geofencing, trip tracking and base maps.",
      "url": "https://www.anchorterminal.com/tools/radar",
      "markdownUrl": "https://www.anchorterminal.com/tools/radar.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/radar.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/radar.json",
      "repo": "https://github.com/radarlabs/radar-sdk-js",
      "license": "Proprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.radar.io/v1",
      "packages": [
        {
          "registry": "npm",
          "name": "radar-sdk-js"
        }
      ],
      "auth": "api-key",
      "authNotes": "API key in the `Authorization` header, with no query-string option documented. Each project has four keys, test and live, publishable and secret. Publishable keys reach 16 of the 36 documented operations, including all geocoding, search and routing calls, and can be restricted by website domain or mobile app identifier. Secret keys reach the rest and can read or write any data. Keys come from the dashboard. Whether sign-up is self-serve was not established, because dashboard.radar.com's robots.txt closes every path.",
      "pricing": "paid",
      "pricingNotes": "Core Maps (forward, reverse and IP geocoding, autocomplete, static maps, distance, directions, matrix) starts at $0.50 per 1,000 API calls and Premium Maps (address validation, places search, route matching, route optimisation, satellite maps) at $2.00. Matrix bills per element. Every plan is an annual commitment with a monthly quota, at a rate Radar sets by quote. The pricing page says there is no free tier, and that teams can start with a technical validation period arranged with sales (https://radar.com/pricing).",
      "priceSummary": "$0.50 / 1k req",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the API reference, the docs index or the pricing page (checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://docs.radar.com/api",
      "llmsTxt": "https://docs.radar.com/llms.txt",
      "capabilities": [
        "geo.geocode",
        "geo.reverse",
        "geo.places",
        "geo.routing",
        "geo.tiles"
      ],
      "tags": [
        "hosted",
        "api-key",
        "llms-txt",
        "status-page",
        "sales-led",
        "annual-contract",
        "soc2",
        "closed-source"
      ],
      "lastRelease": "2026-09-14",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 53.3,
        "grade": "D",
        "agentReady": false,
        "rank": 713,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 12,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 65,
          "maintenance": 77,
          "payments": 10,
          "reliability": 70,
          "schema": 50,
          "security": 56,
          "transparency": 55
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": -2,
        "negativeNotes": [
          "9 October 2026. The Maps product page says the geocoding APIs come with 'the right to store, reuse, and export results freely' (https://radar.com/product/maps), while section 2(d) of the Terms of Use forbids storing address or point-of-interest data from the geocoding, autocomplete or place search APIs for more than 30 days (https://radar.com/terms) and the geocoding docs repeat the 30-day limit (https://docs.radar.com/maps/geocoding.md). 2 points for a claim the published terms contradict. A quoted enterprise agreement may differ and is not published."
        ],
        "verdict": "Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found.",
        "bestFor": "A company that already has a Radar contract, or wants geofencing and trip tracking with geocoding and routing on one key.",
        "strengths": [
          "Each of the 36 documented operations states its key level and a default rate limit, from 10 to 100 requests a second",
          "docs.radar.com publishes llms.txt and a Markdown twin of every page, including the whole API reference in one file",
          "Statuspage history lists two API incidents in the 90 days to 9 October 2026, of 3 minutes and about an hour",
          "Publishable keys are limited to 16 client-safe operations and can be restricted by website domain or mobile app identifier",
          "The DPA names two sub-processors (AWS and MongoDB) and the FAQ states default retention periods"
        ],
        "weaknesses": [
          "The pricing page says Radar has no free tier and every plan is an annual commitment set by quote",
          "No OpenAPI description and no API changelog were found in the docs index",
          "The terms cap storage of geocoding, autocomplete and place results at 30 days, while the Maps product page claims a right to store results freely",
          "The terms of 24 May 2023 let Radar change or stop the services without notice, and still describe a free version",
          "A secret key can read or write any project data, with no scopes found",
          "The terms forbid using the services to develop or test other geocoding, autocomplete or place search APIs, which matters before any probe is run"
        ],
        "agentNotes": [
          "Send the key in the `Authorization` header with no `Bearer` prefix, and call `https://api.radar.io/v1`, not radar.com",
          "Use a publishable key for geocoding, search and routing. Keep the secret key for users, trips, geofences and beacons",
          "Call `/v1/search/autocomplete` for partial addresses and place names. `/v1/geocode/forward` is documented as best for complete addresses",
          "Set `units=metric` on routing calls. The default is imperial, with distances in feet",
          "Treat 429 as one of three things (rate limit, no state change or selective throttling) and 402 as usage exceeded. No Retry-After header is documented",
          "Do not keep geocoding, autocomplete or place results for more than 30 days"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "D",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 53.3
          }
        ],
        "editorialScores": {
          "ergonomics": 65,
          "maintenance": 77,
          "payments": 10,
          "reliability": 70,
          "schema": 50,
          "security": 56,
          "transparency": 51
        },
        "provenanceScore": 58
      },
      "connect": {
        "install": "npm install radar-sdk-js",
        "http": "curl \"https://api.radar.io/v1/geocode/forward?query=20+jay+st+brooklyn+ny\" -H \"Authorization: $RADAR_PUBLISHABLE_KEY\""
      },
      "letme": {
        "capability": "https://letme.dev/geo.geocode",
        "tool": "https://letme.dev/radar"
      },
      "area": "everyday",
      "unitPrices": [
        {
          "item": "Core Maps API calls, starting price",
          "unit": "1k-requests",
          "usd": 0.5,
          "note": "Geocoding, autocomplete, static maps, distance, directions, matrix (per element). Annual commitment, rate set by quote"
        },
        {
          "item": "Premium Maps API calls, starting price",
          "unit": "1k-requests",
          "usd": 2,
          "note": "Address validation, places search, route matching, route optimisation, satellite maps. Annual commitment, rate set by quote"
        }
      ],
      "provenance": {
        "legalEntity": "Radar Labs, Inc.",
        "domain": "radar.com",
        "domainRegistered": "1994-12-16",
        "endpointOnVendorDomain": false,
        "terms": "https://radar.com/terms",
        "privacy": "https://radar.com/privacy",
        "statusPage": "https://status.radar.com",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-10-09",
        "notes": [
          "The privacy notice (last updated 13 May 2025) names Radar Labs, Inc., a Delaware corporation at 111 5th Ave, 12th Floor, New York, NY 10003.",
          "The Terms of Use (last updated 24 May 2023) cover the SDK and Radar's APIs and incorporate the DPA at radar.com/dpa. They describe a free version, which the pricing page says Radar does not have. Paid plans are by quote, and no enterprise agreement is published.",
          "The API answers at api.radar.io, a second domain. Nothing was sent to it, and its registrant was not checked.",
          "radar.com/.well-known/security.txt answers 404. The FAQ gives security@radar.com for reports.",
          "No API changelog was found in the docs index. The web SDK repository has dated release tags.",
          "RDAP gives 16 December 1994 as the registration date of radar.com.",
          "robots.txt answers on the day. radar.com 200 with a sitemap line only. docs.radar.com 200 with ai-input=yes. status.radar.com 200 disallowing /api/ and /embed/. dashboard.radar.com 200 disallowing every path. trust.radar.com answers the request with its page shell."
        ],
        "score": 58
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/radar.json",
      "live": {
        "slug": "radar",
        "probe": {
          "target": "https://api.radar.io/v1",
          "method": "get",
          "lastAt": "2026-10-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"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Amazon Web Services",
        "b": "Radar Labs",
        "name": "Vendor"
      },
      {
        "a": "https://places.geo.us-east-1.amazonaws.com",
        "b": "https://api.radar.io/v1",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "$0.50 per 1,000 requests",
        "b": "not published",
        "name": "Price for geocoding"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under the AWS Customer Agreement and AWS Service Terms. The AWS SDK clients and the agent context package on GitHub are Apache-2.0",
        "b": "Proprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-08-17",
        "b": "2026-09-14",
        "name": "Last release"
      },
      {
        "a": "2026-10-01",
        "b": "2023-05-24",
        "name": "Terms last updated"
      },
      {
        "a": "2026-05-18",
        "b": "2025-05-13",
        "name": "Privacy policy last updated"
      },
      {
        "a": "yes, with an opt-out",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "427k npm/wk",
        "b": "none",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Amazon Location Service scores 74.1 (BB) on agent readiness against Radar's 53.3 (D), and leads in 6 of 7 scored categories. Radar leads on maintenance \u0026 community.",
        "question": "Which is better for AI agents, Amazon Location Service or Radar?"
      },
      {
        "answer": "Both need an API key.",
        "question": "Do Amazon Location Service and Radar need an API key?"
      },
      {
        "answer": "Yes. Amazon Location Service has a hosted endpoint at https://places.geo.us-east-1.amazonaws.com and Radar at https://api.radar.io/v1.",
        "question": "Can an agent call Amazon Location Service and Radar without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 95 against 70",
          "Schema \u0026 documentation, 87 against 50",
          "Agent ergonomics, 88 against 65",
          "Security \u0026 auth, 73 against 56",
          "Payments \u0026 pricing, 20 against 10",
          "Transparency \u0026 trust, 70 against 55"
        ],
        "also": [
          "Agent-ready, a grade of BB or better"
        ],
        "goodFor": "Operators already on AWS who want geocoding, places and routing inside IAM, CloudTrail and one bill, with HERE data and GrabMaps for Southeast Asia.",
        "slug": "amazon-location",
        "watchFor": "The API key is sent as the `key` query parameter, the only documented way to present it"
      },
      {
        "aheadOn": [
          "Maintenance \u0026 community, 77 against 60"
        ],
        "also": null,
        "goodFor": "A company that already has a Radar contract, or wants geofencing and trip tracking with geocoding and routing on one key.",
        "slug": "radar",
        "watchFor": "The pricing page says Radar has no free tier and every plan is an annual commitment set by quote"
      }
    ],
    "job": {
      "capability": "geo.geocode",
      "name": "Geocoding"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/amazon-location-vs-arcgis.json",
        "title": "Amazon Location Service vs ArcGIS Location Platform",
        "url": "https://www.anchorterminal.com/compare/amazon-location-vs-arcgis"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps.json",
        "title": "Amazon Location Service vs Azure Maps",
        "url": "https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amazon-location-vs-geoapify.json",
        "title": "Amazon Location Service vs Geoapify Location Platform + MCP",
        "url": "https://www.anchorterminal.com/compare/amazon-location-vs-geoapify"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amazon-location-vs-google-maps-platform.json",
        "title": "Amazon Location Service vs Google Maps Platform + Grounding Lite MCP",
        "url": "https://www.anchorterminal.com/compare/amazon-location-vs-google-maps-platform"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.json",
        "title": "Amazon Location Service vs HERE Location Services",
        "url": "https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amazon-location-vs-locationiq.json",
        "title": "Amazon Location Service vs LocationIQ",
        "url": "https://www.anchorterminal.com/compare/amazon-location-vs-locationiq"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amazon-location-vs-mapbox.json",
        "title": "Amazon Location Service vs Mapbox APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/amazon-location-vs-mapbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amazon-location-vs-mapquest.json",
        "title": "Amazon Location Service vs MapQuest",
        "url": "https://www.anchorterminal.com/compare/amazon-location-vs-mapquest"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amazon-location-vs-opencage.json",
        "title": "Amazon Location Service vs OpenCage Geocoding API",
        "url": "https://www.anchorterminal.com/compare/amazon-location-vs-opencage"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.json",
        "title": "Amazon Location Service vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps"
      },
      {
        "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/azure-maps-vs-radar.json",
        "title": "Azure Maps vs Radar",
        "url": "https://www.anchorterminal.com/compare/azure-maps-vs-radar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/geoapify-vs-radar.json",
        "title": "Geoapify Location Platform + MCP vs Radar",
        "url": "https://www.anchorterminal.com/compare/geoapify-vs-radar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-radar.json",
        "title": "Google Maps Platform + Grounding Lite MCP vs Radar",
        "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-radar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/here-location-services-vs-radar.json",
        "title": "HERE Location Services vs Radar",
        "url": "https://www.anchorterminal.com/compare/here-location-services-vs-radar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/locationiq-vs-radar.json",
        "title": "LocationIQ vs Radar",
        "url": "https://www.anchorterminal.com/compare/locationiq-vs-radar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mapbox-vs-radar.json",
        "title": "Mapbox APIs + MCP vs Radar",
        "url": "https://www.anchorterminal.com/compare/mapbox-vs-radar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mapquest-vs-radar.json",
        "title": "MapQuest vs Radar",
        "url": "https://www.anchorterminal.com/compare/mapquest-vs-radar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/opencage-vs-radar.json",
        "title": "OpenCage Geocoding API vs Radar",
        "url": "https://www.anchorterminal.com/compare/opencage-vs-radar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/radar-vs-stadia-maps.json",
        "title": "Radar vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/radar-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/radar-vs-tomtom.json",
        "title": "Radar vs TomTom Maps APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/radar-vs-tomtom"
      }
    ],
    "scores": [
      {
        "amazon-location": 95,
        "by": 25,
        "edge": "amazon-location",
        "key": "reliability",
        "name": "Reliability",
        "radar": 70,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "amazon-location": 87,
        "by": 37,
        "edge": "amazon-location",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "radar": 50,
        "weight": 13
      },
      {
        "amazon-location": 88,
        "by": 23,
        "edge": "amazon-location",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "radar": 65,
        "weight": 13
      },
      {
        "amazon-location": 73,
        "by": 17,
        "edge": "amazon-location",
        "key": "security",
        "name": "Security \u0026 auth",
        "radar": 56,
        "weight": 14
      },
      {
        "amazon-location": 20,
        "by": 10,
        "edge": "amazon-location",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "radar": 10,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "amazon-location": 60,
        "by": 17,
        "edge": "radar",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "radar": 77,
        "weight": 7
      },
      {
        "amazon-location": 70,
        "by": 15,
        "edge": "amazon-location",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "radar": 55,
        "weight": 7
      }
    ],
    "summary": "Amazon Location Service scores 74.1 (BB) on agent readiness against Radar's 53.3 (D), and leads in 6 of 7 scored categories. Radar leads on maintenance \u0026 community. Both do geocoding.",
    "verdicts": {
      "amazon-location": "Places, Routes and Maps calls work over plain HTTPS with an API key limited to named actions, and every one of the 17 operations is read-only with typed inputs. Access starts with an AWS account a person opens, the key travels in the URL query string, and stored results cost eight times the single-use rate.",
      "radar": "Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/amazon-location-vs-radar",
    "json": "https://www.anchorterminal.com/compare/amazon-location-vs-radar.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/amazon-location-vs-radar.md",
    "slim": "https://www.anchorterminal.com/compare/amazon-location-vs-radar.min.md"
  },
  "markdown": "Amazon Location Service scores 74.1 (BB) on agent readiness against Radar's 53.3 (D), and leads in 6 of 7 scored categories. Radar leads on maintenance \u0026 community. Both do geocoding.\n\n- Amazon Location Service: grade BB, 74.1/100, rank #77 of 950. Markdown https://www.anchorterminal.com/tools/amazon-location.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-location.json\n- Radar: grade D, 53.3/100, rank #713 of 950. Markdown https://www.anchorterminal.com/tools/radar.md · JSON https://www.anchorterminal.com/api/v1/tools/radar.json\n- Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md\n- All 78 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md\n\n## Which one, for what\n\n### Amazon Location Service (BB)\n\nGood for: Operators already on AWS who want geocoding, places and routing inside IAM, CloudTrail and one bill, with HERE data and GrabMaps for Southeast Asia.\n\nAhead on:\n- Reliability, 95 against 70\n- Schema \u0026 documentation, 87 against 50\n- Agent ergonomics, 88 against 65\n- Security \u0026 auth, 73 against 56\n- Payments \u0026 pricing, 20 against 10\n- Transparency \u0026 trust, 70 against 55\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: The API key is sent as the `key` query parameter, the only documented way to present it\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- Maintenance \u0026 community, 77 against 60\n\nWatch for: The pricing page says Radar has no free tier and every plan is an annual commitment set by quote\n\n\n## Score by category\n\n| Category | Weight | Amazon Location Service | Radar | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 95 | 70 | Amazon Location Service +25 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 50 | Amazon Location Service +37 |\n| Agent ergonomics | 13% (16.2 this run) | 88 | 65 | Amazon Location Service +23 |\n| Security \u0026 auth | 14% (17.5 this run) | 73 | 56 | Amazon Location Service +17 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 10 | Amazon Location Service +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 77 | Radar +17 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 55 | Amazon Location Service +15 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **74.1 · BB** | **53.3 · D** | |\n\n## Facts side by side\n\n| Fact | Amazon Location Service | Radar |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Radar Labs |\n| Hosted endpoint | `https://places.geo.us-east-1.amazonaws.com` | `https://api.radar.io/v1` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Paid |\n| Price for geocoding | $0.50 per 1,000 requests | not published |\n| x402 | no | no |\n| Licence | Proprietary service under the AWS Customer Agreement and AWS Service Terms. The AWS SDK clients and the agent context package on GitHub are Apache-2.0 | Proprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| Last release | 2026-08-17 | 2026-09-14 |\n| Terms last updated | 2026-10-01 | 2023-05-24 |\n| Privacy policy last updated | 2026-05-18 | 2025-05-13 |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 427k npm/wk | none |\n\n## Verdicts\n\n**Amazon Location Service.** Places, Routes and Maps calls work over plain HTTPS with an API key limited to named actions, and every one of the 17 operations is read-only with typed inputs. Access starts with an AWS account a person opens, the key travels in the URL query string, and stored results cost eight times the single-use rate.\n\n**Radar.** Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found.\n\n## Before you call either\n\n### Amazon Location Service\n\n1. Call the v2 endpoints (`places.geo.\u003cregion\u003e.amazonaws.com/v2/geocode`, `routes.geo`, `maps.geo`). They need no resource creation, unlike the v1 place index and route calculator calls\n2. Set `IntendedUse` to `Storage` before saving or caching any Places result. The default `SingleUse` results may not be stored under section 82.4 of the AWS Service Terms\n3. Read `PricingBucket` in each response. Requesting `Contact`, `Access`, `TimeZone` or `Phonemes` in `AdditionalFeatures` moves a Places call from $0.50 to $1.50 per 1,000\n4. Keep the API key out of logs and shared URLs, since it travels as `?key=`. Use SigV4 with an IAM role for server-side work, and for the Jobs API, which refuses API keys\n5. Back off on HTTP 429 `ThrottlingException`. The burst allowance is 80 per cent of the per-second rate within any part of a second\n\n### Radar\n\n1. Send the key in the `Authorization` header with no `Bearer` prefix, and call `https://api.radar.io/v1`, not radar.com\n2. Use a publishable key for geocoding, search and routing. Keep the secret key for users, trips, geofences and beacons\n3. Call `/v1/search/autocomplete` for partial addresses and place names. `/v1/geocode/forward` is documented as best for complete addresses\n4. Set `units=metric` on routing calls. The default is imperial, with distances in feet\n5. Treat 429 as one of three things (rate limit, no state change or selective throttling) and 402 as usage exceeded. No Retry-After header is documented\n6. Do not keep geocoding, autocomplete or place results for more than 30 days\n\n## Questions\n\n### Which is better for AI agents, Amazon Location Service or Radar?\n\nAmazon Location Service scores 74.1 (BB) on agent readiness against Radar's 53.3 (D), and leads in 6 of 7 scored categories. Radar leads on maintenance \u0026 community.\n\n### Do Amazon Location Service and Radar need an API key?\n\nBoth need an API key.\n\n### Can an agent call Amazon Location Service and Radar without installing anything?\n\nYes. Amazon Location Service has a hosted endpoint at https://places.geo.us-east-1.amazonaws.com and Radar at https://api.radar.io/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-location-vs-radar.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-location-vs-radar.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-location\", \"b\": \"radar\"}`. From a terminal: `anchor compare amazon-location radar`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-location.json and https://www.anchorterminal.com/api/v1/tools/radar.json\n\n## Other comparisons with Amazon Location Service or Radar\n\n- [Amazon Location Service vs ArcGIS Location Platform](https://www.anchorterminal.com/compare/amazon-location-vs-arcgis.md)\n- [Amazon Location Service vs Azure Maps](https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps.md)\n- [Amazon Location Service vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-geoapify.md)\n- [Amazon Location Service vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/amazon-location-vs-google-maps-platform.md)\n- [Amazon Location Service vs HERE Location Services](https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.md)\n- [Amazon Location Service vs LocationIQ](https://www.anchorterminal.com/compare/amazon-location-vs-locationiq.md)\n- [Amazon Location Service vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-mapbox.md)\n- [Amazon Location Service vs MapQuest](https://www.anchorterminal.com/compare/amazon-location-vs-mapquest.md)\n- [Amazon Location Service vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/amazon-location-vs-opencage.md)\n- [Amazon Location Service vs Stadia Maps](https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.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- [Azure Maps vs Radar](https://www.anchorterminal.com/compare/azure-maps-vs-radar.md)\n- [Geoapify Location Platform + MCP vs Radar](https://www.anchorterminal.com/compare/geoapify-vs-radar.md)\n- [Google Maps Platform + Grounding Lite MCP vs Radar](https://www.anchorterminal.com/compare/google-maps-platform-vs-radar.md)\n- [HERE Location Services vs Radar](https://www.anchorterminal.com/compare/here-location-services-vs-radar.md)\n- [LocationIQ vs Radar](https://www.anchorterminal.com/compare/locationiq-vs-radar.md)\n- [Mapbox APIs + MCP vs Radar](https://www.anchorterminal.com/compare/mapbox-vs-radar.md)\n- [MapQuest vs Radar](https://www.anchorterminal.com/compare/mapquest-vs-radar.md)\n- [OpenCage Geocoding API vs Radar](https://www.anchorterminal.com/compare/opencage-vs-radar.md)\n- [Radar vs Stadia Maps](https://www.anchorterminal.com/compare/radar-vs-stadia-maps.md)\n- [Radar vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/radar-vs-tomtom.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-10",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Amazon Location Service vs Radar",
        "url": ""
      }
    ],
    "description": "Amazon Location Service scores 74.1 (BB) to Radar's 53.3 (D) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Amazon Location Service BB 74.1",
      "Radar D 53.3",
      "scores"
    ],
    "h1": "Amazon Location Service vs Radar",
    "image": "https://www.anchorterminal.com/assets/og/compare-amazon-location-vs-radar.png",
    "path": "/compare/amazon-location-vs-radar",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Amazon Location Service vs Radar for AI agents (2026)",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/amazon-location-vs-radar"
  },
  "tokens": {
    "markdown": 2600,
    "slim": 730
  },
  "version": 1
}