Realtor.com Agents Scraper — Profiles & Contact Data

Scrape Realtor.com real estate agent profiles by US city or ZIP — then download structured agent contact data as Excel, CSV, or JSON.

This Actor is a practical Realtor.com agent API alternative for lead generation, brokerage research, and market outreach. Enter a location such as Austin, TX or a ZIP like 78701, and get agent rows with phones, office/broker, ratings, sales stats, languages, specializations, and served areas when present on the profile.

• Search real estate agents on Realtor.com
• Resolve city or ZIP via Realtor.com geo suggest (tx_austin marketing area or postal code)
• Optionally enrich each agent with the AgentBranding profile (phones, MLS, office address)
• Filter by agent name, Realtor member flag, and price band
• Export to Excel / CSV / JSON, or connect Make, n8n, Zapier, Python, or MCP
• Pay per event — Actor start + each Dataset agent; no subscription

---

What does the Realtor.com Agents Scraper do?

It turns a US city or ZIP agent search on Realtor.com into a clean Apify Dataset of agent profiles.

Under the hood, the Actor:

1. Resolves your location through Realtor.com geo suggest
2. Runs the search_agents GraphQL query for matching profiles
3. Optionally fetches AgentBranding enrichment for phones, office, MLS, and specializations
4. Writes normalized records you can download or push into automations

Apify RESIDENTIAL proxy is required on cloud runs (prefilled). Direct/datacenter traffic is often blocked.

---

What data can you extract from Realtor.com agents?

Data point	Included
Agent name & profile URL	✅
Phone(s)	✅
Office / broker name	✅
Ratings & review counts	✅
For-sale / recently sold stats	✅
Languages & specializations	✅
Served areas	✅
License number / state	✅
MLS memberships	✅
Avatar, website, social links	✅
Bio / designations	✅

Every Dataset row also includes scrapedAt and source = realtor.com. A RUN_SUMMARY record in the key-value store reports counts and warnings.

---

What you can do with it

1. Build a Realtor.com agent lead list for a city

Enter a city like Austin, TX, set max results, and export names, phones, offices, and profile URLs for outreach or CRM import.

2. Scrape agents by ZIP code

Use a ZIP such as 78701 when you need a tighter local market than a full city marketing area.

3. Enrich agent contact and brokerage details

Keep Enrich profiles enabled to pull AgentBranding fields (phones, office address, MLS, specializations) on top of search stubs.

4. Filter by name, member status, or price band

Narrow results with agentName, isRealtor, and optional minPrice / maxPrice before saving rows.

5. Feed agent data into automations

Schedule the Actor and send the Dataset to Sheets, Slack, CRM, Make, n8n, Zapier, or an AI agent via Apify MCP / API.

---

How to scrape Realtor.com agents (no code required)

1. Click Try for free
2. Enter a location (Austin, TX or 78701)
3. Optionally set agent name filter, max results, and enrich toggle
4. Keep Apify RESIDENTIAL proxy enabled
5. Click Start — open the Dataset tab when the run finishes

Start with maxResults: 5–10 to verify the market, then scale up.

---

Pricing — how much does it cost to scrape Realtor.com agents?

Pay per event. No subscription.

Event	Price	When charged
apify-actor-start	$0.005	When a normal run starts (scaled by allocated memory GB)
apify-default-dataset-item (result)	$2.50 / 1,000 ($0.0025 each)	Each agent written to the default Dataset

User pays platform usage costs: Yes — compute, residential proxy, and other platform usage are billed to the user in addition to event charges.

Example product charges (events only):

Scenario	Approx. event charge
Canary: 10 agents	$0.005 + 10 × $0.0025 = $0.030
City scan: 100 agents	$0.005 + $0.25 = $0.255
1,000 agents	$0.005 + $2.50 = $2.505

Platform usage (especially residential proxy) is separate and depends on run duration and memory.

---

Input

Field	Description
location	City and state or ZIP, e.g. Austin, TX / 78701
agentName	Optional name filter
maxResults	1–500 (default 20)
isRealtor	Restrict to Realtor.com members
minPrice / maxPrice	Optional USD price-band filters
enrichProfiles	Fetch AgentBranding details (default true)
proxyConfiguration	Apify RESIDENTIAL recommended

Open the Input tab in Console for the full form and tooltips.

---

Output example

You can download the Dataset as JSON, CSV, Excel, or HTML.

{
  "agentId": "5678",
  "name": "Jane Smith",
  "profileUrl": "https://www.realtor.com/realestateagents/jane-smith_austin_tx_5678",
  "phone": "5125550100",
  "officeName": "Example Realty",
  "brokerName": "Example Brokerage",
  "averageRating": 4.8,
  "reviewsCount": 42,
  "forSaleCount": 12,
  "recentlySoldCount": 28,
  "languages": ["English", "Spanish"],
  "specializations": ["Buyer's Agent", "Listing Agent"],
  "licenseNumber": "123456",
  "source": "realtor.com",
  "scrapedAt": "2026-07-17T00:00:00+00:00"
}

Core fields include contact (phone, phones, officePhones), brokerage (officeName, brokerName), ratings, listing stats, servedAreas, languages, specializations, license/MLS, and profileUrl.

---

Live View endpoints

When Standby / Live View is enabled, the Actor exposes a small OpenAPI surface for readiness and discovery:

Endpoint	Purpose
GET /	Readiness / service info
GET /health	Health check
GET /input-example	Low-cost example input
GET /openapi.json	Deployed OpenAPI document

Scraping still runs through a normal Actor run — Live View does not scrape Realtor.com by itself.

---

Connect from code

Actor ID: lentic_clockss/realtor-com-agents-scraper

from apify_client import ApifyClient

client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("lentic_clockss/realtor-com-agents-scraper").call(
    run_input={
        "location": "Austin, TX",
        "maxResults": 10,
        "enrichProfiles": True,
        "proxyConfiguration": {
            "useApifyProxy": True,
            "apifyProxyGroups": ["RESIDENTIAL"],
            "apifyProxyCountry": "US",
        },
    }
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item.get("name"), item.get("phone"), item.get("profileUrl"))

Use the same Actor ID in Make, n8n, Zapier, or Apify MCP for AI-agent workflows.

---

FAQ

Is there a free Realtor.com agent API?

Realtor.com does not offer a simple public agent-directory API for bulk export. This Actor gives you structured agent profiles through Apify runs, Dataset exports, and integrations.

Can I scrape agents by ZIP as well as city?

Yes. Pass a 5-digit US ZIP (e.g. 78701) or a City, ST string. The Actor resolves both through Realtor.com geo suggest.

Why is a residential proxy required?

Realtor.com blocks many datacenter and direct IPs. Apify RESIDENTIAL is required for reliable cloud runs.

Does enrichProfiles cost more?

Enrichment uses extra GraphQL profile calls and may use more proxy/compute, but event pricing still charges only Actor start + each Dataset item. Platform usage is billed separately when enabled.

Can I schedule daily Realtor.com agent scrapes?

Yes. Create an Apify schedule with the same input and send the Dataset to Sheets, Slack, a CRM, or your pipeline.

Is it legal to scrape Realtor.com agents?

Use this Actor for legitimate research and outreach only. Respect Realtor.com terms of use and applicable law. Results may include publicly displayed professional contact information; do not use personal data without a lawful basis.

---

Related Actors

• Realtor.com Scraper — homes for sale and rent listings
• US Real Estate Scraper — multi-site US aggregation

Browse all Actors: apify.com/lentic_clockss