# Amazon Location Service vs Azure Maps (slim)

> Amazon Location Service scores 74.1 (BB) on agent readiness against Azure Maps's 67.9 (B), and leads in 4 of 7 scored categories. Azure Maps leads on maintenance & community. Both do geo geocode. Amazon Location Service is cheaper for geo geocode, $0.50 against $4.50 per 1,000…

- Full: https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps.md (~2,600 tokens) · this version ~780 tokens · JSON https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps.json · canonical https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-08

Amazon Location Service scores 74.1 (BB) on agent readiness against Azure Maps's 67.9 (B), and leads in 4 of 7 scored categories. Azure Maps leads on maintenance & community. Both do geo geocode. Amazon Location Service is cheaper for geo geocode, $0.50 against $4.50 per 1,000 requests.

- Amazon Location Service: BB 74.1, rank #68 of 722 · https://www.anchorterminal.com/tools/amazon-location.min.md
- Azure Maps: B 67.9, rank #196 of 722 · https://www.anchorterminal.com/tools/azure-maps.min.md
- Amazon Location Service, good 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. Ahead on Reliability, 95 against 81; Agent ergonomics, 88 against 73; Security & auth, 73 against 66. Also Cheaper for geo geocode, $0.50 against $4.50 per 1,000 requests; Agent-ready, a grade of BB or better.
- Azure Maps, good for Teams already on Azure that want geocoding and routing under Entra ID roles and one flat price. Ahead on Maintenance & community, 67 against 60.

| Category | Amazon Location Service | Azure Maps |
| --- | --- | --- |
| Reliability (16%) | 95 | 81 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 83 |
| Agent ergonomics (13%) | 88 | 73 |
| Security & auth (14%) | 73 | 66 |
| Payments & pricing (10%) | 20 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 60 | 67 |
| Transparency & trust (7%) | 70 | 74 |

| Fact (where they differ) | Amazon Location Service | Azure Maps |
| --- | --- | --- |
| Vendor | Amazon Web Services | Microsoft Azure |
| Hosted endpoint | `https://places.geo.us-east-1.amazonaws.com` | `https://atlas.microsoft.com` |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for geo geocode | $0.50 per 1,000 requests | $4.50 per 1,000 requests |
| Licence | Proprietary service under the AWS Customer Agreement and AWS Service Terms. The AWS SDK clients and the agent context package on GitHub are Apache-2.0 | Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Last release | 2026-08-17 | 2026-09-30 |
| Terms last updated | 2026-10-01 | no date given |
| Privacy policy last updated | 2026-05-18 | 2026-09-01 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | 427k npm/wk | 9.1k npm/wk, 25k PyPI/wk |