Use Case
Skip tracing for debt collection agencies
Right-party contact data for collections — designed around FCRA, TCPA, and Regulation F so your compliance team can sleep.
Debt collection skip tracing isn't a price-shopping decision — it's a compliance decision. One $267M class action settlement against a collector for using bad-source skip-traced numbers should be enough to make every CFO read this page twice. The point of skip tracing in collections isn't just to find someone; it's to find them without exposing your agency to FDCPA, TCPA, or Regulation F liability.
Skip Trace API is built around that constraint. The trade group ACA International publishes the cleanest practitioner-level summaries of these rules if you need a reference for your compliance team.
Compliance posture
Our identity graph sources data through licensed channels with documented consent and FCRA-permissible-purpose tracking. We log every lookup with the requesting client, the timestamp, and the input fields, so you have an audit trail when a regulator asks. We do not source from data brokers with disputed legality (no scraped social media, no leaked databases).
The data we return is intended for permissible purposes under FCRA §604, including collection of an account. You're responsible for documenting your permissible purpose in your own systems; we make the audit trail easy.
What right-party contact looks like in 2026
The old definition of "right-party contact" was a phone number that connects you to the debtor. The new definition, post-Reg F, is more like: a contact channel where (a) you can verify you're talking to the right person, (b) you have a documented basis to believe consent applies, and (c) you're not over the call frequency caps. Skip Trace API helps with (a). The other two are on you and your dialer/compliance stack.
What the API returns for collections workflows
- Mobile and landline phones with line-type identification (so you can route to your TCPA-aware dialer correctly)
- Current and prior addresses for legal notice service
- Email addresses for written communication channels
- Confidence scores so high-confidence matches go to the live dialer first
- Audit-ready response payloads with timestamp and requestor ID
What we don't do
We don't do TCPA litigator scrubbing — that's a separate vendor (LitigatorScrub, BlackList Alliance, etc). We don't do DNC scrubbing — that's separate. We don't operate a dialer. Skip Trace API is the data layer; you bring your own scrubbing and dialing stack. This is intentional. Bundling makes things look easy until your scrubbing vendor needs to be swapped and you can't.
Honest assessment vs. enterprise providers
If you're a 200+ seat agency, you probably already have a contract with LexisNexis Accurint, TLO, or IRBsearch and you're paying $0.50–$2.00 per record on a flat monthly minimum. We're not pitching to displace those — we're built for the 1–50 seat agency that doesn't have $5K/month to commit and needs flexible per-lookup pricing. If you're at the high end and want to compare, the math usually only flips in our favor below ~10,000 monthly lookups.