Skip Trace & People Finder — Phone, Address, Relatives

Skip Trace & People Finder — Phone, Address, Relatives

US people search and skip-trace lookup from public records. Input a name (+ optional city/state), get back the matched person's phone numbers, current address, age, relatives, and known aliases — no external API key required.

Use Cases

• Skip tracing — locate debtors, defendants, or lost contacts for debt collection and process serving
• Real-estate wholesaling — find and contact property owners associated with an address
• Sales lead enrichment — append phone and address to a name list before outreach
• Due diligence — verify identity, address history, and associative links for fraud investigation
• Investigative research — confirm person's location, relatives, and aliases from public records

Input

Field	Type	Description
names	string[]	Full names to search. Append ; City, ST to narrow results. Example: "John Smith; Dallas, TX"
maxResultsPerName	integer	How many matched people to return per name (default: 5, max: 20)
fetchProfile	boolean	Open each profile for full phone + address (default: true)
proxyConfiguration	proxy	Apify Residential proxy (recommended, default on)
maxConcurrency	integer	Parallel fetches (default: 4)

Example Input

{
  "names": [
    "James Whitsitt; Dallas, TX",
    "John Smith; CA"
  ],
  "maxResultsPerName": 5,
  "fetchProfile": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

Output

Each matched person is one dataset item:

{
  "inputName": "James Whitsitt; Dallas, TX",
  "name": "James Whitsitt",
  "age": "38",
  "birthYear": "1987",
  "currentAddress": "4405 Windward Cir, Dallas, TX 75287",
  "previousAddresses": ["Dallas, TX"],
  "phones": ["(214) 458-0516", "(214) 349-3972"],
  "relatives": ["Mallary A Whitsitt", "Amalia G Castillo", "Beau Whitsitt"],
  "aliases": ["James Edwin Whitsitt"],
  "profileUrl": "https://radaris.com/~James-Whitsitt/1624974868",
  "parseConfidence": "full",
  "source": "radaris.com"
}

Notes

• No external API key required. Uses Apify's built-in residential proxy — the proxy cost is billed to your run, not to us.
• Data is sourced from US public records aggregated by Radaris.
• relatives, aliases, and age are returned for virtually every match. phones and currentAddress are returned when the source exposes them on that profile — public-record coverage varies person to person, so some records carry the identity/relationship fields without a phone or address. You are billed per returned record regardless of contact-field fill (see Pricing).
• For lawful use only. Not a consumer report. Do not use for FCRA-regulated decisions (credit, employment, housing, insurance). Verify data independently.
• Email is not available in this actor (not exposed in public records). For email enrichment combine with an email-finder actor.

💰 Pricing & how we compare

Pay-per-result (PPE): $6.90 per 1,000 records. You are billed per person-result actually returned — no subscription, no API key, no proxy fee on top, no separate start fee.

Our edge: every match ships relatives and aliases in the base output — the comparable $7/1K actor gates those to its $15/1K premium tier. Name search with optional city/state narrowing; clean flat one-record-per-person.

How rivals price the same job (live Apify Store, checked 2026-06-14)

Actor	Their price	How we compare
apivault_labs/skip-trace-people-finder	$0.007 / result (Basic)	same exact job — we undercut to $0.0069 and include relatives + aliases they gate to $0.015 Premium
one-api/skip-trace	$0.02 / result (Free tier)	the usage king — richer (emails, carrier, address history) but ~3× our price
crawlerbros/radaris-people-search	$0.002 / result	same Radaris source but no phone numbers, and thinner name coverage

Prices above are competitors' live Store prices at the time of writing; ours is set to sit just below the strongest comparable at our feature tier.

🤖 Use with AI agents (MCP)

This actor is agent-ready — callable from any MCP client (Claude Desktop, Cursor, n8n AI, LangGraph) via Apify's MCP endpoint:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?actors=bovi/skip-trace-people-finder",
      "headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }
    }
  }
}

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Trustpilot Reviews Scraper
• Upwork Talent Scraper
• Website Contact Extractor
• Yellowpages Scraper
• Yelp Scraper
• Zoominfo Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.