# Amazon Location Service vs OpenCage Geocoding API (slim)

> Amazon Location Service scores 74.1 (BB) on agent readiness against OpenCage Geocoding API's 69.2 (B), and leads in 4 of 7 scored categories. OpenCage Geocoding API leads on payments & pricing, maintenance & community and transparency & trust. Both do geo geocode. Category…

- Full: https://www.anchorterminal.com/compare/amazon-location-vs-opencage.md (~2,500 tokens) · this version ~830 tokens · JSON https://www.anchorterminal.com/compare/amazon-location-vs-opencage.json · canonical https://www.anchorterminal.com/compare/amazon-location-vs-opencage
- 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 OpenCage Geocoding API's 69.2 (B), and leads in 4 of 7 scored categories. OpenCage Geocoding API leads on payments & pricing, maintenance & community and transparency & trust. Both do geo geocode.

- Amazon Location Service: BB 74.1, rank #68 of 722 · https://www.anchorterminal.com/tools/amazon-location.min.md
- OpenCage Geocoding API: B 69.2, rank #164 of 722 · https://www.anchorterminal.com/tools/opencage.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 85; Schema & documentation, 87 against 77; Security & auth, 73 against 47. Also Agent-ready, a grade of BB or better.
- OpenCage Geocoding API, good for Bulk or repeated geocoding where results go into a database, and for EU data residency. Ahead on Payments & pricing, 35 against 20; Maintenance & community, 66 against 60; Transparency & trust, 84 against 70. Also Runs on your own machine; Free to start without a card.

| Category | Amazon Location Service | OpenCage Geocoding API |
| --- | --- | --- |
| Reliability (16%) | 95 | 85 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 77 |
| Agent ergonomics (13%) | 88 | 86 |
| Security & auth (14%) | 73 | 47 |
| Payments & pricing (10%) | 20 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 60 | 66 |
| Transparency & trust (7%) | 70 | 84 |

| Fact (where they differ) | Amazon Location Service | OpenCage Geocoding API |
| --- | --- | --- |
| Vendor | Amazon Web Services | OpenCage |
| Hosted endpoint | `https://places.geo.us-east-1.amazonaws.com` | `https://api.opencagedata.com/geocode/v1/json` |
| Transports | HTTP | HTTP, stdio |
| Pricing | Pay per use | Paid |
| Price for geo geocode | $0.50 per 1,000 requests | not published |
| 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) |
| Tools exposed | none | 3 |
| Read-only variant documented | yes | no |
| MCP registry | not listed | `io.github.OpenCageData/opencage-geocoding-mcp` |
| Last release | 2026-08-17 | 2026-06-25 |
| Terms last updated | 2026-10-01 | no date given |
| Privacy policy last updated | 2026-05-18 | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | 427k npm/wk | 19 stars, 5.5k npm/wk, 138k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |