Head to head · Geo geocode · October 2026 research run

Amazon Location Service vs MapQuest

Amazon Location Service scores 74.1 (BB) on agent readiness against MapQuest's 35.1 (F), and leads in 6 of 7 scored categories. MapQuest leads on payments & pricing. Both do geo geocode.

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 23
  • Schema & documentation, 87 against 47
  • Agent ergonomics, 88 against 60
  • Security & auth, 73 against 28
  • Maintenance & community, 60 against 23
  • Transparency & trust, 70 against 28

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

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

MapQuest F

Good for An agent that needs US-centred geocoding, routing with truck profiles, traffic and place search behind one account, with an MCP server ready to connect.

Ahead on

  • Payments & pricing, 30 against 20

Watch for

No API terms of service found. The legal link leads to System1's 2021 website terms, which allow personal, non-commercial use only

Score by category

CategoryWeight this runAmazon Location ServiceMapQuestEdge
Reliability16%209523Amazon Location Service +72
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28747Amazon Location Service +40
Agent ergonomics13%16.28860Amazon Location Service +28
Security & auth14%17.57328Amazon Location Service +45
Payments & pricing10%12.52030MapQuest +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86023Amazon Location Service +37
Transparency & trust7%8.87028Amazon Location Service +42
Negative events≤1500
Total74.1 · BB35.1 · F

Facts side by side

FactAmazon Location ServiceMapQuest
KindHTTP APIHTTP API
VendorAmazon Web ServicesMapQuest (System1)
Hosted endpointhttps://places.geo.us-east-1.amazonaws.comhttps://www.mapquestapi.com
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPay per usePay per use
Price for geo geocode$0.50 per 1,000 requestsnot published
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.0Proprietary service. No API terms were found published without a login
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-08-172026-07-16
Terms last updated2026-10-01no document linked
Privacy policy last updated2026-05-18no document linked
Customer content may train modelsyes, with an opt-out
Terms restrict automated accessyes
Terms restrict benchmarkingyes
Terms or service can change without noticeyes
Arbitration or class-action waivernot found in the text
Popularity427k npm/wknone

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.

MapQuest

One account reaches geocoding, routing, place search and traffic through a REST API or a hosted MCP server with OAuth, at a published $0.0045 a transaction. No API terms, status page, changelog or product OpenAPI spec was found, and REST keys travel in the query string.

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

MapQuest

  1. Register an account and create an API key before connecting the MCP server. Every tool needs an active key, chosen by nickname on first use
  2. Send REST calls to https://www.mapquestapi.com with key in the query string, and redact it from logged URLs
  3. Read info.statuscode in geocoding and directions responses. 0 is success, and errors such as 610 (ambiguous location) arrive in the body
  4. Set thumbMaps=false and maxResults on geocoding, and pageSize (1 to 50) on place search, to keep responses small
  5. Do not store or cache geocodes on a monthly or pay-as-you-go plan

Questions

Which is better for AI agents, Amazon Location Service or MapQuest?

Amazon Location Service scores 74.1 (BB) on agent readiness against MapQuest's 35.1 (F), and leads in 6 of 7 scored categories. MapQuest leads on payments & pricing.

Do Amazon Location Service and MapQuest need an API key?

Amazon Location Service needs an API key. MapQuest takes an API key or an OAuth sign-in.

Can an agent call Amazon Location Service and MapQuest without installing anything?

Yes. Amazon Location Service has a hosted endpoint at https://places.geo.us-east-1.amazonaws.com and MapQuest at https://www.mapquestapi.com.

Other comparisons with Amazon Location Service or MapQuest

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.