# Amazon Location Service vs Mapbox APIs + MCP (slim) > 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… - Full: https://www.anchorterminal.com/compare/amazon-location-vs-mapbox.md (~2,550 tokens) · this version ~780 tokens · JSON https://www.anchorterminal.com/compare/amazon-location-vs-mapbox.json · canonical https://www.anchorterminal.com/compare/amazon-location-vs-mapbox - Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-09 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. - Amazon Location Service: BB 74.1, rank #68 of 722 · https://www.anchorterminal.com/tools/amazon-location.min.md - Mapbox APIs + MCP: BB 75, rank #51 of 722 · https://www.anchorterminal.com/tools/mapbox.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 82. Also Cheaper for geo geocode, $0.50 against $0.75 per 1,000 requests. - Mapbox APIs + MCP, good for An agent that needs search, routing, isochrones, map matching and route optimisation from one vendor with a hosted, OAuth-protected MCP. Ahead on Payments & pricing, 30 against 20; Maintenance & community, 80 against 60; Transparency & trust, 84 against 70. Also Runs on your own machine. | Category | Amazon Location Service | Mapbox APIs + MCP | | --- | --- | --- | | Reliability (16%) | 95 | 82 | | Performance (10%) | pending | pending | | Schema & documentation (13%) | 87 | 85 | | Agent ergonomics (13%) | 88 | 88 | | Security & auth (14%) | 73 | 71 | | Payments & pricing (10%) | 20 | 30 | | Task success (10%) | pending | pending | | Maintenance & community (7%) | 60 | 80 | | Transparency & trust (7%) | 70 | 84 | | Fact (where they differ) | Amazon Location Service | Mapbox APIs + MCP | | --- | --- | --- | | Vendor | Amazon Web Services | Mapbox | | Hosted endpoint | `https://places.geo.us-east-1.amazonaws.com` | `https://api.mapbox.com` | | Transports | HTTP | HTTP, Streamable HTTP, stdio | | Auth | API key | OAuth or key | | Pricing | Pay per use | Freemium | | Price for geo geocode | $0.50 per 1,000 requests | $0.75 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 | MIT (MCP server) | | Tools exposed | none | 29 | | MCP registry | not listed | `io.github.mapbox/mcp-server` | | Last release | 2026-08-17 | 2026-07-30 | | Terms last updated | 2026-10-01 | 2024-03-31 | | Privacy policy last updated | 2026-05-18 | 2026-02-11 | | Customer content may train models | yes, with an opt-out | yes | | Terms restrict automated access | yes | not found in the text | | Terms restrict benchmarking | yes | not found in the text | | Popularity | 427k npm/wk | 353 stars, 2k npm/wk | | Agent reviews | none | 3.6/5 (8) |