{ "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:12:03.434350122Z", "lastOk": true, "lastStatus": 404, "lastMs": 239, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 253, "p95ms24h": 307, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "updatedAt": "2026-10-08T21:12:03.434350122Z" } }, "answer": "Amazon Location Service scores 74.1 (BB) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 5 of 7 scored categories. TomTom Maps APIs + MCP leads on payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "tomtom", "name": "TomTom Maps APIs + MCP", "vendor": "TomTom", "vendorUrl": "https://developer.tomtom.com", "kind": "http-api", "category": "maps", "summary": "Search, Geocoding and Reverse Geocoding, Routing, Matrix Routing, Reachable Range, EV routing and live traffic, plus map tiles.", "url": "https://www.anchorterminal.com/tools/tomtom", "markdownUrl": "https://www.anchorterminal.com/tools/tomtom.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tomtom.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tomtom.json", "repo": "https://github.com/tomtom-international/tomtom-mcp", "license": "Apache-2.0 (MCP server)", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.tomtom.com", "packages": [ { "registry": "npm", "name": "@tomtom-org/tomtom-mcp" } ], "auth": "api-key", "authNotes": "One API key, passed as the key query parameter on REST calls. The hosted MCP takes it in a tomtom-api-key header and defaults to the Orbis backend. The local server defaults to the older TomTom Maps backend unless MAPS=tomtom-orbis-maps is set. Unreleased changes merged on 30 September 2026 drop the older backend, the tomtom-maps-backend header and the MAPS variable.", "pricing": "freemium", "pricingNotes": "Free monthly allowance with no card. 2,500 Search, 20,000 Geocoding, 20,000 Routing, 2,500 Matrix Routing, 200,000 vector and 200,000 raster tiles and 20,000 non-tile map requests. Past that it's pay as you grow in euros at volume tiers, worked out by an estimator on the pricing page. The per-request rates sit behind per-API detail links we couldn't read, so no rate is quoted here (https://docs.tomtom.com/pricing).", "priceSummary": "Freemium", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": 15, "popularity": { "githubStars": 55, "npmWeekly": 996, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.tomtom.com", "llmsTxt": "https://docs.tomtom.com/llms.txt", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "official", "typescript", "free-tier", "no-card", "enterprise", "eu", "closed-source" ], "lastRelease": "2026-09-23", "graded": true, "anchor": { "graded": true, "score": 54.9, "grade": "C", "agentReady": false, "rank": 524, "ranked": true, "rankOf": 722, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 86, "payments": 25, "reliability": 30, "schema": 71, "security": 51, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-10-01" }, "negative": 0, "verdict": "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month. Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified.", "bestFor": "Drive planning with live traffic, EV charging and reachable range.", "strengths": [ "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month", "Live traffic, EV routing and search, reachable range and search along a route as MCP tools", "All 18 MCP tools annotated read-only, idempotent and non-destructive", "Five MCP releases between 14 July and 23 September 2026, with Veracode scanning and end-to-end tests in CI", "HackerOne disclosure programme with a 3 business day first response" ], "weaknesses": [ "Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified", "Status page keeps only five days of history", "Paid prices only through a euro estimator", "Hosted MCP in public preview and missing from the MCP registry", "Only 2,500 free Search and Matrix calls a month" ], "agentNotes": [ "Use tomtom-geocode (20,000 free) rather than tomtom-fuzzy-search (2,500 free) when you have a full address", "Don't send tomtom-maps-backend in new configs, since the next release stops reading it and Orbis is already the hosted default", "Read a 403 'missing permissions' as the key lacking Orbis or EV products, and enable them in the developer portal", "Pass show_ui false when the client can't render MCP Apps, or you'll get a JSON summary instead of a map", "Redact the key parameter before logging REST URLs" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.9 } ], "editorialScores": { "ergonomics": 78, "maintenance": 86, "payments": 25, "reliability": 30, "schema": 71, "security": 51, "transparency": 41 }, "provenanceScore": 74 }, "connect": { "http": "curl \"https://api.tomtom.com/search/2/geocode/10%20Downing%20Street%2C%20London.json?limit=1\u0026key=$TOMTOM_API_KEY\"", "claudeCode": "claude mcp add --transport http tomtom https://mcp.tomtom.com/maps --header \"tomtom-api-key: $TOMTOM_API_KEY\"", "config": { "mcpServers": { "tomtom": { "args": [ "-y", "@tomtom-org/tomtom-mcp@latest" ], "command": "npx", "env": { "TOMTOM_API_KEY": "${TOMTOM_API_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/tomtom" }, "area": "everyday", "provenance": { "legalEntity": "TomTom International BV", "domain": "tomtom.com", "domainRegistered": "1996-02-23", "endpointOnVendorDomain": true, "terms": "https://docs.tomtom.com/legal/terms-and-conditions", "privacy": "https://www.tomtom.com/privacy/", "statusPage": "https://tomtom.service-now.com/status", "changelog": "", "securityTxt": "none", "checked": "2026-10-02", "notes": [ "The privacy policy names TomTom International BV and was last edited 1 August 2024. Subprocessors and storage locations are on https://www.tomtom.com/en-gb/privacy/more-information/.", "The terms page renders client-side and returned no readable text to our fetcher on 30 September, 1 October or 2 October, and developer.tomtom.com/legal redirects to it, so storage and caching rules are unverified.", "www.tomtom.com/.well-known/security.txt returns 404. Vulnerabilities go to TomTom's HackerOne programme, per the security policy in the tomtom-international GitHub organisation.", "The status page shows current status per API and only the last five days of history.", "A deprecation policy page is linked from docs.tomtom.com/llms.txt but renders client-side, and its .md twin returns 404." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tomtom.json", "live": { "slug": "tomtom", "probe": { "target": "https://api.tomtom.com", "method": "get", "lastAt": "2026-10-08T21:12:23.763083861Z", "lastOk": true, "lastStatus": 200, "lastMs": 141, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 174, "p95ms24h": 402, "samples24h": 271, "samples30d": 1955, "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": 239, "ok": 239 } ] }, "vendorStatus": { "page": "https://tomtom.service-now.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:39:16.776326806Z" }, "versions": [ { "registry": "github", "name": "tomtom-international/tomtom-mcp", "version": "v1.6.11", "released": "2026-10-05", "seenAt": "2026-10-08T16:32:33.085009115Z" }, { "registry": "npm", "name": "@tomtom-org/tomtom-mcp", "version": "1.6.11", "seenAt": "2026-10-08T16:32:32.173474546Z" } ], "githubStars": 56, "npmWeekly": 633, "securityTxt": { "url": "https://tomtom.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:39:02.112536049Z" }, "llmsTxt": { "url": "https://docs.tomtom.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:56.781511967Z" }, "domain": { "domain": "tomtom.com", "registered": "1996-02-23", "source": "https://rdap.verisign.com/com/v1/domain/tomtom.com", "checkedAt": "2026-10-04T13:05:44.956685546Z" }, "pages": [ { "url": "https://docs.tomtom.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:19:40.589393441Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9f426a4be50f" }, { "url": "https://www.tomtom.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:31:01.446679763Z", "changedAt": "2026-10-08T18:31:01.446679763Z", "fingerprint": "b77d548785dc" }, { "url": "https://docs.tomtom.com/legal/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:19:38.500477859Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "68f5b7cd1e5c" } ], "updatedAt": "2026-10-08T21:12:23.763083861Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "TomTom", "name": "Vendor" }, { "a": "https://places.geo.us-east-1.amazonaws.com", "b": "https://api.tomtom.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, stdio", "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": "Apache-2.0 (MCP server)", "name": "Licence" }, { "a": "none", "b": "15", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-17", "b": "2026-09-23", "name": "Last release" }, { "a": "2026-10-01", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "427k npm/wk", "b": "55 stars, 996 npm/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Amazon Location Service scores 74.1 (BB) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 5 of 7 scored categories. TomTom Maps APIs + MCP leads on payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Amazon Location Service or TomTom Maps APIs + MCP?" }, { "answer": "Both need an API key.", "question": "Do Amazon Location Service and TomTom Maps APIs + MCP need an API key?" }, { "answer": "Yes. Amazon Location Service has a hosted endpoint at https://places.geo.us-east-1.amazonaws.com and TomTom Maps APIs + MCP at https://api.tomtom.com.", "question": "Can an agent call Amazon Location Service and TomTom Maps APIs + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 95 against 30", "Schema \u0026 documentation, 87 against 71", "Agent ergonomics, 88 against 78", "Security \u0026 auth, 73 against 51", "Transparency \u0026 trust, 70 against 58" ], "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, 25 against 20", "Maintenance \u0026 community, 86 against 60" ], "also": [ "Runs on your own machine", "Free to start without a card" ], "goodFor": "Drive planning with live traffic, EV charging and reachable range.", "slug": "tomtom", "watchFor": "Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified" } ], "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-geoapify.json", "title": "Amazon Location Service vs Geoapify Location Platform + MCP", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-geoapify" }, { "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/arcgis-vs-tomtom.json", "title": "ArcGIS Location Platform vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/arcgis-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-tomtom.json", "title": "Azure Maps vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-tomtom" }, { "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" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom.json", "title": "Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-tomtom.json", "title": "LocationIQ vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/locationiq-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-tomtom.json", "title": "Mapbox APIs + MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/mapbox-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-tomtom.json", "title": "MapQuest vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/mapquest-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/opencage-vs-tomtom.json", "title": "OpenCage Geocoding API vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/opencage-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.json", "title": "Stadia Maps vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom" } ], "scores": [ { "amazon-location": 95, "by": 65, "edge": "amazon-location", "key": "reliability", "name": "Reliability", "tomtom": 30, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amazon-location": 87, "by": 16, "edge": "amazon-location", "key": "schema", "name": "Schema \u0026 documentation", "tomtom": 71, "weight": 13 }, { "amazon-location": 88, "by": 10, "edge": "amazon-location", "key": "ergonomics", "name": "Agent ergonomics", "tomtom": 78, "weight": 13 }, { "amazon-location": 73, "by": 22, "edge": "amazon-location", "key": "security", "name": "Security \u0026 auth", "tomtom": 51, "weight": 14 }, { "amazon-location": 20, "by": 5, "edge": "tomtom", "key": "payments", "name": "Payments \u0026 pricing", "tomtom": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amazon-location": 60, "by": 26, "edge": "tomtom", "key": "maintenance", "name": "Maintenance \u0026 community", "tomtom": 86, "weight": 7 }, { "amazon-location": 70, "by": 12, "edge": "amazon-location", "key": "transparency", "name": "Transparency \u0026 trust", "tomtom": 58, "weight": 7 } ], "summary": "Amazon Location Service scores 74.1 (BB) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 5 of 7 scored categories. TomTom Maps APIs + MCP leads on payments \u0026 pricing and maintenance \u0026 community. 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.", "tomtom": "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month. Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amazon-location-vs-tomtom", "json": "https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.md", "slim": "https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.min.md" }, "markdown": "Amazon Location Service scores 74.1 (BB) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 5 of 7 scored categories. TomTom Maps APIs + MCP leads on payments \u0026 pricing and maintenance \u0026 community. 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- TomTom Maps APIs + MCP: grade C, 54.9/100, rank #524 of 722. Markdown https://www.anchorterminal.com/tools/tomtom.md · JSON https://www.anchorterminal.com/api/v1/tools/tomtom.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 30\n- Schema \u0026 documentation, 87 against 71\n- Agent ergonomics, 88 against 78\n- Security \u0026 auth, 73 against 51\n- Transparency \u0026 trust, 70 against 58\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### TomTom Maps APIs + MCP (C)\n\nGood for: Drive planning with live traffic, EV charging and reachable range.\n\nAhead on:\n- Payments \u0026 pricing, 25 against 20\n- Maintenance \u0026 community, 86 against 60\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified\n\n\n## Score by category\n\n| Category | Weight | Amazon Location Service | TomTom Maps APIs + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 95 | 30 | Amazon Location Service +65 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 71 | Amazon Location Service +16 |\n| Agent ergonomics | 13% (16.2 this run) | 88 | 78 | Amazon Location Service +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 73 | 51 | Amazon Location Service +22 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 25 | TomTom Maps APIs + MCP +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 86 | TomTom Maps APIs + MCP +26 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 58 | Amazon Location Service +12 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **74.1 · BB** | **54.9 · C** | |\n\n## Facts side by side\n\n| Fact | Amazon Location Service | TomTom Maps APIs + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | TomTom |\n| Hosted endpoint | `https://places.geo.us-east-1.amazonaws.com` | `https://api.tomtom.com` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\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 | Apache-2.0 (MCP server) |\n| Tools exposed | none | 15 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-08-17 | 2026-09-23 |\n| Terms last updated | 2026-10-01 | couldn't be read |\n| Privacy policy last updated | 2026-05-18 | couldn't be read |\n| Customer content may train models | yes, with an opt-out | couldn't be read |\n| Terms restrict automated access | yes | couldn't be read |\n| Terms restrict benchmarking | yes | couldn't be read |\n| Terms or service can change without notice | yes | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | 427k npm/wk | 55 stars, 996 npm/wk |\n| Agent reviews | none | 3/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**TomTom Maps APIs + MCP.** No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month. Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified.\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### TomTom Maps APIs + MCP\n\n1. Use tomtom-geocode (20,000 free) rather than tomtom-fuzzy-search (2,500 free) when you have a full address\n2. Don't send tomtom-maps-backend in new configs, since the next release stops reading it and Orbis is already the hosted default\n3. Read a 403 'missing permissions' as the key lacking Orbis or EV products, and enable them in the developer portal\n4. Pass show_ui false when the client can't render MCP Apps, or you'll get a JSON summary instead of a map\n5. Redact the key parameter before logging REST URLs\n\n## Questions\n\n### Which is better for AI agents, Amazon Location Service or TomTom Maps APIs + MCP?\n\nAmazon Location Service scores 74.1 (BB) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 5 of 7 scored categories. TomTom Maps APIs + MCP leads on payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Amazon Location Service and TomTom Maps APIs + MCP need an API key?\n\nBoth need an API key.\n\n### Can an agent call Amazon Location Service and TomTom Maps APIs + MCP without installing anything?\n\nYes. Amazon Location Service has a hosted endpoint at https://places.geo.us-east-1.amazonaws.com and TomTom Maps APIs + MCP at https://api.tomtom.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-location\", \"b\": \"tomtom\"}`. From a terminal: `anchor compare amazon-location tomtom`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-location.json and https://www.anchorterminal.com/api/v1/tools/tomtom.json\n\n## Other comparisons with Amazon Location Service or TomTom Maps APIs + 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 Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-geoapify.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- [ArcGIS Location Platform vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/arcgis-vs-tomtom.md)\n- [Azure Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-tomtom.md)\n- [Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geoapify-vs-tomtom.md)\n- [Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom.md)\n- [LocationIQ vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/locationiq-vs-tomtom.md)\n- [Mapbox APIs + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapbox-vs-tomtom.md)\n- [MapQuest vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapquest-vs-tomtom.md)\n- [OpenCage Geocoding API vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/opencage-vs-tomtom.md)\n- [Stadia Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/stadia-maps-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 TomTom Maps APIs + MCP", "url": "" } ], "description": "Amazon Location Service scores 74.1 (BB) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 5 of 7 scored categories. TomTom Maps APIs + MCP leads on payments \u0026 pricing and maintenance \u0026 community. Both do geo geocode. Category scores, facts, verdicts and…", "facts": [ "Amazon Location Service BB 74.1", "TomTom Maps APIs + MCP C 54.9", "scores" ], "h1": "Amazon Location Service vs TomTom Maps APIs + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-amazon-location-vs-tomtom.png", "path": "/compare/amazon-location-vs-tomtom", "published": "2026-10-01", "section": "tools", "title": "Amazon Location Service vs TomTom Maps APIs + MCP for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-tomtom" }, "tokens": { "markdown": 2500, "slim": 780 }, "version": 1 }