# Amazon Location Service > 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. - Canonical: https://www.anchorterminal.com/tools/amazon-location - Markdown: https://www.anchorterminal.com/tools/amazon-location.md (~8,350 tokens) - Slim: https://www.anchorterminal.com/tools/amazon-location.min.md (~2,030 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/amazon-location.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade BB · 74.1/100 · rank #68 of 722 · #2 in Maps, geocoding & places · agent-ready · confidence high** More from Amazon Web Services, listed separately because each is its own product: [Amazon Bedrock Guardrails](https://www.anchorterminal.com/tools/amazon-bedrock-guardrails.md) (Guardrails & safety filters), [Amazon Transcribe](https://www.anchorterminal.com/tools/amazon-transcribe.md) (Speech-to-text), [Amazon Polly](https://www.anchorterminal.com/tools/amazon-polly.md) (Text-to-speech), [AWS Secrets Manager](https://www.anchorterminal.com/tools/aws-secrets-manager.md) (Secrets & credential vaults), [AWS MCP Servers](https://www.anchorterminal.com/tools/aws-mcp-servers.md) (Cloud & infrastructure), [Amazon SES](https://www.anchorterminal.com/tools/amazon-ses.md) (Email delivery APIs), [Amazon Translate](https://www.anchorterminal.com/tools/amazon-translate.md) (Translation), [Amazon Ads API](https://www.anchorterminal.com/tools/amazon-ads-api.md) (Advertising & campaign operations). ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Amazon Web Services (https://aws.amazon.com/location/) | | Kind | HTTP API | | Category | Maps, geocoding & places (https://www.anchorterminal.com/categories/maps) | | Transport | HTTP | | Endpoint | `https://places.geo.us-east-1.amazonaws.com` | | Auth | API key · 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 | Pay per use ($0.50 / 1k req) · 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). | | x402 | No · No x402, MPP or L402 in the developer guide's llms.txt, the service models or the pricing page (checked 2026-10-08). | | 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 | | Packages | npm: `@aws-sdk/client-geo-places`; npm: `@aws-sdk/client-geo-routes`; npm: `@aws-sdk/client-geo-maps`; pypi: `boto3` | | Source | https://github.com/aws-geospatial/amazon-location-agent-context | | Docs | https://docs.aws.amazon.com/location/latest/developerguide/what-is.html | | llms.txt | https://docs.aws.amazon.com/location/latest/developerguide/llms.txt | | Last release | 2026-08-17 | | npm downloads / week | 426,988 | | APIs | Places v2 (7 operations), Routes v2 (5), Maps v2 (5), plus the `location` API (64 operations) for API keys, geofences, trackers, jobs and the v1 resources. API version 2020-11-19 | | Endpoints | `places.geo..amazonaws.com`, `routes.geo..amazonaws.com`, `maps.geo..amazonaws.com`, with dual-stack twins under `api.aws` | | Credentials | API keys for Maps, Places and Routes (allowed actions and resources, optional expiry, referrer or app restrictions), Amazon Cognito, or SigV4 with IAM for every API | | Default rates | 100 a second for each Places operation. 20 for `CalculateRoutes`, `CalculateIsolines` and `SnapToRoads`, 5 for `CalculateRouteMatrix` and `OptimizeWaypoints`. Burst 80 per cent of the rate. Self-service increase to twice the default | | Limits | 6 MB compressed response. `MaxResults` 1 to 100 and `QueryText` up to 200 characters on `Geocode`. 50 waypoints for `OptimizeWaypoints`, 5,000 trace points for `SnapToRoads` | | Storage rule | Results may be stored only with `IntendedUse` set to `Storage`, billed at the stored price. Autocomplete and Suggest results can't be stored. HERE data for Japan can't be stored or cached (Service Terms 82.4 and 82.5) | | Data providers | HERE, Esri, GrabMaps (eight Southeast Asian countries) and AWS open data maps built on Overture and OpenStreetMap | | Free allowance | Monthly for the first three months. 20,000 core Places requests, 10,000 label Autocomplete or Suggest requests, 10,000 routes, 500,000 map tiles, 5,000 static maps | | SLA | 99.9 per cent monthly uptime per region. Credits of 10 per cent below 99.9, 25 below 99.0 and 100 below 95.0 (last updated 5 May 2022) | | Retention | Device positions 30 days. Geofences until deleted. Queries have customer metadata removed before going to data providers, which may process them outside the request's region | | Audit | CloudTrail management events by default, data events on request. CloudWatch metrics by `ApiKeyName` | | Agent tooling | `aws-geospatial/amazon-location-agent-context` v1.2.0 (Apache-2.0), a Claude Code and Cursor plugin, Kiro power and Agent Skill. Its MCP config points at the AWS MCP Server, not a server specific to Amazon Location | | Address validation | Batch only, through the Jobs API with S3 input and output. United States, Canada, United Kingdom and Australia. $10.50 per 1,000 for the first 100,000 (core) | | 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 | | JSON | https://www.anchorterminal.com/api/v1/tools/amazon-location.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: high. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 95 | 19.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 87 | 14.1 | | Agent ergonomics | 13% | 16.2 | 88 | 14.3 | | Security & auth | 14% | 17.5 | 73 | 12.8 | | Payments & pricing | 10% | 12.5 | 20 | 2.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 60 | 5.2 | | Transparency & trust (editorial 52, provenance 88) | 7% | 8.8 | 70 | 6.1 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **74.1 → BB** | ### Why each score - Reliability 95: Hosted reading. AWS Health Dashboard with a feed per service and region (20). The Amazon Location feeds for us-east-1 and eu-west-1 held no events on 8 October 2026, and the dashboard's event history from 10 July 2026 names no Amazon Location event. The public dashboard lists only broad events, so a clean feed says less than a small vendor's detailed page. The us-east-1 event of 20 October 2025 listed Amazon Location among affected services, outside the 90 days (30). Default rates published per operation, 100 a second for each Places call, 20 for `CalculateRoutes`, 5 for `CalculateRouteMatrix`, with a burst of 80 per cent (15). Throttling returns `ThrottlingException` with HTTP 429, marked retryable in the service model, and every v2 call is a read, but the guide gives no backoff or `Retry-After` guidance (10 of 15). Amazon Location SLA at 99.9 per cent monthly uptime per region (10). GA (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 87: The Smithy service models for `geo-places`, `geo-routes`, `geo-maps` and `location` (API version 2020-11-19) are public in aws/api-models-aws and in every AWS SDK, a machine-readable contract in the role OpenAPI plays (25). llms.txt for the developer guide, a Markdown twin of each page and the whole guide as `full.md` (10). A choose-an-API page and per-operation pages with use cases say when each call fits, with less on when not to use one (15 of 20). Inputs carry enums and ranges, such as `MaxResults` 1 to 100 and `QueryText` up to 200 characters (15). How-to pages give sample requests, responses, cURL and CLI commands, and each action lists its errors with HTTP codes, but the `ValidationException` fields are documented as "Test stub" (12 of 15). Versioned paths (`/v2/`), yet the document history has one entry, dated 31 October 2024, and changes are announced only in AWS What's New posts (10 of 15). - Agent ergonomics 88: API reading of the checklist. Places responses stay at the core fields unless `AdditionalFeatures` asks for more, and `MaxResults` caps the count, but there is no field selection and route responses can reach the 6 MB limit (20 of 25). `MaxResults` on six of seven Places calls, `NextToken` on `SearchText` and `SearchNearby`, and filters by country, bounding box and place type (18 of 20). Four typed errors per API, with a reason and field list on `ValidationException` (17 of 20). Every v2 operation is marked read-only in the model, so retries are safe. No hints apply to a plain API (18 of 20). One required field or none on most calls, an API key that avoids SigV4 signing, and SDKs on npm and PyPI among others (15). - Security & auth 73: Three credential routes, SigV4 with IAM, Amazon Cognito, and API keys limited to named actions and resources with optional expiry and referrer or app restrictions, which earns 30. Less 10 because the API key is sent in the `key` query parameter, the only documented way to present it (20). API keys reach only read calls on Maps, Places and Routes, and IAM policies scope each action and resource (18 of 20). Results carry place names and third-party map data, and no prompt-injection guidance was found in the reviewed documentation (5 of 15). CloudTrail records management events by default and data events on request, and CloudWatch reports usage by `ApiKeyName` (15). A vulnerability disclosure programme on HackerOne, audit reports in AWS Artifact and a FedRAMP High announcement of 28 October 2024. The security.txt on aws.amazon.com passed its Expires date on 24 September 2026, and no paid bounty was found (15 of 20). - Payments & pricing 20: No x402, MPP or L402 (0). Per-1,000 prices for every operation and bucket published without a login (20). The pricing page lists monthly allowances for the first three months and up to $200 of credits for new customers, but an AWS account is needed. We did not re-read the sign-up flow today and follow the 1 October reading on the other AWS listings that a card is required (0). A person signs up in a browser. `CreateKey` mints API keys by API only after an account exists (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 60: Read as a closed service. The newest API change is in the `geo-maps` model on 17 August 2026 (point-of-interest density and category filters on maps), 52 days before the check (20 of 30). In the last 90 days we found that one model change plus two releases of the agent context package, v1.1.0 on 6 August and v1.2.0 on 11 September 2026. The `geo-places` change of 8 July falls two days outside (10 of 20). AWS What's New posts for the service run to 2 April 2026, re:Post and paid support exist, and the agent context repository had no open issues (10 of 15). Official SDKs are current, `@aws-sdk/client-geo-places` 3.1147.0 on 6 October 2026 and boto3 1.43.109 on 7 October (15). SDKs regenerate from the model on AWS's release train, CI not checked (5 of 10). - Transparency & trust 70: Closed service under the AWS Service Terms, whose section 82 sets out storage, caching and attribution rules in detail (15 of 30). The guide says device positions are kept 30 days, geofences until deleted, and that queries are stripped of customer metadata before they go to data providers. Section 82.1 agrees and adds that providers may process requests outside the chosen region. No retention period was found for Places and Routes requests (20 of 30). Section 82.3 allows AWS to change or drop a provider or feature on notice "where practicable", and no dated deprecation notice or end date for the v1 APIs was found (5 of 20). The data providers (HERE, Esri, GrabMaps and AWS's open data) are named and the region is chosen per request. The AWS sub-processor list was not read today (12 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (15 items): https://www.anchorterminal.com/fixes/amazon-location.md (JSON https://www.anchorterminal.com/fixes/amazon-location.json) ### What we couldn't check - unchecked: whether opening an AWS account on the free plan needs a payment card. We did not go through sign-up and scored the free tier as the other AWS listings did on 1 October 2026. - unchecked: the AWS sub-processor list and the AWS Data Processing Addendum were not read today. - Prices are those for US East (N. Virginia) in the feed the pricing page loads. Other regions were not compared. - The What's New listing we read is filtered by AWS's own product tag and may omit posts, such as the Jobs API and address validation launch, whose date we did not establish. - We read the status feeds for us-east-1 and eu-west-1 only, plus the dashboard's cross-region event history. - No retention period for Places and Routes request data was found in the reviewed documentation. ### Sources - developer guide llms.txt: (seen 2026-10-08) - pricing page and the price data it loads (US East): (seen 2026-10-08) - price data feed read by the pricing page: (seen 2026-10-08) - Places quotas: (seen 2026-10-08) - Routes quotas: (seen 2026-10-08) - Service Quotas and burst rule: (seen 2026-10-08) - API keys: (seen 2026-10-08) - authentication best practices: (seen 2026-10-08) - Geocode API reference: (seen 2026-10-08) - geocode how-to with cURL: (seen 2026-10-08) - service models and their history: (seen 2026-10-08) - status feed us-east-1: (seen 2026-10-08) - AWS Health Dashboard and the event history it loads: (seen 2026-10-08) - Amazon Location SLA: (seen 2026-10-08) - AWS Service Terms, section 82: (seen 2026-10-08) - AWS Privacy Notice: (seen 2026-10-08) - data retention: (seen 2026-10-08) - data privacy: (seen 2026-10-08) - CloudTrail logging: (seen 2026-10-08) - document history: (seen 2026-10-08) - Build with AI agents: (seen 2026-10-08) - agent context repository, changelog and tags: (seen 2026-10-08) - AWS What's New posts tagged Amazon Location Service: (seen 2026-10-08) - npm client: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - endpoints: (seen 2026-10-08) ## Who's behind it (provenance 88/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Amazon Web Services, Inc. | 20/20 | | Domain age | amazon.com, registered 1994-11-01 (31 years) | 15/15 | | Endpoint on the vendor's domain | places.geo.us-east-1.amazonaws.com | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 3 clauses that cost points | 3.1/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | health.aws.amazon.com/health/status | 10/10 | | Changelog | published | 10/10 | | security.txt | published but past its Expires date | 5/10 | 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. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://aws.amazon.com/service-terms/), read 2026-10-08, dated 2026-10-01, states 6 of the 7 things a reader expects. - To know. Says it may use customer content to train or improve models, and gives an opt-out. "You may instruct AWS not to use and store Amazon WorkSpaces AI Content processed by Amazon WorkSpaces AI Features to develop and improve the Service or technologies of AWS or its affiliates by configuring an AI services opt-out policy using AWS Organizations." - To know. Restricts automated access (costs points). "Reverse engineer, decompile, attempt to reconstruct, scrape, systematically collect, or duplicate Address Validation Data." - To know. Restricts benchmarking or competitive use (costs points). "You may not, and may not allow any third party to, use Amazon CloudWatch Network Monitoring, or any data or information made available through Amazon CloudWatch Network Monitoring, to, directly or indirectly, develop, improve, or offer a similar or competing product or service." - To know. Says the terms or the service can change without notice (costs points). "We may change, discontinue, or deprecate support for any third-party software development services at any time without prior notice." - Gives the date it was last updated. Last updated 2026-10-01. - Not found in the text. Names the governing law or courts. - Says how changes to the terms are announced. Gives 30 days of notice before a change. **Privacy policy** (https://aws.amazon.com/privacy/), read 2026-10-08, dated 2026-05-18, states 8 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "To help you receive more useful and relevant ads on other sites and services and to measure their effectiveness, AWS shares limited personal information with our advertising partners." - Gives the date it was last updated. Last updated 2026-05-18. - Says how long data is kept. For as long as needed, with no period named. - Gives a privacy contact. Names a data protection officer. - Says where data is transferred or stored. Relies on the Data Privacy Framework. - Also in the text (2026-10-08). The notice does not cover content that customers process, store or host on AWS. It refers to the customer agreement for how that content is handled. "This Privacy Notice does not apply to the “content” processed, stored, or hosted by our customers using AWS Offerings in connection with an AWS account." ## Live (updated 2026-10-08 22:39 UTC) - Right now: up, HTTP 404, 266 ms, checked 2026-10-08 22:39 UTC (get on `https://places.geo.us-east-1.amazonaws.com`) - Uptime 24h 100.0% (36 probes) · 30 days 100.0% (36 probes) · p50 252 ms · p95 307 ms - Always current: https://www.anchorterminal.com/api/v1/live/amazon-location.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Geocode, reverse geocode, place search (core) | $0.50 | per 1,000 requests | US East. `SingleUse` results, not for storage | | Geocode, reverse geocode, place search (advanced) | $1.50 | per 1,000 requests | With contacts, opening hours, access points or time zone | | Geocode, reverse geocode, place search (stored) | $4 | per 1,000 requests | `IntendedUse` set to `Storage` | | Autocomplete and Suggest (label) | $0.20 | per 1,000 requests | | | Routes calculated (core) | $0.50 | per 1,000 requests | Car, truck or pedestrian. A matrix bills origins times destinations | | Routes with toll cost (premium) | $4 | per 1,000 requests | | | Dynamic map tiles | $0.04 | per 1,000 requests | | | Static map images | $0.50 | per 1,000 requests | | Across all listings: https://www.anchorterminal.com/prices/index.md ## 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 ## Before you call it (notes for agents) 1. Call the v2 endpoints (`places.geo..amazonaws.com/v2/geocode`, `routes.geo`, `maps.geo`). They need no resource creation, unlike the v1 place index and route calculator calls 2. 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 3. 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 4. 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 5. Back off on HTTP 429 `ThrottlingException`. The burst allowance is 80 per cent of the per-second rate within any part of a second ## Connect Install: ```bash pip install boto3 # or: npm i @aws-sdk/client-geo-places ``` First request: ```bash curl --request POST \ --url 'https://places.geo.eu-central-1.amazonaws.com/v2/geocode?key=Your_Key' \ --header 'Content-Type: application/json' \ --data '{"QueryText": "510 W Georgia St, Vancouver, BC"}' ``` Claude Code: ```bash /plugin install amazon-location-service@claude-plugins-official ``` Through letme (picks today, calling later): https://letme.dev/amazon-location (letme picks it for geo.geocode, the top-graded tool for the job, letme picks it for geo.tiles, the top-graded tool for the job). letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Mapbox APIs + MCP | BB | 75 | 51 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/mapbox.md | | Google Maps Platform + Grounding Lite MCP | B | 68.2 | 189 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/google-maps-platform.md | | Azure Maps | B | 67.9 | 196 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/azure-maps.md | | ArcGIS Location Platform | B | 65.4 | 259 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/arcgis.md | | Stadia Maps | B | 65.2 | 261 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/stadia-maps.md | | LocationIQ | C | 60.3 | 405 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/locationiq.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The v2 Places, Routes and Maps APIs need no resource creation and answer at `places.geo`, `routes.geo` and `maps.geo` under `.amazonaws.com`. The v1 place index and route calculator calls remain in the `location` API (source: ) - Section 82.4 of the AWS Service Terms bars storing or caching location data, except geocoding results requested with the storage parameter and HERE or Esri route results for up to 30 days (source: ) - Each response names the `PricingBucket` it was billed at (source: ) - Data comes from HERE, Esri, GrabMaps and AWS open data maps, and section 82.1 of the Service Terms says providers may process request parameters outside the AWS region of the request (source: ) - The Build with AI agents page installs an agent context package as a Claude Code or Cursor plugin, a Kiro power or an Agent Skill. Its MCP configuration is the general AWS MCP Server (source: ) - Autocomplete is not available in Japan, and address validation runs only as batch jobs for the United States, Canada, the United Kingdom and Australia (source: ) - The `@aws-sdk/client-geo-places` package had 426,988 npm downloads in the week before 8 October 2026 (source: ) ## Compare - [Amazon Location Service vs ArcGIS Location Platform](https://www.anchorterminal.com/compare/amazon-location-vs-arcgis.md): BB 74.1 vs B 65.4 - [Amazon Location Service vs Azure Maps](https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps.md): BB 74.1 vs B 67.9 - [Amazon Location Service vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-geoapify.md): BB 74.1 vs C 55.3 - [Amazon Location Service vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/amazon-location-vs-google-maps-platform.md): BB 74.1 vs B 68.2 - [Amazon Location Service vs LocationIQ](https://www.anchorterminal.com/compare/amazon-location-vs-locationiq.md): BB 74.1 vs C 60.3 - [Amazon Location Service vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-mapbox.md): BB 74.1 vs BB 75 - [Amazon Location Service vs MapQuest](https://www.anchorterminal.com/compare/amazon-location-vs-mapquest.md): BB 74.1 vs F 35.1 - [Amazon Location Service vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/amazon-location-vs-opencage.md): BB 74.1 vs B 69.2 - [Amazon Location Service vs Stadia Maps](https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.md): BB 74.1 vs B 65.2 - [Amazon Location Service vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.md): BB 74.1 vs C 54.9 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on amazon.com or one of its subdomains, or the README of github.com/aws-geospatial/amazon-location-agent-context. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "amazon-location", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Amazon Location Service on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Amazon Location Service on Anchor Terminal](https://www.anchorterminal.com/badges/amazon-location.svg)](https://www.anchorterminal.com/tools/amazon-location) ``` Plain link: ```html Amazon Location Service on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Amazon Location Service is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/amazon-location-dark.png - Light: https://www.anchorterminal.com/assets/share/amazon-location-light.png