# Real Estate Agent Lead Scraper (`mrdoe/real-estate-agent-leads`) Actor

Scrapes real estate brokerage/agency websites for agent rosters and profile pages, and enriches leads with verified contact emails.

- **URL**: https://apify.com/mrdoe/real-estate-agent-leads.md
- **Developed by:** [MrDoe](https://apify.com/mrdoe) (community)
- **Categories:** Real estate, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $1.70 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Real Estate Agent Leads + Verified Emails - Agent Contacts From Any Brokerage Site

Turn a real estate brokerage or agency website into a list of individual agent leads - name, title, phone, and a verified email even when the site hides it from scrapers behind client-side JavaScript.

### What does this Actor do?

Give it one or more brokerage/agency website URLs and it returns one structured record per agent, including:

- **Agent details** - name, job title (REALTOR®, Broker Associate, etc.), phone, LinkedIn
- **Brokerage details** - name, website, domain
- **Contact email** - read directly from the page when present, or found by the agent's name + the brokerage's domain (or LinkedIn handle) when it isn't - many agent sites obfuscate emails with JavaScript specifically to block scrapers
- **Optional email verification** - deliverability check

Nothing is guessed or invented - fields with no available data are returned as `null`.

### How it works

1. Loads each brokerage's homepage and follows links to its agent/team/roster page(s).
2. On a roster page, reads inline agent cards where name, email, and phone are grouped together, and collects links to any individual agent profile pages for agents without an on-page email.
3. Visits each individual agent profile page (up to **Max agents per site**) to extract that agent's name, title, phone, and email.
4. For any agent found by name but with no email on the page, looks up an email using the agent's name and the brokerage's domain (or LinkedIn handle, if found on the page).
5. If a site has no discoverable agent roster at all, falls back to a single company-level lead, so the brokerage still isn't skipped entirely.

This Actor is HTTP-only (no headless browser), so it's fast and lightweight even across many brokerage sites.

### How to use

1. [Sign up](https://apify.com/sign-up) for a free Apify account.
2. Open this Actor and enter one or more **Brokerage/agency website URLs**.
3. Set **Max agents per site** and **Max total leads** as needed.
4. Click **Start** and export results as JSON, CSV, Excel, or via API.

### Output

Each dataset item follows a standard lead shape shared across this Actor family:

| Field | Description |
|---|---|
| `companyName`, `companyUrl`, `domain`, `companyWebsite` | Brokerage identity |
| `contactName`, `firstName`, `lastName`, `jobTitle` | Agent identity and role |
| `email`, `emailType`, `emailConfidence`, `emailVerificationStatus`, `emailSources` | Contact email data |
| `phone`, `linkedinUrl` | Agent contact channels |
| `source`, `sourceUrl`, `profileUrl`, `scrapedAt` | Provenance metadata |

Fields with no available data are returned as `null` rather than omitted or guessed.

### Cost & performance notes

- Enrichment lookups only run for agents with a known name but no on-page email; agents whose email is already visible cost nothing extra.
- Email verification is opt-in and off by default.
- Concurrency is kept conservative to stay reliable at scale.

# Actor input Schema

## `startUrls` (type: `array`):

Real estate brokerage or agency website URLs to scrape for agent leads, e.g. https://www.example-realty.com

## `maxAgentsPerSite` (type: `integer`):

Maximum number of agents to return per brokerage website.

## `maxTeamPagesPerSite` (type: `integer`):

How many team/roster pages linked from the homepage to check.

## `maxItems` (type: `integer`):

Overall cap on leads returned across all sites. Set to 0 for unlimited.

## `proxyConfiguration` (type: `object`):

Proxy settings for the run.

## `enableContactEnrichment` (type: `boolean`):

When enabled, agents found without an on-page email are automatically looked up by name + domain (many agent sites obfuscate emails from scrapers with client-side JS). Sites with no agent roster found at all fall back to one company-level lead.

## `enableEmailVerification` (type: `boolean`):

When enabled, every returned email is additionally checked for deliverability. Disabled by default.

## Actor input object example

```json
{
  "startUrls": [
    "https://lctteam.com"
  ],
  "maxAgentsPerSite": 15,
  "maxTeamPagesPerSite": 2,
  "maxItems": 0,
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "enableContactEnrichment": true,
  "enableEmailVerification": false
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        "https://lctteam.com"
    ],
    "maxAgentsPerSite": 15,
    "maxTeamPagesPerSite": 2,
    "maxItems": 0,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("mrdoe/real-estate-agent-leads").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "startUrls": ["https://lctteam.com"],
    "maxAgentsPerSite": 15,
    "maxTeamPagesPerSite": 2,
    "maxItems": 0,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("mrdoe/real-estate-agent-leads").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    "https://lctteam.com"
  ],
  "maxAgentsPerSite": 15,
  "maxTeamPagesPerSite": 2,
  "maxItems": 0,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call mrdoe/real-estate-agent-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,mrdoe/real-estate-agent-leads"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/wLZjlf9QfnVUfL7MN/builds/BMQd7VvHWyjaksP5M/openapi.json