The whole Google menu and LinkedIn in one clean API.
No proxy to configure, no HTML to parse. You send one GET request and get clean JSON back in about a second. The example below is a Maps search:
The same businesses as CSV, so they drop straight into Sheets or a CRM:
Swap type=maps for news, shopping, reviews, and the rest. The key and the schema stay the same across every type.
Every result comes back parsed and complete, so you build a list or a dataset with no second call and no raw HTML to clean up. The same business as CSV, ready for Sheets or a database:
Or the same record as JSON:
Scrapingdog is a general web scraping API with dedicated endpoints for sites like Google, LinkedIn, and Amazon. CrustAPI is one clean data API for the whole Google menu, plus LinkedIn profiles and local business leads. The difference is billing, balance expiry, and what you get back.
| Scrapingdog | CrustAPI | |
|---|---|---|
| Billing model | Monthly subscription; the credit cost of a request changes with the features you turn on, like JS rendering or premium proxies | Pay only for results; no compute or storage fees |
| Free tier | A free trial with a limited number of credits | free to try, no card |
| Balance expiry | The plan allowance resets each billing cycle; unused requests do not roll over | Prepaid funds never expire |
| Data in response | Returned in the response; the general web scraping API hands back raw HTML you parse yourself | Clean JSON in the response, one stable schema per type, or the same rows as CSV |
| Site coverage | Broad: a generic scraping API plus dedicated scrapers for sites like LinkedIn and Amazon | The whole Google menu, plus LinkedIn profiles and local business leads, returned as clean records |
| Google surfaces | Dedicated Google Search, Maps, and News APIs | Search, Maps, News, Shopping, Images, Videos, Scholar, Patents, Places, Reviews, Autocomplete |
| Setup | Set request params, handle parsing per site for the general API | One GET request, clean records back in about a second |
Maps bills the Maps rate per business returnedGoogle Search starts at $1.00 per 1,000 successful requests, Maps at $1.96 per 1,000 businesses, LinkedIn reads at $6.00 per 1,000 successful requests, and People, Jobs and Refresh at $1.96 per 1,000 billing units. Full profiles in People use the LinkedIn read rate per full profile. Each deposit saves its own prices until spent. 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.
Paid funds never expire. Endpoint prices and the price saved with each deposit determine the charge. Your dashboard shows an estimate before each run.
Nothing to configure and no HTML to parse. From zero to clean records in about two minutes:
Create a free account. Try it free, no card needed.
Type a search in the playground. Something like coffee in portland me. The results land in a table.
Export the CSV, or run the curl above. Copy your key from the dashboard for the API.
One key and one schema across the whole Google menu. Each type returns clean parsed records you can keep and export.
Related: Google Search API · Google Maps scraper API · Google News API · Serper alternative · Docs
When Scrapingdog is the better pick: if you need to scrape arbitrary websites, or sites like Amazon beyond Google and LinkedIn, Scrapingdog has endpoints for those and CrustAPI does not. CrustAPI is one clean data API for the whole Google menu, plus LinkedIn profiles and local business leads, priced one way, with paid funds that never expire. The two are not exclusive; plenty of teams use both.
It is one clean data API for the whole Google menu (Search, Maps, News, Shopping, Images, Videos, Scholar, Patents, Places, Reviews, Autocomplete) through one endpoint, plus LinkedIn profiles and local business leads. Instead of configuring proxies and parsing HTML, you send one request and get clean JSON back, or the same rows as CSV. You pay the applicable endpoint price for successful data, and paid funds never expire.
Pay only for results at the applicable endpoint rate. Google Search bills per successful request and Maps per business returned. LinkedIn reads bill per successful request, People and Jobs per successful search, Refresh per accessible profile, and enriched People per full profile. Empty and failed requests are free. The pricing page lists every rate.
No. Prepaid funds never expire, and the free plan needs no card. A subscription allowance resets each billing cycle; a CrustAPI pack waits for your next project instead.
The whole Google menu (Search, Maps, News, Shopping, Images, Videos, Scholar, Patents, Places, Reviews, Autocomplete) through one endpoint, and the CrustAPI platform also covers LinkedIn profiles and local business leads. That is a deliberate set next to the many arbitrary sites Scrapingdog's generic scraper and dedicated endpoints span.
Yes. The two are not exclusive. Many teams use CrustAPI for Google and lead data because the billing is flat and the paid funds never expire, and keep Scrapingdog for arbitrary URLs or sites like Amazon that CrustAPI does not cover.
Yes. Data is returned in the response as clean records, not raw HTML. Keep it, export it to a spreadsheet or a database, and build on it.
the free plan covers real work. Send one request and look at the JSON that comes back.
Try for free