Find public business contacts by city and business type, or supply a list of company website URLs. Export published business emails, phones, social links, and source pages to JSON, CSV, or Excel.
This Actor finds companies, not people. It does not use Apollo, ZoomInfo, Lusha, private contact databases, login credentials, or guessed email addresses.
Quick start
{
"sector": "dentist",
"country": "United States",
"cities": [
"Chicago"
],
"maxLeads": 5,
"maxPagesPerSite": 2,
"requireEmail": true,
"verifyMx": true
}
Discovery processes the supplied cities. Start with one city and split larger searches into separate runs. Supplying startUrls uses those websites instead of city discovery.
Example output
Illustrative business record; the example company and contact details are not a verified lead.
{
"companyName": "Example Dental",
"domain": "example.com",
"website": "https://example.com/",
"country": "United States",
"sector": "dentist",
"address": "123 Main St, Chicago, IL",
"discoveryUrl": "https://www.openstreetmap.org/node/123",
"companyEmails": [{"email": "hello@example.com", "sourceUrl": "https://example.com/contact"}],
"primaryEmail": "hello@example.com",
"emailMxStatus": "mx_present",
"phones": ["+1 555 0100"],
"socials": {"linkedin": null, "facebook": null, "instagram": null, "twitter": null},
"pagesScraped": ["https://example.com/", "https://example.com/contact"],
"scrapedAt": "2026-08-30T00:00:00.000Z"
}
Input settings
| Setting | JSON key | Type / default | What it does |
|---|---|---|---|
| Business type | sector |
string / not set | Business-type pattern matched against public OpenStreetMap amenity, office, shop, or craft tag values, for example dentist. This is not a universal industry directory. |
| Country | country |
string / not set | Country used to bound OpenStreetMap city discovery. |
| Cities | cities |
array / not set | Cities to process for public business discovery. Start with one city; split larger searches into separate runs for clearer coverage. |
| Public business website URLs | startUrls |
array / not set | Optional direct public-site seeds. These use the independent public-site route instead of OpenStreetMap discovery. |
| Maximum businesses | maxLeads |
integer / 5 |
Hard cap on unique business rows. Minimum 1; maximum 100. |
| Maximum public pages per site | maxPagesPerSite |
integer / 2 |
Homepage plus same-site contact/about/team pages to inspect. Minimum 1; maximum 5. |
| Only keep businesses with a public email | requireEmail |
boolean / true |
Enabled by default so lead-discovery rows always include a visibly published public email. Disable only for public business-directory research where contact availability is optional. |
| Check email-domain MX | verifyMx |
boolean / true |
Checks whether the business domain has MX records. This is not a mailbox deliverability check. |
| Discovery offset | customOffset |
integer / 0 |
Skip this many discovered businesses before processing. Use to resume a bounded batch. Minimum 0; maximum 10000. |
What you get
- City-bounded public business discovery
- Public website, phone, address, and source record URL
- Emails visibly published on the business website, with the page URL
- Optional domain MX status (not a mailbox deliverability claim)
- Linked business social links and fetched-page provenance
Tips and limits
Start with one city and a small maximum. Not every public business has a website or publishes an email; disable requireEmail when you need a company-research list rather than an email-ready list. Public source availability can change or rate-limit requests, so valid partial results are retained with their provenance.
Who is it for?
- Local sales and outreach teams building a source-backed company list before personal contact.
- Agencies and researchers who need repeatable city-and-sector discovery with exportable provenance.
- Operations teams that already have a list of public company sites and want to collect only visible business contacts.
API usage
Use your Apify API token through the APIFY_TOKEN environment variable. Node.js and Python examples wait for the run and read its first dataset page; paginate the dataset for larger exports.
Node.js
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/leads-finder').call({
"sector": "dentist",
"country": "United States",
"cities": [
"Chicago"
],
"maxLeads": 5,
"maxPagesPerSite": 2,
"requireEmail": true,
"verifyMx": true
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
Python
import json
import os
from apify_client import ApifyClient
client = ApifyClient(os.environ["APIFY_TOKEN"])
run_input = json.loads('''{
"sector": "dentist",
"country": "United States",
"cities": [
"Chicago"
],
"maxLeads": 5,
"maxPagesPerSite": 2,
"requireEmail": true,
"verifyMx": true
}''')
run = client.actor("fetch_cat/leads-finder").call(run_input=run_input)
print(client.dataset(run["defaultDatasetId"]).list_items().items)
cURL
Save the quickstart JSON as input.json. This request starts a run asynchronously; use its returned run ID to check completion and its defaultDatasetId to retrieve results.
curl -X POST "https://api.apify.com/v2/acts/fetch_cat~leads-finder/runs" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
--data-binary @input.json
MCP and AI agents
Use the official Apify MCP server, not a separate custom server. The focused URL below selects this Actor. Authenticate with Apify when your client prompts you; configuration syntax and OAuth support depend on the client.
Claude Code
claude mcp add --transport http apify "https://mcp.apify.com?tools=fetch_cat/leads-finder"
HTTP-capable MCP client configuration
{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=fetch_cat/leads-finder"
}
}
}
Example prompt: "Find up to five dentist businesses in Chicago that publish an email. Return the company, public email, phone, and supporting source page. Do not infer personal contacts."
Use the same input keys as the input table. Review the returned source URLs and any error or availability fields before using results in an automated summary.
Support
If a run fails or output looks wrong, open an issue from the Actor page. Include the Apify run ID or run URL, non-sensitive input JSON, expected output, actual output, and one reproducible public URL (or the exact search input). Do not share tokens, cookies, passwords, or private data.