A Google Places API alternative that keeps Google's data

Search a city and get the same Google places you'd see yourself: name, address, rating, and coordinates.

Google's own place data 1 credit per search Credits never expire
PULLED LIVE FROM THE API, JULY 15, 2026

One request, ten places

# one search returns the whole set of places for 1 credit; an empty result is free curl "https://crustapi.com/v1/search?type=places&q=coffee&location=Austin, TX" -H "x-api-key: YOUR_KEY"
// the first place returned, unedited: { "position": 1, "title": "Trippy Buck Coffee", "address": "720 Brazos St, Austin, TX 78701", "latitude": 30.2694, "longitude": -97.7411, "rating": 4.9, "ratingCount": 36, "category": "Coffee shop", "cid": "581431293581611026", "priceLevel": null }

That call returned 10 places in about 1.8 seconds and cost 1 credit for the whole search. The priceLevel field was null here because Google didn't show a price band for this place. It's only present when Google lists one, so treat it as best-effort.

WHAT EVERY PLACE INCLUDES

The fields you get back

RankPosition NameTitle LocationAddress CoordinatesLat + long ReputationRating VolumeReview count TypeCategory IDcid Best effortPrice level
THE PART MOST ALTERNATIVES SKIP

Most "alternatives" hand you a different dataset

When people search for a Google Places API alternative, the usual answers are Mapbox, HERE, OpenStreetMap, or Foursquare. Those are real map providers, and for some jobs they fit well. The catch is they are a different set of places, ratings, and review counts than the ones Google shows. If your app or your customers expect the numbers they see on Google, swapping the dataset changes the answer.

CrustAPI is the alternative that keeps Google's own live place data. You search a term and a city, and you get the same public results a person would see, in a lean flat shape. No field-by-field pricing tiers, no restrictions on where you can show the data, and 1 credit per search no matter how many places come back.

SIDE BY SIDE

Switching dataset vs keeping Google's

Different-dataset alternativesCrustAPI Places
Whose dataMapbox, HERE, OSM, or FoursquareGoogle's own public places
Ratings and review countsMatch that provider, not GoogleThe Google numbers people see
ShapeVaries by providerLean flat JSON, one schema
BillingVaries by provider1 credit per search, empty is free
Free tierVaries by provider3,000 credits / month, no card

The data is public and logged out. We run the infrastructure so you don't stand up and babysit a scraper, and you read plain JSON back.

Search a city free
3,000 credits a month. No card, no contract.
Get started →
WHO IT'S FOR

Who this fits

Local directories

Lead-gen by city

Store locators and maps

PRICING

One credit per search

A search that returns ten places costs 1 credit, not ten. A search that returns nothing costs nothing. Prepaid packs, credits never expire: 25k for $49, 100k for $149, 500k for $549, up to 250M, all self-serve, ex-tax. The free tier refills at 3,000 credits a month with no card.

FAIR PLAY

When you want richer per-business fields: type=places is the lean flat-rate shape, built for the fields above at 1 credit per search. If you need more detail per business, that lives on the Google Maps endpoint. And if Mapbox, HERE, or Foursquare data is genuinely what your product needs, one of those providers is the right call, not this.

BEFORE YOU ASK

Common questions

Written by Dawson Young, founder of CrustAPI. Receipt pulled live from the API on July 15, 2026. This is a spoke of the Google Search API; for richer per-business detail see the Google Maps scraper API.

Keep Google's data, drop the field pricing

3,000 free credits covers a real run across a few cities. Point a place query at the API and read the JSON.

Get 3,000 free credits
No credit card required