Google Places API vs OpenStreetMap (Nominatim and Overpass) for AI agents
Google Places API is a paid Google Maps Platform web service that returns place data (search, details, photos, autocomplete) from Google Maps. Free, donation-run public servers for searching OpenStreetMap data: Nominatim for geocoding and place search, Overpass for querying OSM objects.
The short answer
- Google Places API: The broadest, freshest global place data, with ratings, reviews, hours and photos, for teams that can pay per call and follow Google's display rules.
- OpenStreetMap (Nominatim and Overpass): Free, openly licensed geocoding and occasional place lookups at low volume, or a base to self-host. It is not a backend for a public app at scale.
Side by side
| Google Places API | OpenStreetMap (Nominatim and Overpass) | |
|---|---|---|
| Searches | Places worldwide from Google Maps: businesses, points of interest, addresses, through Text Search, Nearby Search, Place Details and Autocomplete. | OpenStreetMap data worldwide: addresses, places and mapped POIs. |
| Returns | JSON. You pick fields with a field mask, and the most expensive field you ask for sets the price tier (Essentials, Pro, Enterprise). Fields include place ID, name, address, location, phone numbers, website, hours, ratings, photos and reviews. | Nominatim returns xml, json, jsonv2 (the default), geojson or geocodejson. With extratags=1 it adds extra tags such as opening hours or a wikipedia link when mapped. |
| Before the first call | A Google Cloud project with billing enabled, plus an API key or OAuth token. | No account or key. Nominatim requires a valid User-Agent or Referer that identifies your app, and visible attribution. |
| Free | A free monthly usage cap for each SKU: 5,000 Text Search Pro or Nearby Search Pro calls, 1,000 at the Enterprise tier, 10,000 Place Details Essentials, and unlimited ID-only searches. The pricing page does not mention the old $200 monthly credit. | Free within strict limits. Nominatim allows an absolute maximum of 1 request per second. Overpass asks users to stay at or below roughly 10,000 requests and 1 GB a day. |
| Paid | Text Search Pro and Nearby Search Pro cost $32 per 1,000 calls (up to 100,000 a month). Enterprise, the tier that includes phone and website, costs $35 per 1,000. Place Details Pro costs $17 per 1,000. | No paid tier. Heavy users are told to run their own instance or use commercial third-party providers. |
| Acting on a result | Phone numbers and website are Enterprise-tier fields. There is no way to message a business through the API. | Phone or website appear only when mappers tagged them in OSM, through Nominatim's extratags. There is no messaging. |
| Limits on keeping or showing results | No pre-fetching, caching or storing beyond the stated exceptions. Place IDs may be stored indefinitely, and latitude/longitude for up to 30 days. Results may be shown without a map, but then the Google logo is required. When shown on a map it must be a Google Map, never a non-Google map. | Data is ODbL (share-alike), and you must credit OpenStreetMap and its contributors. Nominatim requires results to be cached for bulk jobs. It bans systematic queries, downloading all POIs in an area, autocomplete, and reselling results. |
| AI in its terms | The Maps Platform Terms forbid using Google Maps Content to improve ML or AI models, including to train, test, validate or fine-tune them. Grounding an LLM is allowed only through Maps Grounding Lite, which requires source links and forbids using Grounded Output to train models. | Nominatim's policy has a "Usage in LLMs" section. LLMs may only suggest the service if they prominently point to the usage policy. The public API must not be built into or offered through no-code, low-code or vibe-coding platforms as a generic place-search service. |
| Coverage | Worldwide (Google Maps place data). | Worldwide OpenStreetMap data. POI completeness depends on volunteer mapping. |
| MCP server | Maps Grounding Lite, a Google-hosted MCP endpoint at https://mapstools.googleapis.com/mcp (tools include search_places). Docs: https://developers.google.com/maps/ai/grounding-lite | No official server listed |
Where Openpath fits
If the agent needs a local business to message in Austin, Texas, Openpath returns the listings themselves, free and with no key. See Openpath vs Google Places API and Openpath vs OpenStreetMap (Nominatim and Overpass).
Questions people ask
What do I need before I can use Google Places API?
A Google Cloud project with billing enabled, plus an API key or OAuth token.
Is Google Places API free?
A free monthly usage cap for each SKU: 5,000 Text Search Pro or Nearby Search Pro calls, 1,000 at the Enterprise tier, 10,000 Place Details Essentials, and unlimited ID-only searches. The pricing page does not mention the old $200 monthly credit.
What do I need before I can use OpenStreetMap (Nominatim and Overpass)?
No account or key. Nominatim requires a valid User-Agent or Referer that identifies your app, and visible attribution.
Is OpenStreetMap (Nominatim and Overpass) free?
Free within strict limits. Nominatim allows an absolute maximum of 1 request per second. Overpass asks users to stay at or below roughly 10,000 requests and 1 GB a day.
Sources
Every line about another company comes from its own pages. Prices and terms change, so check the source before you rely on one.
Google Places API, read on October 15, 2026:
- developers.google.com/maps/billing-and-pricing/pricing: “Places API Text Search Pro 4FDA-34B1-A910 5,000 $32.00”
- developers.google.com/maps/billing-and-pricing/pricing: “Places API Text Search Enterprise E967-44BC-B44D 1,000 $35.00”
- developers.google.com/maps/billing-and-pricing/pricing: “Places API Place Details Pro 4ED6-464A-2AFC 5,000 $17.00”
- developers.google.com/maps/billing-and-pricing/pricing: “Places API Text Search Essentials (IDs Only) 635D-A9DD-C520 Unlimited”
- developers.google.com/maps/documentation/places/web-service/usage-and-billing: “To use the Places API, you must enable billing on each of your projects and include an API key or OAuth token”
- developers.google.com/maps/documentation/places/web-service/usage-and-billing: “if you select fields in both the Essentials and the Pro SKUs, you are billed based on the Pro SKU”
- developers.google.com/maps/documentation/places/web-service/data-fields: “International phone number internationalPhoneNumber Place Details Enterprise Text Search Enterprise Nearby Search Enterprise”
- developers.google.com/maps/documentation/places/web-service/data-fields: “Website URI websiteUri Place Details Enterprise Text Search Enterprise Nearby Search Enterprise”
- developers.google.com/maps/documentation/places/web-service/overview: “returns a JSON response. Places API (New) supports authorization by API key and OAuth token.”
- developers.google.com/maps/documentation/places/web-service/policies: “You must not pre-fetch, cache, or store Places API content beyond the allowed exceptions.”
- developers.google.com/maps/documentation/places/web-service/policies: “You can therefore store place ID values indefinitely.”
- developers.google.com/maps/documentation/places/web-service/policies: “When displaying Places API data without a Google Map, you must include the Google logo”
- cloud.google.com/maps-platform/terms/maps-service-terms: “Customer may temporarily cache latitude and longitude values from the Places API for up to 30 consecutive calendar days”
- cloud.google.com/maps-platform/terms/maps-service-terms: “Customer may use Google Maps Content from the Places API in Customer Applications without a corresponding Google Map.”
- cloud.google.com/maps-platform/terms: “use Google Maps Content to improve machine learning and artificial intelligence models, including to train, test, validate or fine-tune the models”
- cloud.google.com/maps-platform/terms/maps-service-terms: “use Grounded Output to train, develop, or improve any machine learning models or artificial intelligence systems”
- developers.google.com/maps/ai/grounding-lite: “a service with Model Context Protocol (MCP) support”
- developers.google.com/maps/documentation/places/web-service/overview: “built on one of the most accurate, up-to-date, and comprehensive place models of the real world”
OpenStreetMap (Nominatim and Overpass), read on October 15, 2026:
- operations.osmfoundation.org/policies/nominatim: “No heavy uses (an absolute maximum of 1 request per second ).”
- operations.osmfoundation.org/policies/nominatim: “Provide a valid HTTP Referer or User-Agent identifying the application”
- operations.osmfoundation.org/policies/nominatim: “LLMs may only suggest this service, if they prominently point to this usage policy and explain the restrictions of use to the user.”
- operations.osmfoundation.org/policies/nominatim: “must not be built into, offered through, suggested by, or automatically generated by no-code, low-code, or vibe-coding platforms”
- operations.osmfoundation.org/policies/nominatim: “This includes reverse queries in a grid, searching for complete lists of postcodes, towns etc. and downloading all POIs in an area.”
- operations.osmfoundation.org/policies/nominatim: “If your requirements are even larger you can install your own instance of Nominatim.”
- dev.overpass-api.de/overpass-doc/en/preface/commons.html: “users are expected to send a maximum of about 10000 requests per day and keep their download volume below about 1 GB per day”
- nominatim.org/release-docs/latest/api/Search: “the response include any additional information in the result that is available in the database, e.g. wikipedia link, opening hours”
- openstreetmap.org/copyright: “You are free to copy, distribute, transmit and adapt our data, as long as you credit OpenStreetMap and its contributors.”