Documentation Index
Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Playbook
IPQS — Agent Routing
Phone validation: use Trestle instead
For phone validation, usetrestle_phone_validation first, not IPQS.
Trestle returns activity_score (0–100) which tells you whether a line is active or disconnected — IPQS phone validation does not. Activity score is the most useful signal for filtering stale numbers before cold outreach.
| Scenario | Use |
|---|---|
| Validate a phone after enrichment | trestle_phone_validation |
| Verify phone belongs to a specific person (name match) | trestle_real_contact |
| IPQS phone validate | Last resort only — no activity score |
Email validation: use LeadMagic instead
Do not useipqs_email_verify or ipqs_batch_email_verify for outbound email validation.
IPQS email validation returns a boolean valid field with no catch_all distinction. The Deepline waterfall stack depends on catch_all status to decide whether to fall through to the next provider. Use leadmagic_email_validation instead — it returns structured email_status (valid / catch_all / invalid) at $0.006/call.
Priority for email validation: leadmagic_email_validation → zerobounce_validate → IPQS (last resort).
What IPQS is good for
- Fraud scoring:
fraud_scoreon email or phone - Disposable/honeypot detection:
disposable,honeypotfields - Spam trap detection on email
- DNC status on phone (use
trestle_phone_validationfor line type + activity though)