{ "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 Geocodio's 72.2 (BB), and leads in 3 of 7 scored categories. Geocodio leads on schema \u0026 documentation, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "geocodio", "name": "Geocodio", "vendor": "Dotsquare LLC", "vendorUrl": "https://www.geocod.io", "kind": "http-api", "category": "maps", "summary": "Geocodio is a hosted geocoding API from Dotsquare LLC for addresses in the US, Canada, Mexico, the UK, Australia and New Zealand. It does forward, reverse and batch geocoding, distance matrices and census, district and timezone data appends.", "url": "https://www.anchorterminal.com/tools/geocodio", "markdownUrl": "https://www.anchorterminal.com/tools/geocodio.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/geocodio.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/geocodio.json", "dns": "geocodio.grade.anchorterminal.com", "repo": "https://github.com/Geocodio/geocodio-cli", "transports": [ "http" ], "packages": [ { "registry": "pypi", "name": "geocodio-library-python" }, { "registry": "npm", "name": "geocodio-library-node" } ], "auth": "api-key", "authNotes": "API key from the dashboard at dash.geocod.io after a browser signup, sent as `Authorization: Bearer` (since March 2025) or the `api_key` query parameter, which the docs and the OpenAPI spec still lead with. Five keys on pay-as-you-go. A new key reaches single and batch geocoding only; the Lists and Distance APIs must be enabled per key.", "pricing": "freemium", "pricingNotes": "2,500 lookups a day free on pay-as-you-go with no card until usage passes the free tier, then $1 per 1,000 lookups billed on the 1st of the next month. Each data append is one more lookup. Flex plans from $315 a month for 350,000 credits, Unlimited from $1,600 a month per dedicated instance.", "priceSummary": "$1 / 1k req", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, AGENTS.md, the docs or the OpenAPI spec (checked 2026-11-06). Billing is by card on file, monthly in arrears on pay-as-you-go.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 20984, "pypiWeekly": 921, "asOf": "2026-11-06" }, "docsUrl": "https://www.geocod.io/docs/", "llmsTxt": "https://www.geocod.io/llms.txt", "openapi": "https://api.geocod.io/openapi-spec.json", "capabilities": [ "geo.geocode", "geo.reverse", "geo.routing" ], "tags": [ "hosted", "api-key", "freemium", "free-tier", "no-card", "llms-txt", "openapi", "official", "cli", "agent-skills", "python", "typescript", "php", "ruby", "batch", "async-jobs", "status-page", "security-txt", "enterprise", "soc2", "closed-source" ], "lastRelease": "2026-11-03", "graded": true, "anchor": { "graded": true, "score": 72.2, "grade": "BB", "agentReady": true, "rank": 138, "ranked": true, "rankOf": 1510, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 86, "payments": 40, "reliability": 70, "schema": 92, "security": 58, "transparency": 87 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-11-06" }, "negative": 0, "verdict": "Geocodio publishes llms.txt, an AGENTS.md on cost and retries, an OpenAPI spec and a dated changelog, and its results may be stored permanently. Coverage stops at six countries, there's no MCP server or published SLA for self-serve plans, and the docs still put the key in the query string by default.", "bestFor": "Batch geocoding and district or census enrichment of addresses in the US, Canada, Mexico, the UK, Australia and New Zealand, where results must be stored.", "strengths": [ "llms.txt and AGENTS.md cover billing arithmetic, retry rules, idempotency on the client and when not to use the API", "2,500 free lookups a day with no card, then $1 per 1,000, and zero-result lookups aren't billed", "Results may be stored and reused permanently, except UK reverse geocoding addresses", "Dated API changelog with versioned paths, and replaced versions kept for at least 12 months", "Official Python, Node, PHP and Ruby libraries and a CLI with an agent output mode, all MIT" ], "weaknesses": [ "Covers only the US, Canada, Mexico, the UK, Australia and New Zealand, and UK needs a Flex or Unlimited plan", "The docs lead with the api_key query parameter, and the OpenAPI spec defines only that scheme", "No idempotency key on batch or list creation, so a retried upload is billed again", "No MCP server, and no published SLA on self-serve plans", "SOC 2 Type II and penetration tests apply to the separate Enterprise platform only" ], "agentNotes": [ "Always set `country`, because an address with none falls back to the US and is billed even when it's wrong", "Send the key as `Authorization: Bearer`, not in the query string, so it stays out of logs", "Use batch POST /geocode (up to 10,000 lookups) or the Lists API rather than looping single requests", "Treat accuracy_type place, county or state as not found, and check `_warnings` for appends that were billed but skipped", "Don't retry 403 or 422. On 429 read X-RateLimit headers and back off, and never re-upload a list sitting in ENQUEUED" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 72.2 } ], "editorialScores": { "ergonomics": 80, "maintenance": 86, "payments": 40, "reliability": 70, "schema": 92, "security": 58, "transparency": 80 }, "provenanceScore": 93, "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": "pip install geocodio-library-python", "http": "curl -H \"Authorization: Bearer $GEOCODIO_API_KEY\" \"https://api.geocod.io/v2.1/geocode?q=1109+N+Highland+St,+Arlington+VA\u0026country=USA\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/geocodio" }, "area": "everyday", "unitPrices": [ { "item": "Lookup after the free tier, pay-as-you-go", "unit": "1k-requests", "usd": 1, "note": "2,500 lookups a day free. A lookup is one address or coordinate, and each data append is one more" }, { "item": "Flex 350 plan", "unit": "month", "usd": 315, "note": "350,000 credits a month ($0.90 per 1,000), rolling over while subscribed" }, { "item": "Unlimited Geocoding plan", "unit": "month", "usd": 1600, "note": "One dedicated instance, up to 5 million lookups a day; distance credits extra at $1 per 1,000" } ], "provenance": { "legalEntity": "Dotsquare LLC", "domain": "geocod.io", "domainRegistered": "2013-06-05", "endpointOnVendorDomain": true, "terms": "https://www.geocod.io/terms-of-use", "privacy": "https://www.geocod.io/privacy-policy", "statusPage": "https://status.geocod.io", "changelog": "https://www.geocod.io/docs/#changelog", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "The terms name Dotsquare LLC, dba Geocodio, 440 Monticello Ave Ste 1802 #43146, Norfolk, Virginia, and choose Virginia law.", "The terms' acceptable use section bars customers from 'web scraping or data scraping on or related to the System, including ... any bot or web crawler'. Recorded as a fact; robots.txt on www.geocod.io allows all agents.", "security.txt at www.geocod.io/security.txt names security@geocod.io, a PGP key and a responsible disclosure policy, and expires 30 January 2030.", "RDAP gives geocod.io a registration date of 5 June 2013. The about page says Geocodio launched in 2014.", "llms.txt links https://www.geocod.io/pricing.md as the current pricing in Markdown, but that URL returned a 404 page on 6 November 2026, so prices come from the HTML pricing page." ], "score": 93 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/geocodio.json", "live": { "slug": "geocodio", "vendorStatus": { "page": "https://status.geocod.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:22:12.77760537Z" }, "versions": [ { "registry": "github", "name": "Geocodio/geocodio-cli", "version": "v3.3.0", "released": "2026-08-31", "seenAt": "2026-11-06T23:28:00.884456202Z" }, { "registry": "npm", "name": "geocodio-library-node", "version": "2.2.0", "seenAt": "2026-11-06T23:28:00.414999469Z" }, { "registry": "pypi", "name": "geocodio-library-python", "version": "1.6.0", "released": "2026-10-16", "seenAt": "2026-11-06T23:27:57.978816079Z" } ], "githubStars": 3, "npmWeekly": 20984, "pypiWeekly": 921, "securityTxt": { "url": "https://geocod.io/.well-known/security.txt", "state": "valid", "expires": "2030-01-30T00:00:00.000Z", "checkedAt": "2026-11-07T16:01:17.012285777Z" }, "llmsTxt": { "url": "https://www.geocod.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:35.723551581Z" }, "pages": [ { "url": "https://www.geocod.io/docs/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:29:02.899876797Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9bcdba9ab6f4" }, { "url": "https://www.geocod.io/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:29:05.843886759Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "712b2145deac" }, { "url": "https://www.geocod.io/terms-of-use", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:29:07.288294893Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ff5d2a37483d" } ], "updatedAt": "2026-11-07T19:22:12.77760537Z" } }, "edges": [ { "by": 26, "category": "maintenance", "leads": "geocodio", "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": "API v2.1 released 3 November 2026 (Australia and New Zealand), and PHP library 3.4.1 on 4 November (30). Dated changelog entries on 8 September, 1, 8, 9, 19, 22 and 31 October and 3 November 2026, plus library releases in October (20). Public changelog, support by email and a team-staffed help desk named on the pricing page. We didn't read GitHub issue reply times (12). Official Python 1.6.0 and Node 2.3.0 from 12 October and PHP 3.4.1 from 4 November are current (15). Each library and the CLI run CI on GitHub Actions; we didn't check whether the runs pass (9). 30+20+12+15+9 = 86." }, "scores": { "a": 60, "b": 86 } }, { "by": 25, "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. incident.io status page at status.geocod.io with five components (Geocodio API, Dashboard, Enterprise API, Enterprise Dashboard, Website) and an incidents feed at /api/v2/incidents.json (20). In the 90 days to 6 November 2026 the feed lists one incident marked major, 'Spreadsheet geocoding jobs are failing' on 27 October from 12:35 to 15:15 UTC, and a PHP security patch on 21 October marked no impact, so one major outage of a core feature (10). 1,000 requests a minute on single geocoding for pay-as-you-go and Flex, 100 on Enterprise Flex (15). 429 carries X-RateLimit-Remaining, -Limit and -Period, and llms.txt and AGENTS.md give a retry rule per status code with capped backoff, plus client-side idempotency guidance for the non-idempotent list and batch writes (15). The pricing page lists custom SLAs as an add-on on Unlimited and Enterprise plans, with no published terms, so no SLA (0). GA (10). 20+10+15+15+0+10 = 70." }, "scores": { "a": 95, "b": 70 } }, { "by": 18, "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, five on pay-as-you-go, each with permissions (Lists and Distance off by default), which earns 25. Less 10 because the docs say 'All requests require \u0026api_key=YOUR_API_KEY' and the OpenAPI spec defines only the query scheme, though an Authorization header has worked since March 2025 (15). Per-key permissions limit what a key can reach. DELETE on lists and distance jobs needs no confirmation (13). Results are addresses and government district, census and legislator data rather than user-written text. No prompt-injection guidance found (9). Usage per API key in the dashboard, downloadable as CSV, and billable-lookup headers on every response (8). Valid security.txt to 30 January 2030 with a PGP key and a responsible disclosure policy. SOC 2 Type II and annual penetration tests apply to the Enterprise platform only. No bug bounty found (13). 15+13+9+8+13 = 58." }, "scores": { "a": 76, "b": 58 } }, { "by": 10, "category": "payments", "leads": "geocodio", "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). $1 per 1,000 lookups after the free tier, and per-credit rates for every Flex tier, public without login (20). 2,500 lookups a day free with no card until usage passes the free tier (20). Signup and key creation are a browser flow at dash.geocod.io (0). 0+20+20+0 = 40." }, "scores": { "a": 30, "b": 40 } }, { "by": 10, "category": "transparency", "leads": "geocodio", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under the AWS Service Terms (last updated 30 October 2026, re-read on 1 November), whose section 82 sets out storage, caching and attribution rules in detail (15 of 30). The guide says device positions are kept 30 days, geofences until deleted, and that queries are stripped of customer metadata before they go to data providers (per the 8 October check). Section 82.1 agrees and adds that providers may process requests outside the chosen region. No retention period was found for Places and Routes requests (20 of 30). Section 82.3 still allows AWS to change or drop a provider or feature on notice \"where practicable\", and no dated deprecation notice or end date for the v1 APIs was found (5 of 20). AWS's sub-processor page, re-read on 1 November (last updated 30 October 2026), lists Esri for Amazon Location in Australia, Germany and the USA and Grabtaxi Holdings and HERE North America in Ireland, Japan, Singapore and the USA, says processing happens in the customer's selected Regions and the providers' locations, and promises 30 days' notice of a new sub-processor. The region is chosen per request (20 of 20, as for S3, SES and Secrets Manager). 15 + 20 + 5 + 20 = 60.", "b": "Editorial half only. Closed service with clear, dated terms under Virginia law, and libraries and CLI under MIT (20). The privacy policy says API and spreadsheet input and results are deleted within 45 days, error logs kept 90 days, and customer data isn't used to train AI models. A separate data retention policy and llms.txt put Lists API data at 72 hours. Results may be stored permanently by the customer (27). Replaced API versions are guaranteed for at least 12 months, breaking changes come only with a new version, and the changelog marks each one 'Breaking' (18). The privacy policy names its processors, such as Sentry and Laravel Nightwatch, and the security page says self-serve is hosted in Europe (15). 20+27+18+15 = 80." }, "scores": { "a": 77, "b": 87 } }, { "by": 8, "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`, opt-in `fields` appends and `stable_address_key` re-lookups size responses and cost, and results are ordered best first (20). Batches of 10,000 lookups, Lists for 10 million, distance filters (max_distance, max_results, order_by) and paginated list listings (17). Codes 403, 422, 429 and 500 each carry a documented meaning and retry rule, error bodies link a help page, and `_warnings` reports ignored parameters (18). Geocoding reads are safe to retry, but there's no idempotency key on batch or list creation and AGENTS.md says a retried request is billed again (10). One required parameter on a single geocode, and official libraries for Python, Node, PHP and Ruby plus a CLI with `--agent` output (15). 20+17+18+10+15 = 80." }, "scores": { "a": 88, "b": 80 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Dotsquare LLC", "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": "$1600 per month (plan)", "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-11-03", "name": "Last release" }, { "a": "2026-10-01", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "2018-05-25", "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": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "427k npm/wk", "b": "21k npm/wk, 921 PyPI/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 Geocodio's 72.2 (BB), and leads in 3 of 7 scored categories. Geocodio leads on schema \u0026 documentation, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Amazon Location Service or Geocodio?" }, { "answer": "Both need an API key.", "question": "Do Amazon Location Service and Geocodio 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 Geocodio.", "question": "Can an agent call Amazon Location Service and Geocodio without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 95 against 70", "Agent ergonomics, 88 against 80", "Security \u0026 auth, 76 against 58" ], "also": [ "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": [ "Schema \u0026 documentation, 92 against 87", "Payments \u0026 pricing, 40 against 30", "Maintenance \u0026 community, 86 against 60", "Transparency \u0026 trust, 87 against 77" ], "also": null, "goodFor": "Batch geocoding and district or census enrichment of addresses in the US, Canada, Mexico, the UK, Australia and New Zealand, where results must be stored.", "slug": "geocodio", "watchFor": "Covers only the US, Canada, Mexico, the UK, Australia and New Zealand, and UK needs a Flex or Unlimited plan" } ], "history": { "amazon-location": [ { "causes": [ "security", "evidence", "correction" ], "date": "2026-10-17", "delta": 2.4, "from": 74.1, "fromGrade": "BB", "to": 76.5, "toGrade": "BB" } ], "geocodio": 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-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-maptiler.json", "title": "Amazon Location Service vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-maptiler" }, { "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-geocodio.json", "title": "ArcGIS Location Platform vs Geocodio", "url": "https://www.anchorterminal.com/compare/arcgis-vs-geocodio" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-geocodio.json", "title": "Azure Maps vs Geocodio", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-geocodio" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-geocodio.json", "title": "Geoapify Location Platform + MCP vs Geocodio", "url": "https://www.anchorterminal.com/compare/geoapify-vs-geocodio" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-google-maps-platform.json", "title": "Geocodio vs Google Maps Platform + Grounding Lite MCP", "url": "https://www.anchorterminal.com/compare/geocodio-vs-google-maps-platform" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-here-location-services.json", "title": "Geocodio vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/geocodio-vs-here-location-services" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-locationiq.json", "title": "Geocodio vs LocationIQ", "url": "https://www.anchorterminal.com/compare/geocodio-vs-locationiq" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-mapbox.json", "title": "Geocodio vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/geocodio-vs-mapbox" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-mapquest.json", "title": "Geocodio vs MapQuest", "url": "https://www.anchorterminal.com/compare/geocodio-vs-mapquest" }, { "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/geocodio-vs-nextbillion.json", "title": "Geocodio vs NextBillion.ai", "url": "https://www.anchorterminal.com/compare/geocodio-vs-nextbillion" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-nominatim.json", "title": "Geocodio vs Nominatim", "url": "https://www.anchorterminal.com/compare/geocodio-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-opencage.json", "title": "Geocodio vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/geocodio-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-radar.json", "title": "Geocodio vs Radar", "url": "https://www.anchorterminal.com/compare/geocodio-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps.json", "title": "Geocodio vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-tomtom.json", "title": "Geocodio vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/geocodio-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-woosmap.json", "title": "Geocodio vs Woosmap", "url": "https://www.anchorterminal.com/compare/geocodio-vs-woosmap" } ], "panel": null, "scores": [ { "amazon-location": 95, "by": 25, "edge": "amazon-location", "geocodio": 70, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amazon-location": 87, "by": 5, "edge": "geocodio", "geocodio": 92, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "amazon-location": 88, "by": 8, "edge": "amazon-location", "geocodio": 80, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "amazon-location": 76, "by": 18, "edge": "amazon-location", "geocodio": 58, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "amazon-location": 30, "by": 10, "edge": "geocodio", "geocodio": 40, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amazon-location": 60, "by": 26, "edge": "geocodio", "geocodio": 86, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "amazon-location": 77, "by": 10, "edge": "geocodio", "geocodio": 87, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Amazon Location Service scores 76.5 (BB) on agent readiness against Geocodio's 72.2 (BB), and leads in 3 of 7 scored categories. Geocodio leads on schema \u0026 documentation, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. 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.", "geocodio": "Geocodio publishes llms.txt, an AGENTS.md on cost and retries, an OpenAPI spec and a dated changelog, and its results may be stored permanently. Coverage stops at six countries, there's no MCP server or published SLA for self-serve plans, and the docs still put the key in the query string by default." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amazon-location-vs-geocodio", "json": "https://www.anchorterminal.com/compare/amazon-location-vs-geocodio.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amazon-location-vs-geocodio.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/amazon-location-vs-geocodio.min.md" }, "markdown": "Amazon Location Service scores 76.5 (BB) on agent readiness against Geocodio's 72.2 (BB), and leads in 3 of 7 scored categories. Geocodio leads on schema \u0026 documentation, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. 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- Geocodio: grade BB, 72.2/100, rank #138 of 1510. Markdown https://www.anchorterminal.com/tools/geocodio.md · JSON https://www.anchorterminal.com/api/v1/tools/geocodio.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 70\n- Agent ergonomics, 88 against 80\n- Security \u0026 auth, 76 against 58\n\nAlso in its favour:\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### Geocodio (BB)\n\nGood for: Batch geocoding and district or census enrichment of addresses in the US, Canada, Mexico, the UK, Australia and New Zealand, where results must be stored.\n\nAhead on:\n- Schema \u0026 documentation, 92 against 87\n- Payments \u0026 pricing, 40 against 30\n- Maintenance \u0026 community, 86 against 60\n- Transparency \u0026 trust, 87 against 77\n\nWatch for: Covers only the US, Canada, Mexico, the UK, Australia and New Zealand, and UK needs a Flex or Unlimited plan\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Geocodio +26\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- Geocodio (86): API v2.1 released 3 November 2026 (Australia and New Zealand), and PHP library 3.4.1 on 4 November (30). Dated changelog entries on 8 September, 1, 8, 9, 19, 22 and 31 October and 3 November 2026, plus library releases in October (20). Public changelog, support by email and a team-staffed help desk named on the pricing page. We didn't read GitHub issue reply times (12). Official Python 1.6.0 and Node 2.3.0 from 12 October and PHP 3.4.1 from 4 November are current (15). Each library and the CLI run CI on GitHub Actions; we didn't check whether the runs pass (9). 30+20+12+15+9 = 86.\n\n### Reliability: Amazon Location Service +25\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- Geocodio (70): Hosted lines. incident.io status page at status.geocod.io with five components (Geocodio API, Dashboard, Enterprise API, Enterprise Dashboard, Website) and an incidents feed at /api/v2/incidents.json (20). In the 90 days to 6 November 2026 the feed lists one incident marked major, 'Spreadsheet geocoding jobs are failing' on 27 October from 12:35 to 15:15 UTC, and a PHP security patch on 21 October marked no impact, so one major outage of a core feature (10). 1,000 requests a minute on single geocoding for pay-as-you-go and Flex, 100 on Enterprise Flex (15). 429 carries X-RateLimit-Remaining, -Limit and -Period, and llms.txt and AGENTS.md give a retry rule per status code with capped backoff, plus client-side idempotency guidance for the non-idempotent list and batch writes (15). The pricing page lists custom SLAs as an add-on on Unlimited and Enterprise plans, with no published terms, so no SLA (0). GA (10). 20+10+15+15+0+10 = 70.\n\n### Security \u0026 auth: Amazon Location Service +18\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- Geocodio (58): Revocable keys, five on pay-as-you-go, each with permissions (Lists and Distance off by default), which earns 25. Less 10 because the docs say 'All requests require \u0026api_key=YOUR_API_KEY' and the OpenAPI spec defines only the query scheme, though an Authorization header has worked since March 2025 (15). Per-key permissions limit what a key can reach. DELETE on lists and distance jobs needs no confirmation (13). Results are addresses and government district, census and legislator data rather than user-written text. No prompt-injection guidance found (9). Usage per API key in the dashboard, downloadable as CSV, and billable-lookup headers on every response (8). Valid security.txt to 30 January 2030 with a PGP key and a responsible disclosure policy. SOC 2 Type II and annual penetration tests apply to the Enterprise platform only. No bug bounty found (13). 15+13+9+8+13 = 58.\n\n### Payments \u0026 pricing: Geocodio +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- Geocodio (40): No x402, MPP or L402 (0). $1 per 1,000 lookups after the free tier, and per-credit rates for every Flex tier, public without login (20). 2,500 lookups a day free with no card until usage passes the free tier (20). Signup and key creation are a browser flow at dash.geocod.io (0). 0+20+20+0 = 40.\n\n### Transparency \u0026 trust: Geocodio +10\n\n- Amazon Location Service (77): Closed service under the AWS Service Terms (last updated 30 October 2026, re-read on 1 November), whose section 82 sets out storage, caching and attribution rules in detail (15 of 30). The guide says device positions are kept 30 days, geofences until deleted, and that queries are stripped of customer metadata before they go to data providers (per the 8 October check). Section 82.1 agrees and adds that providers may process requests outside the chosen region. No retention period was found for Places and Routes requests (20 of 30). Section 82.3 still allows AWS to change or drop a provider or feature on notice \"where practicable\", and no dated deprecation notice or end date for the v1 APIs was found (5 of 20). AWS's sub-processor page, re-read on 1 November (last updated 30 October 2026), lists Esri for Amazon Location in Australia, Germany and the USA and Grabtaxi Holdings and HERE North America in Ireland, Japan, Singapore and the USA, says processing happens in the customer's selected Regions and the providers' locations, and promises 30 days' notice of a new sub-processor. The region is chosen per request (20 of 20, as for S3, SES and Secrets Manager). 15 + 20 + 5 + 20 = 60.\n- Geocodio (87): Editorial half only. Closed service with clear, dated terms under Virginia law, and libraries and CLI under MIT (20). The privacy policy says API and spreadsheet input and results are deleted within 45 days, error logs kept 90 days, and customer data isn't used to train AI models. A separate data retention policy and llms.txt put Lists API data at 72 hours. Results may be stored permanently by the customer (27). Replaced API versions are guaranteed for at least 12 months, breaking changes come only with a new version, and the changelog marks each one 'Breaking' (18). The privacy policy names its processors, such as Sentry and Laravel Nightwatch, and the security page says self-serve is hosted in Europe (15). 20+27+18+15 = 80.\n\n### Agent ergonomics: Amazon Location Service +8\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- Geocodio (80): API reading. `limit`, opt-in `fields` appends and `stable_address_key` re-lookups size responses and cost, and results are ordered best first (20). Batches of 10,000 lookups, Lists for 10 million, distance filters (max_distance, max_results, order_by) and paginated list listings (17). Codes 403, 422, 429 and 500 each carry a documented meaning and retry rule, error bodies link a help page, and `_warnings` reports ignored parameters (18). Geocoding reads are safe to retry, but there's no idempotency key on batch or list creation and AGENTS.md says a retried request is billed again (10). One required parameter on a single geocode, and official libraries for Python, Node, PHP and Ruby plus a CLI with `--agent` output (15). 20+17+18+10+15 = 80.\n\n## Score by category\n\n| Category | Weight | Amazon Location Service | Geocodio | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 95 | 70 | Amazon Location Service +25 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 92 | Geocodio +5 |\n| Agent ergonomics | 13% (16.2 this run) | 88 | 80 | Amazon Location Service +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 76 | 58 | Amazon Location Service +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | Geocodio +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 86 | Geocodio +26 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 87 | Geocodio +10 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **76.5 · BB** | **72.2 · BB** | |\n\n## Facts side by side\n\n| Fact | Amazon Location Service | Geocodio |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Dotsquare LLC |\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 | $1600 per month (plan) |\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-11-03 |\n| Terms last updated | 2026-10-01 | no date given |\n| Privacy policy last updated | 2026-05-18 | 2018-05-25 |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 427k npm/wk | 21k npm/wk, 921 PyPI/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### Geocodio\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**Geocodio.** Geocodio publishes llms.txt, an AGENTS.md on cost and retries, an OpenAPI spec and a dated changelog, and its results may be stored permanently. Coverage stops at six countries, there's no MCP server or published SLA for self-serve plans, and the docs still put the key in the query string by default.\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### Geocodio\n\n1. Always set `country`, because an address with none falls back to the US and is billed even when it's wrong\n2. Send the key as `Authorization: Bearer`, not in the query string, so it stays out of logs\n3. Use batch POST /geocode (up to 10,000 lookups) or the Lists API rather than looping single requests\n4. Treat accuracy_type place, county or state as not found, and check `_warnings` for appends that were billed but skipped\n5. Don't retry 403 or 422. On 429 read X-RateLimit headers and back off, and never re-upload a list sitting in ENQUEUED\n\n## Questions\n\n### Which is better for AI agents, Amazon Location Service or Geocodio?\n\nAmazon Location Service scores 76.5 (BB) on agent readiness against Geocodio's 72.2 (BB), and leads in 3 of 7 scored categories. Geocodio leads on schema \u0026 documentation, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Amazon Location Service and Geocodio need an API key?\n\nBoth need an API key.\n\n### Can an agent call Amazon Location Service and Geocodio 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 Geocodio.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-location-vs-geocodio.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-location-vs-geocodio.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-location\", \"b\": \"geocodio\"}`. From a terminal: `anchor compare amazon-location geocodio`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-location.json and https://www.anchorterminal.com/api/v1/tools/geocodio.json\n\n## Other comparisons with Amazon Location Service or Geocodio\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 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 MapTiler Cloud](https://www.anchorterminal.com/compare/amazon-location-vs-maptiler.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 Geocodio](https://www.anchorterminal.com/compare/arcgis-vs-geocodio.md)\n- [Azure Maps vs Geocodio](https://www.anchorterminal.com/compare/azure-maps-vs-geocodio.md)\n- [Geoapify Location Platform + MCP vs Geocodio](https://www.anchorterminal.com/compare/geoapify-vs-geocodio.md)\n- [Geocodio vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/geocodio-vs-google-maps-platform.md)\n- [Geocodio vs HERE Location Services](https://www.anchorterminal.com/compare/geocodio-vs-here-location-services.md)\n- [Geocodio vs LocationIQ](https://www.anchorterminal.com/compare/geocodio-vs-locationiq.md)\n- [Geocodio vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/geocodio-vs-mapbox.md)\n- [Geocodio vs MapQuest](https://www.anchorterminal.com/compare/geocodio-vs-mapquest.md)\n- [Geocodio vs MapTiler Cloud](https://www.anchorterminal.com/compare/geocodio-vs-maptiler.md)\n- [Geocodio vs NextBillion.ai](https://www.anchorterminal.com/compare/geocodio-vs-nextbillion.md)\n- [Geocodio vs Nominatim](https://www.anchorterminal.com/compare/geocodio-vs-nominatim.md)\n- [Geocodio vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/geocodio-vs-opencage.md)\n- [Geocodio vs Radar](https://www.anchorterminal.com/compare/geocodio-vs-radar.md)\n- [Geocodio vs Stadia Maps](https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps.md)\n- [Geocodio vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geocodio-vs-tomtom.md)\n- [Geocodio vs Woosmap](https://www.anchorterminal.com/compare/geocodio-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 Geocodio", "url": "" } ], "description": "Amazon Location Service scores 76.5 (BB) to Geocodio's 72.2 (BB) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Amazon Location Service BB 76.5", "Geocodio BB 72.2", "scores" ], "h1": "Amazon Location Service vs Geocodio", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/amazon-location-vs-geocodio", "published": "2026-10-01", "section": "tools", "title": "Amazon Location Service vs Geocodio for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-geocodio" }, "tokens": { "markdown": 5700, "slim": 3480 }, "version": 1 }