Realtor Agents Scraper — Fast API & Leads

Realtor Agents Scraper collects public real-estate agent directory data from Realtor.com by US city, state, ZIP code, or direct agent-search URL. It is built for proptech sales, mortgage and title marketing, brokerage recruiting, territory research, CRM enrichment, and AI-agent workflows that need consistent JSON rather than manually copied profile pages.

The default fast mode calls Realtor.com's first-party agent search GraphQL API. This keeps runs short while returning names, brokerages, ratings, reviews, testimonials, production counts, price bands, recent markets, photos, and profile URLs. Turn on profile enrichment when you also need public phone, website, address, language, specialty, or service-area fields. Realtor.com's current profile API does not normally expose agent email addresses, so email is returned as null. Private and login-only data are outside this Actor's scope.

Each unique agent record costs $0.005. A 100-agent run therefore has a maximum result-event cost of $0.50, plus the low synthetic Actor-start event and any platform usage shown by Apify.

What data can I extract with Realtor Agents Scraper?

Field	Description
agentId	Stable Realtor.com or NRDS-style identifier
name	Agent or team display name
profileUrl	Public Realtor.com profile URL
photoUrl	Agent photo URL when available
brokerage	Brokerage or office name
rating	Realtor.com rating value
reviewCount	Public review count
testimonialCount	Public testimonial count
salesLast12Months	Production count shown for the previous 12 months
priceRangeMin, priceRangeMax	Normalized property price band
recentSalesLocations	Markets visible on the directory card
phone, website	Public profile contacts when enrichment is enabled
email	Reserved stable field; currently normally null because the source API does not expose it
officeAddress	Public office address when available
languages, specialties, serviceAreas	Public profile enrichment fields
locationQuery	Input market that produced the record
sourceUrl, scrapedAt	Provenance and extraction timestamp

All optional scalar fields are returned explicitly as null; optional lists are returned as empty arrays. This stable shape makes the dataset suitable for Apify MCP, database imports, typed API clients, and downstream validation.

Use cases for Realtor.com agent data

• Build territory-specific real-estate agent prospect lists for mortgage, title, insurance, staging, photography, software, and home-service sales.
• Identify productive agents using ratings, review volume, testimonials, price bands, and recent 12-month sales counts.
• Research brokerage presence by city or ZIP code.
• Recruit agents for brokerages and real-estate teams using public professional data.
• Enrich an existing CRM with public Realtor.com profile and production fields.
• Feed structured agent records to Claude, ChatGPT, LangChain, n8n, Make, Zapier, or a custom data pipeline.
• Monitor changes in agent coverage and market activity through scheduled runs.

Do not use this Actor for Realtor.com property listings, private MLS data, identity verification, email verification, consumer contact data, or bypassing access controls. A separate property-listing scraper is a better tool for homes, prices, beds, baths, and listing photos.

How much will scraping Realtor.com agents cost?

The Actor uses transparent pay-per-event pricing:

Event	Price
Actor start	$0.00005 per synthetic start unit
Agent result	$0.005 per unique record saved

Worked examples for result events:

• 25 agents: up to $0.125
• 100 agents: up to $0.50
• 500 agents: up to $2.50
• 1,000 agents: up to $5.00

The Actor prints the maximum result-event cost before scraping and reports the actual billed result count at the end. maxResults, Apify's maximum paid dataset-item limit, and the caller's maximum total charge all stop further output when reached. Failed pages are not billed as agent results.

Profile enrichment makes one additional first-party API request per agent but does not create a second custom event. Platform compute charges depend on the billing option and account configuration shown in Apify Console; the Actor does not require residential proxies.

How to use Realtor Agents Scraper

The smallest valid input uses the working default:

{
  "locations": ["Austin, TX"],
  "maxResults": 25,
  "includeProfileDetails": false
}

Search several markets in one run:

{
  "locations": ["Miami, FL", "Dallas, TX", "90210"],
  "maxResults": 300,
  "includeProfileDetails": false,
  "maxConcurrency": 6
}

Use a direct Realtor.com agent-directory URL:

{
  "startUrls": [
    { "url": "https://www.realtor.com/realestateagents/New-York_NY" }
  ],
  "maxResults": 100,
  "includeProfileDetails": true
}

When startUrls is supplied, it replaces locations. The Actor validates that every URL belongs to Realtor.com and begins with /realestateagents. Pagination is handled automatically and results are deduplicated by agent ID across pages and locations.

Fast mode or profile enrichment?

Use includeProfileDetails: false for bulk discovery, market analysis, production scoring, or any workflow that primarily needs directory-card fields. This is the default and avoids one extra page visit per agent.

Use includeProfileDetails: true when public phone, website, office address, languages, specialties, and service areas matter more than runtime. Realtor.com does not provide every field for every agent, so enriched fields can still be null or empty. The current profile API normally leaves email as null.

Output example

{
  "agentId": "785038427",
  "name": "Clark Gray",
  "profileUrl": "https://www.realtor.com/realestateagents/Clark-Gray_785038427",
  "photoUrl": "https://ap.rdcpix.com/example.webp",
  "brokerage": "Mercer Street Group, LLC",
  "officeAddress": null,
  "phone": null,
  "email": null,
  "website": null,
  "rating": 5,
  "reviewCount": 35,
  "testimonialCount": 144,
  "salesLast12Months": 42,
  "priceRangeMin": 180000,
  "priceRangeMax": 1750000,
  "priceRangeText": "$180k - $1.75M",
  "languages": [],
  "specialties": [],
  "serviceAreas": [],
  "recentSalesLocations": ["East Elmhurst, NY", "Jackson Heights, NY"],
  "locationQuery": "New York, NY",
  "sourceUrl": "https://www.realtor.com/realestateagents/New-York_NY",
  "scrapedAt": "2026-07-13T12:00:00.000Z"
}

The run also writes an OUTPUT summary to the default key-value store. It reports results pushed, billed events, blocked requests, empty pages, warnings, enrichment mode, and terminal status.

Use the Apify API

JavaScript with apify-client:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('YOUR_USERNAME/fast-realtor-agents-api-scraper').call({
  locations: ['Austin, TX'],
  maxResults: 100,
  includeProfileDetails: false,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python:

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("YOUR_USERNAME/fast-realtor-agents-api-scraper").call(run_input={
    "locations": ["Austin, TX"],
    "maxResults": 100,
    "includeProfileDetails": False,
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

cURL:

curl -X POST \
  "https://api.apify.com/v2/acts/YOUR_USERNAME~fast-realtor-agents-api-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"locations":["Austin, TX"],"maxResults":25,"includeProfileDetails":false}'

Use Realtor Agents Scraper through an MCP Server

Apify exposes Store actors through its hosted MCP server. The Actor's input descriptions are written for tool routing, and the dataset schema uses stable semantic keys with explicit nulls. An AI agent can call the Actor for requests such as “find 50 active Realtor.com agents in Austin and return brokerage, rating, reviews, sales count, and profile URL.”

Do not select this tool when the user asks for property listings, home valuations, private MLS fields, or verified emails. The expected price is $0.005 per returned agent plus the disclosed start and platform usage costs.

Reliability and limits

The Actor uses Realtor.com's public first-party GraphQL operations for location resolution, paginated agent search, and optional profile enrichment. Requests have bounded exponential retries for transient 403, 429, timeout, and 5xx responses. If every input fails, the run ends honestly as failed instead of silently returning an empty success.

Partial data is preserved. If an enriched profile fails after retries, the Actor returns the already discovered directory-card record and adds a warning to OUTPUT. Long runs persist agent IDs and counters so host migration does not duplicate results or charges.

Public page structure and available fields can change. Some agents do not publish contact details, and results can vary by location, Realtor.com ranking, time, and geography. The Actor does not guarantee exhaustive MLS membership or contact completeness.

Other dedicated scrapers

• Realtor Lead Scraper
• Google Maps Scraper
• Leads Finder Pro
• Yellow Pages US Scraper
• Contractor Lead Scraper
• HVAC Lead Scraper
• USA Plumbers Scraper
• Justia Lawyer Directory Scraper
• Email Address Validator
• CSLB California Scraper

FAQ

How many results can I scrape with Realtor Agents Scraper?

Set maxResults from 1 to 5,000. The available total depends on Realtor.com's public directory for the requested markets. The Actor stops at the configured cap and deduplicates agents across pages and locations.

Can I integrate Realtor Agents Scraper with other apps?

Yes. Use Apify integrations, webhooks, Zapier, Make, n8n, Google Sheets, cloud storage, or your own database pipeline. Dataset exports are available as JSON, CSV, Excel, XML, and other Apify-supported formats.

Can I use Realtor Agents Scraper with the Apify API?

Yes. Start asynchronous runs, call synchronously, read dataset items, and fetch the OUTPUT summary through the Apify API or official clients. Examples are included above.

Can I use Realtor Agents Scraper through an MCP Server?

Yes. Configure Apify's hosted MCP server with this Actor. The compact, stable schema is suitable for agent selection, validation, pagination, and downstream tool chains.

Do I need proxies to use this Actor?

No. This version calls Realtor.com's first-party public GraphQL API and does not require Apify Proxy. That reduces runtime, memory, and proxy cost compared with browser scraping.

Is it legal to scrape Realtor.com data?

This Actor extracts publicly displayed professional information. You are responsible for reviewing Realtor.com's terms, privacy and marketing laws, applicable state rules, and the legal basis for your use. Do not use the output for harassment, unlawful discrimination, spam, identity theft, or access to non-public data. Consult qualified counsel for high-risk or regulated use cases.

Your feedback

If a public field changes or a market returns incomplete results, open an Actor issue with the run ID, input, and expected field. Do not include private credentials or personal data in issue reports.