Radaris Scraper

Batch-search public Radaris people records by name and turn visible matches into structured data for lawful real-estate prospect research, identity resolution, and manual outreach preparation.

The Actor accepts names or Radaris name-search URLs. It returns attributed matches with age, birth year, current location, aliases, possible relatives, prior locations, and source profile links. It does not invent phone numbers, emails, ownership records, or match confidence that the public source does not expose.

What does Radaris Scraper do?

For each input name, the Actor:

1. Builds or validates a Radaris name-search URL.
2. Requests the public page through a US residential proxy.
3. Detects challenge pages and retries with a fresh bounded session.
4. Extracts server-rendered person matches.
5. Applies the optional state filter to the displayed current location.
6. Deduplicates matches by Radaris person ID.
7. Saves typed records to the default Apify dataset.

Who is this Actor for?

• Real-estate teams enriching a lawful prospect list before manual research.
• Researchers resolving common names to likely city/state matches.
• Data teams converting a Radaris search page into JSON, CSV, or Excel.
• Privacy professionals auditing which public identity signals appear for a supplied name.
• Automation builders feeding attributed public records into a review queue.

Do not use the output for credit, employment, housing, insurance, tenant screening, or another FCRA-regulated eligibility decision.

Why use this Radaris people search Actor?

• Batch input: process up to 100 names or source URLs per run.
• Source attribution: every record includes the search URL and exposed profile URL.
• Conservative matching: state filters are applied to the displayed location before saving.
• Useful structure: aliases, relatives, and prior locations are arrays rather than flattened text.
• Failure transparency: persistent challenges fail the run instead of returning a misleading empty result.
• Integration-ready: use the default dataset from Apify API, webhooks, schedules, Make, Zapier, or MCP.

What data can you extract?

Field	Meaning
personId	Stable identifier exposed on the Radaris result card
fullName	Displayed matched name
age	Displayed age, when available
birthYear	Displayed year associated with the age
currentLocation	Displayed current city and state
aliases	Alternate names shown by Radaris
relatives	Possible relative names, ages, and Radaris links
previousLocations	Previously associated city/state values
profileUrl	Attributed Radaris profile URL exposed by the card
searchUrl	Source name-search page
queryFirstName	Input first name
queryLastName	Input last name
queryState	Optional input state filter
scrapedAt	UTC extraction timestamp

Phone numbers, email addresses, full street addresses, property ownership, criminal records, and background-report content are not part of the supported public output.

How to run your first search

1. Open the Actor input page.
2. Add one or more objects under People to search.
3. Enter firstName and lastName.
4. Optionally add a two-letter state code.
5. Set Maximum results.
6. Click Start.
7. Open Dataset to inspect or export the matches.

Example:

{
  "searches": [
    {
      "firstName": "John",
      "lastName": "Smith",
      "state": "CA"
    }
  ],
  "maxItems": 10
}

Input parameters

Parameter	Type	Required	Description
searches	array	Conditional	Objects with firstName, lastName, and optional two-letter state
startUrls	array	Conditional	Radaris URLs shaped like /p/First/Last/, optionally with ?ql=CA
maxItems	integer	No	Total unique matches to save, from 1 to 1,000; default 100

Provide at least one searches entry or startUrls URL. Combined input is limited to 100 searches/URLs per run.

The Actor always uses a US residential proxy. There is no lower-cost direct mode because direct requests were not reliable during implementation validation.

Output example

A current result has this shape (example values are anonymized):

{
  "queryFirstName": "Jordan",
  "queryLastName": "Taylor",
  "queryState": "CA",
  "personId": "1234567890",
  "fullName": "Jordan A Taylor",
  "age": 42,
  "birthYear": 1984,
  "currentLocation": "Sample City, CA",
  "aliases": ["Jordan Taylor"],
  "relatives": [
    {
      "name": "Sample Relative",
      "age": 65,
      "sourceUrl": "https://radaris.com/p/Sample/Relative/"
    }
  ],
  "previousLocations": ["Other City, TX"],
  "profileUrl": "https://sample.radaris.com/person/~Jordan-Taylor/1234567890",
  "searchUrl": "https://radaris.com/p/Jordan/Taylor/?ql=CA",
  "scrapedAt": "2026-01-15T12:00:00.000Z"
}

Fields can be null or arrays can be empty when Radaris does not display that signal.

How much does it cost to enrich people from Radaris?

Pricing uses one $0.005 start event per run plus one item event for each saved match. The Free-tier item price is $0.0015364 per match; paid Apify plans receive progressively lower tier prices.

At the Free-tier event price, a run with 10 matches charges one start event and 10 item events; a run with 100 matches charges one start event and 100 item events. Calculate the total as 0.005 USD + saved matches × active item-tier price.

No item event is charged for duplicate, rejected, failed, or state-filtered records. Apify displays your applicable tier before the run.

Batch enrichment workflow

For recurring real-estate research:

1. Export only names you may lawfully research.
2. Convert rows to searches objects.
3. Include a state when it is known.
4. Run on an Apify schedule.
5. Export the dataset to your review system.
6. Compare personId, aliases, and locations with your own source records.
7. Keep a human in the loop before outreach or identity conclusions.

This Actor produces candidate public-record matches, not proof that two people are the same person.

Export and integration options

The default dataset supports:

• JSON for applications and AI workflows.
• CSV or Excel for spreadsheet review.
• XML and RSS through Apify dataset endpoints.
• Webhooks after successful runs.
• Scheduled runs for repeatable list processing.
• Make, Zapier, Google Sheets, and other Apify integrations.

Run with the Apify API

Replace APIFY_TOKEN with your token.

cURL

curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~skip-trace-people-property-enrichment/runs?token=APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searches":[{"firstName":"John","lastName":"Smith","state":"CA"}],"maxItems":10}'

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/skip-trace-people-property-enrichment').call({
  searches: [{ firstName: 'John', lastName: 'Smith', state: 'CA' }],
  maxItems: 10,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient("APIFY_TOKEN")
run = client.actor("automation-lab/skip-trace-people-property-enrichment").call(
    run_input={
        "searches": [{"firstName": "John", "lastName": "Smith", "state": "CA"}],
        "maxItems": 10,
    }
)
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

Use with Apify MCP

Claude Code setup

Add the Actor to Claude Code:

claude mcp add --transport http apify \
  "https://mcp.apify.com?tools=automation-lab/skip-trace-people-property-enrichment"

Claude Desktop setup

Use this configuration in Claude Desktop:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/skip-trace-people-property-enrichment"
    }
  }
}

Cursor setup

Add the same MCP server URL in Cursor's MCP settings.

VS Code setup

Add the same MCP server URL to your VS Code MCP configuration.

Example prompts:

• “Search public Radaris records for these names, restricted to California, and return a review table.”
• “Run the Radaris URL extractor on this list and export name, age, aliases, relatives, and locations.”
• “Compare these prospect names with the returned public signals, but do not make eligibility decisions.”

Tips for better matches

• Add a state when you know it; common names can return many candidates.
• Start with a small maxItems while validating your input.
• Treat relatives and prior locations as possible associations, not verified relationships.
• Keep the source URLs for auditability.
• Schedule moderate batches instead of launching many overlapping runs.
• Deduplicate your own input list before running it.

Limits and failure behavior

• Only public name-search pages are supported.
• State filtering checks the location displayed on each result card.
• City-level filtering, reverse-phone lookup, reverse-address lookup, and property-owner lookup are not implemented.
• Radaris may show incomplete, stale, or inaccurate public-record associations.
• The source can change HTML or anti-bot rules without notice.
• A persistent challenge or upstream failure makes the run fail after three attempts.
• A valid search with no matching visible cards succeeds with zero items.
• The Actor does not open paid background reports or bypass source access controls.

Legality and responsible use

You are responsible for your input, purpose, retention, and downstream use. Follow Radaris terms, Apify terms, privacy and data-protection law, marketing rules, and all applicable opt-out or suppression obligations.

Do not use this Actor to stalk, harass, discriminate, impersonate, expose sensitive people, or decide eligibility for credit, employment, housing, insurance, or another regulated benefit. Respect consumer requests and verify important facts from authoritative sources.

Troubleshooting

Why did the run fail with a challenge message?

Radaris rejected all three bounded US residential sessions. Wait before retrying, reduce overlapping runs, and check the run log. The Actor intentionally fails instead of saving challenge HTML.

Why did a state-filtered search return fewer records?

Only cards whose displayed current location ends with the requested state code are saved. Remove state to inspect broader name matches.

Why are phone, email, or property fields missing?

They are not exposed by the supported public result page and are intentionally not claimed or emitted.

FAQ

Can I submit a Radaris URL?

Yes. Use an HTTPS URL shaped like https://radaris.com/p/First/Last/. Other hosts and detail-page formats are rejected.

Does one name produce one person?

Not necessarily. A name can produce many candidate matches. Use state and your own lawful source data for review.

Are relatives verified?

No. They are possible relationships displayed by Radaris.

Does the Actor store data outside Apify?

The implementation writes primary output to your run's default Apify dataset. Normal Apify platform retention and your account settings apply.

Can I use the data for tenant or employment screening?

No. This tool is not a consumer-reporting agency product and must not be used for regulated eligibility decisions.

Related Actors

This is a standalone compliance-sensitive enrichment product. Browse the automation-lab Store profile for other source-specific real-estate and lead-research Actors. Cross-link outputs only when the downstream workflow has a lawful purpose and preserves source attribution.