{ "data": { "a": { "slug": "amazon-location", "name": "Amazon Location Service", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/location/", "kind": "http-api", "category": "maps", "summary": "Amazon Location Service is AWS's API for geocoding, place search, routing and map tiles, with geofences and device tracking. Agents call regional REST endpoints with an API key or IAM credentials, or through the AWS SDKs and CLI.", "url": "https://www.anchorterminal.com/tools/amazon-location", "markdownUrl": "https://www.anchorterminal.com/tools/amazon-location.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/amazon-location.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/amazon-location.json", "repo": "https://github.com/aws-geospatial/amazon-location-agent-context", "license": "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", "transports": [ "http" ], "remoteUrl": "https://places.geo.us-east-1.amazonaws.com", "packages": [ { "registry": "npm", "name": "@aws-sdk/client-geo-places" }, { "registry": "npm", "name": "@aws-sdk/client-geo-routes" }, { "registry": "npm", "name": "@aws-sdk/client-geo-maps" }, { "registry": "pypi", "name": "boto3" } ], "auth": "api-key", "authNotes": "Access needs an AWS account. Maps, Places and Routes accept an Amazon Location API key in the `key` query parameter, created in the console, the CLI or the `CreateKey` call, limited to named actions and resources, with optional expiry and referrer or mobile app restrictions. Every API also accepts AWS Signature Version 4 with IAM credentials or a role, and Amazon Cognito identity pools for unauthenticated clients. Geofences, trackers and the Jobs API refuse API keys. API keys can't be used over AWS PrivateLink (https://docs.aws.amazon.com/location/latest/developerguide/using-apikeys.html).", "pricing": "usage", "pricingNotes": "Geocoding, reverse geocoding and place search cost $0.50 per 1,000 requests (core), $1.50 with advanced fields and $4.00 when results are stored, in US East (N. Virginia). Routes cost $0.50 per 1,000 for car, truck or pedestrian, map tiles $0.04 per 1,000. No sandbox or contract is needed, but an AWS account is. The pricing page lists monthly allowances for the first three months (20,000 core Places requests, 10,000 routes, 500,000 tiles) and up to $200 of credits for customers who joined after 15 July 2025. Volume discounts above $5,000 a month are by quote (https://aws.amazon.com/location/pricing/, checked 2026-10-08).", "priceSummary": "$0.50 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer guide's llms.txt, the service models or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 426988, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.aws.amazon.com/location/latest/developerguide/what-is.html", "llmsTxt": "https://docs.aws.amazon.com/location/latest/developerguide/llms.txt", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "closed-source", "python", "typescript", "enterprise", "llms-txt", "card-required", "sla", "status-page", "batch" ], "lastRelease": "2026-08-17", "graded": true, "anchor": { "graded": true, "score": 74.1, "grade": "BB", "agentReady": true, "rank": 68, "ranked": true, "rankOf": 722, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 88, "maintenance": 60, "payments": 20, "reliability": 95, "schema": 87, "security": 73, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "Operators already on AWS who want geocoding, places and routing inside IAM, CloudTrail and one bill, with HERE data and GrabMaps for Southeast Asia.", "strengths": [ "API keys are limited to named actions and resources, can expire, and can be restricted by referrer or mobile app identifier", "All 17 Places, Routes and Maps operations are marked read-only in the public Smithy models, with enums and numeric ranges on inputs", "Default rates are published per operation (100 a second for each Places call, 20 for `CalculateRoutes`) and can be doubled by self-service", "An SLA of 99.9 per cent monthly uptime per region, with credits of 10, 25 and 100 per cent", "llms.txt, a Markdown twin of every guide page and an Apache-2.0 agent context package (v1.2.0, 11 September 2026)" ], "weaknesses": [ "The API key is sent as the `key` query parameter, the only documented way to present it", "Storing or caching results is barred unless `IntendedUse` is `Storage`, billed at $4.00 per 1,000 against $0.50 for single use", "An AWS account opened by a person in a browser is needed before any call, and no keyless or machine-payment route exists", "The developer guide gives no backoff or `Retry-After` guidance for `ThrottlingException` (429)", "The guide's document history holds one entry, dated 31 October 2024, so API changes have to be read from the SDK models" ], "agentNotes": [ "Call the v2 endpoints (`places.geo.\u003cregion\u003e.amazonaws.com/v2/geocode`, `routes.geo`, `maps.geo`). They need no resource creation, unlike the v1 place index and route calculator calls", "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", "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", "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", "Back off on HTTP 429 `ThrottlingException`. The burst allowance is 80 per cent of the per-second rate within any part of a second" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 74.1 } ], "editorialScores": { "ergonomics": 88, "maintenance": 60, "payments": 20, "reliability": 95, "schema": 87, "security": 73, "transparency": 52 }, "provenanceScore": 88 }, "connect": { "install": "pip install boto3 # or: npm i @aws-sdk/client-geo-places", "http": "curl --request POST \\\n --url 'https://places.geo.eu-central-1.amazonaws.com/v2/geocode?key=Your_Key' \\\n --header 'Content-Type: application/json' \\\n --data '{\"QueryText\": \"510 W Georgia St, Vancouver, BC\"}'", "claudeCode": "/plugin install amazon-location-service@claude-plugins-official" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/amazon-location" }, "sameCompany": [ "amazon-bedrock-guardrails", "amazon-transcribe", "amazon-polly", "aws-secrets-manager", "aws-mcp-servers", "amazon-ses", "amazon-translate", "amazon-ads-api" ], "area": "everyday", "unitPrices": [ { "item": "Geocode, reverse geocode, place search (core)", "unit": "1k-requests", "usd": 0.5, "note": "US East. `SingleUse` results, not for storage" }, { "item": "Geocode, reverse geocode, place search (advanced)", "unit": "1k-requests", "usd": 1.5, "note": "With contacts, opening hours, access points or time zone" }, { "item": "Geocode, reverse geocode, place search (stored)", "unit": "1k-requests", "usd": 4, "note": "`IntendedUse` set to `Storage`" }, { "item": "Autocomplete and Suggest (label)", "unit": "1k-requests", "usd": 0.2 }, { "item": "Routes calculated (core)", "unit": "1k-requests", "usd": 0.5, "note": "Car, truck or pedestrian. A matrix bills origins times destinations" }, { "item": "Routes with toll cost (premium)", "unit": "1k-requests", "usd": 4 }, { "item": "Dynamic map tiles", "unit": "1k-requests", "usd": 0.04 }, { "item": "Static map images", "unit": "1k-requests", "usd": 0.5 } ], "provenance": { "legalEntity": "Amazon Web Services, Inc.", "domain": "amazon.com", "domainRegistered": "1994-11-01", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/service-terms/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/location/latest/developerguide/doc-history.html", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The AWS Service Terms (last updated 1 October 2026) govern the service, with Amazon Location Service at section 82. The AWS Customer Agreement sits above them.", "The AWS Privacy Notice (last updated 18 May 2026) names Amazon Web Services, Inc., 410 Terry Avenue North, Seattle, WA 98109-5210.", "The endpoints are on amazonaws.com and api.aws, both AWS domains.", "aws.amazon.com/.well-known/security.txt carries Expires 2026-09-24T16:25:03Z, which had passed on the day of the check. It points to a HackerOne disclosure programme.", "RDAP for amazon.com gives a registration date of 1994-11-01.", "The document history page has one entry, dated 31 October 2024. API changes are otherwise visible in AWS What's New posts and the SDK service models." ], "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/amazon-location.json", "live": { "slug": "amazon-location", "probe": { "target": "https://places.geo.us-east-1.amazonaws.com", "method": "get", "lastAt": "2026-10-08T21:53:15.033838513Z", "lastOk": true, "lastStatus": 404, "lastMs": 252, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 252, "p95ms24h": 307, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-08", "probes": 28, "ok": 28 } ] }, "updatedAt": "2026-10-08T21:53:15.033838513Z" } }, "answer": "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 \u0026 pricing.", "b": { "slug": "geoapify", "name": "Geoapify Location Platform + MCP", "vendor": "Geoapify", "vendorUrl": "https://www.geoapify.com", "kind": "http-api", "category": "maps", "summary": "Geocoding, reverse geocoding, autocomplete, Places search by category, Routing, Route Matrix, isolines and map tiles, with OpenStreetMap attribution required on every plan.", "url": "https://www.anchorterminal.com/tools/geoapify", "markdownUrl": "https://www.anchorterminal.com/tools/geoapify.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/geoapify.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/geoapify.json", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.geoapify.com/v1", "packages": [], "auth": "api-key", "authNotes": "API key as the apiKey query parameter or the x-api-key header, both defined in the OpenAPI specs. The hosted MCP takes x-api-key. api-eu.geoapify.com serves the same API on EU infrastructure.", "pricing": "freemium", "pricingNotes": "Free 3,000 credits a day at 5 requests a second, commercial and production use allowed, no card, with a Geoapify attribution link required. API 10 $59 a month (10,000 credits a day, 12 a second), API 25 $109 (25,000), API 50 $179 (50,000), API 100 $299 (100,000), API 250 $609 (250,000), Custom from $860. A simple geocoding, places or routing request costs 1 credit (https://www.geoapify.com/pricing/). Over MCP, initialize, tools/list and notifications cost nothing and each tools/call is billed as the Geoapify API operation behind it (https://apidocs.geoapify.com/how-to/api-tooling-ai/connect-ai-client-mcp/).", "priceSummary": "$59 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 11, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://apidocs.geoapify.com/docs", "openapi": "https://apidocs.geoapify.com/open-api/", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "official", "free-tier", "no-card", "open-data", "eu", "closed-source" ], "graded": true, "anchor": { "graded": true, "score": 55.3, "grade": "C", "agentReady": false, "rank": 510, "ranked": true, "rankOf": 722, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 61, "payments": 30, "reliability": 60, "schema": 74, "security": 29, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Free plan allows commercial production use, 3,000 credits a day, no card. No security.txt, disclosure policy, bug bounty or certification found.", "bestFor": "Cheap geocoding, category place search, routing and isolines on OpenStreetMap data, with commercial use on the free plan and EU hosting.", "strengths": [ "Free plan allows commercial production use, 3,000 credits a day, no card", "OpenAPI 3.1 specs for 22 APIs and one per MCP tool, with error examples", "Data for successful requests held no longer than 24 hours, hosted in the EU", "99.5 per cent monthly availability on paid plans, with discounts below it", "MCP tool descriptions say which tool to use instead" ], "weaknesses": [ "No security.txt, disclosure policy, bug bounty or certification found", "No public changelog or deprecation policy, and the terms allow changes without notice", "Storage rights appear in the docs but not in the terms", "The specs recommend the apiKey query parameter for public APIs", "Credits are counted per day, so bursts hit the cap early" ], "agentNotes": [ "Send the key as x-api-key, which the specs support, rather than apiKey in the URL", "Use api-eu.geoapify.com when the data has to stay on EU infrastructure", "Use calculate_route for geometry and directions, and calculate_route_matrix only for travel times between many points", "Read a 429 'Quota exceeded' as the day's credits being gone, not a burst, and wait for the daily reset", "Show OpenStreetMap attribution wherever you display results" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.3 } ], "editorialScores": { "ergonomics": 72, "maintenance": 61, "payments": 30, "reliability": 60, "schema": 74, "security": 29, "transparency": 52 }, "provenanceScore": 72 }, "connect": { "http": "curl \"https://api.geoapify.com/v1/geocode/search?text=10%20Downing%20Street%2C%20London\u0026limit=1\u0026format=json\u0026apiKey=$GEOAPIFY_API_KEY\"", "claudeCode": "claude mcp add --transport http geoapify https://api.geoapify.com/v1/mcp --header \"x-api-key: $GEOAPIFY_API_KEY\"", "config": { "mcpServers": { "geoapify": { "headers": { "x-api-key": "${GEOAPIFY_API_KEY}" }, "type": "http", "url": "https://api.geoapify.com/v1/mcp" } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/geoapify" }, "area": "everyday", "unitPrices": [ { "item": "API 10 plan", "unit": "month", "usd": 59, "note": "10,000 credits a day, 12 requests a second" }, { "item": "API 25 plan", "unit": "month", "usd": 109, "note": "25,000 credits a day" }, { "item": "API 100 plan", "unit": "month", "usd": 299, "note": "100,000 credits a day, 25 requests a second" }, { "item": "API 250 plan", "unit": "month", "usd": 609, "note": "250,000 credits a day" } ], "provenance": { "legalEntity": "KEPTAGO LTD", "domain": "geoapify.com", "domainRegistered": "2018-10-26", "endpointOnVendorDomain": true, "terms": "https://www.geoapify.com/terms-and-conditions/", "privacy": "https://www.geoapify.com/privacy-policy/", "statusPage": "https://status.geoapify.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-01", "notes": [ "The terms name KEPTAGO LTD, registered in Paphos, Cyprus, trading as Geoapify. Version 5, dated 2 February 2024.", "www.geoapify.com/.well-known/security.txt returns 404.", "status.geoapify.com redirects to an UptimeRobot status page.", "We found no public changelog. The OpenAPI specs repository on GitHub has dated commits.", "The privacy policy was last modified 1 April 2026." ], "score": 72 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/geoapify.json", "live": { "slug": "geoapify", "probe": { "target": "https://api.geoapify.com/v1", "method": "get", "lastAt": "2026-10-08T21:53:22.816450481Z", "lastOk": true, "lastStatus": 401, "lastMs": 124, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 122, "p95ms24h": 200, "samples24h": 270, "samples30d": 1962, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 246, "ok": 246 } ] }, "vendorStatus": { "page": "https://status.geoapify.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:38:35.319090337Z" }, "securityTxt": { "url": "https://geoapify.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:39:06.518497806Z" }, "domain": { "domain": "geoapify.com", "registered": "2018-10-26", "source": "https://rdap.verisign.com/com/v1/domain/geoapify.com", "checkedAt": "2026-10-04T13:07:12.953394282Z" }, "pages": [ { "url": "https://www.geoapify.com/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-10-08T18:27:52.214592435Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f9a9f1600f52" }, { "url": "https://www.geoapify.com/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-10-08T18:27:54.387212133Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "37eb22e1e50f" }, { "url": "https://www.geoapify.com/terms-and-conditions/", "kind": "terms", "status": 304, "checkedAt": "2026-10-08T18:27:56.317196709Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c5c95d7b727d" } ], "updatedAt": "2026-10-08T21:53:22.816450481Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Geoapify", "name": "Vendor" }, { "a": "https://places.geo.us-east-1.amazonaws.com", "b": "https://api.geoapify.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "$0.50 per 1,000 requests", "b": "not published", "name": "Price for geo geocode" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "none", "name": "Licence" }, { "a": "none", "b": "11", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-08-17", "b": "none", "name": "Last release" }, { "a": "2026-10-01", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "427k npm/wk", "b": "none", "name": "Popularity" }, { "a": "none", "b": "4/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "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 \u0026 pricing.", "question": "Which is better for AI agents, Amazon Location Service or Geoapify Location Platform + MCP?" }, { "answer": "Both need an API key.", "question": "Do Amazon Location Service and Geoapify Location Platform + MCP need an API key?" }, { "answer": "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.", "question": "Can an agent call Amazon Location Service and Geoapify Location Platform + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 95 against 60", "Schema \u0026 documentation, 87 against 74", "Agent ergonomics, 88 against 72", "Security \u0026 auth, 73 against 29", "Transparency \u0026 trust, 70 against 62" ], "also": [ "Agent-ready, a grade of BB or better" ], "goodFor": "Operators already on AWS who want geocoding, places and routing inside IAM, CloudTrail and one bill, with HERE data and GrabMaps for Southeast Asia.", "slug": "amazon-location", "watchFor": "The API key is sent as the `key` query parameter, the only documented way to present it" }, { "aheadOn": [ "Payments \u0026 pricing, 30 against 20" ], "also": [ "Free to start without a card" ], "goodFor": "Cheap geocoding, category place search, routing and isolines on OpenStreetMap data, with commercial use on the free plan and EU hosting.", "slug": "geoapify", "watchFor": "No security.txt, disclosure policy, bug bounty or certification found" } ], "job": { "capability": "geo.geocode", "name": "Geo geocode" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-arcgis.json", "title": "Amazon Location Service vs ArcGIS Location Platform", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-arcgis" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps.json", "title": "Amazon Location Service vs Azure Maps", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-google-maps-platform.json", "title": "Amazon Location Service vs Google Maps Platform + Grounding Lite MCP", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-google-maps-platform" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-locationiq.json", "title": "Amazon Location Service vs LocationIQ", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-locationiq" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-mapbox.json", "title": "Amazon Location Service vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-mapbox" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-mapquest.json", "title": "Amazon Location Service vs MapQuest", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-opencage.json", "title": "Amazon Location Service vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.json", "title": "Amazon Location Service vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.json", "title": "Amazon Location Service vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-geoapify.json", "title": "ArcGIS Location Platform vs Geoapify Location Platform + MCP", "url": "https://www.anchorterminal.com/compare/arcgis-vs-geoapify" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-geoapify.json", "title": "Azure Maps vs Geoapify Location Platform + MCP", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-geoapify" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-google-maps-platform.json", "title": "Geoapify Location Platform + MCP vs Google Maps Platform + Grounding Lite MCP", "url": "https://www.anchorterminal.com/compare/geoapify-vs-google-maps-platform" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-locationiq.json", "title": "Geoapify Location Platform + MCP vs LocationIQ", "url": "https://www.anchorterminal.com/compare/geoapify-vs-locationiq" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-mapbox.json", "title": "Geoapify Location Platform + MCP vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/geoapify-vs-mapbox" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-mapquest.json", "title": "Geoapify Location Platform + MCP vs MapQuest", "url": "https://www.anchorterminal.com/compare/geoapify-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-opencage.json", "title": "Geoapify Location Platform + MCP vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/geoapify-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps.json", "title": "Geoapify Location Platform + MCP vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom.json", "title": "Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom" } ], "scores": [ { "amazon-location": 95, "by": 35, "edge": "amazon-location", "geoapify": 60, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amazon-location": 87, "by": 13, "edge": "amazon-location", "geoapify": 74, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "amazon-location": 88, "by": 16, "edge": "amazon-location", "geoapify": 72, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "amazon-location": 73, "by": 44, "edge": "amazon-location", "geoapify": 29, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "amazon-location": 20, "by": 10, "edge": "geoapify", "geoapify": 30, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amazon-location": 60, "by": 1, "edge": "geoapify", "geoapify": 61, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "amazon-location": 70, "by": 8, "edge": "amazon-location", "geoapify": 62, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "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 \u0026 pricing. Both do geo geocode.", "verdicts": { "amazon-location": "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": "Free plan allows commercial production use, 3,000 credits a day, no card. No security.txt, disclosure policy, bug bounty or certification found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amazon-location-vs-geoapify", "json": "https://www.anchorterminal.com/compare/amazon-location-vs-geoapify.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amazon-location-vs-geoapify.md", "slim": "https://www.anchorterminal.com/compare/amazon-location-vs-geoapify.min.md" }, "markdown": "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 \u0026 pricing. Both do geo geocode.\n\n- Amazon Location Service: grade BB, 74.1/100, rank #68 of 722. Markdown https://www.anchorterminal.com/tools/amazon-location.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-location.json\n- Geoapify Location Platform + MCP: grade C, 55.3/100, rank #510 of 722. Markdown https://www.anchorterminal.com/tools/geoapify.md · JSON https://www.anchorterminal.com/api/v1/tools/geoapify.json\n\n## Which one, for what\n\n### Amazon Location Service (BB)\n\nGood 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.\n\nAhead on:\n- Reliability, 95 against 60\n- Schema \u0026 documentation, 87 against 74\n- Agent ergonomics, 88 against 72\n- Security \u0026 auth, 73 against 29\n- Transparency \u0026 trust, 70 against 62\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: The API key is sent as the `key` query parameter, the only documented way to present it\n\n### Geoapify Location Platform + MCP (C)\n\nGood for: Cheap geocoding, category place search, routing and isolines on OpenStreetMap data, with commercial use on the free plan and EU hosting.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 20\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No security.txt, disclosure policy, bug bounty or certification found\n\n\n## Score by category\n\n| Category | Weight | Amazon Location Service | Geoapify Location Platform + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 95 | 60 | Amazon Location Service +35 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 74 | Amazon Location Service +13 |\n| Agent ergonomics | 13% (16.2 this run) | 88 | 72 | Amazon Location Service +16 |\n| Security \u0026 auth | 14% (17.5 this run) | 73 | 29 | Amazon Location Service +44 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 30 | Geoapify Location Platform + MCP +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 61 | Geoapify Location Platform + MCP +1 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 62 | Amazon Location Service +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **74.1 · BB** | **55.3 · C** | |\n\n## Facts side by side\n\n| Fact | Amazon Location Service | Geoapify Location Platform + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Geoapify |\n| Hosted endpoint | `https://places.geo.us-east-1.amazonaws.com` | `https://api.geoapify.com/v1` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Freemium |\n| Price for geo geocode | $0.50 per 1,000 requests | not published |\n| x402 | no | no |\n| 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 | none |\n| Tools exposed | none | 11 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | no |\n| Last release | 2026-08-17 | none |\n| Terms last updated | 2026-10-01 | no date given |\n| Privacy policy last updated | 2026-05-18 | no date given |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 427k npm/wk | none |\n| Agent reviews | none | 4/5 (2) |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Amazon Location Service\n\n1. Call the v2 endpoints (`places.geo.\u003cregion\u003e.amazonaws.com/v2/geocode`, `routes.geo`, `maps.geo`). They need no resource creation, unlike the v1 place index and route calculator calls\n2. 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\n3. 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\n4. 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\n5. Back off on HTTP 429 `ThrottlingException`. The burst allowance is 80 per cent of the per-second rate within any part of a second\n\n### Geoapify Location Platform + MCP\n\n1. Send the key as x-api-key, which the specs support, rather than apiKey in the URL\n2. Use api-eu.geoapify.com when the data has to stay on EU infrastructure\n3. Use calculate_route for geometry and directions, and calculate_route_matrix only for travel times between many points\n4. Read a 429 'Quota exceeded' as the day's credits being gone, not a burst, and wait for the daily reset\n5. Show OpenStreetMap attribution wherever you display results\n\n## Questions\n\n### Which is better for AI agents, Amazon Location Service or Geoapify Location Platform + MCP?\n\nAmazon 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 \u0026 pricing.\n\n### Do Amazon Location Service and Geoapify Location Platform + MCP need an API key?\n\nBoth need an API key.\n\n### Can an agent call Amazon Location Service and Geoapify Location Platform + MCP without installing anything?\n\nYes. 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.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-location-vs-geoapify.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-location-vs-geoapify.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-location\", \"b\": \"geoapify\"}`. From a terminal: `anchor compare amazon-location geoapify`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-location.json and https://www.anchorterminal.com/api/v1/tools/geoapify.json\n\n## Other comparisons with Amazon Location Service or Geoapify Location Platform + MCP\n\n- [Amazon Location Service vs ArcGIS Location Platform](https://www.anchorterminal.com/compare/amazon-location-vs-arcgis.md)\n- [Amazon Location Service vs Azure Maps](https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps.md)\n- [Amazon Location Service vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/amazon-location-vs-google-maps-platform.md)\n- [Amazon Location Service vs LocationIQ](https://www.anchorterminal.com/compare/amazon-location-vs-locationiq.md)\n- [Amazon Location Service vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-mapbox.md)\n- [Amazon Location Service vs MapQuest](https://www.anchorterminal.com/compare/amazon-location-vs-mapquest.md)\n- [Amazon Location Service vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/amazon-location-vs-opencage.md)\n- [Amazon Location Service vs Stadia Maps](https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.md)\n- [Amazon Location Service vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.md)\n- [ArcGIS Location Platform vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/arcgis-vs-geoapify.md)\n- [Azure Maps vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-geoapify.md)\n- [Geoapify Location Platform + MCP vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/geoapify-vs-google-maps-platform.md)\n- [Geoapify Location Platform + MCP vs LocationIQ](https://www.anchorterminal.com/compare/geoapify-vs-locationiq.md)\n- [Geoapify Location Platform + MCP vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/geoapify-vs-mapbox.md)\n- [Geoapify Location Platform + MCP vs MapQuest](https://www.anchorterminal.com/compare/geoapify-vs-mapquest.md)\n- [Geoapify Location Platform + MCP vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/geoapify-vs-opencage.md)\n- [Geoapify Location Platform + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps.md)\n- [Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geoapify-vs-tomtom.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Amazon Location Service vs Geoapify Location Platform + MCP", "url": "" } ], "description": "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 \u0026 pricing. Both do geo geocode. Category scores, facts, verdicts and agent…", "facts": [ "Amazon Location Service BB 74.1", "Geoapify Location Platform + MCP C 55.3", "scores" ], "h1": "Amazon Location Service vs Geoapify Location Platform + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-amazon-location-vs-geoapify.png", "path": "/compare/amazon-location-vs-geoapify", "published": "2026-10-01", "section": "tools", "title": "Amazon Location Service vs Geoapify Location Platform + MCP", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-geoapify" }, "tokens": { "markdown": 2500, "slim": 780 }, "version": 1 }