# Amazon Location Service vs Stadia Maps (slim)

> 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 & pricing, maintenance & community and transparency & trust. Both do geo geocode. Stadia Maps is cheaper for geo…

- Full: https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.md (~2,500 tokens) · this version ~780 tokens · JSON https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.json · canonical https://www.anchorterminal.com/compare/amazon-location-vs-stadia-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 Stadia Maps's 65.2 (B), and leads in 4 of 7 scored categories. Stadia Maps leads on payments & pricing, maintenance & community and transparency & trust. Both do geo geocode. Stadia Maps is cheaper for geo geocode, $0.40 against $0.50 per 1,000 requests.

- Amazon Location Service: BB 74.1, rank #68 of 722 · https://www.anchorterminal.com/tools/amazon-location.min.md
- Stadia Maps: B 65.2, rank #261 of 722 · https://www.anchorterminal.com/tools/stadia-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 63; Agent ergonomics, 88 against 80; Security & auth, 73 against 40. Also Agent-ready, a grade of BB or better.
- Stadia Maps, good for Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026. Ahead on Payments & pricing, 40 against 20; Maintenance & community, 80 against 60; Transparency & 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.

| Category | Amazon Location Service | Stadia Maps |
| --- | --- | --- |
| Reliability (16%) | 95 | 63 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 86 |
| Agent ergonomics (13%) | 88 | 80 |
| Security & auth (14%) | 73 | 40 |
| Payments & pricing (10%) | 20 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 60 | 80 |
| Transparency & trust (7%) | 70 | 76 |

| Fact (where they differ) | Amazon Location Service | Stadia Maps |
| --- | --- | --- |
| Vendor | Amazon Web Services | Stadia Maps |
| Hosted endpoint | `https://places.geo.us-east-1.amazonaws.com` | `https://api.stadiamaps.com` |
| Transports | HTTP | HTTP, stdio |
| Pricing | Pay per use | Freemium |
| Price for geo geocode | $0.50 per 1,000 requests | $0.40 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 | BSD-3-Clause (MCP server) |
| Tools exposed | none | 6 |
| Read-only variant documented | yes | no |
| Last release | 2026-08-17 | 2026-09-30 |
| Terms last updated | 2026-10-01 | 2026-03-18 |
| Privacy policy last updated | 2026-05-18 | 2026-10-01 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Popularity | 427k npm/wk | 23 stars, 6.1k npm/wk, 192 PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |