Property Skip Tracing — Address → People for Real-Estate Leads 🔎

🎯 Resolve a US Street Address to Connected People in Seconds

Wholesalers, real-estate investors, title researchers, and B2B due-diligence teams — turn addresses into leads with names, ages, locations, and reported relatives

---

🔍 What is Property Skip Tracing — and when should you use it?

Property Skip Tracing takes a US street address and gives you back the people the public record connects to it: current and former residents, their ages, where they live now, where they lived before, and their reported relatives. Rows are flat and ready for a spreadsheet, a CRM import or an AI agent. No portal login, no county-by-county lookup, no browser automation to keep alive.

Use it when you need: names, ages, current city, prior cities, reported relatives, and (with enrichment on) phone numbers, emails and full address history for the people tied to an address.

Use something else when: you want the property rather than the people — price history, beds, baths, taxes, Zestimate. Use Zillow Property Scraper for that, then bring the address back here for the owner.

---

🤖 Use with AI agents

Already connected to the Apify MCP server? Just ask for this Actor by name: sian.agency/property-skip-tracing

Your agent can pay for its own runs. This Actor is eligible for agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — without an Apify account or API token of its own. Billing is the same either way: per matched address, never for empty lookups.

Otherwise copy this prompt into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to turn a list of US property addresses into named contacts using the Apify Actor `sian.agency/property-skip-tracing`.

Use it when I need: the people tied to an address — names, ages, current and prior cities, reported relatives, and optionally phones, emails and address history.

Don't use it when: I want the property's own price, beds, taxes or Zestimate — use `zillow-property-scraper` instead.

How to call it: one address at a time with `street` + `citystatezip`; a list with `bulkAddresses`; or a hosted CSV with `addressesFromUrl` (both need a paid Apify plan). Add `includePersonDetails: true` to get phones and emails per contact.

Start with this input:
{
  "street": "3828 Double Oak Ln",
  "citystatezip": "Irving, TX 75061",
  "includePersonDetails": false
}

Ask me for the address (or the CSV link) and whether I want phone and email enrichment, then run the Actor and summarise the contacts as a table.

Things you can ask your agent for:

• "Take these 40 foreclosure addresses and give me one call sheet with the current resident, their age and their relatives."
• "Check whether the owner named on this deed still shows up as a resident at the property."
• "Run our new vendor's registered business address and tell me who else is tied to it."

Machine-readable API, MCP config and OpenAPI definition for this Actor are published at apify.com/sian.agency/property-skip-tracing.md.

---

📋 Overview

Submit a US street address; get back the people connected to it — current and former residents, with ages, current city, prior locations, and reported relatives. Designed for wholesalers building lead lists from a property list, investors verifying owner-occupied vs. absentee status, and B2B teams running address-based due diligence.

What you get:

• 🚫 No charge on empty results — you pay only when matches are returned, not for blank lookups
• 📦 Three input modes built-in — single address, bulk array, or CSV/TXT file URL — no custom plumbing
• 👥 One row per person — output is flat (one record = one contact), denormalized with the input address for instant CSV / Sheet workflows
• 🆓 FREE tier — 3 addresses per run, no credit card, full feature parity
• ⚖️ Compliance-first — clear FCRA boundary documented in input UI, README, and HTML report

---

✨ Features

• 🏠 Address-first design — pass street + citystatezip (e.g. "Irving, TX 75061"); get back everyone the source associates with that address
• 📦 Single / bulk / file input — single address on FREE; arrays or CSV/TXT URL on PAID
• 👥 Per-person fields — name, age, livesIn, usedToLiveIn, relatedTo, profileUrl, plus stable personId
• 📞 Person-details enrichment (PAID) — set includePersonDetails: true to add phone numbers (type, carrier, last-reported date), email addresses, full current + previous address history, relatives, and associates to every matched contact
• 🔁 Built-in deduplication — same person returning across pages is removed automatically
• 📄 HTML run report — match rate, per-address breakdown, and the lawful-use reminder
• 💰 Match-only billing — SkipTraceCompleted charge fires only when at least one match comes back for that address
• 📱 Standard Apify exports — JSON, CSV, XLSX, RSS, HTML

---

🎬 Quick Start

curl -X POST 'https://api.apify.com/v2/acts/sian.agency~property-skip-tracing/runs?token=[YOUR_TOKEN]' \
  -H 'Content-Type: application/json' \
  -d '{"street":"3828 Double Oak Ln","citystatezip":"Irving, TX 75061"}'

---

🚀 Getting Started (3 Simple Steps)

Step 1: Pick Your Input Mode

• Single — fill street + citystatezip
• Bulk (PAID) — pass bulkAddresses: [{street, citystatezip}, ...]
• From file (PAID) — pass addressesFromUrl to a CSV/TXT URL with two columns

Step 2: Run

Hit Run. Each address is one lookup, and every person it returns becomes one row in your dataset.

Step 3: Export

Download as JSON / CSV / Excel. Open the HTML report in the key-value store for the run summary.

---

📥 Input Configuration

Field	Type	Required	Description
street	string	Single mode	US street address line (e.g. 3828 Double Oak Ln)
citystatezip	string	Single mode	City, ST ZIP (e.g. Irving, TX 75061)
bulkAddresses	array	No	Array of {street, citystatezip} objects (PAID)
addressesFromUrl	string	No	Public CSV/TXT URL with two columns (PAID)
includePersonDetails	boolean	No	Enrich each matched contact with phones, emails, address history, relatives, and associates (PAID). Each successfully enriched contact adds 1 SkipTraceCompleted charge; no charge when nothing extra is found

Example — Single address:

{
  "street": "3828 Double Oak Ln",
  "citystatezip": "Irving, TX 75061"
}

Example — Bulk addresses (PAID):

{
  "bulkAddresses": [
    { "street": "3828 Double Oak Ln", "citystatezip": "Irving, TX 75061" },
    { "street": "187 Kent Ave",       "citystatezip": "Brooklyn, NY 11249" }
  ]
}

Example — CSV file URL (PAID):

{
  "addressesFromUrl": "https://example.com/leads.csv"
}

CSV format (comma-separated, header optional):

street,citystatezip
3828 Double Oak Ln,"Irving, TX 75061"
187 Kent Ave,"Brooklyn, NY 11249"

---

📤 Output

Each dataset record represents one person connected to the input address:

Field	Type	Description
inputStreet	string	Street address submitted
inputCityStateZip	string	City/state/ZIP submitted
name	string	Full name
personId	string	Stable identifier from the underlying people-search index
age	integer	Reported age
livesIn	string	Most recent city/state of residence
usedToLiveIn	string	Past addresses / cities (comma-separated)
relatedTo	string	Reported relatives or close associates
profileUrl	string	Public profile URL on the source
page	integer	Page index this record came from
scrapedAt	string	ISO timestamp

Example record:

{
  "inputStreet": "3828 Double Oak Ln",
  "inputCityStateZip": "Irving, TX 75061",
  "name": "Hortencia Puente",
  "personId": "px860662uu9n6u8r04888",
  "age": 53,
  "livesIn": "Irving, TX",
  "usedToLiveIn": "Dallas TX",
  "relatedTo": "Juan Puente, Alberto Rodriguez, Juan Puent...",
  "profileUrl": "https://www.truepeoplesearch.com/find/person/px860662uu9n6u8r04888",
  "page": 1,
  "scrapedAt": "2026-05-05T22:14:00.000Z"
}

---

💼 Use Cases & Examples

1. Wholesaler Lead List

Wholesalers turning a target-property list into named leads Input: CSV of 200 distressed-property addresses Output: Names + ages + relatives per address, ready for cold outreach Use: Skip the title-search step; build call/text lists in minutes.

2. Owner-Occupied vs. Absentee Verification

Real-estate investors confirming owner residency Input: A property's street + citystatezip Output: Current residents — does the deed-name appear? Use: Identify likely-absentee owners for direct-mail campaigns.

3. B2B Vendor Due Diligence

Procurement / fraud-prevention checking a registered business address Input: Vendor's listed business address Output: People associated with the address; cross-check with company filings Use: Spot shell-company patterns before signing.

4. Title / Probate Research Assist

Title researchers preparing comp packets Input: Subject property address Output: Current and former occupants for genealogy / probate context Use: Reduce hours of manual public-records lookup.

5. Asset Recovery & Judgment Enforcement

Recovery agents locating a debtor's last known address Input: The address on the original agreement Output: Everyone the record ties to it, plus where they moved to Use: Follow the trail forward without buying a full investigator subscription.

---

🔗 Integration Examples

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });

const run = await client.actor('sian.agency/property-skip-tracing').call({
  bulkAddresses: [
    { street: '3828 Double Oak Ln', citystatezip: 'Irving, TX 75061' }
  ]
});

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

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')

run = client.actor('sian.agency/property-skip-tracing').call(
    run_input={
        'street': '3828 Double Oak Ln',
        'citystatezip': 'Irving, TX 75061'
    }
)
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

cURL

curl -X POST 'https://api.apify.com/v2/acts/sian.agency~property-skip-tracing/runs?token=YOUR_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"street":"3828 Double Oak Ln","citystatezip":"Irving, TX 75061"}'

Automation Workflows (N8N / Zapier / Make)

1. Trigger — new property address added to your CRM / pipeline
2. HTTP Request — call this actor with the address
3. Process — pick top contact, enrich with phone/email via your downstream tool
4. Action — push to dialer / SMS / mail-merge

---

📊 Performance & Pricing

FREE Tier

• 3 addresses per run, no credit card
• Single-address mode only
• Same data quality as PAID
• Perfect for testing the data fit before scaling

PAID Tier

• Unlimited addresses per run
• Bulk array + CSV/TXT URL input modes
• Pay-per-result: only charged on confirmed matches

💰 Transparent per-result pricing — pay $0.01 per run start and $0.75 only when a match is found. Empty lookups (no people returned for the address) are NOT charged. Compared to per-API-key wholesaler tools at $0.30–$1.00 per lookup with no empty-result protection, you only pay for matches.

🔗 View current pricing

---

❓ Frequently Asked Questions

Q: Where does the data come from? A: The Actor wraps a public records aggregator that indexes openly-available people-search content. Profile URLs in each record link to the underlying source.

Q: What if no people are returned for an address? A: You're not charged the SkipTraceCompleted event for empty matches. The run-start charge ($0.01) still applies once per run.

Q: Why are some addresses returning unrelated people? A: Public people-search indexes return everyone historically associated with the address — current owner, previous tenants, family of past tenants. Use livesIn / usedToLiveIn to filter.

Q: Are international addresses supported? A: No — US addresses only at this time.

Q: Can I use this output to deny someone housing or a job? A: No. This Actor is not a consumer reporting agency and is not FCRA-regulated. Outputs MUST NOT be used as a factor in eligibility for credit, employment, insurance, housing, or tenant-screening decisions. See the legal section below.

Q: What output formats are available? A: JSON, CSV, Excel — exported directly from the Apify dataset.

---

🐛 Troubleshooting

"citystatezip must match "City, ST ZIP""

• Use the exact format: Irving, TX 75061. Comma after the city, 2-letter state code, then ZIP.

Bulk input rejected on FREE tier

• Bulk and file input require a PAID Apify account. Use single-address mode to test.

Returns 0 people on a known-occupied address

• Public records lag for new construction and recent moves. Try a variant spelling (Ln vs Lane), or wait a billing cycle for the index to refresh.

FREE tier hit at 3 addresses

• That's the FREE cap. Upgrade to a paying Apify plan for unlimited.

---

⚠️ Trademark & Source Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Zillow Group, Inc., TruePeopleSearch, or any consumer reporting agency. Brand and source names are used solely in a descriptive sense to identify the public data the Actor reads from. All trademarks, service marks, and trade names referenced in this Actor or its documentation are the property of their respective owners.

---

⚖️ Compliance & Legal

Lawful B2B use only. This Actor returns information about individuals derived from public records. Outputs are intended for legitimate business uses such as real-estate investing, due diligence, fraud prevention, and asset recovery.

FCRA — Hard Boundary

This Actor is NOT a consumer reporting agency under the U.S. Fair Credit Reporting Act, and the data it returns is NOT a "consumer report" within the meaning of the FCRA. You MAY NOT use any output of this Actor — directly or indirectly, in whole or in part — as a factor in establishing a person's eligibility for any of the following:

• Credit or insurance for personal, family, or household purposes
• Employment, promotion, reassignment, or retention
• Housing or tenant screening
• Any other purpose covered by Section 604 of the FCRA, 15 U.S.C. § 1681b

Other Compliance

You are responsible for compliance with all state and local laws governing PII, including but not limited to:

• CCPA / CPRA (California)
• VCDPA (Virginia)
• CPA (Colorado)
• GDPR (when processing data of EU/UK residents)
• DPPA, GLBA, and any sector-specific regulations applicable to your use case

If you are unsure whether your intended use is permitted, consult qualified legal counsel.

Data Source

Data originates from publicly accessible people-search content. Profile URLs in each record link back to the underlying source. We make no representations or warranties about the accuracy, completeness, or currentness of any record returned.

You can also read Apify's blog post on the legality of web scraping.

---

🤝 Support

Join our active support community

• For issues or questions, open an issue in the actor's repository
• Check SIÁN Agency Store for more automation tools
• 📧 apify@sian-agency.online

---

Built by SIÁN Agency | More Tools