Catalog

Google Maps API

Google Maps data through one normalized API - per-request USD pricing, no subscriptions, and automatic failover on redundant endpoints.

Endpoints5Providers6From · search$1.75/1k req · LynxFull breakdownRead docs
Uptime
99.27%
30d · 6,608 calls
Requests
6,662
30d · weekly, last 12 wks
Response
6.6s
median · 30d
POST

Search

Most used
/v1/run/maps.searchmaps.search
Search Google Maps for places matching a query and location: up to 20 normalized place records with ratings, addresses, and contact basics per request.
4,554 /mo
â–²479.7%
99.78%
2601ms p50
3
from$1.75/1k req
Lynx
POST

Place

/v1/run/maps.placemaps.place
Look up a place on Google Maps by name or search query (optionally scoped to a location) and get the best-matching place with available address, contact, rating, and coordinate details as normalized JSON.
920 /mo
â–¼10.1%
99.78%
2727ms p50
3
from$1.75/1k req
Lynx
POST

Reviews

/v1/run/maps.reviewsmaps.reviews
Fetch up to 100 Google Maps reviews for a place by place ID, sorted the way you need, in one normalized response.
713 /mo
â–¼83.4%
100.00%
7564ms p50
3
from$3.50/1k req
Ibex
POST

Contacts

/v1/run/maps.contactsmaps.contacts
Search Google Maps for businesses and enrich each result with contact details (emails, phones, and social profiles from their websites), up to 20 records per request.
473 /mo
â–¼28.2%
91.63%
60298ms p50
1
price$4.72/1k resultsup to $0.0991 / request
Octopus
POST

Search nearby

/v1/run/maps.search_nearbymaps.search_nearby
Search Google Maps around an exact latitude and longitude and get up to 20 normalized places per call, each with the address broken into street, city, state, postal code and country. Use this when you have coordinates and want the map viewport centred on them; use maps.search when you only have a place name. Pass the returned nextCursor back as cursor for the next 20 places.
2 /mo
100.00%
3640ms p50
1
price$1.30/1k req
Chameleon

About the Google Maps API

Every provider prices each endpoint independently, so the table shows the cheapest per endpoint. Open one to compare all providers.

Measured performance

What the Google Maps API actually does

Every call through AnyAPI over the last 30 days, counted here rather than promised.

99.3%
of calls succeeded (6,608 calls)
Succeeded on first lane 99.1%Recovered by failover 0.2%Failed 0.7%
Response time estimate (6,560 calls across endpoints)
Weighted p50 estimate
6.6s
Request-weighted average of endpoint p50 values, not a combined request percentile
Weighted p99 estimate
59.7s
Request-weighted average of endpoint p99 values, not a combined request percentile

FAQ

About the Google Maps API

The AnyAPI Google Maps API returns Google Maps data as normalized JSON across 5 endpoints: contacts, place, reviews, search, and search nearby. You call one endpoint per job with a single key, and AnyAPI routes each request across 6 sources, falling back automatically when one fails. Pricing is in US dollars, from $1.30 per 1,000 requests on the cheapest endpoint, with no subscription and no monthly minimum. Over the last 30 days, 99.3% of Google Maps calls through AnyAPI succeeded, with a request-weighted median response time of 6.6 seconds across 6,608 measured calls.

Pricing is in US dollars, from $1.30 per 1,000 requests on the cheapest endpoint, with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.

5 endpoints: contacts, place, reviews, search, and search nearby. Every one takes the same authentication and returns the same normalized response shape, so reaching a second Google Maps endpoint is a change of URL and nothing else.

Over the last 30 days, 99.3% of Google Maps calls through AnyAPI succeeded, with a request-weighted median response time of 6.6 seconds across 6,608 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.