Finished data, not HTML to parse. Clean JSON, one charge per call.
No page to fetch, no HTML to parse. You send one GET request and get clean records back in about a second. The example below is a web search:
The API sends back clean JSON, and the same results are available as CSV so they drop straight into Sheets or a CRM with no parsing:
Swap type=web for maps, news, shopping, images, videos, scholar, patents, places, reviews, or autocomplete. Same key, same shape, no HTML to clean up.
No crawler to configure. 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. Pick any type from the menu. The results land in a table.
Export CSV, or run the curl above. Same records, ready for Sheets or your code.
Each result arrives structured and complete, so you build a feed or a dataset with no second call and no selectors to write. Here is the same record as CSV, ready for Sheets or a database:
Or the clean JSON the API returns:
With Crawlbase you fetch the page and write the parser. Here the structure is already done.
Both pull public web data. The difference is what comes back and how you pay. Crawlbase is general crawling infrastructure; CrustAPI is one clean data API: the whole Google menu, LinkedIn profiles, and local business leads.
| Crawlbase | CrustAPI | |
|---|---|---|
| Billing model | Per request, and the cost rises when you turn on JavaScript rendering or premium and residential proxies | 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. |
| Free tier | A limited free trial of requests to start | Free to try, no card |
| Balance expiry | Tied to a monthly plan | Prepaid funds never expire |
| Data in the response | Returns the fetched page of a URL for you to parse, with ready-made data only for the sites its own scrapers cover | Clean JSON from the API in one stable schema, or the same rows as CSV, no parsing |
| Coverage | Any URL you point it at, plus scrapers for certain sites | Google Search, Maps, News, Shopping, Images, Videos, Scholar, Patents, Places, Reviews, Autocomplete |
| Setup | Fetch a URL and parse it, or configure a crawler | One GET request, clean JSON back in about a second |
You pay the applicable price per successful call. Maps bills per business returned; other Google endpoints bill per successful request. Empty and failed requests are free.
| 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.
One key and one schema across the whole Google menu, and the same account covers LinkedIn profiles and local business leads too. Each type returns clean records you can keep, with no page to render and no selectors to write.
Related: Web scraper API · Google Search API · Google Maps scraper API · ScrapingBee alternative · Docs
When Crawlbase is the better pick: For arbitrary URLs and custom extraction, compare general scraping tools. CrustAPI returns structured data from its supported Google and LinkedIn endpoints, with prices shown before a dashboard run.
It is one clean data API for the data you actually want: 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 fetching a page and parsing the HTML yourself, you send one request and get clean records back. 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. Every endpoint returns finished records as clean JSON in one stable schema, and the same rows are available as CSV, so there is no page to render and no HTML to clean up. If you specifically need the raw HTML of an arbitrary URL to run your own selectors against, Crawlbase is the better fit for that job.
No. Prepaid funds never expire, and you can try it free with no card. An unused pack waits for your next project.
The whole Google menu: Search, Maps, News, Shopping, Images, Videos, Scholar, Patents, Places, Reviews, and Autocomplete, plus LinkedIn profiles and local business leads. It returns finished records for those surfaces rather than fetching any URL you point it at.
When you need to scrape a site that is not on our menu, render a specific page's JavaScript, rotate residential proxies, get past a CAPTCHA, run an asynchronous crawl with callbacks, or capture a screenshot of a URL. That is what a general web-scraping platform is built for.
the free plan covers real work. Run one search and look at the clean JSON that comes back.
Try for free