# Geocodio vs Google Maps Platform + Grounding Lite MCP > Google Maps Platform + Grounding Lite MCP scores 75.4 (BB) to Geocodio's 72.2 (BB) for geocoding. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/geocodio-vs-google-maps-platform - Markdown: https://www.anchorterminal.com/compare/geocodio-vs-google-maps-platform.md (~5,900 tokens) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-07 Google Maps Platform + Grounding Lite MCP scores 75.4 (BB) on agent readiness against Geocodio's 72.2 (BB), and leads in 3 of 7 scored categories. Geocodio leads on schema & documentation, maintenance & community and transparency & trust. Both do geocoding. - 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 - Google Maps Platform + Grounding Lite MCP: grade BB, 75.4/100, rank #63 of 1510. Markdown https://www.anchorterminal.com/tools/google-maps-platform.md · JSON https://www.anchorterminal.com/api/v1/tools/google-maps-platform.json - Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md - All 153 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md ## Which one, for what ### Geocodio (BB) Good 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. Ahead on: - Schema & documentation, 92 against 77 - Maintenance & community, 86 against 80 - Transparency & trust, 87 against 72 Also in its favour: - Free to start without a card Watch for: Covers only the US, Canada, Mexico, the UK, Australia and New Zealand, and UK needs a Flex or Unlimited plan ### Google Maps Platform + Grounding Lite MCP (BB) Good for: Best when the answer has to match what the user sees in Google Maps, for place details, opening hours and reviews. Ahead on: - Reliability, 90 against 70 - Agent ergonomics, 85 against 80 - Security & auth, 73 against 58 Also in its favour: - A hosted endpoint, with nothing to install Watch for: Free monthly caps beyond the prototyping Demo Key need a Cloud billing account with a payment method ## Why the edge ### Reliability: Google Maps Platform + Grounding Lite MCP +20 - 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. - Google Maps Platform + Grounding Lite MCP (90): Google Cloud's status dashboard has a Maps Platform section with per-product incident history and a JSON feed, re-read on 1 November (20). The 26 July traffic-data incident has left the 90-day window (cause time). Four incidents since 3 August. Directions, Distance Matrix and Routes had elevated errors and latency from 18:56 to 20:40 UTC on 19 October. Reverse-geocoding requests to the Geocoding API resolved to an address in Vietnam from 02:40 to 04:42 UTC on 23 October, which Google labels an outage, and some street results came back with incomplete or wrongly localised addresses from 25 October, resolved by 30 October with data restoration still running. A Maps SDK for Android crash on some Adreno GPUs on 28 September isn't on this listing's surfaces. Each touches one product, one group of products or some requests, so each is partial and read as minor, as this run reads Google's dashboard on google-speech-to-text and google-cloud-document-ai (20). Grounding Lite (now Maps Experience agent tools) quotas are 300 queries a minute per project for search, weather and routes and 600 for the resolvers, per the 1 October check, not re-read on 1 November (15). The Geocoding best-practice page gives exponential backoff with a worked example, 100 ms doubling to 5 s, and says which status codes to retry, per the 1 October check (15). A 99.9 per cent monthly SLA with 10, 25 and 50 per cent credits, re-read on 1 November (10). Places (New), Routes and the agent tools' Essentials SKU are GA; the Pro SKU is in Restricted GA (10). 20 + 20 + 15 + 15 + 10 + 10 = 90. ### Schema & documentation: Geocodio +15 - 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. - Google Maps Platform + Grounding Lite MCP (77): No OpenAPI, but the Places v1, Routes v2, Geocode, Weather and Isochrones contracts are public protobuf definitions in googleapis/googleapis (25). developers.google.com/maps/llms.txt returns 404 and we found no Markdown docs for agents (0). The REST reference explains each field and which SKU a field triggers. We couldn't read the Grounding Lite tool definitions, since the server is closed (12). Enums, required fields and field masks in the protos (13). Request and response examples on each method page, and documented status codes for Geocoding (12). Versioned paths (places v1, routes v2), dated release notes and a deprecations page (15). ### Security & auth: Google Maps Platform + Grounding Lite MCP +15 - 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 &api_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. - Google Maps Platform + Grounding Lite MCP (73): API keys with API restrictions and IP restrictions, documented rotation with an overlap window, and OAuth 2.0 with per-method scopes (such as maps-platform.places.textsearch in the Places discovery document) and the maps-platform.mapstools scope for the agent tools, which earns 30. Less 10 because a credential can travel in the URL. Classic Geocoding and Static Maps take the key as the `key` query parameter, and on 1 November Places API (New) answered a made-up `?key=` with API_KEY_INVALID and a made-up `?access_token=` with 401 invalid credentials (not missing), with both listed as query parameters in its discovery document. That's one deduction, the same test and reading as google-weather-api and gmail-api (20). A key can be restricted to the APIs it needs, and no agent-facing call writes anything (16). Places and the agent tools return reviews and AI-generated place summaries, which are third-party text, and we found no prompt-injection guidance (5). Cloud Monitoring's Metrics Explorer shows usage per key and per API (12). google.com's security.txt is valid to 1 April 2030 and names the vulnerability reward programme, and the Maps Platform trust centre lists ISO/IEC 27001:2022 and 27017, SOC 2 and SOC 3, both read on 1 November. Read as Google's hosted APIs whose product a certification names are read in this run (gmail-api, google-drive-api, google-cloud-document-ai, google-model-armor, google-speech-to-text) (20). 20 + 16 + 5 + 12 + 20 = 73. ### Transparency & trust: Geocodio +15 - 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. - Google Maps Platform + Grounding Lite MCP (72): Closed service with long, specific terms that were last modified 26 August 2026, and Apache-2.0 client libraries (18). The service terms spell out caching (coordinates 30 days, place IDs exempt, a per-user geocode cache allowed) and Grounding Lite says Maps content isn't cached, stored or used to improve the model. The privacy policy is Google's general one (22). A 12-month deprecation policy and a deprecations page with dates, such as the Heatmap Layer deprecated May 2025 and gone May 2026 (20). Separate EEA terms and regional contracting entities are disclosed. A Maps Platform subprocessor list wasn't at the URL we tried (5). ### Maintenance & community: Geocodio +6 - 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. - Google Maps Platform + Grounding Lite MCP (80): Newest dated API change is the Routes API note of 23 October 2026 on route tokens passed to the Navigation SDK, 9 days before this check (30). Three dated release-note entries in the 90 days from 3 August, Places API (New) on 6 August (entrances and navigation points), Geocoding API on 13 October (entrance display names and Experimental parking facilities) and Routes API on 23 October. The listed googlemaps Python client and Node services library tagged nothing in the window (20). Dated release notes, emailed change notices and a paid support route (12). Current generated clients such as @googlemaps/places, but the listed Python library googlemaps last tagged v4.10.0 on 26 January 2023 and its README now sends new APIs to the Cloud client libraries, and the Node services library last tagged v3.4.2 on 6 July 2025 (12). The generated clients are built in googleapis' CI. The older libraries say they sit outside the SLA and deprecation policy (6). 30 + 20 + 12 + 12 + 6 = 80. ### Agent ergonomics: Google Maps Platform + Grounding Lite MCP +5 - 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. - Google Maps Platform + Grounding Lite MCP (85): Grounding Lite has three tools plus two experimental resolvers, and the REST APIs size their responses with X-Goog-FieldMask, which also sets the price (25). pageSize and pageToken on Text Search, includedTypes, locationBias and locationRestriction (20). google.rpc status codes with messages, and Geocoding's OK, UNKNOWN_ERROR, OVER_QUERY_LIMIT and INVALID_REQUEST split into retryable and not (16). Every agent-facing call is a read and the backoff guidance is explicit. We couldn't check MCP annotations on the closed server (14). Official generated clients in many languages, such as @googlemaps/places 3.0.1 on npm, but a missing field mask on Places (New) or Routes is an error rather than a default, which costs a turn (10). ## Score by category | Category | Weight | Geocodio | Google Maps Platform + Grounding Lite MCP | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 70 | 90 | Google Maps Platform + Grounding Lite MCP +20 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 92 | 77 | Geocodio +15 | | Agent ergonomics | 13% (16.2 this run) | 80 | 85 | Google Maps Platform + Grounding Lite MCP +5 | | Security & auth | 14% (17.5 this run) | 58 | 73 | Google Maps Platform + Grounding Lite MCP +15 | | Payments & pricing | 10% (12.5 this run) | 40 | 40 | even | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 86 | 80 | Geocodio +6 | | Transparency & trust | 7% (8.8 this run) | 87 | 72 | Geocodio +15 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **72.2 · BB** | **75.4 · BB** | | ## Facts side by side | Fact | Geocodio | Google Maps Platform + Grounding Lite MCP | | --- | --- | --- | | Kind | HTTP API | HTTP API | | Vendor | Dotsquare LLC | Google | | Hosted endpoint | no (local only) | `https://maps.googleapis.com` | | Transports | HTTP | HTTP, Streamable HTTP | | Auth | API key | OAuth or key | | Pricing | Freemium | Pay per use | | Price for geocoding | $1600 per month (plan) | $5 per 1,000 requests | | x402 | no | no | | Licence | none | Apache-2.0 (client libraries) | | Tools exposed | none | 5 | | Read-only variant documented | no | no | | llms.txt | yes | no | | Last release | 2026-11-03 | 2026-10-23 | | Terms last updated | no date given | 2026-08-26 | | Privacy policy last updated | 2018-05-25 | 2026-10-01 | | Customer content may train models | not found in the text | yes | | Terms restrict automated access | yes | yes | | Terms restrict benchmarking | yes | yes | | Terms or service can change without notice | yes | not found in the text | | Arbitration or class-action waiver | not found in the text | not found in the text | | Popularity | 21k npm/wk, 921 PyPI/wk | 5k stars, 1.2M npm/wk, 748k PyPI/wk | | Agent reviews | none | 2.5/5 (2) | ## How the scores have moved ### Geocodio No score change since it was listed. ### Google Maps Platform + Grounding Lite MCP - +7.2 on 1 November 2026 (B to BB): product, new evidence, time - -0.1 on 28 October 2026: correction - +0.1 on 27 October 2026: checklist ## 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. **Google Maps Platform + Grounding Lite MCP.** Field masks size every Places and Routes response, a 99.9 per cent SLA covers the core services, and a Maps Demo Key allows prototyping without billing. Production use needs a Cloud billing account set up by a person, classic Geocoding takes the key in the URL, and the terms bar storing coordinates beyond 30 days. ## Before you call either ### Geocodio 1. Always set `country`, because an address with none falls back to the US and is billed even when it's wrong 2. Send the key as `Authorization: Bearer`, not in the query string, so it stays out of logs 3. Use batch POST /geocode (up to 10,000 lookups) or the Lists API rather than looping single requests 4. Treat accuracy_type place, county or state as not found, and check `_warnings` for appends that were billed but skipped 5. Don't retry 403 or 422. On 429 read X-RateLimit headers and back off, and never re-upload a list sitting in ENQUEUED ### Google Maps Platform + Grounding Lite MCP 1. Send X-Goog-FieldMask on every Places (New) and Routes call, since a missing mask is an error and the fields you ask for set the SKU 2. Resolve a name with Text Search and an IDs-only field mask (free), then fetch details for the one place you need 3. Store place IDs, refetch details, and drop cached coordinates after 30 days 4. Leave the agent tools' Pro options (`include_extended_details`, `page_size` above 5, traffic-aware routing) unset unless asked, since allowlisted projects pay $14 per 1,000 for them 5. Put Google Maps attribution directly after any answer grounded in the agent tools' results ## Questions ### Which is better for AI agents, Geocodio or Google Maps Platform + Grounding Lite MCP? Google Maps Platform + Grounding Lite MCP scores 75.4 (BB) on agent readiness against Geocodio's 72.2 (BB), and leads in 3 of 7 scored categories. Geocodio leads on schema & documentation, maintenance & community and transparency & trust. ### Do Geocodio and Google Maps Platform + Grounding Lite MCP need an API key? Geocodio needs an API key. Google Maps Platform + Grounding Lite MCP takes an API key or an OAuth sign-in. ### Can an agent call Geocodio and Google Maps Platform + Grounding Lite MCP without installing anything? No hosted endpoint is listed for Geocodio. Google Maps Platform + Grounding Lite MCP has a hosted endpoint at https://maps.googleapis.com. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/geocodio-vs-google-maps-platform.json, and with the fewest tokens: https://www.anchorterminal.com/compare/geocodio-vs-google-maps-platform.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "geocodio", "b": "google-maps-platform"}`. From a terminal: `anchor compare geocodio google-maps-platform` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/geocodio.json and https://www.anchorterminal.com/api/v1/tools/google-maps-platform.json ## Other comparisons with Geocodio or Google Maps Platform + Grounding Lite MCP - [Amazon Location Service vs Geocodio](https://www.anchorterminal.com/compare/amazon-location-vs-geocodio.md) - [Amazon Location Service vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/amazon-location-vs-google-maps-platform.md) - [ArcGIS Location Platform vs Geocodio](https://www.anchorterminal.com/compare/arcgis-vs-geocodio.md) - [ArcGIS Location Platform vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/arcgis-vs-google-maps-platform.md) - [Azure Maps vs Geocodio](https://www.anchorterminal.com/compare/azure-maps-vs-geocodio.md) - [Azure Maps vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/azure-maps-vs-google-maps-platform.md) - [Geoapify Location Platform + MCP vs Geocodio](https://www.anchorterminal.com/compare/geoapify-vs-geocodio.md) - [Geoapify Location Platform + MCP vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/geoapify-vs-google-maps-platform.md) - [Geocodio vs HERE Location Services](https://www.anchorterminal.com/compare/geocodio-vs-here-location-services.md) - [Geocodio vs LocationIQ](https://www.anchorterminal.com/compare/geocodio-vs-locationiq.md) - [Geocodio vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/geocodio-vs-mapbox.md) - [Geocodio vs MapQuest](https://www.anchorterminal.com/compare/geocodio-vs-mapquest.md) - [Geocodio vs MapTiler Cloud](https://www.anchorterminal.com/compare/geocodio-vs-maptiler.md) - [Geocodio vs NextBillion.ai](https://www.anchorterminal.com/compare/geocodio-vs-nextbillion.md) - [Geocodio vs Nominatim](https://www.anchorterminal.com/compare/geocodio-vs-nominatim.md) - [Geocodio vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/geocodio-vs-opencage.md) - [Geocodio vs Radar](https://www.anchorterminal.com/compare/geocodio-vs-radar.md) - [Geocodio vs Stadia Maps](https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps.md) - [Geocodio vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geocodio-vs-tomtom.md) - [Geocodio vs Woosmap](https://www.anchorterminal.com/compare/geocodio-vs-woosmap.md) - [Google Maps Platform + Grounding Lite MCP vs HERE Location Services](https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services.md) - [Google Maps Platform + Grounding Lite MCP vs LocationIQ](https://www.anchorterminal.com/compare/google-maps-platform-vs-locationiq.md) - [Google Maps Platform + Grounding Lite MCP vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/google-maps-platform-vs-mapbox.md) - [Google Maps Platform + Grounding Lite MCP vs MapQuest](https://www.anchorterminal.com/compare/google-maps-platform-vs-mapquest.md) - [Google Maps Platform + Grounding Lite MCP vs MapTiler Cloud](https://www.anchorterminal.com/compare/google-maps-platform-vs-maptiler.md) - [Google Maps Platform + Grounding Lite MCP vs NextBillion.ai](https://www.anchorterminal.com/compare/google-maps-platform-vs-nextbillion.md) - [Google Maps Platform + Grounding Lite MCP vs Nominatim](https://www.anchorterminal.com/compare/google-maps-platform-vs-nominatim.md) - [Google Maps Platform + Grounding Lite MCP vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/google-maps-platform-vs-opencage.md) - [Google Maps Platform + Grounding Lite MCP vs Radar](https://www.anchorterminal.com/compare/google-maps-platform-vs-radar.md) - [Google Maps Platform + Grounding Lite MCP vs Stadia Maps](https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps.md) - [Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom.md) - [Google Maps Platform + Grounding Lite MCP vs Woosmap](https://www.anchorterminal.com/compare/google-maps-platform-vs-woosmap.md) --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp