{ "data": { "a": { "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" } }, "answer": "Geocodio scores 72.2 (BB) on agent readiness against Stadia Maps's 65.2 (B), and leads in 5 of 7 scored categories.", "b": { "slug": "stadia-maps", "name": "Stadia Maps", "vendor": "Stadia Maps", "vendorUrl": "https://stadiamaps.com", "kind": "http-api", "category": "maps", "summary": "Geocoding, reverse geocoding, autocomplete and place details, routing, matrix, isochrones, static maps and hosted vector, raster and satellite tiles, sold in credits on plans from $20 a month.", "url": "https://www.anchorterminal.com/tools/stadia-maps", "markdownUrl": "https://www.anchorterminal.com/tools/stadia-maps.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/stadia-maps.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/stadia-maps.json", "dns": "stadia-maps.grade.anchorterminal.com", "repo": "https://github.com/stadiamaps/stadiamaps-mcp-server-ts", "license": "BSD-3-Clause (MCP server)", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.stadiamaps.com", "packages": [ { "registry": "npm", "name": "@stadiamaps/api" }, { "registry": "pypi", "name": "stadiamaps" } ], "auth": "api-key", "authNotes": "API key as the api_key query parameter or in an `Authorization: Stadia-Auth \u003ckey\u003e` header. Browser apps can use domain-based auth with no key, checked against the Origin and Referer headers. The MCP server reads API_KEY.", "pricing": "freemium", "pricingNotes": "Free 200,000 credits a month for development, testing and demos only, no commercial use. Starter $20 a month (1 million credits), Standard $80 (7.5 million), Professional $250 (25 million), with overage at $0.03, $0.02 and $0.015 per 1,000 credits. A forward, reverse or structured geocode, a place lookup, an Autocomplete v1 search or a route is 20 credits, Autocomplete v2 is 1, a matrix element 10, a map tile 1 and a satellite tile 4, so Starter covers 50,000 geocodes. New accounts get a 14-day Professional trial with no card (https://stadiamaps.com/pricing/). When credits run out you get 429 until the next cycle unless pay-as-you-go is on (https://stadiamaps.com/faqs/).", "priceSummary": "$20 / mo", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": 6, "popularity": { "githubStars": 23, "npmWeekly": 6058, "pypiWeekly": 192, "asOf": "2026-09-30" }, "docsUrl": "https://docs.stadiamaps.com", "llmsTxt": "https://docs.stadiamaps.com/llms.txt", "openapi": "https://api.stadiamaps.com/openapi.yaml", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "llms-txt", "official", "typescript", "python", "free-tier", "no-card", "open-data" ], "lastRelease": "2026-10-26", "graded": true, "anchor": { "graded": true, "score": 65.2, "grade": "B", "agentReady": false, "rank": 433, "ranked": true, "rankOf": 1510, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 80, "payments": 40, "reliability": 63, "schema": 86, "security": 40, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": 0, "verdict": "Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only.", "bestFor": "Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.", "strengths": [ "Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs", "Published credit costs, with 50,000 geocodes for $20 a month on Starter", "Header auth keeps the key out of URLs, and keys rotate through an API", "Server logs kept about 7 to 14 days, and a DPA", "14 dated changelog entries between June and September 2026" ], "weaknesses": [ "Free plan is for development, testing and demos only", "The same 429 signals a burst or a spent month of credits, with no Retry-After", "No SLA, no security.txt and no disclosure policy found", "MCP server has no release, no CI and no commits since 29 July 2025", "The terms forbid benchmarking against competitors without written permission" ], "agentNotes": [ "Send the key as `Authorization: Stadia-Auth \u003ckey\u003e` rather than in the URL", "Try Autocomplete v2 (1 credit) before a full geocode (20 credits) when a name is enough", "Check the dashboard's credit balance before retrying a 429, since it may mean the month is spent", "Don't write geocodes to a database on Free or Starter", "Use bulk-geocode for addresses only, not POI names" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 65.2 } ], "editorialScores": { "ergonomics": 80, "maintenance": 80, "payments": 40, "reliability": 63, "schema": 86, "security": 40, "transparency": 72 }, "provenanceScore": 80, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-10-08", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -H \"Authorization: Stadia-Auth $STADIA_API_KEY\" \"https://api.stadiamaps.com/geocoding/v1/search?text=10%20Downing%20Street%2C%20London\u0026size=1\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/stadia-maps" }, "area": "everyday", "unitPrices": [ { "item": "Starter plan", "unit": "month", "usd": 20, "note": "1 million credits, about 50,000 geocodes" }, { "item": "Standard plan", "unit": "month", "usd": 80, "note": "7.5 million credits, permanent geocode storage" }, { "item": "Professional plan", "unit": "month", "usd": 250, "note": "25 million credits" }, { "item": "Geocoding within Starter", "unit": "1k-requests", "usd": 0.4, "note": "20 credits each, $20 for 1 million credits" }, { "item": "Geocoding overage on Starter", "unit": "1k-requests", "usd": 0.6, "note": "20 credits each at $0.03 per 1,000 credits" } ], "provenance": { "legalEntity": "Stadia Maps, Inc.", "domain": "stadiamaps.com", "domainRegistered": "2016-11-30", "endpointOnVendorDomain": true, "terms": "https://stadiamaps.com/terms-of-service/", "privacy": "https://stadiamaps.com/privacy/privacy-policy/", "statusPage": "https://status.stadiamaps.com", "changelog": "https://stadiamaps.com/changelog/", "securityTxt": "none", "checked": "2026-11-02", "notes": [ "The terms name Stadia Maps, Inc., a Delaware corporation with an address in East Lansing, Michigan, under Delaware law. Last updated 18 March 2026.", "Pages showing Traffic Products must carry \"© Stadia Maps © TomTom\".", "stadiamaps.com/.well-known/security.txt returned 404 on 2026-09-30 and again on 2026-11-02." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/stadia-maps.json", "live": { "slug": "stadia-maps", "probe": { "target": "https://api.stadiamaps.com", "method": "get", "lastAt": "2026-11-07T19:22:35.986794709Z", "lastOk": true, "lastStatus": 404, "lastMs": 59, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 38, "p95ms24h": 121, "samples24h": 238, "samples30d": 7920, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "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": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "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 } ] }, "vendorStatus": { "page": "https://status.stadiamaps.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:48.860153105Z" }, "versions": [ { "registry": "npm", "name": "@stadiamaps/api", "version": "9.1.0", "seenAt": "2026-11-07T00:08:18.390771756Z" }, { "registry": "pypi", "name": "stadiamaps", "version": "8.1.0", "released": "2026-04-27", "seenAt": "2026-11-07T00:08:19.436197982Z" } ], "githubStars": 25, "npmWeekly": 5629, "pypiWeekly": 257, "securityTxt": { "url": "https://stadiamaps.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:53.421563591Z" }, "llmsTxt": { "url": "https://docs.stadiamaps.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:02.632314399Z" }, "domain": { "domain": "stadiamaps.com", "registered": "2016-11-30", "source": "https://rdap.verisign.com/com/v1/domain/stadiamaps.com", "checkedAt": "2026-11-01T14:16:14.439995302Z" }, "pages": [ { "url": "https://stadiamaps.com/changelog/", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:20:47.194860696Z", "changedAt": "2026-11-03T07:59:24.869309921Z", "fingerprint": "84f157f93d47" }, { "url": "https://stadiamaps.com/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:20:49.286778217Z", "changedAt": "2026-10-30T05:49:14.583115496Z", "fingerprint": "1129178e256e" }, { "url": "https://stadiamaps.com/privacy/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:20:51.230633816Z", "changedAt": "2026-10-30T05:49:16.651265989Z", "fingerprint": "dea22601908a" }, { "url": "https://stadiamaps.com/terms-of-service/", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:20:53.28669173Z", "changedAt": "2026-10-30T05:49:18.614187045Z", "fingerprint": "f6e28a9f6a07" } ], "github": { "repo": "stadiamaps/stadiamaps-mcp-server-ts", "checkedAt": "2026-11-02T09:27:58.17869331Z", "stars": 25, "archived": false, "issuesEnabled": true, "pushedAt": "2025-07-29T09:13:45Z", "openIssues": 1, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "replies": { "sampled": 1, "unanswered": 1 } }, "updatedAt": "2026-11-07T19:22:35.986794709Z" } }, "edges": [ { "by": 18, "category": "security", "leads": "geocodio", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "Revocable keys per property with rotation through the Account Management API and a header option (`Authorization: Stadia-Auth`), which earns 25. Less 10 because api_key in the query string is a documented option (the authentication page re-read on 2 November calls it the simplest) and the OpenAPI document defines only that scheme (15). The APIs only read, but keys aren't scoped to particular APIs (12). Results carry OpenStreetMap names, websites and opening hours, which are community-edited text, and we found no prompt-injection guidance (7). Dashboard usage and billing threshold alerts added on 20 August 2026 (6). stadiamaps.com/.well-known/security.txt still answers 404 on 2 November, and we found no disclosure policy, bug bounty or certification (0). 15+12+7+6+0 = 40." }, "scores": { "a": 58, "b": 40 } }, { "by": 11, "category": "transparency", "leads": "geocodio", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "Closed service with clear terms, last updated 18 March 2026, a BSD-3-Clause MCP server and open-source SDKs (20). Server logs kept about 7 to 14 days, account data deleted within 30 days of closure, a DPA, and per-plan storage rules spelt out. The privacy policy was updated 1 October 2026 (28). No deprecation policy. The terms promise 30 days' notice for fee increases and reasonable efforts for other material changes (6). Third-party processors listed with locations in the privacy policy, and hosting described as primarily US (18). 20+28+6+18 = 72." }, "scores": { "a": 87, "b": 76 } }, { "by": 7, "category": "reliability", "leads": "geocodio", "name": "Reliability", "reasons": { "a": "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.", "b": "Instatus page with 27 components across maps, routing, geocoding and data APIs, plus RSS and Atom history back to April 2025 (20). One incident in the 90 days to 2 November (history feed re-read on 2 November), on 25 September 2026, when a software update on edge nodes caused elevated request errors \"in the initial deployment regions\" across 24 listed components from 10:20 to 10:22 UTC before it was rolled back. Limited to some regions and two minutes, so minor (20). The FAQ says there's no fixed requests-a-second limit and the cap is the monthly credit pool, with credits per call published (12). A 429 is what you get when credits run out until the next cycle, with no Retry-After and no backoff guidance, so an agent can't tell a spent month from a burst (3). No SLA. The terms say the service is provided as is (0). The APIs are GA, but the MCP server has no release (8). 20+20+12+3+0+8 = 63." }, "scores": { "a": 70, "b": 63 } }, { "by": 6, "category": "schema", "leads": "geocodio", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.0.1 spec, version 2.1.0, with 11 paths (25). llms.txt and an AGENTS.md written for agents (10). llms.txt and AGENTS.md say when to use each endpoint and when not to, such as the Lists API over looping single calls, the upload tool for a one-off spreadsheet and straightline over driving distance unless road distance is needed (19). Typed parameters with country values, component fields and documented limits, though `fields` is a comma-separated string (12). Error table with retry guidance, examples throughout, but the spec documents 200, 400, 403, 404, 422 and 424 and not 429 or 500 (11). Versioned paths from v1 to v2.1 and a dated public changelog with entries back to 2024 (15). 25+10+19+12+11+15 = 92.", "b": "Public OpenAPI 3.1.0 document at api.stadiamaps.com/openapi.yaml, version 11.1.0 (re-read on 2 November), from which the TypeScript and Python SDKs are generated (25). llms.txt at docs.stadiamaps.com, re-read on 2 November (10). The MCP's six tool descriptions say when not to use a tool, for example bulk-geocode warns against POI names (14). Zod inputs with minimums such as at least two route locations, but some fields are loose strings (12). Docs examples per endpoint. We didn't read an error reference (10). A dated public changelog with 14 entries between 12 August and 26 October 2026 and a Keep a Changelog file in each SDK (15). 25+10+14+12+10+15 = 86." }, "scores": { "a": 92, "b": 86 } }, { "by": 6, "category": "maintenance", "leads": "geocodio", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Changelog entry on 26 October 2026, a forward geocoding fix for Unicode edge cases (30). 14 dated changelog entries between 12 August and 26 October 2026, among them the 20 October Static Maps rebuild and the 17 October geocoding data release (20). A public changelog and support desk, but the MCP repo's last commit is still 29 July 2025 on 2 November (10). Official TypeScript SDK v9.1.0 and Python SDK v8.1.0, both tagged 27 April 2026 and still the newest tags (15). SDK CI runs integration tests against the live API, but the MCP server has no CI, no tagged release, no npm package and no registry entry (5). 30+20+10+15+5 = 80." }, "scores": { "a": 86, "b": 80 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Dotsquare LLC", "b": "Stadia Maps", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.stadiamaps.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "$1600 per month (plan)", "b": "$0.40 per 1,000 requests", "name": "Price for geocoding" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "BSD-3-Clause (MCP server)", "name": "Licence" }, { "a": "none", "b": "6", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-11-03", "b": "2026-10-26", "name": "Last release" }, { "a": "no date given", "b": "2026-03-18", "name": "Terms last updated" }, { "a": "2018-05-25", "b": "2026-10-01", "name": "Privacy policy last updated" }, { "a": "not found in the text", "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": "21k npm/wk, 921 PyPI/wk", "b": "23 stars, 6.1k npm/wk, 192 PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Geocodio scores 72.2 (BB) on agent readiness against Stadia Maps's 65.2 (B), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, Geocodio or Stadia Maps?" }, { "answer": "Both need an API key.", "question": "Do Geocodio and Stadia Maps need an API key?" }, { "answer": "No hosted endpoint is listed for Geocodio. Stadia Maps has a hosted endpoint at https://api.stadiamaps.com.", "question": "Can an agent call Geocodio and Stadia Maps without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 70 against 63", "Schema \u0026 documentation, 92 against 86", "Security \u0026 auth, 58 against 40", "Maintenance \u0026 community, 86 against 80", "Transparency \u0026 trust, 87 against 76" ], "also": [ "Agent-ready, a grade of BB or better" ], "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" }, { "aheadOn": null, "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine" ], "goodFor": "Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.", "slug": "stadia-maps", "watchFor": "Free plan is for development, testing and demos only" } ], "history": { "geocodio": null, "stadia-maps": [ { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 65.5, "fromGrade": "B", "to": 65.2, "toGrade": "B" } ] }, "job": { "capability": "geo.geocode", "name": "Geocoding" }, "others": [ { "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-stadia-maps.json", "title": "Amazon Location Service vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-geocodio.json", "title": "ArcGIS Location Platform vs Geocodio", "url": "https://www.anchorterminal.com/compare/arcgis-vs-geocodio" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps.json", "title": "ArcGIS Location Platform vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps" }, { "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/azure-maps-vs-stadia-maps.json", "title": "Azure Maps vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps" }, { "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/geoapify-vs-stadia-maps.json", "title": "Geoapify Location Platform + MCP vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/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-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" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps.json", "title": "Google Maps Platform + Grounding Lite MCP vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.json", "title": "HERE Location Services vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps.json", "title": "LocationIQ vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps.json", "title": "Mapbox APIs + MCP vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.json", "title": "MapQuest vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps" }, { "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/nominatim-vs-stadia-maps.json", "title": "Nominatim vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/nominatim-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/opencage-vs-stadia-maps.json", "title": "OpenCage Geocoding API vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/opencage-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/radar-vs-stadia-maps.json", "title": "Radar vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/radar-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.json", "title": "Stadia Maps vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap.json", "title": "Stadia Maps vs Woosmap", "url": "https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/nextbillion-vs-stadia-maps.json", "title": "NextBillion.ai vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/nextbillion-vs-stadia-maps" } ], "panel": null, "scores": [ { "by": 7, "edge": "geocodio", "geocodio": 70, "key": "reliability", "name": "Reliability", "stadia-maps": 63, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 6, "edge": "geocodio", "geocodio": 92, "key": "schema", "name": "Schema \u0026 documentation", "stadia-maps": 86, "weight": 13 }, { "by": 0, "edge": "", "geocodio": 80, "key": "ergonomics", "name": "Agent ergonomics", "stadia-maps": 80, "weight": 13 }, { "by": 18, "edge": "geocodio", "geocodio": 58, "key": "security", "name": "Security \u0026 auth", "stadia-maps": 40, "weight": 14 }, { "by": 0, "edge": "", "geocodio": 40, "key": "payments", "name": "Payments \u0026 pricing", "stadia-maps": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 6, "edge": "geocodio", "geocodio": 86, "key": "maintenance", "name": "Maintenance \u0026 community", "stadia-maps": 80, "weight": 7 }, { "by": 11, "edge": "geocodio", "geocodio": 87, "key": "transparency", "name": "Transparency \u0026 trust", "stadia-maps": 76, "weight": 7 } ], "summary": "Geocodio scores 72.2 (BB) on agent readiness against Stadia Maps's 65.2 (B), and leads in 5 of 7 scored categories. Both do geocoding.", "tasks": null, "tutorials": [], "verdicts": { "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.", "stadia-maps": "Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps", "json": "https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps.min.md" }, "markdown": "Geocodio scores 72.2 (BB) on agent readiness against Stadia Maps's 65.2 (B), and leads in 5 of 7 scored categories. Both do geocoding.\n\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- Stadia Maps: grade B, 65.2/100, rank #433 of 1510. Markdown https://www.anchorterminal.com/tools/stadia-maps.md · JSON https://www.anchorterminal.com/api/v1/tools/stadia-maps.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### 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- Reliability, 70 against 63\n- Schema \u0026 documentation, 92 against 86\n- Security \u0026 auth, 58 against 40\n- Maintenance \u0026 community, 86 against 80\n- Transparency \u0026 trust, 87 against 76\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\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### Stadia Maps (B)\n\nGood for: Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n\nWatch for: Free plan is for development, testing and demos only\n\n\n## Why the edge\n\n### Security \u0026 auth: Geocodio +18\n\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- Stadia Maps (40): Revocable keys per property with rotation through the Account Management API and a header option (`Authorization: Stadia-Auth`), which earns 25. Less 10 because api_key in the query string is a documented option (the authentication page re-read on 2 November calls it the simplest) and the OpenAPI document defines only that scheme (15). The APIs only read, but keys aren't scoped to particular APIs (12). Results carry OpenStreetMap names, websites and opening hours, which are community-edited text, and we found no prompt-injection guidance (7). Dashboard usage and billing threshold alerts added on 20 August 2026 (6). stadiamaps.com/.well-known/security.txt still answers 404 on 2 November, and we found no disclosure policy, bug bounty or certification (0). 15+12+7+6+0 = 40.\n\n### Transparency \u0026 trust: Geocodio +11\n\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- Stadia Maps (76): Closed service with clear terms, last updated 18 March 2026, a BSD-3-Clause MCP server and open-source SDKs (20). Server logs kept about 7 to 14 days, account data deleted within 30 days of closure, a DPA, and per-plan storage rules spelt out. The privacy policy was updated 1 October 2026 (28). No deprecation policy. The terms promise 30 days' notice for fee increases and reasonable efforts for other material changes (6). Third-party processors listed with locations in the privacy policy, and hosting described as primarily US (18). 20+28+6+18 = 72.\n\n### Reliability: Geocodio +7\n\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- Stadia Maps (63): Instatus page with 27 components across maps, routing, geocoding and data APIs, plus RSS and Atom history back to April 2025 (20). One incident in the 90 days to 2 November (history feed re-read on 2 November), on 25 September 2026, when a software update on edge nodes caused elevated request errors \"in the initial deployment regions\" across 24 listed components from 10:20 to 10:22 UTC before it was rolled back. Limited to some regions and two minutes, so minor (20). The FAQ says there's no fixed requests-a-second limit and the cap is the monthly credit pool, with credits per call published (12). A 429 is what you get when credits run out until the next cycle, with no Retry-After and no backoff guidance, so an agent can't tell a spent month from a burst (3). No SLA. The terms say the service is provided as is (0). The APIs are GA, but the MCP server has no release (8). 20+20+12+3+0+8 = 63.\n\n### Schema \u0026 documentation: Geocodio +6\n\n- Geocodio (92): OpenAPI 3.0.1 spec, version 2.1.0, with 11 paths (25). llms.txt and an AGENTS.md written for agents (10). llms.txt and AGENTS.md say when to use each endpoint and when not to, such as the Lists API over looping single calls, the upload tool for a one-off spreadsheet and straightline over driving distance unless road distance is needed (19). Typed parameters with country values, component fields and documented limits, though `fields` is a comma-separated string (12). Error table with retry guidance, examples throughout, but the spec documents 200, 400, 403, 404, 422 and 424 and not 429 or 500 (11). Versioned paths from v1 to v2.1 and a dated public changelog with entries back to 2024 (15). 25+10+19+12+11+15 = 92.\n- Stadia Maps (86): Public OpenAPI 3.1.0 document at api.stadiamaps.com/openapi.yaml, version 11.1.0 (re-read on 2 November), from which the TypeScript and Python SDKs are generated (25). llms.txt at docs.stadiamaps.com, re-read on 2 November (10). The MCP's six tool descriptions say when not to use a tool, for example bulk-geocode warns against POI names (14). Zod inputs with minimums such as at least two route locations, but some fields are loose strings (12). Docs examples per endpoint. We didn't read an error reference (10). A dated public changelog with 14 entries between 12 August and 26 October 2026 and a Keep a Changelog file in each SDK (15). 25+10+14+12+10+15 = 86.\n\n### Maintenance \u0026 community: Geocodio +6\n\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- Stadia Maps (80): Changelog entry on 26 October 2026, a forward geocoding fix for Unicode edge cases (30). 14 dated changelog entries between 12 August and 26 October 2026, among them the 20 October Static Maps rebuild and the 17 October geocoding data release (20). A public changelog and support desk, but the MCP repo's last commit is still 29 July 2025 on 2 November (10). Official TypeScript SDK v9.1.0 and Python SDK v8.1.0, both tagged 27 April 2026 and still the newest tags (15). SDK CI runs integration tests against the live API, but the MCP server has no CI, no tagged release, no npm package and no registry entry (5). 30+20+10+15+5 = 80.\n\n## Score by category\n\n| Category | Weight | Geocodio | Stadia Maps | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 63 | Geocodio +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 92 | 86 | Geocodio +6 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 80 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 40 | Geocodio +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 40 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 86 | 80 | Geocodio +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 87 | 76 | Geocodio +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **72.2 · BB** | **65.2 · B** | |\n\n## Facts side by side\n\n| Fact | Geocodio | Stadia Maps |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Dotsquare LLC | Stadia Maps |\n| Hosted endpoint | no (local only) | `https://api.stadiamaps.com` |\n| Transports | HTTP | HTTP, stdio |\n| Auth | API key | API key |\n| Pricing | Freemium | Freemium |\n| Price for geocoding | $1600 per month (plan) | $0.40 per 1,000 requests |\n| x402 | no | no |\n| Licence | none | BSD-3-Clause (MCP server) |\n| Tools exposed | none | 6 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-11-03 | 2026-10-26 |\n| Terms last updated | no date given | 2026-03-18 |\n| Privacy policy last updated | 2018-05-25 | 2026-10-01 |\n| Customer content may train models | not found in the text | 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 | 21k npm/wk, 921 PyPI/wk | 23 stars, 6.1k npm/wk, 192 PyPI/wk |\n| Agent reviews | none | 3.5/5 (2) |\n\n## How the scores have moved\n\n### Geocodio\n\nNo score change since it was listed.\n\n### Stadia Maps\n\n- -0.3 on 8 October 2026: checklist\n\n## Verdicts\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**Stadia Maps.** Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only.\n\n## Before you call either\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### Stadia Maps\n\n1. Send the key as `Authorization: Stadia-Auth \u003ckey\u003e` rather than in the URL\n2. Try Autocomplete v2 (1 credit) before a full geocode (20 credits) when a name is enough\n3. Check the dashboard's credit balance before retrying a 429, since it may mean the month is spent\n4. Don't write geocodes to a database on Free or Starter\n5. Use bulk-geocode for addresses only, not POI names\n\n## Questions\n\n### Which is better for AI agents, Geocodio or Stadia Maps?\n\nGeocodio scores 72.2 (BB) on agent readiness against Stadia Maps's 65.2 (B), and leads in 5 of 7 scored categories.\n\n### Do Geocodio and Stadia Maps need an API key?\n\nBoth need an API key.\n\n### Can an agent call Geocodio and Stadia Maps without installing anything?\n\nNo hosted endpoint is listed for Geocodio. Stadia Maps has a hosted endpoint at https://api.stadiamaps.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps.json, and with the fewest tokens: https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"geocodio\", \"b\": \"stadia-maps\"}`. From a terminal: `anchor compare geocodio stadia-maps`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/geocodio.json and https://www.anchorterminal.com/api/v1/tools/stadia-maps.json\n\n## Other comparisons with Geocodio or Stadia Maps\n\n- [Amazon Location Service vs Geocodio](https://www.anchorterminal.com/compare/amazon-location-vs-geocodio.md)\n- [Amazon Location Service vs Stadia Maps](https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.md)\n- [ArcGIS Location Platform vs Geocodio](https://www.anchorterminal.com/compare/arcgis-vs-geocodio.md)\n- [ArcGIS Location Platform vs Stadia Maps](https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps.md)\n- [Azure Maps vs Geocodio](https://www.anchorterminal.com/compare/azure-maps-vs-geocodio.md)\n- [Azure Maps vs Stadia Maps](https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps.md)\n- [Geoapify Location Platform + MCP vs Geocodio](https://www.anchorterminal.com/compare/geoapify-vs-geocodio.md)\n- [Geoapify Location Platform + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps.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 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- [Google Maps Platform + Grounding Lite MCP vs Stadia Maps](https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps.md)\n- [HERE Location Services vs Stadia Maps](https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.md)\n- [LocationIQ vs Stadia Maps](https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps.md)\n- [Mapbox APIs + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps.md)\n- [MapQuest vs Stadia Maps](https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.md)\n- [MapTiler Cloud vs Stadia Maps](https://www.anchorterminal.com/compare/maptiler-vs-stadia-maps.md)\n- [Nominatim vs Stadia Maps](https://www.anchorterminal.com/compare/nominatim-vs-stadia-maps.md)\n- [OpenCage Geocoding API vs Stadia Maps](https://www.anchorterminal.com/compare/opencage-vs-stadia-maps.md)\n- [Radar vs Stadia Maps](https://www.anchorterminal.com/compare/radar-vs-stadia-maps.md)\n- [Stadia Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.md)\n- [Stadia Maps vs Woosmap](https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap.md)\n- [NextBillion.ai vs Stadia Maps](https://www.anchorterminal.com/compare/nextbillion-vs-stadia-maps.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": "Geocodio vs Stadia Maps", "url": "" } ], "description": "Geocodio scores 72.2 (BB) to Stadia Maps's 65.2 (B) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Geocodio BB 72.2", "Stadia Maps B 65.2", "scores" ], "h1": "Geocodio vs Stadia Maps", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/geocodio-vs-stadia-maps", "published": "2026-10-01", "section": "tools", "title": "Geocodio vs Stadia Maps for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps" }, "tokens": { "markdown": 4500, "slim": 2530 }, "version": 1 }