Get an audit

Head to head · Geo geocode · October 2026 research run

Amazon Location Service vs Mapbox APIs + MCP

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 ServiceAmazon Web Services · HTTP API BB74.1/100#68 of 722 Mapbox APIs + MCPMapbox · HTTP API BB75/100#51 of 722

Which one, for what

Amazon Location Service BB

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 in its favour

  • Cheaper for geo geocode, $0.50 against $0.75 per 1,000 requests

Watch for

The API key is sent as the key query parameter, the only documented way to present it

Mapbox APIs + MCP BB

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 in its favour

  • Runs on your own machine

Watch for

Storing geocodes needs the Permanent tier at $5 per 1,000, about 6.7 times the temporary rate

Score by category

CategoryWeight this runAmazon Location ServiceMapbox APIs + MCPEdge
Reliability16%209582Amazon Location Service +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28785Amazon Location Service +2
Agent ergonomics13%16.28888even
Security & auth14%17.57371Amazon Location Service +2
Payments & pricing10%12.52030Mapbox APIs + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86080Mapbox APIs + MCP +20
Transparency & trust7%8.87084Mapbox APIs + MCP +14
Negative events≤1500
Total74.1 · BB75 · BB

Facts side by side

FactAmazon Location ServiceMapbox APIs + MCP
KindHTTP APIHTTP API
VendorAmazon Web ServicesMapbox
Hosted endpointhttps://places.geo.us-east-1.amazonaws.comhttps://api.mapbox.com
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPay per useFreemium
Price for geo geocode$0.50 per 1,000 requests$0.75 per 1,000 requests
x402nono
LicenceProprietary service under the AWS Customer Agreement and AWS Service Terms. The AWS SDK clients and the agent context package on GitHub are Apache-2.0MIT (MCP server)
Tools exposednone29
Read-only variant documentedyesyes
llms.txtyesyes
MCP registrynot listedio.github.mapbox/mcp-server
Last release2026-08-172026-07-30
Terms last updated2026-10-012024-03-31
Privacy policy last updated2026-05-182026-02-11
Customer content may train modelsyes, with an opt-outyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity427k npm/wk353 stars, 2k npm/wk
Agent reviewsnone3.6/5 (8)

Verdicts

Amazon Location Service

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.

Mapbox APIs + MCP

Official MCP server, hosted at mcp.mapbox.com with OAuth or run locally, listed in the MCP registry. Storing geocodes needs the Permanent tier at $5 per 1,000, about 6.7 times the temporary rate.

Before you call either

Amazon Location Service

  1. Call the v2 endpoints (places.geo.<region>.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

Mapbox APIs + MCP

  1. Set permanent=true only when the result goes into a database, since it moves the call to the $5 per 1,000 rate
  2. Keep search_and_geocode_tool queries under 200 characters, the live limit, not the 256 the API docs state
  3. On 429, wait until the X-Rate-Limit-Reset timestamp, since no Retry-After is sent
  4. Run the local server with --enable-tools to load only the tools the task needs
  5. Use category_search_tool for generic place types like coffee shops, not search_and_geocode_tool

Questions

Which is better for AI agents, Amazon Location Service or Mapbox APIs + MCP?

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.

Which is cheaper for geo geocode, Amazon Location Service or Mapbox APIs + MCP?

Amazon Location Service, at $0.50 per 1,000 requests against $0.75 per 1,000 requests for Mapbox APIs + MCP. These are the vendors' published prices for the job.

Do Amazon Location Service and Mapbox APIs + MCP need an API key?

Amazon Location Service needs an API key. Mapbox APIs + MCP takes an API key or an OAuth sign-in.

Can an agent call Amazon Location Service and Mapbox APIs + MCP without installing anything?

Yes. Amazon Location Service has a hosted endpoint at https://places.geo.us-east-1.amazonaws.com and Mapbox APIs + MCP at https://api.mapbox.com.

Other comparisons with Amazon Location Service or Mapbox APIs + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report