Resolve US street addresses to connected people — current and former residents, ages, locations and relatives. Single or bulk address input, one record per matched person. Lawful B2B use only; not for FCRA-covered credit, employment or tenant decisions.
All notable changes to Property Skip Tracing will be documented in this file.
[2026-08-24]
📄 A real run report, every time
New run report. Every run now writes a report.html you can open from the run's Key-value store: the headline numbers first, an agent-ready copy panel, links to your dataset as JSON or CSV, and an itemized statement of exactly what you were charged.
Gaps are explained, not just counted. Addresses that came back without a match are listed with the reason and a concrete next step, plus a copy-and-paste input to retry only those records.
The report survives a crash. It is written at the end of every run, including runs that stop early.
Clearer run log. The log now confirms your tier and its limits, and explains when a free run stops at its cap rather than ending silently.
[2026-08-15]
🐛 Fixed
Bulk runs no longer look up the example address — when Bulk Addresses or Addresses From URL are supplied, the single-address fields (street / citystatezip) are now ignored instead of being added to the queue. Previously the built-in example address was looked up and charged alongside your own addresses on API and MCP runs, even though it was never submitted. Affected runs are being credited.
[2026-07-30]
✨ New
📞 Person-Details Enrichment (PAID) — new includePersonDetails toggle turns every matched contact into an actionable lead: all reported phone numbers (type, carrier, last-reported date), email addresses, current + previous address history with counties and time spans, relatives, and associates. Each successfully enriched contact consumes 1 additional SkipTraceCompleted charge; contacts with no extra data are never charged.
The Overview table now surfaces primaryPhone and emails for instant lead export.
[2026-07-03]
🛠 Improvements
Try-it-now defaults — street and citystatezip now ship with a working example address (prefill + default), so Store test runs and bare API calls return real results out of the box (single lookup, minimal cost)
[2026-05-05]
🎉 Property Skip Tracing — Launch!
Address → People resolver — Submit a US street address, receive the people connected to it: current/former residents, ages, current city, prior locations, and reported relatives
Three input modes — Single address (street + citystatezip), bulk array (bulkAddresses[], PAID), or CSV/TXT file URL (addressesFromUrl, PAID)
One row per person — Output is flat: each dataset record is one contact, denormalized with the input address for instant CSV / Sheet workflows
Built-in deduplication — Same personId returning across pages is collapsed automatically
HTML run report — Match rate, per-address breakdown, and the lawful-use reminder
No-charge-on-empty billing — SkipTraceCompleted event fires only when at least one match comes back for an address; empty lookups are not charged
💰 Transparent Pricing
$0.01 run start — once per run, whatever the run does
$0.75 per matched address — billed only when at least one person comes back
$0 for empty lookups — comparable per-lookup contact APIs charge $0.30–$1.00 whether or not they find anyone
⚖️ Compliance
FCRA hard boundary documented in INPUT_SCHEMA, README, and HTML report
Trademark & source disclaimers in actor description and README
Replace per-address title searches with one lookup
Wholesalers — turn property lists into named leads in minutes
B2B due diligence — verify business addresses without leaving the dataset
Investors — owner-occupied vs. absentee at a glance
🎯 Use Cases
Real estate wholesaler lead generation from distressed-property lists
Owner-occupied vs. absentee verification for direct-mail underwriting
B2B vendor due diligence and shell-company detection
Title / probate research support
Asset recovery and fraud-prevention background checks
📄 Pagination
v1.0 returns the top-relevance page of contacts per address (typically up to ~9 records). Results are ranked by relevance, so page-1 contacts are the strongest matches for the property; subsequent pages contain weaker associations (e.g. distant historical occupants). This keeps per-address pricing stable.
