{ "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", "dns": "amazon-location.grade.anchorterminal.com", "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", "free-tier", "no-card", "sla", "status-page", "batch" ], "lastRelease": "2026-08-17", "graded": true, "anchor": { "graded": true, "score": 76.5, "grade": "BB", "agentReady": true, "rank": 43, "ranked": true, "rankOf": 1510, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 88, "maintenance": 60, "payments": 30, "reliability": 95, "schema": 87, "security": 76, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-11-01" }, "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", "AWS's sub-processor list names the map data providers (Esri, Grab, HERE) and where each processes requests" ], "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": 4, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 76.5 } ], "editorialScores": { "ergonomics": 88, "maintenance": 60, "payments": 30, "reliability": 95, "schema": 87, "security": 76, "transparency": 60 }, "provenanceScore": 94, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-10-17", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "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", "amazon-nova-embeddings", "amazon-bedrock-guardrails", "amazon-transcribe", "amazon-polly", "amazon-nova-sonic", "agentcore-memory", "agentcore-identity", "aws-secrets-manager", "agentcore-web-search", "aws-mcp-servers", "amazon-ses", "amazon-translate", "amazon-ads-api", "amazon-creators-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": "valid", "checked": "2026-11-01", "notes": [ "The AWS Service Terms (last updated 30 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, re-read on 1 November) 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 2027-10-16T16:25:03.000Z on 2026-11-01. It points to the AWS VDP at vdp.aws.security and HackerOne.", "RDAP for amazon.com gives a registration date of 1994-11-01 (per the 17 October check).", "The document history page still has one entry, dated 31 October 2024. API changes are otherwise visible in AWS What's New posts and the SDK service models." ], "score": 94 }, "requirements": { "setupChecked": true, "complianceChecked": true, "card": "paid-only", "freeTier": true, "minutes": 15, "credential": "mixed", "hosting": [ "US", "CA", "EU", "UK", "APAC" ], "euResidency": "unknown", "trainsOnData": "no", "zeroRetention": "unknown", "certifications": [ "SOC 2 Type II", "ISO 27001", "ISO 27701", "CSA STAR", "HIPAA (BAA available)", "FedRAMP", "GDPR" ], "dpa": true, "selfHost": "no" }, "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-11-07T19:21:51.547774009Z", "lastOk": true, "lastStatus": 404, "lastMs": 339, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 268, "p95ms24h": 361, "samples24h": 238, "samples30d": 7430, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "versions": [ { "registry": "github", "name": "aws-geospatial/amazon-location-agent-context", "version": "v1.2.0", "released": "2026-09-11", "seenAt": "2026-11-06T23:05:30.940459269Z" }, { "registry": "npm", "name": "@aws-sdk/client-geo-maps", "version": "3.1164.0", "seenAt": "2026-11-06T23:05:28.818167205Z" }, { "registry": "npm", "name": "@aws-sdk/client-geo-places", "version": "3.1164.0", "seenAt": "2026-11-06T23:05:26.619179513Z" }, { "registry": "npm", "name": "@aws-sdk/client-geo-routes", "version": "3.1164.0", "seenAt": "2026-11-06T23:05:26.847110347Z" }, { "registry": "pypi", "name": "boto3", "version": "1.43.126", "released": "2026-11-06", "seenAt": "2026-11-06T23:05:30.814388437Z" } ], "githubStars": 7, "npmWeekly": 593835, "pypiWeekly": 637851852, "securityTxt": { "url": "https://amazon.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:00:18.354437696Z" }, "llmsTxt": { "url": "https://docs.aws.amazon.com/location/latest/developerguide/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:21.83498799Z" }, "domain": { "domain": "amazon.com", "registered": "1994-11-01", "source": "https://rdap.verisign.com/com/v1/domain/amazon.com", "checkedAt": "2026-11-01T14:09:08.477101866Z" }, "pages": [ { "url": "https://docs.aws.amazon.com/location/latest/developerguide/doc-history.html", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:05:18.263690376Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "57dff2a88a23" }, { "url": "https://aws.amazon.com/location/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:00:02.589087884Z", "changedAt": "2026-11-06T13:22:49.376396018Z", "fingerprint": "e7280b5141f2" } ], "github": { "repo": "aws-geospatial/amazon-location-agent-context", "checkedAt": "2026-11-02T08:33:04.302845017Z", "stars": 7, "archived": false, "issuesEnabled": true, "pushedAt": "2026-09-11T18:18:23Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 9, "ci": { "branch": "main", "runs": 33, "success": 33, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-09-11T18:29:49Z" } }, "updatedAt": "2026-11-07T19:21:51.547774009Z" } }, "answer": "Amazon Location Service scores 76.5 (BB) on agent readiness against MapTiler Cloud's 62.1 (B), and leads in 4 of 7 scored categories. MapTiler Cloud leads on payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "maptiler", "name": "MapTiler Cloud", "vendor": "MapTiler AG", "vendorUrl": "https://www.maptiler.com", "kind": "http-api", "category": "maps", "summary": "MapTiler Cloud is a hosted maps platform from MapTiler AG in Switzerland. Its read-only REST APIs serve map styles, vector and raster tiles, static maps, forward and reverse geocoding, IP geolocation, elevation, coordinate transforms and weather data.", "url": "https://www.anchorterminal.com/tools/maptiler", "markdownUrl": "https://www.anchorterminal.com/tools/maptiler.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/maptiler.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/maptiler.json", "dns": "maptiler.grade.anchorterminal.com", "repo": "https://github.com/maptiler/maptiler-client-js", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@maptiler/client" }, { "registry": "npm", "name": "@maptiler/sdk" } ], "auth": "api-key", "authNotes": "API key from the MapTiler Cloud account after a browser signup, always passed as the `key` query parameter. Keys can be limited to HTTP origins and a User-Agent substring and are managed through the Service API. From a backend, a service token can sign each request with a `signature` parameter instead. The Service API (uploads, tilesets, keys, analytics) needs a service token.", "pricing": "freemium", "pricingNotes": "Free plan with 100,000 API requests, 5,000 sessions and 1,000 search sessions a month, no card, for testing and non-commercial use; service pauses at the limit. Flex is $30 a month with 500,000 requests, then $0.15 per 1,000 requests and $2.50 per 1,000 search sessions. Custom contracts carry a 99.9% SLA.", "priceSummary": "$0.15 / 1k req", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, OpenAPI spec, llms.txt or pricing page (checked 2026-11-06). Paid plans are billed by FastSpring.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 114682, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.maptiler.com/cloud/api/", "llmsTxt": "https://docs.maptiler.com/llms.txt", "openapi": "https://docs.maptiler.com/_data/cloud/api/openapi.yml", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.tiles", "data.weather" ], "tags": [ "hosted", "api-key", "freemium", "free-tier", "no-card", "llms-txt", "openapi", "official", "agent-skills", "typescript", "status-page", "security-txt", "iso27001", "eu", "eu-region", "sla", "closed-source" ], "lastRelease": "2026-10-02", "graded": true, "anchor": { "graded": true, "score": 62.1, "grade": "B", "agentReady": false, "rank": 576, "ranked": true, "rankOf": 1510, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 70, "maintenance": 70, "payments": 40, "reliability": 43, "schema": 79, "security": 64, "transparency": 80 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "MapTiler Cloud has an OpenAPI 3.1 reference, llms.txt with Markdown pages, an agent skill and ISO 27001 certification, and allows geocoding results to be stored. The key always travels in the query string, there's no routing API, no documented rate limit or 429 handling, and the free plan excludes commercial use.", "bestFor": "Map tiles, static maps and worldwide geocoding with storable results for apps that also show a map, with EU data residency.", "strengths": [ "OpenAPI 3.1.0 spec, llms.txt, llms-full.txt and a Markdown version of every docs page", "Geocoding results may be bulk downloaded and used outside the service with attribution", "Keys can be restricted by origin and User-Agent, and service tokens can sign requests instead", "ISO/IEC 27001:2022 certification, security.txt and a vulnerability disclosure policy", "EU-only endpoint at api.maptiler.eu and hosting mainly in Switzerland and the EEA" ], "weaknesses": [ "The API key is always sent as a query parameter", "No routing, directions or matrix API", "No per-second rate limit, 429 behaviour or retry guidance found in the documentation", "The free plan is for testing and non-commercial use only, and pauses at its monthly limit", "Official clients are JavaScript and TypeScript only" ], "agentNotes": [ "Restrict the key to an origin or User-Agent, or sign requests with a service token from a backend, since the key appears in every URL", "Use the batch geocoding path (up to 50 semicolon-separated queries) rather than one call per address", "Use api.maptiler.eu when the user's requests must stay in the EU", "Read docs pages as Markdown by appending .md, starting from https://docs.maptiler.com/llms.txt", "Don't cache map tiles server-side; the Cloud terms forbid it, though geocoding results may be stored with attribution" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.1 } ], "editorialScores": { "ergonomics": 70, "maintenance": 70, "payments": 40, "reliability": 43, "schema": 79, "security": 64, "transparency": 64 }, "provenanceScore": 96, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install @maptiler/client", "http": "curl \"https://api.maptiler.com/geocoding/Zurich.json?language=en\u0026limit=3\u0026key=$MAPTILER_API_KEY\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/maptiler" }, "area": "everyday", "unitPrices": [ { "item": "API requests over the Flex allowance", "unit": "1k-requests", "usd": 0.15, "note": "Flex includes 500,000 a month" }, { "item": "Search sessions over the Flex allowance", "unit": "1k-requests", "usd": 2.5, "note": "Priced per 1,000 search sessions through MapTiler SDK JS" }, { "item": "Flex plan", "unit": "month", "usd": 30, "note": "Extra usage billed monthly" } ], "provenance": { "legalEntity": "MapTiler AG", "domain": "maptiler.com", "domainRegistered": "2008-08-08", "endpointOnVendorDomain": true, "terms": "https://www.maptiler.com/terms/", "privacy": "https://www.maptiler.com/privacy-policy/", "statusPage": "https://status.maptiler.com", "changelog": "https://docs.maptiler.com/updates/", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "The general terms name MapTiler AG, Zugerstrasse 22, 6314 Unterägeri, Switzerland, under Swiss law with courts in Zug.", "security.txt at www.maptiler.com/.well-known/security.txt names sysadmin@maptiler.com, a PGP key and a signature, and has no Expires field.", "status.maptiler.com is a StatusCake public report whose data loads from app.statuscake.com. That host's robots.txt answered with a redirect, so it wasn't fetched and no uptime or incident history was read.", "RDAP gives maptiler.com a registration date of 8 August 2008.", "No clause on automated access to the website was found in the general terms. robots.txt on www.maptiler.com and docs.maptiler.com allows all agents apart from a few paths." ], "score": 96 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/maptiler.json", "live": { "slug": "maptiler", "vendorStatus": { "page": "https://status.maptiler.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:02.124798696Z" }, "versions": [ { "registry": "github", "name": "maptiler/maptiler-client-js", "version": "v3.1.0", "released": "2026-10-02", "seenAt": "2026-11-06T23:42:38.646681081Z" }, { "registry": "npm", "name": "@maptiler/client", "version": "3.1.0", "seenAt": "2026-11-06T23:42:36.419318643Z" }, { "registry": "npm", "name": "@maptiler/sdk", "version": "4.2.1", "seenAt": "2026-11-06T23:42:37.315182633Z" } ], "githubStars": 25, "npmWeekly": 114682, "securityTxt": { "url": "https://maptiler.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T15:59:35.51300876Z" }, "llmsTxt": { "url": "https://docs.maptiler.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:57.151624353Z" }, "pages": [ { "url": "https://docs.maptiler.com/updates/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:06:56.724195464Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1152e8fe8b9d" }, { "url": "https://www.maptiler.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:31:21.154658791Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "46d3f1544780" }, { "url": "https://www.maptiler.com/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:31:23.29013826Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "fc740f21aa9f" } ], "updatedAt": "2026-11-07T15:59:35.51300876Z" } }, "edges": [ { "by": 52, "category": "reliability", "leads": "amazon-location", "name": "Reliability", "reasons": { "a": "Hosted reading. AWS Health Dashboard with a feed per service and region (20). The Amazon Location feeds for us-east-1 and eu-west-1 held no events on 1 November 2026 (last built 31 October), and the dashboard's event history, re-read on 1 November, names Amazon Location in no event. Its oldest event is the us-east-1 one of 28 October 2025, the open Middle East events of March 2026 don't list it, and the newest update is the API Gateway us-west-2 event of 30 October 2026. The public dashboard lists only broad events, so a clean feed says less than a small vendor's detailed page (30). Default rates published per operation, re-read on 1 November, 100 a second for each Places call, 20 for `CalculateRoutes`, isolines and `SnapToRoads`, 5 for `CalculateRouteMatrix` and `OptimizeWaypoints`, with a burst of 80 per cent (the burst rule per the 8 October check) (15). Throttling returns `ThrottlingException` with HTTP 429, marked retryable in the service model, and every v2 call is a read, but the guide gives no backoff or `Retry-After` guidance (10 of 15). Amazon Location SLA at 99.9 per cent monthly uptime per region (last updated 5 May 2022, re-read on 1 November) (10). GA (10). 20 + 30 + 15 + 10 + 10 + 10 = 95.", "b": "Hosted lines. status.maptiler.com is a StatusCake public uptime report rather than a component incident page (15). Its data loads from app.statuscake.com, whose robots.txt answered with a redirect, so we didn't fetch it and read no history. That's our limit, not a finding, and the rubric gives 5 (5). Monthly request and session quotas are published per plan, but no per-second limit (5). No 429, Retry-After or backoff guidance found in the API reference, the OpenAPI spec or llms-full.txt (0). The pricing page lists a 99.9% SLA on the Custom plan, while the Cloud terms call availability best effort and point to a custom SLA (8). The public APIs are GA (10). 15+5+5+0+8+10 = 43." }, "scores": { "a": 95, "b": 43 } }, { "by": 18, "category": "ergonomics", "leads": "amazon-location", "name": "Agent ergonomics", "reasons": { "a": "API reading of the checklist. Places responses stay at the core fields unless `AdditionalFeatures` asks for more, and `MaxResults` caps the count, but there is no field selection and route responses can reach the 6 MB limit (20 of 25). `MaxResults` on six of seven Places calls, `NextToken` on `SearchText` and `SearchNearby`, and filters by country, bounding box and place type (18 of 20). Four typed errors per API, with a reason and field list on `ValidationException` (17 of 20). Every v2 operation is marked read-only in the model, so retries are safe. No hints apply to a plain API (18 of 20). One required field or none on most calls, an API key that avoids SigV4 signing, and SDKs on npm and PyPI among others (15).", "b": "API reading. limit, types, bbox, proximity, country, language and fuzzyMatch size geocoding results, and the batch endpoint takes up to 50 queries (20). Country, bbox and type filters, no pagination (geocoding rarely needs it) (16). Errors are documented as 400 and 403 with no recovery guidance (10). Every public API reads and is safe to retry (12). Few required parameters, but official clients are JavaScript and TypeScript only, plus native mobile SDKs (12). 20+16+10+12+12 = 70." }, "scores": { "a": 88, "b": 70 } }, { "by": 12, "category": "security", "leads": "amazon-location", "name": "Security \u0026 auth", "reasons": { "a": "Three credential routes, SigV4 with IAM, Amazon Cognito, and API keys limited to named actions and resources with optional expiry and referrer or app restrictions, which earns 30 (the API key page re-read on 1 November). Less 10 because the API key is sent in the `key` query parameter, the only documented way to present it (20). API keys reach only read calls on Maps, Places and Routes, and IAM policies scope each action and resource (18 of 20). Results carry place names and third-party map data, and no prompt-injection guidance was found in the reviewed documentation (5 of 15). CloudTrail records management events by default and data events on request, and CloudWatch reports usage by `ApiKeyName` (15). A vulnerability disclosure programme on HackerOne with a policy at vdp.aws.security, public security bulletins (none from 17 October to 1 November names Amazon Location), audit reports in AWS Artifact, Amazon Location Service in SOC 1, 2 and 3 scope on the list updated 11 August 2026 (per the 17 October check), and a FedRAMP High announcement of 28 October 2024. The aws.amazon.com security.txt, re-read on 1 November, expires on 16 October 2027. No paid bug bounty was found, so 2 points stay held back, as on the S3, SES, Polly and Secrets Manager re-checks of 17 October and the S3 re-check of 1 November (18 of 20). 20 + 18 + 5 + 15 + 18 = 76.", "b": "Revocable keys that can be limited to origins and a User-Agent substring and managed by the API keys API, and service tokens that sign requests so the token itself never travels, which earns 27. Less 10 because the key is 'always passed as a query parameter' (17). The public APIs are read-only, and account changes need a separate service token (16). Geocoding returns OpenStreetMap names and addresses, community-edited text, with no prompt-injection guidance (7). An Analytics API and account usage statistics (8). security.txt, a vulnerability disclosure policy and ISO/IEC 27001:2022 certification per the security page. No bug bounty found (16). 17+16+7+8+16 = 64." }, "scores": { "a": 76, "b": 64 } }, { "by": 10, "category": "payments", "leads": "maptiler", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-1,000 prices for every operation and bucket published without a login, in the price feed the pricing page loads (still the 11 September 2026 publication on 1 November) (20). The pricing page lists monthly allowances for the first three months (20,000 core Places calls, 10,000 routes, 500,000 tiles), and Free Tier FAQ Q4, re-read on 1 November, says a payment method isn't required to sign up for most new customers but may be requested to verify identity. Half the line, as amazon-s3, amazon-polly and aws-secrets-manager got for the same FAQ (10). A person signs up in a browser. `CreateKey` mints API keys by API only after an account exists (0). 0 + 20 + 10 + 0 = 30.", "b": "No x402, MPP or L402 (0). Per-1,000 prices for requests ($0.15) and sessions ($2.50) public without login (20). Free plan with no card, though only for testing and non-commercial use (20). Signup is a browser flow (0). 0+20+20+0 = 40." }, "scores": { "a": 30, "b": 40 } }, { "by": 10, "category": "maintenance", "leads": "maptiler", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service, by the listing's own service models, as the S3 re-check of 1 November read models/s3. The newest API change is still the `geo-maps` model on 17 August 2026 (point-of-interest density and category filters on maps), 76 days before the check. The models repository had commits to 30 October, none touching the `geo-places`, `geo-routes`, `geo-maps` or `location` models (20 of 30). In the last 90 days we found that one model change plus two releases of the agent context package, v1.1.0 on 6 August and v1.2.0 on 11 September 2026, with no later tag. The two package releases are agent guidance for the service, not changes to it, so half, as manifold-mcp's skills releases were read (10 of 20). AWS What's New posts for the service run to 2 April 2026 (none in the feed's 100 items from 20 to 30 October), re:Post and paid support exist, and the agent context repository had no open issues on 8 October (10 of 15). Official SDKs are current, the aws-sdk-js-v3 release v3.1161.0 and boto3 1.43.123, both tagged 30 October 2026 (15). SDKs regenerate from the model on AWS's release train, CI not checked (5 of 10). 20 + 10 + 10 + 15 + 5 = 60.", "b": "@maptiler/client 3.1.0 and @maptiler/sdk 4.2.0 on 2 October 2026, 35 days before this check, with the agent skill updated on 21 October (20). Platform updates entries for August (EU endpoint, key security) and September 2026 (terrain blending) plus the two October releases (20). A Discord community and support answered on a best-effort basis within two business days, per the Cloud terms. We didn't read GitHub issues (10). Official JavaScript client and SDK current, no Python client (12). The SDK repository runs unit and end-to-end tests in CI; we didn't check results (8). 20+20+10+12+8 = 70." }, "scores": { "a": 60, "b": 70 } }, { "by": 8, "category": "schema", "leads": "amazon-location", "name": "Schema \u0026 documentation", "reasons": { "a": "The Smithy service models for `geo-places`, `geo-routes`, `geo-maps` and `location` (API version 2020-11-19) are public in aws/api-models-aws and in every AWS SDK, a machine-readable contract in the role OpenAPI plays (25). llms.txt for the developer guide, a Markdown twin of each page and the whole guide as `full.md` (10). A choose-an-API page and per-operation pages with use cases say when each call fits, with less on when not to use one (15 of 20). Inputs carry enums and ranges, such as `MaxResults` 1 to 100 and `QueryText` up to 200 characters (15). How-to pages give sample requests, responses, cURL and CLI commands, and each action lists its errors with HTTP codes, but the `ValidationException` fields are documented as \"Test stub\" (12 of 15). Versioned paths (`/v2/`), yet the document history, re-read on 1 November, still has one entry, dated 31 October 2024, and changes are announced only in AWS What's New posts (10 of 15).", "b": "OpenAPI 3.1.0 document with 32 paths for the public APIs (25). llms.txt, llms-full.txt and a Markdown twin of every page (10). Each API page says what it's for and when to use the SDK instead (session billing), with little on when not to call it (13). Parameters are typed with defaults, such as limit (default 5 forward, 1 reverse) and a types enum, but bbox and proximity are strings (11). Examples on every endpoint, and the spec documents 400, 403, 404 and 414, without an error reference page (10). A dated platform updates page and a geocoding index changelog, but no version in the API path and the spec is version '1.0' (10). 25+10+13+11+10+10 = 79." }, "scores": { "a": 87, "b": 79 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "MapTiler AG", "name": "Vendor" }, { "a": "https://places.geo.us-east-1.amazonaws.com", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "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 geocoding" }, { "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": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-17", "b": "2026-10-02", "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": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "427k npm/wk", "b": "115k npm/wk", "name": "Popularity" }, { "a": "4/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Amazon Location Service scores 76.5 (BB) on agent readiness against MapTiler Cloud's 62.1 (B), and leads in 4 of 7 scored categories. MapTiler Cloud leads on payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Amazon Location Service or MapTiler Cloud?" }, { "answer": "Both need an API key.", "question": "Do Amazon Location Service and MapTiler Cloud need an API key?" }, { "answer": "Amazon Location Service has a hosted endpoint at https://places.geo.us-east-1.amazonaws.com. No hosted endpoint is listed for MapTiler Cloud.", "question": "Can an agent call Amazon Location Service and MapTiler Cloud without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 95 against 43", "Schema \u0026 documentation, 87 against 79", "Agent ergonomics, 88 against 70", "Security \u0026 auth, 76 against 64" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install" ], "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, 40 against 30", "Maintenance \u0026 community, 70 against 60" ], "also": null, "goodFor": "Map tiles, static maps and worldwide geocoding with storable results for apps that also show a map, with EU data residency.", "slug": "maptiler", "watchFor": "The API key is always sent as a query parameter" } ], "history": { "amazon-location": [ { "causes": [ "security", "evidence", "correction" ], "date": "2026-10-17", "delta": 2.4, "from": 74.1, "fromGrade": "BB", "to": 76.5, "toGrade": "BB" } ], "maptiler": null }, "job": { "capability": "geo.geocode", "name": "Geocoding" }, "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-geocodio.json", "title": "Amazon Location Service vs Geocodio", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-geocodio" }, { "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-here-location-services.json", "title": "Amazon Location Service vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services" }, { "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-nextbillion.json", "title": "Amazon Location Service vs NextBillion.ai", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-nextbillion" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-nominatim.json", "title": "Amazon Location Service vs Nominatim", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-nominatim" }, { "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-radar.json", "title": "Amazon Location Service vs Radar", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-radar" }, { "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/amazon-location-vs-woosmap.json", "title": "Amazon Location Service vs Woosmap", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-maptiler.json", "title": "ArcGIS Location Platform vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/arcgis-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-maptiler.json", "title": "Azure Maps vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-maptiler.json", "title": "Geoapify Location Platform + MCP vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/geoapify-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-maptiler.json", "title": "Geocodio vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/geocodio-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-maptiler.json", "title": "Google Maps Platform + Grounding Lite MCP vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-maptiler.json", "title": "HERE Location Services vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-maptiler.json", "title": "LocationIQ vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/locationiq-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-maptiler.json", "title": "Mapbox APIs + MCP vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/mapbox-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-maptiler.json", "title": "MapQuest vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/mapquest-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-nextbillion.json", "title": "MapTiler Cloud vs NextBillion.ai", "url": "https://www.anchorterminal.com/compare/maptiler-vs-nextbillion" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-nominatim.json", "title": "MapTiler Cloud vs Nominatim", "url": "https://www.anchorterminal.com/compare/maptiler-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-opencage.json", "title": "MapTiler Cloud vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/maptiler-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-radar.json", "title": "MapTiler Cloud vs Radar", "url": "https://www.anchorterminal.com/compare/maptiler-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-stadia-maps.json", "title": "MapTiler Cloud vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/maptiler-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-tomtom.json", "title": "MapTiler Cloud vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/maptiler-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-woosmap.json", "title": "MapTiler Cloud vs Woosmap", "url": "https://www.anchorterminal.com/compare/maptiler-vs-woosmap" } ], "panel": null, "scores": [ { "amazon-location": 95, "by": 52, "edge": "amazon-location", "key": "reliability", "maptiler": 43, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amazon-location": 87, "by": 8, "edge": "amazon-location", "key": "schema", "maptiler": 79, "name": "Schema \u0026 documentation", "weight": 13 }, { "amazon-location": 88, "by": 18, "edge": "amazon-location", "key": "ergonomics", "maptiler": 70, "name": "Agent ergonomics", "weight": 13 }, { "amazon-location": 76, "by": 12, "edge": "amazon-location", "key": "security", "maptiler": 64, "name": "Security \u0026 auth", "weight": 14 }, { "amazon-location": 30, "by": 10, "edge": "maptiler", "key": "payments", "maptiler": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amazon-location": 60, "by": 10, "edge": "maptiler", "key": "maintenance", "maptiler": 70, "name": "Maintenance \u0026 community", "weight": 7 }, { "amazon-location": 77, "by": 3, "edge": "maptiler", "key": "transparency", "maptiler": 80, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Amazon Location Service scores 76.5 (BB) on agent readiness against MapTiler Cloud's 62.1 (B), and leads in 4 of 7 scored categories. MapTiler Cloud leads on payments \u0026 pricing and maintenance \u0026 community. Both do geocoding.", "tasks": null, "tutorials": [], "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.", "maptiler": "MapTiler Cloud has an OpenAPI 3.1 reference, llms.txt with Markdown pages, an agent skill and ISO 27001 certification, and allows geocoding results to be stored. The key always travels in the query string, there's no routing API, no documented rate limit or 429 handling, and the free plan excludes commercial use." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amazon-location-vs-maptiler", "json": "https://www.anchorterminal.com/compare/amazon-location-vs-maptiler.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amazon-location-vs-maptiler.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/amazon-location-vs-maptiler.min.md" }, "markdown": "Amazon Location Service scores 76.5 (BB) on agent readiness against MapTiler Cloud's 62.1 (B), and leads in 4 of 7 scored categories. MapTiler Cloud leads on payments \u0026 pricing and maintenance \u0026 community. Both do geocoding.\n\n- Amazon Location Service: grade BB, 76.5/100, rank #43 of 1510. Markdown https://www.anchorterminal.com/tools/amazon-location.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-location.json\n- MapTiler Cloud: grade B, 62.1/100, rank #576 of 1510. Markdown https://www.anchorterminal.com/tools/maptiler.md · JSON https://www.anchorterminal.com/api/v1/tools/maptiler.json\n- Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md\n- All 153 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md\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 43\n- Schema \u0026 documentation, 87 against 79\n- Agent ergonomics, 88 against 70\n- Security \u0026 auth, 76 against 64\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n\nWatch for: The API key is sent as the `key` query parameter, the only documented way to present it\n\n### MapTiler Cloud (B)\n\nGood for: Map tiles, static maps and worldwide geocoding with storable results for apps that also show a map, with EU data residency.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 30\n- Maintenance \u0026 community, 70 against 60\n\nWatch for: The API key is always sent as a query parameter\n\n\n## Why the edge\n\n### Reliability: Amazon Location Service +52\n\n- Amazon Location Service (95): Hosted reading. AWS Health Dashboard with a feed per service and region (20). The Amazon Location feeds for us-east-1 and eu-west-1 held no events on 1 November 2026 (last built 31 October), and the dashboard's event history, re-read on 1 November, names Amazon Location in no event. Its oldest event is the us-east-1 one of 28 October 2025, the open Middle East events of March 2026 don't list it, and the newest update is the API Gateway us-west-2 event of 30 October 2026. The public dashboard lists only broad events, so a clean feed says less than a small vendor's detailed page (30). Default rates published per operation, re-read on 1 November, 100 a second for each Places call, 20 for `CalculateRoutes`, isolines and `SnapToRoads`, 5 for `CalculateRouteMatrix` and `OptimizeWaypoints`, with a burst of 80 per cent (the burst rule per the 8 October check) (15). Throttling returns `ThrottlingException` with HTTP 429, marked retryable in the service model, and every v2 call is a read, but the guide gives no backoff or `Retry-After` guidance (10 of 15). Amazon Location SLA at 99.9 per cent monthly uptime per region (last updated 5 May 2022, re-read on 1 November) (10). GA (10). 20 + 30 + 15 + 10 + 10 + 10 = 95.\n- MapTiler Cloud (43): Hosted lines. status.maptiler.com is a StatusCake public uptime report rather than a component incident page (15). Its data loads from app.statuscake.com, whose robots.txt answered with a redirect, so we didn't fetch it and read no history. That's our limit, not a finding, and the rubric gives 5 (5). Monthly request and session quotas are published per plan, but no per-second limit (5). No 429, Retry-After or backoff guidance found in the API reference, the OpenAPI spec or llms-full.txt (0). The pricing page lists a 99.9% SLA on the Custom plan, while the Cloud terms call availability best effort and point to a custom SLA (8). The public APIs are GA (10). 15+5+5+0+8+10 = 43.\n\n### Agent ergonomics: Amazon Location Service +18\n\n- Amazon Location Service (88): API reading of the checklist. Places responses stay at the core fields unless `AdditionalFeatures` asks for more, and `MaxResults` caps the count, but there is no field selection and route responses can reach the 6 MB limit (20 of 25). `MaxResults` on six of seven Places calls, `NextToken` on `SearchText` and `SearchNearby`, and filters by country, bounding box and place type (18 of 20). Four typed errors per API, with a reason and field list on `ValidationException` (17 of 20). Every v2 operation is marked read-only in the model, so retries are safe. No hints apply to a plain API (18 of 20). One required field or none on most calls, an API key that avoids SigV4 signing, and SDKs on npm and PyPI among others (15).\n- MapTiler Cloud (70): API reading. limit, types, bbox, proximity, country, language and fuzzyMatch size geocoding results, and the batch endpoint takes up to 50 queries (20). Country, bbox and type filters, no pagination (geocoding rarely needs it) (16). Errors are documented as 400 and 403 with no recovery guidance (10). Every public API reads and is safe to retry (12). Few required parameters, but official clients are JavaScript and TypeScript only, plus native mobile SDKs (12). 20+16+10+12+12 = 70.\n\n### Security \u0026 auth: Amazon Location Service +12\n\n- Amazon Location Service (76): Three credential routes, SigV4 with IAM, Amazon Cognito, and API keys limited to named actions and resources with optional expiry and referrer or app restrictions, which earns 30 (the API key page re-read on 1 November). Less 10 because the API key is sent in the `key` query parameter, the only documented way to present it (20). API keys reach only read calls on Maps, Places and Routes, and IAM policies scope each action and resource (18 of 20). Results carry place names and third-party map data, and no prompt-injection guidance was found in the reviewed documentation (5 of 15). CloudTrail records management events by default and data events on request, and CloudWatch reports usage by `ApiKeyName` (15). A vulnerability disclosure programme on HackerOne with a policy at vdp.aws.security, public security bulletins (none from 17 October to 1 November names Amazon Location), audit reports in AWS Artifact, Amazon Location Service in SOC 1, 2 and 3 scope on the list updated 11 August 2026 (per the 17 October check), and a FedRAMP High announcement of 28 October 2024. The aws.amazon.com security.txt, re-read on 1 November, expires on 16 October 2027. No paid bug bounty was found, so 2 points stay held back, as on the S3, SES, Polly and Secrets Manager re-checks of 17 October and the S3 re-check of 1 November (18 of 20). 20 + 18 + 5 + 15 + 18 = 76.\n- MapTiler Cloud (64): Revocable keys that can be limited to origins and a User-Agent substring and managed by the API keys API, and service tokens that sign requests so the token itself never travels, which earns 27. Less 10 because the key is 'always passed as a query parameter' (17). The public APIs are read-only, and account changes need a separate service token (16). Geocoding returns OpenStreetMap names and addresses, community-edited text, with no prompt-injection guidance (7). An Analytics API and account usage statistics (8). security.txt, a vulnerability disclosure policy and ISO/IEC 27001:2022 certification per the security page. No bug bounty found (16). 17+16+7+8+16 = 64.\n\n### Payments \u0026 pricing: MapTiler Cloud +10\n\n- Amazon Location Service (30): No x402, MPP or L402 (0). Per-1,000 prices for every operation and bucket published without a login, in the price feed the pricing page loads (still the 11 September 2026 publication on 1 November) (20). The pricing page lists monthly allowances for the first three months (20,000 core Places calls, 10,000 routes, 500,000 tiles), and Free Tier FAQ Q4, re-read on 1 November, says a payment method isn't required to sign up for most new customers but may be requested to verify identity. Half the line, as amazon-s3, amazon-polly and aws-secrets-manager got for the same FAQ (10). A person signs up in a browser. `CreateKey` mints API keys by API only after an account exists (0). 0 + 20 + 10 + 0 = 30.\n- MapTiler Cloud (40): No x402, MPP or L402 (0). Per-1,000 prices for requests ($0.15) and sessions ($2.50) public without login (20). Free plan with no card, though only for testing and non-commercial use (20). Signup is a browser flow (0). 0+20+20+0 = 40.\n\n### Maintenance \u0026 community: MapTiler Cloud +10\n\n- Amazon Location Service (60): Read as a closed service, by the listing's own service models, as the S3 re-check of 1 November read models/s3. The newest API change is still the `geo-maps` model on 17 August 2026 (point-of-interest density and category filters on maps), 76 days before the check. The models repository had commits to 30 October, none touching the `geo-places`, `geo-routes`, `geo-maps` or `location` models (20 of 30). In the last 90 days we found that one model change plus two releases of the agent context package, v1.1.0 on 6 August and v1.2.0 on 11 September 2026, with no later tag. The two package releases are agent guidance for the service, not changes to it, so half, as manifold-mcp's skills releases were read (10 of 20). AWS What's New posts for the service run to 2 April 2026 (none in the feed's 100 items from 20 to 30 October), re:Post and paid support exist, and the agent context repository had no open issues on 8 October (10 of 15). Official SDKs are current, the aws-sdk-js-v3 release v3.1161.0 and boto3 1.43.123, both tagged 30 October 2026 (15). SDKs regenerate from the model on AWS's release train, CI not checked (5 of 10). 20 + 10 + 10 + 15 + 5 = 60.\n- MapTiler Cloud (70): @maptiler/client 3.1.0 and @maptiler/sdk 4.2.0 on 2 October 2026, 35 days before this check, with the agent skill updated on 21 October (20). Platform updates entries for August (EU endpoint, key security) and September 2026 (terrain blending) plus the two October releases (20). A Discord community and support answered on a best-effort basis within two business days, per the Cloud terms. We didn't read GitHub issues (10). Official JavaScript client and SDK current, no Python client (12). The SDK repository runs unit and end-to-end tests in CI; we didn't check results (8). 20+20+10+12+8 = 70.\n\n### Schema \u0026 documentation: Amazon Location Service +8\n\n- Amazon Location Service (87): The Smithy service models for `geo-places`, `geo-routes`, `geo-maps` and `location` (API version 2020-11-19) are public in aws/api-models-aws and in every AWS SDK, a machine-readable contract in the role OpenAPI plays (25). llms.txt for the developer guide, a Markdown twin of each page and the whole guide as `full.md` (10). A choose-an-API page and per-operation pages with use cases say when each call fits, with less on when not to use one (15 of 20). Inputs carry enums and ranges, such as `MaxResults` 1 to 100 and `QueryText` up to 200 characters (15). How-to pages give sample requests, responses, cURL and CLI commands, and each action lists its errors with HTTP codes, but the `ValidationException` fields are documented as \"Test stub\" (12 of 15). Versioned paths (`/v2/`), yet the document history, re-read on 1 November, still has one entry, dated 31 October 2024, and changes are announced only in AWS What's New posts (10 of 15).\n- MapTiler Cloud (79): OpenAPI 3.1.0 document with 32 paths for the public APIs (25). llms.txt, llms-full.txt and a Markdown twin of every page (10). Each API page says what it's for and when to use the SDK instead (session billing), with little on when not to call it (13). Parameters are typed with defaults, such as limit (default 5 forward, 1 reverse) and a types enum, but bbox and proximity are strings (11). Examples on every endpoint, and the spec documents 400, 403, 404 and 414, without an error reference page (10). A dated platform updates page and a geocoding index changelog, but no version in the API path and the spec is version '1.0' (10). 25+10+13+11+10+10 = 79.\n\n## Score by category\n\n| Category | Weight | Amazon Location Service | MapTiler Cloud | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 95 | 43 | Amazon Location Service +52 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 79 | Amazon Location Service +8 |\n| Agent ergonomics | 13% (16.2 this run) | 88 | 70 | Amazon Location Service +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 76 | 64 | Amazon Location Service +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | MapTiler Cloud +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 70 | MapTiler Cloud +10 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 80 | MapTiler Cloud +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **76.5 · BB** | **62.1 · B** | |\n\n## Facts side by side\n\n| Fact | Amazon Location Service | MapTiler Cloud |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | MapTiler AG |\n| Hosted endpoint | `https://places.geo.us-east-1.amazonaws.com` | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Freemium |\n| Price for geocoding | $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| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| Last release | 2026-08-17 | 2026-10-02 |\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 | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 427k npm/wk | 115k npm/wk |\n| Agent reviews | 4/5 (4) | none |\n\n## How the scores have moved\n\n### Amazon Location Service\n\n- +2.4 on 17 October 2026: security, new evidence, correction\n\n### MapTiler Cloud\n\nNo score change since it was listed.\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**MapTiler Cloud.** MapTiler Cloud has an OpenAPI 3.1 reference, llms.txt with Markdown pages, an agent skill and ISO 27001 certification, and allows geocoding results to be stored. The key always travels in the query string, there's no routing API, no documented rate limit or 429 handling, and the free plan excludes commercial use.\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### MapTiler Cloud\n\n1. Restrict the key to an origin or User-Agent, or sign requests with a service token from a backend, since the key appears in every URL\n2. Use the batch geocoding path (up to 50 semicolon-separated queries) rather than one call per address\n3. Use api.maptiler.eu when the user's requests must stay in the EU\n4. Read docs pages as Markdown by appending .md, starting from https://docs.maptiler.com/llms.txt\n5. Don't cache map tiles server-side; the Cloud terms forbid it, though geocoding results may be stored with attribution\n\n## Questions\n\n### Which is better for AI agents, Amazon Location Service or MapTiler Cloud?\n\nAmazon Location Service scores 76.5 (BB) on agent readiness against MapTiler Cloud's 62.1 (B), and leads in 4 of 7 scored categories. MapTiler Cloud leads on payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Amazon Location Service and MapTiler Cloud need an API key?\n\nBoth need an API key.\n\n### Can an agent call Amazon Location Service and MapTiler Cloud without installing anything?\n\nAmazon Location Service has a hosted endpoint at https://places.geo.us-east-1.amazonaws.com. No hosted endpoint is listed for MapTiler Cloud.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-location-vs-maptiler.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-location-vs-maptiler.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-location\", \"b\": \"maptiler\"}`. From a terminal: `anchor compare amazon-location maptiler`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-location.json and https://www.anchorterminal.com/api/v1/tools/maptiler.json\n\n## Other comparisons with Amazon Location Service or MapTiler Cloud\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 Geocodio](https://www.anchorterminal.com/compare/amazon-location-vs-geocodio.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 HERE Location Services](https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.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 NextBillion.ai](https://www.anchorterminal.com/compare/amazon-location-vs-nextbillion.md)\n- [Amazon Location Service vs Nominatim](https://www.anchorterminal.com/compare/amazon-location-vs-nominatim.md)\n- [Amazon Location Service vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/amazon-location-vs-opencage.md)\n- [Amazon Location Service vs Radar](https://www.anchorterminal.com/compare/amazon-location-vs-radar.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- [Amazon Location Service vs Woosmap](https://www.anchorterminal.com/compare/amazon-location-vs-woosmap.md)\n- [ArcGIS Location Platform vs MapTiler Cloud](https://www.anchorterminal.com/compare/arcgis-vs-maptiler.md)\n- [Azure Maps vs MapTiler Cloud](https://www.anchorterminal.com/compare/azure-maps-vs-maptiler.md)\n- [Geoapify Location Platform + MCP vs MapTiler Cloud](https://www.anchorterminal.com/compare/geoapify-vs-maptiler.md)\n- [Geocodio vs MapTiler Cloud](https://www.anchorterminal.com/compare/geocodio-vs-maptiler.md)\n- [Google Maps Platform + Grounding Lite MCP vs MapTiler Cloud](https://www.anchorterminal.com/compare/google-maps-platform-vs-maptiler.md)\n- [HERE Location Services vs MapTiler Cloud](https://www.anchorterminal.com/compare/here-location-services-vs-maptiler.md)\n- [LocationIQ vs MapTiler Cloud](https://www.anchorterminal.com/compare/locationiq-vs-maptiler.md)\n- [Mapbox APIs + MCP vs MapTiler Cloud](https://www.anchorterminal.com/compare/mapbox-vs-maptiler.md)\n- [MapQuest vs MapTiler Cloud](https://www.anchorterminal.com/compare/mapquest-vs-maptiler.md)\n- [MapTiler Cloud vs NextBillion.ai](https://www.anchorterminal.com/compare/maptiler-vs-nextbillion.md)\n- [MapTiler Cloud vs Nominatim](https://www.anchorterminal.com/compare/maptiler-vs-nominatim.md)\n- [MapTiler Cloud vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/maptiler-vs-opencage.md)\n- [MapTiler Cloud vs Radar](https://www.anchorterminal.com/compare/maptiler-vs-radar.md)\n- [MapTiler Cloud vs Stadia Maps](https://www.anchorterminal.com/compare/maptiler-vs-stadia-maps.md)\n- [MapTiler Cloud vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/maptiler-vs-tomtom.md)\n- [MapTiler Cloud vs Woosmap](https://www.anchorterminal.com/compare/maptiler-vs-woosmap.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Amazon Location Service vs MapTiler Cloud", "url": "" } ], "description": "Amazon Location Service scores 76.5 (BB) to MapTiler Cloud's 62.1 (B) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Amazon Location Service BB 76.5", "MapTiler Cloud B 62.1", "scores" ], "h1": "Amazon Location Service vs MapTiler Cloud", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/amazon-location-vs-maptiler", "published": "2026-10-01", "section": "tools", "title": "Amazon Location Service vs MapTiler Cloud for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-maptiler" }, "tokens": { "markdown": 5450, "slim": 3280 }, "version": 1 }