Skip Trace Property Owner — Phone, Email & Address Finder

This Apify Actor helps users work from one or more US property addresses and return one record per address with property owner contact data from public records. The accepted input is an array of addresses, and each record represents the result of a single property lookup. Useful fields include owner full name, owner mailing address, phone numbers, email addresses, owner since, relatives, lookup status, source URL, and scraped timestamp. The outcome is a structured dataset that can be reviewed, exported, or read by AI agents through Apify MCP or the Apify API.

Best fit and connected workflows

This Actor fits workflows that start with a property address list and end with owner-contact enrichment in a dataset. It is a natural match for:

• address-based lead generation and list enrichment
• property-owner research from driving-for-dollars lists
• absentee-owner review using the returned owner mailing address
• CRM or spreadsheet cleanup using lookup_status and contact fields
• AI-agent workflows that turn natural-language address requests into structured lookups through Apify MCP

If your workflow starts from a property address, this Actor keeps the process focused on address-to-owner lookup and returns one record per input address.

Focused standalone workflow

This Actor is designed as a focused standalone workflow.

Practical scenario

A real estate assistant has a list of 40 street addresses from a tax-delinquent mailing campaign. They send the addresses into the Actor with phone and email enabled. For each property, the dataset returns the property address, owner full name, phone numbers, email addresses, owner mailing address, and lookup_status. The assistant uses lookup_status to separate found records from partial records, then sends the contact-rich rows to a dialer queue and the mailing-only rows to a direct-mail list.

Input

Field	Type	Description
addresses	array of string	Property addresses to skip trace. Accepts 1 to 500 full US address strings per run.
includePhone	boolean	Includes phone number lookup. Default: true.
includeEmail	boolean	Includes email lookup. Default: true.
maxResults	integer	Caps the number of property records to process and return. Minimum 0, maximum 500. Default: 100.
proxyConfiguration	object	Proxy settings for the Actor.
debugMode	boolean	Saves the first successfully fetched raw HTML to Key Value Store for inspection. Default: false.

Focused input example

{
  "addresses": [
    "123 Main St, Dallas, TX 75201",
    "456 Oak Ave, Austin, TX 78701"
  ],
  "includePhone": true,
  "includeEmail": true,
  "maxResults": 2
}

Output

The dataset contains one item per property address processed. The lookup_status field indicates result quality: found, partial, or not_found.

Field	Type	Description
property_address	string	The input property address that was skip traced.
owner_full_name	string or null	Current owner name or most recent occupant found via public records.
owner_mailing_address	string or null	Mailing address associated with the owner.
phone_numbers	array of string	Phone numbers associated with the owner.
email_addresses	array of string	Email addresses associated with the owner.
owner_since	string or null	Approximate year the owner has been associated with the address.
relatives	array of string	Possible relatives or co-residents from people-search records.
lookup_status	string	Result quality: found, partial, or not_found.
source_url	string	Public records page used to extract the record.
scraped_at	string	ISO 8601 timestamp of extraction.

Illustrative output record

{
  "property_address": "123 Main St, Dallas, TX 75201",
  "owner_full_name": "John D. Smith",
  "owner_mailing_address": "456 Pine Ave, Dallas, TX 75202",
  "phone_numbers": ["(214) 555-0123"],
  "email_addresses": ["jsmith@gmail.com"],
  "owner_since": "2018",
  "relatives": ["Jane Smith"],
  "lookup_status": "found",
  "source_url": "https://www.fastpeoplesearch.com/address/123-main-st_dallas-tx",
  "scraped_at": "2026-03-28T14:30:00.000Z"
}

How it works

The Actor accepts property addresses, processes each address, and writes a dataset record for every lookup. Phone and email lookups are controlled by input flags. The maxResults field limits the number of records processed. The dataset schema also includes views for an overview table and a contact sheet view, making it easier to review owner names, phones, emails, mailing addresses, and status fields in Apify.

Pricing

This Actor uses Pay per event pricing.

• Primary priced event: Property Owner Found
• Price per priced event: $0.12
• Apify platform usage is billed separately according to the Apify platform pricing shown in the live Pricing tab
• Actor start is also charged as defined in the live contract
• For a concrete usage example, 25 found results would produce 25 priced events

For current pricing details, open the live Pricing tab on the Actor page.

Use with AI agents (MCP)

This Actor is usable through Apify MCP as an Apify Actor that accepts property addresses and returns structured owner-contact records.

Exact Actor identity: khadinakbar/skip-trace-property-owner

Tool description: submit property addresses, optionally include phone and email enrichment, and read the resulting dataset rows for each processed address.

"Use khadinakbar/skip-trace-property-owner to skip trace these property addresses. Return the owner name, phones, emails, mailing address, and lookup status for each address, then summarize which rows were found, partial, or not found."

Output interpretation:

• found means owner name plus at least one contact field was returned
• partial means owner name was found and contact fields were not populated
• not_found means the lookup returned no owner data for that address

Provenance and scope:

• records include source_url and scraped_at
• the output is one dataset item per address processed
• the workflow is address-based and outputs public-record contact data for US properties

Pagination and cost guidance:

• use maxResults to cap processed rows on larger address lists
• each saved result row is charged as a result-found event
• actor start is charged separately as defined in the live contract

Apify API example

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
});

const run = await client.actor('khadinakbar/skip-trace-property-owner').call({
  addresses: [
    '123 Main St, Dallas, TX 75201',
    '456 Oak Ave, Austin, TX 78701'
  ],
  includePhone: true,
  includeEmail: true,
  maxResults: 2
});

const datasetItems = await client.dataset(run.defaultDatasetId).listItems();

console.log(datasetItems.items);

Best results and outcome guidance

Use complete US address strings in the addresses array so each record maps cleanly back to the original property. Enable includePhone when phone outreach is part of the workflow, and enable includeEmail when email enrichment is useful. Use maxResults to keep large runs aligned with your current list size. Review lookup_status first when splitting records into follow-up paths such as call, mail, or review.

Design note

I found that the output contract requires phone_numbers, email_addresses, relatives, source_url, and scraped_at on every dataset row, even when the corresponding values are empty arrays or blank-like lookups. That makes the dataset shape consistent for downstream automation.

FAQ

Can I start from property addresses instead of owner names?

Yes. This Actor is built around the addresses input field and processes one or more US property addresses per run.

What does lookup_status tell me?

It identifies whether the row is found, partial, or not_found, which makes it easy to route rows into calling, mailing, or review steps.

Does this Actor return mailing addresses too?

Yes. owner_mailing_address is part of the dataset output and can be used to identify owner mailing locations when they differ from the property address.

Can AI agents use this Actor directly?

Yes. The Actor is MCP-ready and can be called through Apify MCP using the exact Actor identity khadinakbar/skip-trace-property-owner.

Can I limit the run size?

Yes. Use maxResults to cap how many property records are processed in a run.

Responsible use

Use the returned contact and mailing data in ways that fit your applicable laws, consent practices, and outreach rules. Review the public-record provenance in source_url, respect contact preferences, and use the dataset fields carefully when automating outreach or CRM enrichment.