{
  "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": 68,
        "ranked": true,
        "rankOf": 722,
        "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-bedrock-guardrails",
        "amazon-transcribe",
        "amazon-polly",
        "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-08T21:12:03.434350122Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 239,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 253,
          "p95ms24h": 307,
          "samples24h": 21,
          "samples30d": 21,
          "days": [
            {
              "date": "2026-10-08",
              "probes": 21,
              "ok": 21
            }
          ]
        },
        "updatedAt": "2026-10-08T21:12:03.434350122Z"
      }
    },
    "answer": "Amazon Location Service scores 74.1 (BB) on agent readiness against Stadia Maps's 65.2 (B), and leads in 4 of 7 scored categories. Stadia Maps leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.",
    "b": {
      "slug": "stadia-maps",
      "name": "Stadia Maps",
      "vendor": "Stadia Maps",
      "vendorUrl": "https://stadiamaps.com",
      "kind": "http-api",
      "category": "maps",
      "summary": "Geocoding, reverse geocoding, autocomplete and place details, routing, matrix, isochrones, static maps and hosted vector, raster and satellite tiles, sold in credits on plans from $20 a month.",
      "url": "https://www.anchorterminal.com/tools/stadia-maps",
      "markdownUrl": "https://www.anchorterminal.com/tools/stadia-maps.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/stadia-maps.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/stadia-maps.json",
      "repo": "https://github.com/stadiamaps/stadiamaps-mcp-server-ts",
      "license": "BSD-3-Clause (MCP server)",
      "transports": [
        "http",
        "stdio"
      ],
      "remoteUrl": "https://api.stadiamaps.com",
      "packages": [
        {
          "registry": "npm",
          "name": "@stadiamaps/api"
        },
        {
          "registry": "pypi",
          "name": "stadiamaps"
        }
      ],
      "auth": "api-key",
      "authNotes": "API key as the api_key query parameter or in an `Authorization: Stadia-Auth \u003ckey\u003e` header. Browser apps can use domain-based auth with no key, checked against the Origin and Referer headers. The MCP server reads API_KEY.",
      "pricing": "freemium",
      "pricingNotes": "Free 200,000 credits a month for development, testing and demos only, no commercial use. Starter $20 a month (1 million credits), Standard $80 (7.5 million), Professional $250 (25 million), with overage at $0.03, $0.02 and $0.015 per 1,000 credits. A forward, reverse or structured geocode, a place lookup, an Autocomplete v1 search or a route is 20 credits, Autocomplete v2 is 1, a matrix element 10, a map tile 1 and a satellite tile 4, so Starter covers 50,000 geocodes. New accounts get a 14-day Professional trial with no card (https://stadiamaps.com/pricing/). When credits run out you get 429 until the next cycle unless pay-as-you-go is on (https://stadiamaps.com/faqs/).",
      "priceSummary": "$20 / mo",
      "where": "both",
      "x402": {
        "level": "no",
        "endpoints": []
      },
      "toolCount": 6,
      "popularity": {
        "githubStars": 23,
        "npmWeekly": 6058,
        "pypiWeekly": 192,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://docs.stadiamaps.com",
      "llmsTxt": "https://docs.stadiamaps.com/llms.txt",
      "openapi": "https://api.stadiamaps.com/openapi.yaml",
      "capabilities": [
        "geo.geocode",
        "geo.reverse",
        "geo.places",
        "geo.routing",
        "geo.tiles"
      ],
      "tags": [
        "hosted",
        "mcp",
        "llms-txt",
        "official",
        "typescript",
        "python",
        "free-tier",
        "no-card",
        "open-data"
      ],
      "lastRelease": "2026-09-30",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 65.2,
        "grade": "B",
        "agentReady": false,
        "rank": 261,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 7,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 80,
          "maintenance": 80,
          "payments": 40,
          "reliability": 63,
          "schema": 86,
          "security": 40,
          "transparency": 76
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-01"
        },
        "negative": 0,
        "verdict": "Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only.",
        "bestFor": "Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.",
        "strengths": [
          "Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs",
          "Published credit costs, with 50,000 geocodes for $20 a month on Starter",
          "Header auth keeps the key out of URLs, and keys rotate through an API",
          "Server logs kept about 7 to 14 days, and a DPA",
          "14 dated changelog entries between June and September 2026"
        ],
        "weaknesses": [
          "Free plan is for development, testing and demos only",
          "The same 429 signals a burst or a spent month of credits, with no Retry-After",
          "No SLA, no security.txt and no disclosure policy found",
          "MCP server has no release, no CI and no commits since 29 July 2025",
          "The terms forbid benchmarking against competitors without written permission"
        ],
        "agentNotes": [
          "Send the key as `Authorization: Stadia-Auth \u003ckey\u003e` rather than in the URL",
          "Try Autocomplete v2 (1 credit) before a full geocode (20 credits) when a name is enough",
          "Check the dashboard's credit balance before retrying a 429, since it may mean the month is spent",
          "Don't write geocodes to a database on Free or Starter",
          "Use bulk-geocode for addresses only, not POI names"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 65.2
          }
        ],
        "editorialScores": {
          "ergonomics": 80,
          "maintenance": 80,
          "payments": 40,
          "reliability": 63,
          "schema": 86,
          "security": 40,
          "transparency": 72
        },
        "provenanceScore": 79
      },
      "connect": {
        "http": "curl -H \"Authorization: Stadia-Auth $STADIA_API_KEY\" \"https://api.stadiamaps.com/geocoding/v1/search?text=10%20Downing%20Street%2C%20London\u0026size=1\""
      },
      "letme": {
        "capability": "https://letme.dev/geo.geocode",
        "tool": "https://letme.dev/stadia-maps"
      },
      "area": "everyday",
      "unitPrices": [
        {
          "item": "Starter plan",
          "unit": "month",
          "usd": 20,
          "note": "1 million credits, about 50,000 geocodes"
        },
        {
          "item": "Standard plan",
          "unit": "month",
          "usd": 80,
          "note": "7.5 million credits, permanent geocode storage"
        },
        {
          "item": "Professional plan",
          "unit": "month",
          "usd": 250,
          "note": "25 million credits"
        },
        {
          "item": "Geocoding within Starter",
          "unit": "1k-requests",
          "usd": 0.4,
          "note": "20 credits each, $20 for 1 million credits"
        },
        {
          "item": "Geocoding overage on Starter",
          "unit": "1k-requests",
          "usd": 0.6,
          "note": "20 credits each at $0.03 per 1,000 credits"
        }
      ],
      "provenance": {
        "legalEntity": "Stadia Maps, Inc.",
        "domain": "stadiamaps.com",
        "domainRegistered": "2016-11-30",
        "endpointOnVendorDomain": true,
        "terms": "https://stadiamaps.com/terms-of-service/",
        "privacy": "https://stadiamaps.com/privacy/privacy-policy/",
        "statusPage": "https://status.stadiamaps.com",
        "changelog": "https://stadiamaps.com/changelog/",
        "securityTxt": "none",
        "checked": "2026-09-30",
        "notes": [
          "The terms name Stadia Maps, Inc., a Delaware corporation with an address in East Lansing, Michigan, under Delaware law. Last updated 18 March 2026.",
          "Pages showing Traffic Products must carry \"© Stadia Maps © TomTom\".",
          "stadiamaps.com/.well-known/security.txt returns 404."
        ],
        "score": 79
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/stadia-maps.json",
      "live": {
        "slug": "stadia-maps",
        "probe": {
          "target": "https://api.stadiamaps.com",
          "method": "get",
          "lastAt": "2026-10-08T21:12:22.425544464Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 44,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 44,
          "p95ms24h": 77,
          "samples24h": 271,
          "samples30d": 1955,
          "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": 239,
              "ok": 239
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.stadiamaps.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-08T19:39:13.675830614Z"
        },
        "versions": [
          {
            "registry": "npm",
            "name": "@stadiamaps/api",
            "version": "9.1.0",
            "seenAt": "2026-10-08T16:30:17.728868157Z"
          },
          {
            "registry": "pypi",
            "name": "stadiamaps",
            "version": "8.1.0",
            "released": "2026-04-27",
            "seenAt": "2026-10-08T16:30:18.529642748Z"
          }
        ],
        "githubStars": 23,
        "npmWeekly": 7449,
        "pypiWeekly": 272,
        "securityTxt": {
          "url": "https://stadiamaps.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-08T15:38:41.547092705Z"
        },
        "llmsTxt": {
          "url": "https://docs.stadiamaps.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-08T14:00:54.676650391Z"
        },
        "domain": {
          "domain": "stadiamaps.com",
          "registered": "2016-11-30",
          "source": "https://rdap.verisign.com/com/v1/domain/stadiamaps.com",
          "checkedAt": "2026-10-04T13:06:24.947269949Z"
        },
        "pages": [
          {
            "url": "https://stadiamaps.com/changelog/",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-08T18:24:45.357903234Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "fb379c6fd6fb"
          },
          {
            "url": "https://stadiamaps.com/pricing/",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-08T18:24:47.445598266Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "aeba9483f45f"
          },
          {
            "url": "https://stadiamaps.com/privacy/privacy-policy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-08T18:24:49.394695387Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "22f042b735db"
          },
          {
            "url": "https://stadiamaps.com/terms-of-service/",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-08T18:24:51.381996532Z",
            "changedAt": "2026-10-08T18:24:51.381996532Z",
            "fingerprint": "44e2e273da24"
          }
        ],
        "updatedAt": "2026-10-08T21:12:22.425544464Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Amazon Web Services",
        "b": "Stadia Maps",
        "name": "Vendor"
      },
      {
        "a": "https://places.geo.us-east-1.amazonaws.com",
        "b": "https://api.stadiamaps.com",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "$0.50 per 1,000 requests",
        "b": "$0.40 per 1,000 requests",
        "name": "Price for geo geocode"
      },
      {
        "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": "BSD-3-Clause (MCP server)",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "6",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-08-17",
        "b": "2026-09-30",
        "name": "Last release"
      },
      {
        "a": "2026-10-01",
        "b": "2026-03-18",
        "name": "Terms last updated"
      },
      {
        "a": "2026-05-18",
        "b": "2026-10-01",
        "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": "yes",
        "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": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "427k npm/wk",
        "b": "23 stars, 6.1k npm/wk, 192 PyPI/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3.5/5 (2)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Amazon Location Service scores 74.1 (BB) on agent readiness against Stadia Maps's 65.2 (B), and leads in 4 of 7 scored categories. Stadia Maps leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.",
        "question": "Which is better for AI agents, Amazon Location Service or Stadia Maps?"
      },
      {
        "answer": "Stadia Maps, at $0.40 per 1,000 requests against $0.50 per 1,000 requests for Amazon Location Service. These are the vendors' published prices for the job.",
        "question": "Which is cheaper for geo geocode, Amazon Location Service or Stadia Maps?"
      },
      {
        "answer": "Both need an API key.",
        "question": "Do Amazon Location Service and Stadia Maps need an API key?"
      },
      {
        "answer": "Yes. Amazon Location Service has a hosted endpoint at https://places.geo.us-east-1.amazonaws.com and Stadia Maps at https://api.stadiamaps.com.",
        "question": "Can an agent call Amazon Location Service and Stadia Maps without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 95 against 63",
          "Agent ergonomics, 88 against 80",
          "Security \u0026 auth, 73 against 40"
        ],
        "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": [
          "Payments \u0026 pricing, 40 against 20",
          "Maintenance \u0026 community, 80 against 60",
          "Transparency \u0026 trust, 76 against 70"
        ],
        "also": [
          "Cheaper for geo geocode, $0.40 against $0.50 per 1,000 requests",
          "Runs on your own machine",
          "Free to start without a card"
        ],
        "goodFor": "Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.",
        "slug": "stadia-maps",
        "watchFor": "Free plan is for development, testing and demos only"
      }
    ],
    "job": {
      "capability": "geo.geocode",
      "name": "Geo geocode"
    },
    "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-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-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-stadia-maps.json",
        "title": "ArcGIS Location Platform vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps.json",
        "title": "Azure Maps vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps.json",
        "title": "Geoapify Location Platform + MCP vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps.json",
        "title": "Google Maps Platform + Grounding Lite MCP vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps.json",
        "title": "LocationIQ vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps.json",
        "title": "Mapbox APIs + MCP vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.json",
        "title": "MapQuest vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/opencage-vs-stadia-maps.json",
        "title": "OpenCage Geocoding API vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/opencage-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": [
      {
        "amazon-location": 95,
        "by": 32,
        "edge": "amazon-location",
        "key": "reliability",
        "name": "Reliability",
        "stadia-maps": 63,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "amazon-location": 87,
        "by": 1,
        "edge": "amazon-location",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "stadia-maps": 86,
        "weight": 13
      },
      {
        "amazon-location": 88,
        "by": 8,
        "edge": "amazon-location",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "stadia-maps": 80,
        "weight": 13
      },
      {
        "amazon-location": 73,
        "by": 33,
        "edge": "amazon-location",
        "key": "security",
        "name": "Security \u0026 auth",
        "stadia-maps": 40,
        "weight": 14
      },
      {
        "amazon-location": 20,
        "by": 20,
        "edge": "stadia-maps",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "stadia-maps": 40,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "amazon-location": 60,
        "by": 20,
        "edge": "stadia-maps",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "stadia-maps": 80,
        "weight": 7
      },
      {
        "amazon-location": 70,
        "by": 6,
        "edge": "stadia-maps",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "stadia-maps": 76,
        "weight": 7
      }
    ],
    "summary": "Amazon Location Service scores 74.1 (BB) on agent readiness against Stadia Maps's 65.2 (B), and leads in 4 of 7 scored categories. Stadia Maps leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. Both do geo geocode. Stadia Maps is cheaper for geo geocode, $0.40 against $0.50 per 1,000 requests.",
    "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.",
      "stadia-maps": "Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps",
    "json": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.md",
    "slim": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.min.md"
  },
  "markdown": "Amazon Location Service scores 74.1 (BB) on agent readiness against Stadia Maps's 65.2 (B), and leads in 4 of 7 scored categories. Stadia Maps leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. Both do geo geocode. Stadia Maps is cheaper for geo geocode, $0.40 against $0.50 per 1,000 requests.\n\n- Amazon Location Service: grade BB, 74.1/100, rank #68 of 722. Markdown https://www.anchorterminal.com/tools/amazon-location.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-location.json\n- Stadia Maps: grade B, 65.2/100, rank #261 of 722. Markdown https://www.anchorterminal.com/tools/stadia-maps.md · JSON https://www.anchorterminal.com/api/v1/tools/stadia-maps.json\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 63\n- Agent ergonomics, 88 against 80\n- Security \u0026 auth, 73 against 40\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### Stadia Maps (B)\n\nGood for: Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 20\n- Maintenance \u0026 community, 80 against 60\n- Transparency \u0026 trust, 76 against 70\n\nAlso in its favour:\n- Cheaper for geo geocode, $0.40 against $0.50 per 1,000 requests\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Free plan is for development, testing and demos only\n\n\n## Score by category\n\n| Category | Weight | Amazon Location Service | Stadia Maps | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 95 | 63 | Amazon Location Service +32 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 86 | Amazon Location Service +1 |\n| Agent ergonomics | 13% (16.2 this run) | 88 | 80 | Amazon Location Service +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 73 | 40 | Amazon Location Service +33 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 40 | Stadia Maps +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 80 | Stadia Maps +20 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 76 | Stadia Maps +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **74.1 · BB** | **65.2 · B** | |\n\n## Facts side by side\n\n| Fact | Amazon Location Service | Stadia Maps |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Stadia Maps |\n| Hosted endpoint | `https://places.geo.us-east-1.amazonaws.com` | `https://api.stadiamaps.com` |\n| Transports | HTTP | HTTP, stdio |\n| Auth | API key | API key |\n| Pricing | Pay per use | Freemium |\n| Price for geo geocode | $0.50 per 1,000 requests | $0.40 per 1,000 requests |\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 | BSD-3-Clause (MCP server) |\n| Tools exposed | none | 6 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| Last release | 2026-08-17 | 2026-09-30 |\n| Terms last updated | 2026-10-01 | 2026-03-18 |\n| Privacy policy last updated | 2026-05-18 | 2026-10-01 |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | yes | yes |\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 | not found in the text |\n| Popularity | 427k npm/wk | 23 stars, 6.1k npm/wk, 192 PyPI/wk |\n| Agent reviews | none | 3.5/5 (2) |\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**Stadia Maps.** Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only.\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### Stadia Maps\n\n1. Send the key as `Authorization: Stadia-Auth \u003ckey\u003e` rather than in the URL\n2. Try Autocomplete v2 (1 credit) before a full geocode (20 credits) when a name is enough\n3. Check the dashboard's credit balance before retrying a 429, since it may mean the month is spent\n4. Don't write geocodes to a database on Free or Starter\n5. Use bulk-geocode for addresses only, not POI names\n\n## Questions\n\n### Which is better for AI agents, Amazon Location Service or Stadia Maps?\n\nAmazon Location Service scores 74.1 (BB) on agent readiness against Stadia Maps's 65.2 (B), and leads in 4 of 7 scored categories. Stadia Maps leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.\n\n### Which is cheaper for geo geocode, Amazon Location Service or Stadia Maps?\n\nStadia Maps, at $0.40 per 1,000 requests against $0.50 per 1,000 requests for Amazon Location Service. These are the vendors' published prices for the job.\n\n### Do Amazon Location Service and Stadia Maps need an API key?\n\nBoth need an API key.\n\n### Can an agent call Amazon Location Service and Stadia Maps without installing anything?\n\nYes. Amazon Location Service has a hosted endpoint at https://places.geo.us-east-1.amazonaws.com and Stadia Maps at https://api.stadiamaps.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-location\", \"b\": \"stadia-maps\"}`. From a terminal: `anchor compare amazon-location stadia-maps`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-location.json and https://www.anchorterminal.com/api/v1/tools/stadia-maps.json\n\n## Other comparisons with Amazon Location Service or Stadia Maps\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 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 TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.md)\n- [ArcGIS Location Platform vs Stadia Maps](https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps.md)\n- [Azure Maps vs Stadia Maps](https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps.md)\n- [Geoapify Location Platform + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps.md)\n- [Google Maps Platform + Grounding Lite MCP vs Stadia Maps](https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps.md)\n- [LocationIQ vs Stadia Maps](https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps.md)\n- [Mapbox APIs + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps.md)\n- [MapQuest vs Stadia Maps](https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.md)\n- [OpenCage Geocoding API vs Stadia Maps](https://www.anchorterminal.com/compare/opencage-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-08",
    "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 Stadia Maps",
        "url": ""
      }
    ],
    "description": "Amazon Location Service scores 74.1 (BB) on agent readiness against Stadia Maps's 65.2 (B), and leads in 4 of 7 scored categories. Stadia Maps leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. Both do geo geocode. Stadia Maps is cheaper for geo…",
    "facts": [
      "Amazon Location Service BB 74.1",
      "Stadia Maps B 65.2",
      "scores"
    ],
    "h1": "Amazon Location Service vs Stadia Maps",
    "image": "https://www.anchorterminal.com/assets/og/compare-amazon-location-vs-stadia-maps.png",
    "path": "/compare/amazon-location-vs-stadia-maps",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Amazon Location Service vs Stadia Maps for AI agents | Anchor Terminal",
    "toc": null,
    "updated": "2026-10-08",
    "url": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps"
  },
  "tokens": {
    "markdown": 2500,
    "slim": 780
  },
  "version": 1
}