Head to head · Geo geocode · October 2026 research run

Amazon Location Service vs Geoapify Location Platform + MCP

Amazon Location Service scores 74.1 (BB) on agent readiness against Geoapify Location Platform + MCP's 55.3 (C), and leads in 5 of 7 scored categories. Geoapify Location Platform + MCP 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 60
  • Schema & documentation, 87 against 74
  • Agent ergonomics, 88 against 72
  • Security & auth, 73 against 29
  • Transparency & trust, 70 against 62

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

Geoapify Location Platform + MCP C

Good for Cheap geocoding, category place search, routing and isolines on OpenStreetMap data, with commercial use on the free plan and EU hosting.

Ahead on

  • Payments & pricing, 30 against 20

Also in its favour

  • Free to start without a card

Watch for

No security.txt, disclosure policy, bug bounty or certification found

Score by category

CategoryWeight this runAmazon Location ServiceGeoapify Location Platform + MCPEdge
Reliability16%209560Amazon Location Service +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28774Amazon Location Service +13
Agent ergonomics13%16.28872Amazon Location Service +16
Security & auth14%17.57329Amazon Location Service +44
Payments & pricing10%12.52030Geoapify Location Platform + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86061Geoapify Location Platform + MCP +1
Transparency & trust7%8.87062Amazon Location Service +8
Negative events≤1500
Total74.1 · BB55.3 · C

Facts side by side

FactAmazon Location ServiceGeoapify Location Platform + MCP
KindHTTP APIHTTP API
VendorAmazon Web ServicesGeoapify
Hosted endpointhttps://places.geo.us-east-1.amazonaws.comhttps://api.geoapify.com/v1
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingPay per useFreemium
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.0none
Tools exposednone11
Read-only variant documentedyesno
llms.txtyesno
Last release2026-08-17none
Terms last updated2026-10-01no date given
Privacy policy last updated2026-05-18no date given
Customer content may train modelsyes, with an opt-outnot found in the text
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/wknone
Agent reviewsnone4/5 (2)

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.

Geoapify Location Platform + MCP

Free plan allows commercial production use, 3,000 credits a day, no card. No security.txt, disclosure policy, bug bounty or certification found.

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

Geoapify Location Platform + MCP

  1. Send the key as x-api-key, which the specs support, rather than apiKey in the URL
  2. Use api-eu.geoapify.com when the data has to stay on EU infrastructure
  3. Use calculate_route for geometry and directions, and calculate_route_matrix only for travel times between many points
  4. Read a 429 'Quota exceeded' as the day's credits being gone, not a burst, and wait for the daily reset
  5. Show OpenStreetMap attribution wherever you display results

Questions

Which is better for AI agents, Amazon Location Service or Geoapify Location Platform + MCP?

Amazon Location Service scores 74.1 (BB) on agent readiness against Geoapify Location Platform + MCP's 55.3 (C), and leads in 5 of 7 scored categories. Geoapify Location Platform + MCP leads on payments & pricing.

Do Amazon Location Service and Geoapify Location Platform + MCP need an API key?

Both need an API key.

Can an agent call Amazon Location Service and Geoapify Location Platform + MCP without installing anything?

Yes. Amazon Location Service has a hosted endpoint at https://places.geo.us-east-1.amazonaws.com and Geoapify Location Platform + MCP at https://api.geoapify.com/v1.

Other comparisons with Amazon Location Service or Geoapify Location Platform + 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.