{
  "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-09T01:12:39.253515667Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 238,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 250,
          "p95ms24h": 303,
          "samples24h": 63,
          "samples30d": 63,
          "days": [
            {
              "date": "2026-10-08",
              "probes": 50,
              "ok": 50
            },
            {
              "date": "2026-10-09",
              "probes": 13,
              "ok": 13
            }
          ]
        },
        "updatedAt": "2026-10-09T01:12:39.253515667Z"
      }
    },
    "answer": "Mapbox APIs + MCP and Amazon Location Service score within a point of each other on agent readiness, 75 (BB) and 74.1 (BB). Amazon Location Service leads on reliability.",
    "b": {
      "slug": "mapbox",
      "name": "Mapbox APIs + MCP",
      "vendor": "Mapbox",
      "vendorUrl": "https://www.mapbox.com",
      "kind": "http-api",
      "category": "maps",
      "summary": "Geocoding v6 with batch, Search Box for places and categories, Directions, Matrix, Isochrone, Map Matching, route optimisation, static images and map tiles.",
      "url": "https://www.anchorterminal.com/tools/mapbox",
      "markdownUrl": "https://www.anchorterminal.com/tools/mapbox.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mapbox.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mapbox.json",
      "repo": "https://github.com/mapbox/mcp-server",
      "license": "MIT (MCP server)",
      "transports": [
        "http",
        "streamable-http",
        "stdio"
      ],
      "remoteUrl": "https://api.mapbox.com",
      "packages": [
        {
          "registry": "npm",
          "name": "@mapbox/mcp-server"
        }
      ],
      "auth": "mixed",
      "authNotes": "Access tokens (public pk. or secret sk.) passed as the access_token query parameter on every REST call. The hosted MCP at mcp.mapbox.com signs in with an OAuth flow in the browser. The local server reads MAPBOX_ACCESS_TOKEN.",
      "pricing": "freemium",
      "pricingNotes": "Free monthly allowance per API, then tiered pay as you go. Temporary Geocoding 100,000 free, then $0.75 per 1,000 down to $0.45 above 1 million. Permanent Geocoding (results you may store) has no free allowance and costs $5 per 1,000, then $4 above 500,000. Search Box 500 free sessions then $3 per 1,000 sessions, or 50,000 free requests then $1 per 1,000. Directions, Matrix (by element), Isochrone, Map Matching and route optimisation 100,000 free each, then $2 per 1,000 down to $1.20. Static Images 50,000 free then $1 per 1,000. Vector tiles 200,000 free then $0.25 per 1,000. GL JS map loads 50,000 free then $5 per 1,000 (https://www.mapbox.com/pricing).",
      "priceSummary": "$0.75 / 1k req",
      "where": "both",
      "x402": {
        "level": "no",
        "endpoints": []
      },
      "toolCount": 29,
      "popularity": {
        "githubStars": 353,
        "npmWeekly": 1974,
        "pypiWeekly": null,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://docs.mapbox.com/api/",
      "llmsTxt": "https://docs.mapbox.com/llms.txt",
      "registryName": "io.github.mapbox/mcp-server",
      "capabilities": [
        "geo.geocode",
        "geo.reverse",
        "geo.places",
        "geo.routing",
        "geo.tiles"
      ],
      "tags": [
        "hosted",
        "mcp",
        "llms-txt",
        "official",
        "oauth",
        "typescript",
        "free-tier",
        "enterprise",
        "closed-source"
      ],
      "lastRelease": "2026-07-30",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 75,
        "grade": "BB",
        "agentReady": true,
        "rank": 51,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 1,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 88,
          "maintenance": 80,
          "payments": 30,
          "reliability": 82,
          "schema": 85,
          "security": 71,
          "transparency": 84
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-01"
        },
        "negative": 0,
        "verdict": "Official MCP server, hosted at mcp.mapbox.com with OAuth or run locally, listed in the MCP registry. Storing geocodes needs the Permanent tier at $5 per 1,000, about 6.7 times the temporary rate.",
        "bestFor": "An agent that needs search, routing, isochrones, map matching and route optimisation from one vendor with a hosted, OAuth-protected MCP.",
        "strengths": [
          "Official MCP server, hosted at mcp.mapbox.com with OAuth or run locally, listed in the MCP registry",
          "Every MCP tool annotated read-only and idempotent, with typed Zod input and output schemas",
          "Scoped public and secret tokens, URL restrictions and one-hour temporary tokens",
          "SOC 2 Type II, a HackerOne bug bounty and a dated subprocessor list (4 June 2026)",
          "At least 90 days' emailed notice before an API endpoint is deprecated"
        ],
        "weaknesses": [
          "Storing geocodes needs the Permanent tier at $5 per 1,000, about 6.7 times the temporary rate",
          "Geocoding results may only be used with a Mapbox map",
          "REST calls take the token as the access_token query parameter",
          "29 MCP tools load at once on the hosted endpoint, with filtering documented only for the local server",
          "No SLA on the pricing page or in the API docs, and no security.txt"
        ],
        "agentNotes": [
          "Set permanent=true only when the result goes into a database, since it moves the call to the $5 per 1,000 rate",
          "Keep search_and_geocode_tool queries under 200 characters, the live limit, not the 256 the API docs state",
          "On 429, wait until the X-Rate-Limit-Reset timestamp, since no Retry-After is sent",
          "Run the local server with --enable-tools to load only the tools the task needs",
          "Use category_search_tool for generic place types like coffee shops, not search_and_geocode_tool"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 8,
        "avgRating": 3.6,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 75
          }
        ],
        "editorialScores": {
          "ergonomics": 88,
          "maintenance": 80,
          "payments": 30,
          "reliability": 82,
          "schema": 85,
          "security": 71,
          "transparency": 82
        },
        "provenanceScore": 85
      },
      "connect": {
        "http": "curl \"https://api.mapbox.com/search/geocode/v6/forward?q=10%20Downing%20Street%2C%20London\u0026limit=1\u0026access_token=$MAPBOX_ACCESS_TOKEN\"",
        "claudeCode": "claude mcp add --transport http mapbox https://mcp.mapbox.com/mcp",
        "config": {
          "mcpServers": {
            "mapbox": {
              "args": [
                "-y",
                "@mapbox/mcp-server"
              ],
              "command": "npx",
              "env": {
                "MAPBOX_ACCESS_TOKEN": "${MAPBOX_ACCESS_TOKEN}"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/geo.geocode",
        "tool": "https://letme.dev/mapbox"
      },
      "area": "everyday",
      "unitPrices": [
        {
          "item": "Temporary Geocoding",
          "unit": "1k-requests",
          "usd": 0.75,
          "note": "After 100,000 free a month, $0.45 above 1 million"
        },
        {
          "item": "Permanent Geocoding",
          "unit": "1k-requests",
          "usd": 5,
          "note": "No free allowance, $4 above 500,000"
        },
        {
          "item": "Search Box sessions",
          "unit": "1k-requests",
          "usd": 3,
          "note": "Per 1,000 sessions after 500 free"
        },
        {
          "item": "Directions",
          "unit": "1k-requests",
          "usd": 2,
          "note": "After 100,000 free a month, $1.20 above 1 million"
        },
        {
          "item": "Matrix",
          "unit": "1k-requests",
          "usd": 2,
          "note": "Per 1,000 elements after 100,000 free"
        },
        {
          "item": "Static Images",
          "unit": "1k-requests",
          "usd": 1,
          "note": "After 50,000 free a month"
        },
        {
          "item": "Vector tiles",
          "unit": "1k-requests",
          "usd": 0.25,
          "note": "After 200,000 free a month"
        }
      ],
      "provenance": {
        "legalEntity": "Mapbox, Inc.",
        "domain": "mapbox.com",
        "domainRegistered": "2003-11-27",
        "domainNote": "mapbox.com was registered in 2003, years before Mapbox started, so the domain was bought later.",
        "endpointOnVendorDomain": true,
        "terms": "https://www.mapbox.com/legal/tos",
        "privacy": "https://www.mapbox.com/legal/privacy",
        "statusPage": "https://status.mapbox.com",
        "changelog": "https://docs.mapbox.com/api/changelog/",
        "securityTxt": "none",
        "checked": "2026-10-01",
        "notes": [
          "The terms of service were last updated 31 March 2024 and point to separate product terms for per-API rules.",
          "The terms let Mapbox create de-identified aggregated data from customer usage.",
          "www.mapbox.com/.well-known/security.txt returns 404.",
          "The top-level API changelog's newest entry is 5 November 2021. Current changes are in per-service changelogs and the MCP server's CHANGELOG.md on GitHub.",
          "Subprocessor list (22 entries with locations) last updated 4 June 2026."
        ],
        "score": 85
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/mapbox.json",
      "live": {
        "slug": "mapbox",
        "probe": {
          "target": "https://api.mapbox.com",
          "method": "get",
          "lastAt": "2026-10-09T01:12:50.808092518Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 27,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 26,
          "p95ms24h": 59,
          "samples24h": 267,
          "samples30d": 1997,
          "days": [
            {
              "date": "2026-10-01",
              "probes": 109,
              "ok": 109
            },
            {
              "date": "2026-10-02",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-03",
              "probes": 271,
              "ok": 271
            },
            {
              "date": "2026-10-04",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-05",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-06",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-07",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-08",
              "probes": 268,
              "ok": 268
            },
            {
              "date": "2026-10-09",
              "probes": 13,
              "ok": 13
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.mapbox.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-09T01:07:38.458858543Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "mapbox/mcp-server",
            "version": "v0.14.0",
            "released": "2026-07-30",
            "seenAt": "2026-10-08T16:19:52.842790778Z"
          },
          {
            "registry": "mcp-registry",
            "name": "io.github.mapbox/mcp-server",
            "version": "99.0.0-dev",
            "seenAt": "2026-10-08T02:42:52.272076636Z"
          },
          {
            "registry": "npm",
            "name": "@mapbox/mcp-server",
            "version": "0.14.0",
            "seenAt": "2026-10-08T16:19:52.343013533Z"
          }
        ],
        "githubStars": 361,
        "npmWeekly": 1944,
        "securityTxt": {
          "url": "https://mapbox.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-08T15:39:00.711097754Z"
        },
        "llmsTxt": {
          "url": "https://docs.mapbox.com/llms.txt",
          "ok": false,
          "status": 403,
          "checkedAt": "2026-10-08T14:00:36.088985433Z"
        },
        "domain": {
          "domain": "mapbox.com",
          "registered": "2003-11-27",
          "source": "https://rdap.verisign.com/com/v1/domain/mapbox.com",
          "checkedAt": "2026-10-04T13:08:41.082804792Z"
        },
        "pages": [
          {
            "url": "https://docs.mapbox.com/api/changelog/",
            "kind": "changelog",
            "status": 304,
            "checkedAt": "2026-10-08T18:19:03.518767752Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "395e3e05bd01"
          },
          {
            "url": "https://www.mapbox.com/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-08T18:29:06.302646577Z",
            "changedAt": "2026-10-08T18:29:06.302646577Z",
            "fingerprint": "7385a40a4b10"
          },
          {
            "url": "https://www.mapbox.com/legal/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-08T18:29:01.987481033Z",
            "changedAt": "2026-10-08T18:29:01.987481033Z",
            "fingerprint": "51a0d73e5b96"
          },
          {
            "url": "https://www.mapbox.com/legal/tos",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-08T18:29:04.641523555Z",
            "changedAt": "2026-10-08T18:29:04.641523555Z",
            "fingerprint": "54b97792564c"
          }
        ],
        "updatedAt": "2026-10-09T01:12:50.808092518Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Amazon Web Services",
        "b": "Mapbox",
        "name": "Vendor"
      },
      {
        "a": "https://places.geo.us-east-1.amazonaws.com",
        "b": "https://api.mapbox.com",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP, Streamable HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "$0.50 per 1,000 requests",
        "b": "$0.75 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": "MIT (MCP server)",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "29",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "io.github.mapbox/mcp-server",
        "name": "MCP registry"
      },
      {
        "a": "2026-08-17",
        "b": "2026-07-30",
        "name": "Last release"
      },
      {
        "a": "2026-10-01",
        "b": "2024-03-31",
        "name": "Terms last updated"
      },
      {
        "a": "2026-05-18",
        "b": "2026-02-11",
        "name": "Privacy policy last updated"
      },
      {
        "a": "yes, with an opt-out",
        "b": "yes",
        "name": "Customer content may train models"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "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": "353 stars, 2k npm/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3.6/5 (8)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Mapbox APIs + MCP and Amazon Location Service score within a point of each other on agent readiness, 75 (BB) and 74.1 (BB). Amazon Location Service leads on reliability.",
        "question": "Which is better for AI agents, Amazon Location Service or Mapbox APIs + MCP?"
      },
      {
        "answer": "Amazon Location Service, at $0.50 per 1,000 requests against $0.75 per 1,000 requests for Mapbox APIs + MCP. These are the vendors' published prices for the job.",
        "question": "Which is cheaper for geo geocode, Amazon Location Service or Mapbox APIs + MCP?"
      },
      {
        "answer": "Amazon Location Service needs an API key. Mapbox APIs + MCP takes an API key or an OAuth sign-in.",
        "question": "Do Amazon Location Service and Mapbox APIs + MCP need an API key?"
      },
      {
        "answer": "Yes. Amazon Location Service has a hosted endpoint at https://places.geo.us-east-1.amazonaws.com and Mapbox APIs + MCP at https://api.mapbox.com.",
        "question": "Can an agent call Amazon Location Service and Mapbox APIs + MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 95 against 82"
        ],
        "also": [
          "Cheaper for geo geocode, $0.50 against $0.75 per 1,000 requests"
        ],
        "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, 30 against 20",
          "Maintenance \u0026 community, 80 against 60",
          "Transparency \u0026 trust, 84 against 70"
        ],
        "also": [
          "Runs on your own machine"
        ],
        "goodFor": "An agent that needs search, routing, isochrones, map matching and route optimisation from one vendor with a hosted, OAuth-protected MCP.",
        "slug": "mapbox",
        "watchFor": "Storing geocodes needs the Permanent tier at $5 per 1,000, about 6.7 times the temporary rate"
      }
    ],
    "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-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-mapbox.json",
        "title": "ArcGIS Location Platform vs Mapbox APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/arcgis-vs-mapbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/azure-maps-vs-mapbox.json",
        "title": "Azure Maps vs Mapbox APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/azure-maps-vs-mapbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/geoapify-vs-mapbox.json",
        "title": "Geoapify Location Platform + MCP vs Mapbox APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/geoapify-vs-mapbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-mapbox.json",
        "title": "Google Maps Platform + Grounding Lite MCP vs Mapbox APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-mapbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/locationiq-vs-mapbox.json",
        "title": "LocationIQ vs Mapbox APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/locationiq-vs-mapbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mapbox-vs-mapquest.json",
        "title": "Mapbox APIs + MCP vs MapQuest",
        "url": "https://www.anchorterminal.com/compare/mapbox-vs-mapquest"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mapbox-vs-opencage.json",
        "title": "Mapbox APIs + MCP vs OpenCage Geocoding API",
        "url": "https://www.anchorterminal.com/compare/mapbox-vs-opencage"
      },
      {
        "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/mapbox-vs-tomtom.json",
        "title": "Mapbox APIs + MCP vs TomTom Maps APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/mapbox-vs-tomtom"
      }
    ],
    "scores": [
      {
        "amazon-location": 95,
        "by": 13,
        "edge": "amazon-location",
        "key": "reliability",
        "mapbox": 82,
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "amazon-location": 87,
        "by": 2,
        "edge": "amazon-location",
        "key": "schema",
        "mapbox": 85,
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "amazon-location": 88,
        "by": 0,
        "edge": "",
        "key": "ergonomics",
        "mapbox": 88,
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "amazon-location": 73,
        "by": 2,
        "edge": "amazon-location",
        "key": "security",
        "mapbox": 71,
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "amazon-location": 20,
        "by": 10,
        "edge": "mapbox",
        "key": "payments",
        "mapbox": 30,
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "amazon-location": 60,
        "by": 20,
        "edge": "mapbox",
        "key": "maintenance",
        "mapbox": 80,
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "amazon-location": 70,
        "by": 14,
        "edge": "mapbox",
        "key": "transparency",
        "mapbox": 84,
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Mapbox APIs + MCP and Amazon Location Service score within a point of each other on agent readiness, 75 (BB) and 74.1 (BB). Amazon Location Service leads on reliability. Both do geo geocode. Amazon Location Service is cheaper for geo geocode, $0.50 against $0.75 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.",
      "mapbox": "Official MCP server, hosted at mcp.mapbox.com with OAuth or run locally, listed in the MCP registry. Storing geocodes needs the Permanent tier at $5 per 1,000, about 6.7 times the temporary rate."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/amazon-location-vs-mapbox",
    "json": "https://www.anchorterminal.com/compare/amazon-location-vs-mapbox.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/amazon-location-vs-mapbox.md",
    "slim": "https://www.anchorterminal.com/compare/amazon-location-vs-mapbox.min.md"
  },
  "markdown": "Mapbox APIs + MCP and Amazon Location Service score within a point of each other on agent readiness, 75 (BB) and 74.1 (BB). Amazon Location Service leads on reliability. Both do geo geocode. Amazon Location Service is cheaper for geo geocode, $0.50 against $0.75 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- Mapbox APIs + MCP: grade BB, 75/100, rank #51 of 722. Markdown https://www.anchorterminal.com/tools/mapbox.md · JSON https://www.anchorterminal.com/api/v1/tools/mapbox.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 82\n\nAlso in its favour:\n- Cheaper for geo geocode, $0.50 against $0.75 per 1,000 requests\n\nWatch for: The API key is sent as the `key` query parameter, the only documented way to present it\n\n### Mapbox APIs + MCP (BB)\n\nGood for: An agent that needs search, routing, isochrones, map matching and route optimisation from one vendor with a hosted, OAuth-protected MCP.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 20\n- Maintenance \u0026 community, 80 against 60\n- Transparency \u0026 trust, 84 against 70\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: Storing geocodes needs the Permanent tier at $5 per 1,000, about 6.7 times the temporary rate\n\n\n## Score by category\n\n| Category | Weight | Amazon Location Service | Mapbox APIs + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 95 | 82 | Amazon Location Service +13 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 85 | Amazon Location Service +2 |\n| Agent ergonomics | 13% (16.2 this run) | 88 | 88 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 73 | 71 | Amazon Location Service +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 30 | Mapbox APIs + MCP +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 80 | Mapbox APIs + MCP +20 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 84 | Mapbox APIs + MCP +14 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **74.1 · BB** | **75 · BB** | |\n\n## Facts side by side\n\n| Fact | Amazon Location Service | Mapbox APIs + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Mapbox |\n| Hosted endpoint | `https://places.geo.us-east-1.amazonaws.com` | `https://api.mapbox.com` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Freemium |\n| Price for geo geocode | $0.50 per 1,000 requests | $0.75 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 | MIT (MCP server) |\n| Tools exposed | none | 29 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.mapbox/mcp-server` |\n| Last release | 2026-08-17 | 2026-07-30 |\n| Terms last updated | 2026-10-01 | 2024-03-31 |\n| Privacy policy last updated | 2026-05-18 | 2026-02-11 |\n| Customer content may train models | yes, with an opt-out | yes |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\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 | 353 stars, 2k npm/wk |\n| Agent reviews | none | 3.6/5 (8) |\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**Mapbox APIs + MCP.** Official MCP server, hosted at mcp.mapbox.com with OAuth or run locally, listed in the MCP registry. Storing geocodes needs the Permanent tier at $5 per 1,000, about 6.7 times the temporary rate.\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### Mapbox APIs + MCP\n\n1. Set permanent=true only when the result goes into a database, since it moves the call to the $5 per 1,000 rate\n2. Keep search_and_geocode_tool queries under 200 characters, the live limit, not the 256 the API docs state\n3. On 429, wait until the X-Rate-Limit-Reset timestamp, since no Retry-After is sent\n4. Run the local server with --enable-tools to load only the tools the task needs\n5. Use category_search_tool for generic place types like coffee shops, not search_and_geocode_tool\n\n## Questions\n\n### Which is better for AI agents, Amazon Location Service or Mapbox APIs + MCP?\n\nMapbox APIs + MCP and Amazon Location Service score within a point of each other on agent readiness, 75 (BB) and 74.1 (BB). Amazon Location Service leads on reliability.\n\n### Which is cheaper for geo geocode, Amazon Location Service or Mapbox APIs + MCP?\n\nAmazon Location Service, at $0.50 per 1,000 requests against $0.75 per 1,000 requests for Mapbox APIs + MCP. These are the vendors' published prices for the job.\n\n### Do Amazon Location Service and Mapbox APIs + MCP need an API key?\n\nAmazon Location Service needs an API key. Mapbox APIs + MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call Amazon Location Service and Mapbox APIs + MCP without installing anything?\n\nYes. Amazon Location Service has a hosted endpoint at https://places.geo.us-east-1.amazonaws.com and Mapbox APIs + MCP at https://api.mapbox.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-location-vs-mapbox.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-location-vs-mapbox.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-location\", \"b\": \"mapbox\"}`. From a terminal: `anchor compare amazon-location mapbox`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-location.json and https://www.anchorterminal.com/api/v1/tools/mapbox.json\n\n## Other comparisons with Amazon Location Service or Mapbox APIs + MCP\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 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 Mapbox APIs + MCP](https://www.anchorterminal.com/compare/arcgis-vs-mapbox.md)\n- [Azure Maps vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-mapbox.md)\n- [Geoapify Location Platform + MCP vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/geoapify-vs-mapbox.md)\n- [Google Maps Platform + Grounding Lite MCP vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/google-maps-platform-vs-mapbox.md)\n- [LocationIQ vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/locationiq-vs-mapbox.md)\n- [Mapbox APIs + MCP vs MapQuest](https://www.anchorterminal.com/compare/mapbox-vs-mapquest.md)\n- [Mapbox APIs + MCP vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/mapbox-vs-opencage.md)\n- [Mapbox APIs + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps.md)\n- [Mapbox APIs + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapbox-vs-tomtom.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-09",
    "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 Mapbox APIs + MCP",
        "url": ""
      }
    ],
    "description": "Mapbox APIs + MCP and Amazon Location Service score within a point of each other on agent readiness, 75 (BB) and 74.1 (BB). Amazon Location Service leads on reliability. Both do geo geocode. Amazon Location Service is cheaper for geo geocode, $0.50 against $0.75 per 1,000…",
    "facts": [
      "Amazon Location Service BB 74.1",
      "Mapbox APIs + MCP BB 75",
      "scores"
    ],
    "h1": "Amazon Location Service vs Mapbox APIs + MCP",
    "image": "https://www.anchorterminal.com/assets/og/compare-amazon-location-vs-mapbox.png",
    "path": "/compare/amazon-location-vs-mapbox",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Amazon Location Service vs Mapbox APIs + MCP for AI agents",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/amazon-location-vs-mapbox"
  },
  "tokens": {
    "markdown": 2550,
    "slim": 780
  },
  "version": 1
}