The same API powers very different jobs. Whether you're scrubbing TCPA litigators before an
SMS campaign, validating identity at signup, cleaning a CRM list, or scoring sales leads, the
best mix of fields and add-ons depends on the use case. Pick yours below to see the recipe.
SMS marketers, lead-gen, outbound dialers
TCPA litigator scrub for SMS and outbound campaigns
Professional TCPA plaintiffs file thousands of suits a year. One name in your list can cost more than your year of marketing.
Enable litigatorFilter on every lookup to get the litigator flag, type, and on-record name to route them out before you send.
Read the use case → Fintech, crypto, payments, gaming
KYC phone verification for fintech and crypto onboarding
Fraudsters use VoIP and recently-ported numbers to bypass identity checks.
Combine nanpType, dipCarrierType, dipPorted, dipCarrierSubType, and ipResult to score a number's legitimacy at signup.
Read the use case → CRM ops, B2B sales, marketing ops
Contact list hygiene for CRM and B2B sales
Lists drift. Numbers get deactivated, reassigned, and re-ported. Email-style validation can't see any of this.
Use deliverable, reason, deactivationDate, and dipCarrier to rebuild a clean, current list on a schedule.
Read the use case → SDR teams, lead-gen agencies
Sales lead validation and routing
Bad leads waste prospecting time. Mobile vs landline changes the cadence: call or text first?
Use nanpType, dipCarrier, deliverable, and timezone signals to score leads and assign the right channel.
Read the use case → Affiliates, ping-post networks, lead buyers
Phone validation for affiliate marketers and lead-gen marketplaces
Both sides of the lead-gen trade get burned by bad numbers: sellers lose acceptance, buyers pay for trash, and one litigator on the list triggers a TCPA claim.
Validate at form-submit, attach metadata to the ping, let buyers re-validate on the post, with a litigator filter on every lookup.
Read the use case →