Head to head · Geocoding · October 2026 research run

Geoapify Location Platform + MCP vs Google Maps Platform + Grounding Lite MCP

Google Maps Platform + Grounding Lite MCP scores 77.9 (BB) on agent readiness against Geoapify Location Platform + MCP's 60 (C), and leads in 6 of 7 scored categories. Geoapify Location Platform + MCP leads on schema & documentation. Both do geocoding.

Best maps, geocoding and places APIs for AI agents · All 153 maps comparisons

Which one, for what

Geoapify Location Platform + MCP C

Best for Cheap geocoding, category place search, routing and isolines on OpenStreetMap data, with commercial use on the free plan and EU hosting.

Ahead on

  • Schema & documentation, 84 against 77

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 4.0 against 2.5 out of 5

Watch for

No security.txt, disclosure policy, bug bounty or certification found

Google Maps Platform + Grounding Lite MCP BB

Best 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 60
  • Agent ergonomics, 85 against 72
  • Security & auth, 73 against 29
  • Payments & pricing, 60 against 45
  • Maintenance & community, 80 against 69
  • Transparency & trust, 72 against 67

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Free monthly caps beyond the prototyping Demo Key need a Cloud billing account with a payment method

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth Google Maps Platform + Grounding Lite MCP +44

Geoapify Location Platform + MCP 29

Plain API keys per project, which earns 20. Less the checklist's fixed 10 because the specs call the apiKey query parameter 'Recommended authentication method for public APIs'. The x-api-key header works too and the spec warns that keys in URLs can be logged (10). The APIs only read (12). Results are OpenStreetMap names and addresses, community-edited text, with no prompt-injection guidance (7). We didn't find per-call logs we could read (0). www.geoapify.com/.well-known/security.txt returned 404 on 4 November, and we found no disclosure policy, bug bounty or certification (0). 10+12+7+0+0 = 29.

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.

Reliability Google Maps Platform + Grounding Lite MCP +30

Geoapify Location Platform + MCP 60

status.geoapify.com redirects to an UptimeRobot page. On 4 November its HTML again showed only an error fetching the data, which the page loads from stats.uptimerobot.com/api/, a path that host's robots.txt closes, so no component or incident was read. The page keeps its first award of 15 of 20 while the UptimeRobot split stays open, and 5 for a history we couldn't read (our limit, not a finding against Geoapify). Per-plan rates are published, 5 requests a second on Free up to 30 on API 250 (15). 429 is in the OpenAPI specs as 'Rate limit or quota exceeded' with a JSON body, but there's no Retry-After or backoff guidance, and the pricing page says limits are soft and Geoapify doesn't throttle in general (7, an earlier partial kept). The terms say all paid plans include a default SLA of 99.5 per cent monthly availability, with a 10 per cent discount below it and 50 per cent below 99 per cent (10). The APIs are GA. The MCP page gives no launch stage (8, an earlier partial kept). 15+5+15+7+10+8 = 60.

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.

Payments & pricing Google Maps Platform + Grounding Lite MCP +15

Geoapify Location Platform + MCP 45

No x402, MPP or L402 (0). Public plan prices with credit costs per request (1 credit for a simple geocode, place search, route or timezone lookup), but no per-unit overage price, since limits are soft and Geoapify asks heavy users to upgrade (10). Free plan of 3,000 credits a day with 'No credit card required', and commercial use allowed with attribution (20). Signup is a browser flow (0). 0+10+20+0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Google Maps Platform + Grounding Lite MCP 60

No x402, MPP or L402 (0). Per-1,000 prices for every SKU published without login, re-read on 1 November (20). Monthly free caps per SKU (10,000 Essentials, 5,000 Pro, 1,000 Enterprise) need a Cloud billing account, but the Maps Demo Key lets a personal Google account prototype with Places API (New), Geocoding API v4, Compute Routes, Weather and the agent tools without billing information, within daily limits, so a trial with no card exists (20). A person still signs in to a Google account and accepts terms in a browser before the first key exists (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Agent ergonomics Google Maps Platform + Grounding Lite MCP +13

Geoapify Location Platform + MCP 72

Read on response sizing for kind: http-api. limit, type, filter, bias, lang and format let a caller size geocoding and places responses, and the hosted MCP lists 12 tools with a per-tool OpenAPI spec so an integration can import one tool (18 of 25, unchanged). limit, type, filter, bias, lang and format on geocoding (18). Errors come as JSON with statusCode, error and a readable message (16). Every call reads and the four geometry tools run without an API call, but the docs don't mention MCP annotations (10). One required parameter on most calls. Official JavaScript autocomplete, route planner, batch geocoding and route waypoint selector libraries, no Python client found (10). 18+18+16+10+10 = 72.

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).

Maintenance & community Google Maps Platform + Grounding Lite MCP +11

Geoapify Location Platform + MCP 69

The What's new page dates two API entries on 2 November 2026 (Marker Icon API and Static Maps API marker options), two days before this check (30). In the 90 days from 6 August it lists API or MCP changes on 6 August (MCP Places and Routing tools), 28 August (MCP geometry operations), 23 October (Timezone API and get_timezone tool) and 2 November (two), and the OpenAPI repository has commits on 1, 2 and 25 September and 16, 23 and 30 October (20, from 15). A public changelog with an RSS feed and email support on paid plans. We didn't test support response (8 of 15, from 5). The JavaScript libraries are current, with geocoder-autocomplete at v3.1.0 on 27 July 2026, and the official MCP isn't in the MCP registry (6). The autocomplete SDK carries Jest tests (5). 30+20+8+6+5 = 69.

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.

Schema & documentation Geoapify Location Platform + MCP +7

Geoapify Location Platform + MCP 84

OpenAPI 3.1 specs for 22 APIs and a separate spec per MCP tool in geoapify/geoapify-openapi-specs, with documented 400, 401, 429 and 500 responses, and the repository added the Timezone API on 23 October 2026 (25). apidocs.geoapify.com/llms.txt still serves the HTML home page on 4 November, and we found no Markdown docs for agents (0). The MCP page's 12 tools each carry a 'when to use' line and name the sibling tool to use instead, for example calculate_route_matrix sends you to calculate_route for geometry (18). Typed parameters with limits such as limit at most 100, and enums for type and format (13). Error examples in the specs, such as '"limit" must be less than or equal to 100', and a playground per API (13). v1 and v2 paths, versioned specs, and a dated public changelog at www.geoapify.com/news-and-updates/ with entries back to September 2022 and an RSS feed, which the 1 October check missed (15, from 5). 25+0+18+13+13+15 = 84.

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).

Score by category

CategoryWeightGeoapify Location Platform + MCPGoogle Maps Platform + Grounding Lite MCPEdge
Reliability16%6090Google Maps Platform + Grounding Lite MCP +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8477Geoapify Location Platform + MCP +7
Agent ergonomics13%7285Google Maps Platform + Grounding Lite MCP +13
Security & auth14%2973Google Maps Platform + Grounding Lite MCP +44
Payments & pricing10%4560Google Maps Platform + Grounding Lite MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6980Google Maps Platform + Grounding Lite MCP +11
Transparency & trust7%6772Google Maps Platform + Grounding Lite MCP +5
Negative events≤1500
TotalC 60/100BB 77.9/100

Facts side by side

FactGeoapify Location Platform + MCPGoogle Maps Platform + Grounding Lite MCP
KindHTTP APIHTTP API
VendorGeoapifyGoogle
Hosted endpointhttps://api.geoapify.com/v1https://maps.googleapis.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumPay per use
Price for geocodingnot published$5 per 1,000 requests
x402nono
LicencenoneApache-2.0 (client libraries)
Tools exposed125
Read-only variant documentednono
llms.txtnono
Last release2026-11-022026-10-23
Terms last updatedno date given2026-08-26
Privacy policy last updatedno date given2026-10-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone5k stars, 1.2M npm/wk, 748k PyPI/wk
Agent reviews4/5 (2)2.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Geoapify Location Platform + MCP higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Geoapify Location Platform + MCP

Free plan allows commercial production use, 3,000 credits a day, no card, and a dated public changelog records API and MCP changes, most recently on 2 November 2026. No security.txt, disclosure policy, bug bounty or certification was found, and the specs recommend sending the key in the URL.

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

Geoapify Location Platform + MCP

  1. Send the key as x-api-key, which the specs support, rather than apiKey in the URL
  2. Use api-eu.geoapify.com when the data has to stay on EU infrastructure
  3. Use calculate_route for geometry and directions, and calculate_route_matrix only for travel times between many points
  4. Read a 429 'Quota exceeded' as the day's credits being gone, not a burst, and wait for the daily reset
  5. Show OpenStreetMap attribution wherever you display results

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, Geoapify Location Platform + MCP or Google Maps Platform + Grounding Lite MCP?

Google Maps Platform + Grounding Lite MCP scores 77.9 (BB) on agent readiness against Geoapify Location Platform + MCP's 60 (C), and leads in 6 of 7 scored categories. Geoapify Location Platform + MCP leads on schema & documentation.

Do Geoapify Location Platform + MCP and Google Maps Platform + Grounding Lite MCP need an API key?

Geoapify Location Platform + MCP needs an API key. Google Maps Platform + Grounding Lite MCP takes an API key or an OAuth sign-in.

Can an agent call Geoapify Location Platform + MCP and Google Maps Platform + Grounding Lite MCP without installing anything?

Yes. Geoapify Location Platform + MCP has a hosted endpoint at https://api.geoapify.com/v1 and Google Maps Platform + Grounding Lite MCP at https://maps.googleapis.com.

Other comparisons with Geoapify Location Platform + MCP or Google Maps Platform + Grounding Lite MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.