Skip Trace & People Search — Name & Reverse Phone Lookup
Pricing
from $0.30 / person found
Skip Trace & People Search — Name & Reverse Phone Lookup
Find people in the US by name, or find out who is behind a phone number. Get age, aliases, relatives with ages, address history and phone numbers — every match as its own clean record, never merging same-name strangers.
Pricing
from $0.30 / person found
Rating
0.0
(0)
Developer
Yuliia Kulakova
Maintained by CommunityActor stats
0
Bookmarked
209
Total users
37
Monthly active users
8.2 hours
Issues response
17 days ago
Last modified
Categories
Share
Skip Trace People Search

Find people in the US by name, or find out who is behind a phone number. Every match comes back as its own structured record — age, aliases, relatives, address history and phone numbers.
What it does
Search by name and get every matching person as a separate record: their age, the other names they go by, their relatives with ages, the cities they have lived in, and their phone numbers where those are publicly listed.
Search by phone number and get the number's possible owners — their other phone numbers, relatives, cities — plus the carrier, the line type and a spam-risk rating for the number itself.
Built for:
- Investigators & skip tracers — locate people who have moved or changed contact info
- HR & background checks — verify identity and address history
- Legal & collections — find address history and phone numbers for service of process
- Real estate — identify property owners and their contact information
- Sales & lead enrichment — append location and identity data to contact lists
Search modes
| Mode | Input | What you get |
|---|---|---|
| Name | First + last name, optionally narrowed by state and city | Each matching person as a separate record: age, aliases, relatives with ages, address history, phone numbers |
| Phone | Any US phone number | The number's possible owners with their other phone numbers, relatives and cities, plus carrier, line type and spam risk |
Batch mode runs many searches in a single run.
Output fields
| Field | Description |
|---|---|
fullName | Full name |
firstName / lastName | Split name fields |
age | Age in years |
aliases | Other names the person is known by (up to 10) |
currentAddress | Most recent known location |
previousAddresses | Address history (up to 10 locations) |
phoneNumbers | Phone numbers linked to the person (up to 15) |
relatives | Relatives and associates, with their ages where published (up to 20) |
phoneLookup | Phone search only — carrier, lineType (landline/mobile/VoIP) and spamRisk |
nameIsMasked | Phone search only — true when the source published the owner's surname masked |
profileUrls | Link to the person's public profile, when one exists |
dataSources | Which sources contributed to this record |
searchQuery | The input query that produced this result |
scrapedAt | When the data was scraped |
Good to know
- Phone numbers appear on a portion of name-search records — public listings publish them for some people and not others. Every record still carries name, age, aliases, relatives and address history.
- Phone search returns the owner's surname masked (
Alexander A**), because that is how the source publishes it. Records are flagged withnameIsMasked, and no surname is ever guessed. Relatives are returned in full and can be used for a follow-up name search. - Email addresses are not included.
Input options
| Field | Description | Default |
|---|---|---|
searchType | name or phone | name |
firstName | First name (for name search) | — |
lastName | Last name (for name search) | — |
state | US state abbreviation to narrow results | — |
city | City to narrow results | — |
phone | Phone number, any format (for phone search) | — |
queries | Array of queries for batch mode | — |
maxResults | Max person records per query (1–20) | 5 |
fetchPhoneNumbers | Look up phone numbers on public profiles (slower) | true |
sources | Which sources to query | radaris, spokeo |
Batch mode
Search for multiple people in one run by passing a queries array:
{"searchType": "name","maxResults": 3,"queries": [{ "firstName": "John", "lastName": "Smith", "state": "CA" },{ "firstName": "Jane", "lastName": "Doe", "state": "NY", "city": "New York" }]}
Example output
Name search — each matching person is returned as their own record. Values below are illustrative:
{"fullName": "John J Smith","firstName": "John","lastName": "Smith","age": 39,"aliases": ["John A Smith", "John K Smith"],"currentAddress": { "street": null, "city": "Kenmore", "state": "NY", "zip": null },"previousAddresses": [{ "street": null, "city": "Buffalo", "state": "NY", "zip": null },{ "street": null, "city": "Amherst", "state": "NY", "zip": null }],"phoneNumbers": [{ "number": "(716) 555-0142", "type": "unknown" },{ "number": "(716) 555-0177", "type": "unknown" }],"relatives": [{ "name": "Deloris Smith", "age": 64 },{ "name": "Jeremy Smith", "age": 33 }],"profileUrls": { "radaris": "https://newyorkmaps.radaris.com/person/John-Smith/1655930340" },"dataSources": ["radaris"],"scrapedAt": "2026-08-21T02:05:12.031Z"}
Pricing
$0.30 per person found.
You are charged per person record written to the dataset, so a search with maxResults: 5 that finds five different people costs $1.50. Lower maxResults if you only need the top matches. If a search returns no records, there is no per-result charge. A small Actor start fee applies per run.
Proxy requirement
This scraper requires US residential proxies — the source sites are geofenced to US IP addresses and block datacenter traffic. Configure Apify Proxy with Residential + US country in the proxy settings before running.
Integrations
Export results as JSON, CSV, or Excel. Connect to your workflow via:
- Apify API
- Webhooks
- Make (Integromat), n8n, Zapier
FAQ
Does it work for any US person? It searches publicly available records. Results depend on what is indexed — long-term US residents typically return the richest data.
Can I search for multiple people at once?
Yes — use the queries array in batch mode to search for many people in a single run.
Will two people with the same name be merged into one record? No. Records are merged only when something person-specific matches — a shared phone number, email, street address, or a close age within the same state. A shared name alone is never treated as the same person.
Why do some records have phone numbers and others don't? Public listings publish phone numbers for some people and not others. Records without them still include name, age, aliases, relatives and address history.
What happens if a search finds nobody? The run finishes with an empty dataset and no per-result charge. If a source is unreachable, the run fails with the reason instead of quietly returning nothing.
Is the data real-time? Data is fetched live from the source sites on every run. The underlying databases are updated regularly but may not reflect very recent changes.