Every business leads database sold as a file starts aging the day it is built. CrustAPI pulls each record live from Google Maps and LinkedIn public pages when you ask, and bills you only when a query returns results.
Businesses close. Phones get reassigned. Owners sell. People change jobs. A compiled file has no way to flag which rows died after it was built, so you find out the slow way, when calls bounce and mail comes back.
A query does not have that problem. When your list is built at request time, every record shows what the public page says right now, and each one carries a scrapedAt timestamp so you can check the claim yourself.
There is no warehouse of pre-collected rows going stale behind this API. There are 12 live Google search types and a set of LinkedIn public endpoints, and your database is whatever you pull from them, whenever you pull it.
This is a real query and a real record from it, run the day this page was written. Maps responses come back in about a second, and you set how many businesses you want with the limit parameter.
The same record, as a CSV row you can drop straight into a spreadsheet:
The same record as JSON, trimmed to the highlights:
The phone is masked for this page. The API returns the full number, the full address, website, rating, review count, categories, lat and lng, and hours for every day.
A straight answer first: business records from Maps carry phone, website, address, rating, review count, categories, and hours. They do not carry email addresses, because Maps listings do not show one. We will not pretend otherwise.
Emails on CrustAPI come from the people side. The LinkedIn endpoints search public profiles by title, company, or keyword, and each person row can carry a verified work email. An address is returned only after it passes a live verification check. When nothing passes, the field is null instead of a guess, and rows that return nothing cost nothing.
The same endpoint family also returns full profiles, company pages, jobs, and public posts. The LinkedIn people search API page shows a full masked response, and the LinkedIn company scraper covers the company side.
A compiled leads file charges you for every row, including the dead ones. CrustAPI charges 1 credit per record actually returned. A query that returns nothing is free. A query that fails is free. That puts the risk of bad data on us instead of you.
| A compiled leads file | CrustAPI | |
|---|---|---|
| When records are collected | Months before you buy, on the vendor's schedule | The second you run the query |
| What you pay for | Every row in the file, dead or alive | 1 credit per record returned; empty and failed queries free |
| Proof of freshness | None; the file is a snapshot | scrapedAt timestamp on every record |
| Refreshing the list | Buy the file again | Run the query again; credits never expire between runs |
| Emails | Varies by vendor | Verified emails on LinkedIn people results; null when the check fails |
Prepaid packs, and credits never expire: 25k for $49 · 100k for $149 · 500k for $549 · 2.5M for $1,999, all self-serve, ex-tax. That works out to about $2 per 1,000 records at entry and under $1 per 1,000 on the big packs. Before any of that, the free tier gives you 3,000 credits a month with no card, which covers a real list.
Related: B2B database · Lead scraper · Google Maps scraper API · Google Reviews API
When a compiled database is the better pick: you need millions of records on your desk this afternoon in one flat file, your team's workflow is built around a vendor's export tools and filters, or you want firmographic depth like revenue bands and org charts that the big data vendors compile over years. Those products are good at bulk and depth. This one is good at fresh and exact.
Run one query on the free tier and look at the scrapedAt field on every record that comes back. That is the whole pitch.
Get 3,000 free credits