Google Places API Pricing, Decoded
Google reaches $35 per 1,000 and bars storing it. Here is the breakdown.
How much does the Places API cost?
Google Places API pricing is not a single number. It is a stack of per-request SKUs, and the fields you ask for decide which tier you pay for that call.
The tiers run Essentials, Pro, and Enterprise. The basic name and address data sits in the cheaper tiers.
The fields most people want, a business rating, phone number, website, and opening hours, land in the Enterprise tier: $35.00 per 1,000 requests per Google's usage-and-billing page (developers.google.com).
Add reviews and atmosphere fields and you move to Enterprise plus Atmosphere at $40.00 per 1,000.
Two details make the real bill higher than the sticker. First, a Text Search returns up to 20 places per request. To read more than 20 you paginate, and each page is another billed request.
Second, the old $200 monthly credit was retired in March 2025 and replaced with a per-SKU free allowance. Enterprise SKUs get roughly 1,000 free calls a month, Pro gets 5,000, Essentials gets 10,000, and the allowances no longer pool (developers.google.com/maps/billing-and-pricing/march-2025).
Can you store the Places data?
The line item is only half the cost. Google's Places policies restrict what you are allowed to keep after you pay for it.
Per Google's Places policies page (developers.google.com/maps/documentation/places/web-service/policies), an app may not pre-fetch, cache, or store Places content except in narrow cases.
The place ID is the big exception and can be stored indefinitely. Latitude and longitude can be cached for up to 30 consecutive calendar days, then must be deleted.
Everything else, the name, rating, phone, and hours you just paid Enterprise rates for, is meant to be fetched fresh each time you need it.
For a live map that shows one place on demand, that model is fine. For building a database of a market, a lead list, or anything you enrich and keep, you are renting the same rows over and over.
What data do you get?
CrustAPI runs the same kind of query against Google Maps and hands back clean rows you can save. Here is a real shape for type=maps, shown as CSV because that is what most people paste into a sheet.
One call returns up to 100 businesses in about a second, with name, rating, review count, phone, website, full address, weekly hours, categories, and lat/lng on every row.
There is no email field, Google Maps listings do not carry one, so nobody scraping Maps has it. When you need a verified work email, that comes from the LinkedIn profile endpoint, not from Maps.
The rows are yours. Save them, enrich them, resync them next quarter. Related reading: Google Maps API pricing and Google Maps scraper API.
CrustAPI vs the official Places API
Same underlying business data. Different billing model and very different rules on what you can keep.
| Google Places API | CrustAPI | |
|---|---|---|
| Billing unit | Per request, field-tier SKUs | Per successful result |
| Ratings + phone + website + hours | $35 / 1,000 requests (Enterprise) | Included on every row |
| Cost per result | $35 / 1,000 requests, 20 results each | $1.96 per 1,000 businesses at standard prices |
| Results per request | 20 (paginate for more, each billed) | Up to 100 |
| Store the data? | place ID forever, lat/lng 30 days, rest no | Keep everything, no time limit |
| Pay for zero results? | Yes, the request bills either way | No, empty search costs nothing |
| Star histogram | Not available | Optional, per place |
How much does CrustAPI cost?
Maps costs $1.96 per 1,000 businesses at standard prices, down to $0.40 for the largest deposit. Empty and failed searches are free. Every eligible account gets $6 of free usage monthly. Paid funds never expire.
| Deposit | Google Search / 1,000 requests | Maps / 1,000 businesses | LinkedIn reads / 1,000 requests | People, Jobs, Refresh / 1,000 units |
|---|---|---|---|---|
| $10+ | $1.00 | $1.96 | $6.00 | $1.96 |
| $149+ | $0.76 | $1.49 | $4.50 | $1.49 |
| $549+ | $0.56 | $1.10 | $3.30 | $1.10 |
| $1,999+ | $0.41 | $0.80 | $2.45 | $0.80 |
| $6,500+ | $0.33 | $0.65 | $1.95 | $0.65 |
| $27,500+ | $0.28 | $0.55 | $1.65 | $0.55 |
| $50,000+ | $0.26 | $0.50 | $1.50 | $0.50 |
| $100,000+ | $0.20 | $0.40 | $1.50 | $0.40 |
Every eligible account gets $6 of free usage monthly. Each deposit keeps its prices until spent; paid funds never expire. People and Jobs bill per successful search, Refresh per accessible profile. Full profiles in People use the read rate per full profile. See all billing details.
Larger deposits unlock lower endpoint prices. Each deposit keeps its prices until spent. See the full deposit table on the pricing page. Prices in USD, ex-tax.
The free tier is Free to try with no card. Paid funds never expire, so a slow month does not burn them. More rate math on the Maps API pricing page.
How do you get started?
- 1
Create a free account. Try it free, no card needed.
- 2
Type a search in the playground. Something like dentist miami. Up to 100 businesses land in a table.
- 3
Export the CSV or run the curl above. The rows are yours to keep, no 30-day timer.
Who uses this instead?
- Lead gen teams. Build a market list with phone and website and keep it, no fetch-it-fresh rule.
- Agencies. Snapshot every competitor around a client each month and compare the months.
- Developers. Every Maps row includes its available fields. The deposit amount determines the rate.
- Analysts. Store whole-market pulls in a database and enrich them later.
When the official Places API wins
We are not the answer for every use case. Here is where Google's own API wins.
You need Google's own contract: If your product must display live, Google-sanctioned place data with an uptime SLA, official support, and a signed terms relationship, buy from Google directly. That contract and that guarantee are exactly what you are paying the per-request premium for, and we do not replace them.
Related: Google Places API alternative · Google Maps scraper API · Google Maps API pricing
Common questions
It depends on the fields you request. The Enterprise tier that includes rating, phone, website, and opening hours is $35.00 per 1,000 requests per Google's usage-and-billing page. Add reviews and atmosphere fields and you move to Enterprise plus Atmosphere at $40.00 per 1,000. Basic name and address data sits in cheaper Essentials and Pro tiers.
No. Google retired the shared $200 monthly credit in March 2025 and replaced it with a per-SKU free allowance. Enterprise SKUs get about 1,000 free calls a month, Pro gets 5,000, and Essentials gets 10,000. Those allowances no longer pool across products, so each service carries its own cap.
Mostly no. Google's Places policies say you cannot pre-fetch, cache, or store Places content beyond narrow exceptions. The place ID can be kept indefinitely, and latitude and longitude can be cached for up to 30 consecutive calendar days before deletion. Fields like name, rating, phone, and hours are meant to be fetched fresh each time.
Google bills per request, and each request returns up to 20 results whether or not it is full. CrustAPI bills per successful result, returns up to 100 businesses per search, and charges nothing when a search finds nothing. You also keep the rows with no 30-day timer.
No. Google Maps and Places listings do not carry an email field, so no tool scraping Maps returns one. On CrustAPI, verified work emails come from the LinkedIn profile endpoint instead, one verified email per person, not from Maps data.
Every business row carries name, rating, review count, phone, website, full street address, weekly hours, primary and all categories, lat/lng, and open or closed flags. An optional flag adds the one-to-five star histogram per place, which the official Places API does not sell.
Clay
Stop renting your own data back from Google
The official Places API makes you fetch every field fresh and delete most of it on a timer. CrustAPI returns the same business records as clean rows, priced per result, yours to keep. Start on a free plan with no card.
Try for free