How to Build a Database of Real Estate Agents From Redfin

Short answer: Redfin lets people search for agents by location or name and view individual profiles. Its current Terms of Use prohibit automated crawling or querying to obtain information unless you first receive express written permission from the applicable Redfin company. The Services Addendum also restricts copying, redistribution, scraping, and data mining of MLS-derived information. Do not build a database by crawling Redfin or automating profile collection without that permission and any required MLS or data-owner approval.

You can still use Redfin for individual agent discovery. If you need a structured directory for research or business use, first establish an authorized source and permitted uses for every field, then verify and maintain the records. This guide explains the boundary and a practical, permission-first workflow; it does not provide scraping instructions.

1. What Redfin makes available

Redfin’s agent directory supports consumer searches by city, ZIP code, or agent name. Individual profiles may include transaction history, customer reviews, and contact information. An agent’s team number or an “Ask a Question” box may also appear on profiles and listing pages. Redfin’s customer FAQ says agent contact details can appear on listing pages as well as profiles. These are ways to learn about agents one at a time, not evidence of a bulk export or permission to compile the information.

For a non-Redfin agent asking about the Open Book directory or profile edits, Redfin lists openbook@redfin.com as a support contact. Treat that as a route for support questions, not authorization for bulk collection.

2. Check permission before collecting anything

Redfin’s Terms of Use, updated September 29, 2025, prohibit automated crawling or querying to obtain information from its services unless the user has prior express written permission from the applicable Redfin company. The restriction expressly covers screen and database scraping, spiders, robots, crawlers, and other automated activity. The Services Addendum also restricts copying, redistribution, retransmission, scraping, data mining, and activity intended to collect, store, reorganize, summarize, or manipulate Redfin information or related data. It describes MLS-provided information as intended for personal, non-commercial use and notes that MLSs own their listing data. See Redfin’s Terms of Use.

The reviewed Redfin materials do not document a general-purpose bulk export, API, or blanket permission route. Do not infer permission from the fact that a page is publicly viewable, from an individual search feature, or from the support email address.

Before collection, get written answers to these questions

Which specific pages, fields, and volume of records may you collect?
May you store, transform, publish, redistribute, or use the data commercially?
Does the permission cover MLS-originated content, and do the relevant MLS or data owners impose additional conditions?
What retention, attribution, update, deletion, and access limits apply?
Does your intended outreach or other use require separate review under the laws and rules that apply in your jurisdiction?

Ask the applicable Redfin company for express written permission and check the conditions imposed by relevant MLS or data owners before collecting or reusing Redfin information. The reviewed materials do not establish a general permission application process or a guaranteed approval route.

3. Design an authorized agent directory

Once you have an authorized source and have confirmed the intended use, make permission and provenance part of the record design. A spreadsheet can work for a small, maintained directory; a database is more suitable when multiple people need controlled updates, audit history, and repeatable validation. The schema below is a starting point, not a claim that any particular field is available for reuse from Redfin.

Field	What to record
`agent_id`	An internal stable identifier; do not use a profile URL as the only identity key.
`full_name`	Name as shown by an authorized source, plus a checked date.
`brokerage`	Brokerage affiliation and the source used to verify it.
`license_status`	Status, jurisdiction, authoritative verification source, and date checked.
`service_area`	City, county, ZIP codes, or another defined geography, with source and date.
`contact_details`	Only details you are allowed to retain and use; record the source and permitted purpose.
`source_url`	The source record or page, if retaining that URL is permitted.
`permission_reference`	Permission owner, document or case reference, scope, and any limits.
`checked_at`	When the record was last verified.
`review_due_at`	When the record should be reviewed again under your chosen maintenance policy.
`notes`	Concise internal notes that do not add unsupported claims or unnecessary personal data.

Suggested workflow

Define the purpose. State whether the directory supports research, internal reference, publication, or outreach. A permitted collection purpose does not automatically permit every later use.
Document source rights. For each source and field, record what permission or terms allow, who granted it, and any reuse or retention limits. Leave fields out when the permission is unclear.
Choose a data model. Separate agent identity, brokerage affiliation, contact points, source observations, and permission records. This lets you correct a changed affiliation without erasing the provenance of earlier observations.
Collect only through the authorized method. Follow the written scope and applicable source instructions. Do not automate Redfin collection unless the required prior express written permission covers that activity.
Verify independently where permitted. Check identity, brokerage, license status, contact details, and geography against authoritative sources you are authorized to use. The reviewed Redfin sources do not establish a particular license-checking source or method.
Track changes and review dates. Record when each value was checked and revisit records according to your operational needs and source conditions.
Control access and retention. Give access only to people who need it, honor applicable deletion and retention conditions, and avoid keeping data whose permission or purpose has expired.
Review before publishing or contacting agents. Confirm that redistribution and the intended outreach are allowed, and assess jurisdiction-specific requirements with appropriate expertise.

4. Accuracy and ongoing maintenance

Redfin says its listing data comes directly from the MLS and that changes to listing data should be made in the MLS; MLS-powered websites update afterward. Redfin also says it makes no guarantees about the reliability, accuracy, or currentness of information from MLS sources. A profile or transaction record should therefore be treated as a source observation, not as a permanently verified fact.

For each value, store its source and checked date. Set a review cadence that matches the field’s importance and your authorized source’s update behavior. When two authorized sources disagree, retain the conflicting observations and dates until you resolve them rather than silently overwriting one. Do not claim that a record is current unless it has been checked against a source you can use for that purpose.

5. Redfin’s consumer request flow is different

Redfin’s privacy policy explains that when a user submits a request through Redfin, the user authorizes Redfin to share personal information—including contact information, search history, favorites, and saved searches—with a real estate professional so that professional can respond. That describes a consumer-request flow. It does not authorize compiling agent profiles or their contact details into a separate database.

Likewise, the Open Book support route is for profile and directory questions; the reviewed FAQ does not present it as a bulk-export permission channel. Keep consumer requests, profile support, and database collection as separate workflows.

6. What to evaluate when choosing a data source

The reviewed Redfin materials do not establish an approved bulk source for this project. Evaluate any source you consider rather than assuming that another searchable directory permits reuse.

Evaluation area	Questions to answer
Authorization	Do the source terms or written permission cover the collection method and fields?
Reuse and outreach	May you store, publish, share, or use the records for the specific business purpose?
Provenance	Can you retain the source, permission reference, and checked date for each field?
Update process	How are corrections and changes surfaced, and what review work must you do?
Accuracy and coverage	How are identity, geography, brokerage, and contact fields verified, and where are gaps expected?
Privacy and retention	What limits apply to personal information, retention, deletion, and access?

7. Troubleshooting common project problems

Problem	Likely cause	Practical response
“The profiles are public, so can we collect them automatically?”	Visibility is being mistaken for permission.	Pause automated collection. Redfin’s terms require prior express written permission for automated crawling or querying to obtain information. Confirm scope with Redfin and relevant data owners.
“We have permission to view profiles. Can we republish the fields?”	Access and reuse are being treated as the same grant.	Review the written permission and source conditions for storage, copying, redistribution, commercial use, and outreach. Ask for explicit coverage where it is missing.
“The support email did not approve the project.”	A profile-support route was treated as bulk-collection authorization.	Use `openbook@redfin.com` for Open Book or profile questions, and request explicit written authorization from the applicable Redfin company for any proposed collection. Do not infer approval from a support exchange unless it clearly grants it.
“An agent’s Redfin profile differs from another record.”	Sources may update at different times, and MLS information may be incomplete or stale.	Store both source observations and checked dates. Verify against another independently authorized authoritative source before updating the canonical record.
“We cannot find a general Redfin API or export.”	The reviewed materials do not document a general-purpose bulk export, API, or blanket permission route.	Do not substitute browser automation. Ask Redfin about written permission and evaluate other sources under their own terms.
“A consumer asked Redfin to contact an agent.”	A one-to-one request flow is being confused with permission to compile a directory.	Use that flow for its described response purpose; do not treat it as authority to copy agent data into a separate list.

8. Use screenshots for documentation without turning them into a data feed

For a permitted research workflow, a screenshot can document what an individual page looked like at a particular point in time. It is not a substitute for permission to collect, extract, store, or redistribute the page’s information. Keep any captured material within the scope of your authorization and applicable source terms.

If you need a website screenshot API for pages you are authorized to capture, ScreenshotNeo is a website screenshot API and MCP server for developers. It returns PNG, JPEG, WebP, or PDF from a single GET request. Documentation: ScreenshotNeo API docs.

For authorized pages, the basic request is:

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://example.com \
  -o shot.webp

Use only pages you are allowed to capture. Screenshot output preserves a visual record; it does not grant rights to automate access or reuse the underlying data.

Or skip the browser setup

For a page you are authorized to capture, ScreenshotNeo can take the screenshot with one API request. Here are the same call patterns in cURL, Python, and Node.js; replace the example target only with a page you may capture.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webp

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`ScreenshotNeo request failed: ${res.status}`);
await Bun.write('shot.webp', res);

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. These are capture features and billing terms, not permission to collect Redfin data.

9. Performance, reliability, and cost planning

For an authorized directory, the main cost is usually the work required to establish permission, verify records, resolve duplicates, and maintain accuracy. Estimate effort from the number of records, fields, sources, and review frequency rather than from page count alone. A smaller verified directory may be more useful than a larger list with unclear provenance.

Plan for source changes and gaps: preserve checked dates, record failures to verify, and make review work visible. Redfin’s terms disclaim guarantees about MLS information’s reliability, accuracy, and currency, so do not build a process that assumes profile data never changes. Do not use retries, proxies, or browser tooling to work around access controls or permission limits.

10. Frequently asked questions

Can I manually look up agents on Redfin?

Redfin supports consumer searches by location or agent name and provides individual agent profiles. Follow the site terms and do not assume that manual viewing allows bulk copying or reuse.

Does Redfin offer a bulk agent database download?

The reviewed Redfin materials do not document a general bulk export or API for this purpose. Ask Redfin directly about written permission rather than relying on an undocumented route.

Does contacting Open Book support authorize collection?

No such authorization is described in the reviewed FAQ. The address is given for agent directory and profile questions; bulk collection requires explicit permission where the terms require it.

Can I use Redfin profile details for business outreach?

The terms describe MLS-derived information as personal, non-commercial, and restrict copying and redistribution. Establish permission, source rights, and the requirements that apply to your outreach and jurisdiction before using any list.

Are screenshots a compliant way to save agent information?

A screenshot changes the format, not the underlying access or reuse rights. Capture and retain pages only within the permissions and terms that apply.

Sources

Redfin Terms of Use, including sections 2.3.5 and 2.9.7.
Redfin Customer Service Buying FAQ, for agent search and profile information.
Redfin Customer Service Agent FAQ, for profile support and MLS data updates.
Redfin Privacy Policy, for consumer requests to share information with a real estate professional.