Restaurant lead list, USA: 168 venues found in Austin in one run — any city on request
The restaurants trading in the US city, state or metro you name, with operating address, phone, website, the emails published on that website, rating and an active flag. Built from a live Google Maps sweep — 168 venues in Austin in one pass — then enriched site by site. 50 rows free from your own area; from $0.01 per lead via the API, or a done-for-you file from $290 per metro.
50 free rows · source on every row · operating address, not a registered office · CSV or XLSX
What the US restaurant lead list is
It is the roster of restaurants trading in a named US city, county, state or metro — a B2B file about the venues themselves, not a list of anybody’s diners. One row per venue: trading name, Maps category, operating street address, city, state, ZIP, phone, website, the email addresses that website publishes, social profiles, rating, review count, date of the last review and an active flag.
The measurement on this page is Austin, Texas, on 8 September 2026: one google_maps_places run returned 168 venues, 159 of them with a website to enrich and 161 with a phone number on the listing. That is one city in one pass, not a national total, and we will not quote you a national count we have not measured. Name your area and the same pipeline runs against it.
Independents, small groups and franchise units all sit in the same Maps categories, so the cut can be as tight as your product needs — a fine-dining supplier and a delivery platform want very different slices of the same city.
The columns you get
Fourteen columns per venue, the same set whether you run the collectors yourself or we deliver the file.
| Field | Type | What it contains |
|---|---|---|
| Business name | text | Trading name of the venue exactly as it appears on the Google Maps listing. |
| Category | text | Primary Maps category, plus the secondary categories where the listing carries them. |
| Street address | text | The operating address — where the business actually trades, not a registered or billing office. |
| City | text | City or town of the operating address, so you can split the file by market. |
| State | text | Region of the operating address, for territory splits and per-rep assignment. |
| ZIP code | text | Postal code as published on the listing; blank when the listing omits it. |
| Phone | text | Public number from the listing, normalised to international format. |
| Website | URL | Site linked from the listing, plus whether it resolved, redirected or was dead when enrichment ran. |
| text | Found on the business website during enrichment; blank when the site has none. | |
| Social profiles | text | Facebook, Instagram, LinkedIn and X links read off the website’s own markup. |
| Rating and review count | number | Star rating and how many reviews it is based on, from the Maps listing. |
| Last review date | date | Date of the most recent review — the freshness signal behind the active flag. |
| Active flag | enum | active · doubtful · no review for 2+ years, derived from the review dates. |
| Source | text | Which collector produced the row: the Maps listing, the website enrichment, or both. |
How the list is built
How the restaurant list is built
Five steps, all of them repeatable — the same collectors you can call yourself through the API.
1. Google Maps sweep of the area you name
The google_maps_places collector runs the restaurant query against the city, county or metro you name and returns every listing it can reach — 168 in Austin in a single run on 8 September 2026.
2. Dedupe by name and street
Rows are collapsed on a normalised business name plus street name (place ID first when two runs are merged), which took the Austin run to 168 distinct businesses.
3. Website enrichment for emails, phones and socials
The local_business_leads collector opens each website and reads emails from mailto: links, JSON-LD and page text, extra phone numbers, social profiles and whether the site is still live.
4. Active flag from the reviews
Rating, review count and the date of the last review are attached to every row, and anything without a review for two years or more is flagged so you do not mail a closed unit.
5. CSV or XLSX with the source on every row
The file ships as CSV, XLSX or JSON, one row per business, each carrying the collector it came from so any value can be traced back to where it was published.
Free sample · no account needed
Ten real rows from the Austin run
Straight out of the 8 September 2026 run, with the street number and most of the phone masked. Ask for 50 unmasked rows from your own area.
| Business | Street | City | Phone | Website | |
|---|---|---|---|---|---|
| Corner Restaurant | E 2nd St | Austin | +1 512 ••• ••88 | cornerrestaurantaustin.com | on request |
| Fareground Austin | Congress Ave | Austin | +1 512 ••• ••07 | faregroundaustin.com | on request |
| Swift's Attic | Congress Ave. | Austin | +1 512 ••• ••42 | swiftsattic.com | on request |
| Truluck's Ocean's Finest Seafood and Crab | Colorado St | Austin | +1 512 ••• ••00 | trulucks.com | on request |
| Mattie's | W Live Oak St | Austin | +1 512 ••• ••88 | mattiesaustin.com | on request |
| TenTen | W 6th St | Austin | +1 737 ••• ••47 | tentenaustin.com | on request |
| Rogue Radish | Congress Ave | Austin | +1 512 ••• ••36 | rogueradish.org | on request |
| Austin Rotisserie & Sandwicherie | Congress Ave | Austin | +1 512 ••• ••09 | austinrotisserie.com | on request |
| Mason's Famous Lobster Rolls | Congress Ave. | Austin | +1 512 ••• ••06 | masonslobster.com | on request |
| The Onion | Brazos St | Austin | +1 512 ••• ••66 | onionbaby.com | on request |
Street shortened to the street name; phone masked to country code, area code and last two digits; email delivered on request (enrichment not run for the sample). Measured on 2026-09-08 in one run; counts are for the named city, not a national total.
Pricing
What it costs
Two ways to the same rows: run the collectors yourself and pay per delivered lead, or name the area and get the finished file.
local_business_leads collector, $2 free credit per month, failed runs freeEvery price is a starting price: what a city costs depends on how many venues the area holds and whether you want website enrichment on all of them. Ask for the free 50 rows first — it is the same pipeline, and it costs nothing.
Who buys a restaurant list
Everyone whose customer is the venue, not the diner.
POS and payments vendors
Terminals, kitchen displays and card processing are sold venue by venue. Split the file by ZIP for field reps and use the website column to spot who already has online ordering.
Food and beverage wholesalers
Produce, meat, coffee and drinks distributors need the operating address the delivery truck goes to, plus a phone that reaches the kitchen — not a registered office.
Delivery and reservation platforms
Merchant-onboarding teams work a metro at a time; the active flag and last-review date show which venues are trading now and which have gone quiet.
Kitchen equipment and refrigeration suppliers
Combi ovens, walk-ins and extraction systems: review volume tells you which venues are busy enough to be replacing equipment.
Hospitality staffing and booking software
Rota, tips and table-management tools sell by city. The social columns show which venues are marketing themselves and which are not.
Marketing agencies and insurance brokers
A dead site, no published email or no review for two years is the opening line; brokers use the same file for territory planning.
Against a bought static list
The complaints buyers make about purchased files, and what this one does instead.
| Bought static list | This list | |
|---|---|---|
| Freshness | Compiled once and resold for years; you cannot tell when it was assembled. | Built from a live Google Maps run the week you order it, with a monthly refresh feed on request. |
| Source per row | One undifferentiated file — no way to check where a record came from. | Every row names the collector behind it: the Maps listing, the website enrichment, or both. |
| Address | Often the registered or billing office, so mail never reaches the counter. | The operating address of the venue as published on its listing. |
| Email origin | Pattern-guessed or appended from a third-party database. | Read off the business’s own website during enrichment; blank when the site publishes none. |
| Active flag | Closed units stay in the file and burn your sending reputation. | Rating, review count and last review date on the row; anything silent for 2+ years is flagged. |
| Price model | Minimum order for a national file you did not ask for. | From $0.01 per lead via the API, or from $290 for one city or metro — 50 rows free first. |
Compliance: business contacts, and what you may do with them
Every row is a business, not a person: the venue’s trading name, its operating address, the public switchboard number, the website and the addresses that website publishes. There is no consumer data on the file — no home addresses, no personal mobile numbers, no profiles — and sole traders trading under their own name are flagged so you can treat them more carefully than an incorporated practice.
In the United States, commercial email is governed by the CAN-SPAM Act: accurate headers and subject lines, a valid physical postal address in the message, and an opt-out that works and is honoured within ten business days. Calls and text messages to the numbers on the file fall under the TCPA and the FCC rules at 47 CFR § 64.1200, which is why the list is delivered with the phone column separated and why you should screen against the Do Not Call registry before any dialling or SMS campaign.
The data is publicly available business information collected from Google Maps listings and from the businesses’ own websites, and every row carries its source so you can verify it. Once the file is delivered you are the independent controller of it: what you send, to whom, and how you handle removal requests is your decision and your record-keeping. We will remove a business from a future delivery on request, and we do not sell consumer data of any kind.
Sources and standards: FTC — CAN-SPAM Act: A Compliance Guide for Business · 47 U.S.C. § 227 (TCPA) — Cornell Legal Information Institute · 47 CFR § 64.1200 — telephone solicitation rules (eCFR) · Google Maps — Wikipedia
Questions buyers ask
Coverage, freshness, legality and delivery — the eight things every buyer asks before the first file.
Ask for your sample →How many restaurants will I get?
As many as the area holds: we do not sell a fixed national count, we run your area and report what came back. Measured on 8 September 2026, one Google Maps run on Austin, Texas returned 168 distinct venues. A state or a whole country is run city by city and quoted within 24 hours, so you always know the count before you pay.
How fresh is the list?
It is built when you order it. The numbers here come from a run on 8 September 2026, and your area gets a fresh Google Maps sweep on the day — not a slice of a file compiled years ago. Need it to stay current? The monthly refresh feed re-runs the same area and ships the deltas from $390 a month.
Do all rows have an email address?
No, and any vendor claiming otherwise is guessing addresses. In the Austin run, 159 of the 168 venues had a website at all — that is the ceiling, because emails are read off the venue’s own site during enrichment, never pattern-guessed. Rows without a published address arrive with the email column blank and the phone still filled in.
Is it legal to email a list like this in the US?
The file is publicly available business data, and US commercial email is governed by CAN-SPAM rather than a consent rule: accurate headers, your physical postal address in the message, and an opt-out honoured within ten business days. Calls and SMS are different — those fall under the TCPA, so screen before you dial. You are the controller of the file once delivered.
How is it delivered and how fast?
CSV, XLSX or JSON, one row per business, with the source column included. The free 50-row sample arrives within one business day. A single city or metro is normally delivered in two to three business days; a whole country is quoted within 24 hours and scheduled state by state, or region by region, so you can start working the first batch while the rest runs.
Can I buy one city or one state only?
That is the normal order. Name a city, a metro, a county or a state and that is what gets run — one city or metro starts at $290, and states are priced on the number of venues they hold. Buying Austin before buying Texas is cheaper than any national file and tells you whether the data converts.
Should I use the API or ask you for the file?
Use the API when you want to run areas yourself, on your own schedule, inside your own stack: local_business_leads costs from $0.01 per delivered lead and every account gets $2 of credit a month. Ask for the done-for-you file when you want one clean deliverable, deduped across cities and checked by hand, without writing any code.
What if some rows are wrong?
There is no refund mechanism to argue about, because you check the data before you pay: the free 50-row sample comes from the area you actually want, built by the same pipeline as the paid file. On the API, rows are billed per delivered lead — with only_with_contacts on, a business with no reachable phone or website is not delivered and not charged.
Get 50 restaurants from your own city, free
Name the area and what you sell to venues. The sample arrives within one business day — real rows, unmasked, from the same pipeline as the paid file. No card, no account.
Get a free 50-row sampleUpdated 2026-09-08 · Written by the QuanticData team from the collector documentation and the sources cited.