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
Use LeadMagic as a contact-resolution, verification, and intent layer.- Start with cheaper gates:
leadmagic_email_validation,leadmagic_company_search, andleadmagic_jobs_finder. - Escalate to premium contact discovery only after the target is worth it:
leadmagic_email_finder,leadmagic_mobile_finder,leadmagic_profile_search,leadmagic_b2b_social_email, andleadmagic_email_to_profile. - For role-based discovery, use
leadmagic_role_finderfor a single decision-maker andleadmagic_employee_finderwhen you need a wider company roster. leadmagic_email_validationis the final outbound validity gate for this layer. Default acceptance rule isemail_status == valid; treatcatch_allandunknownas unresolved unless the user explicitly accepts risk.- LeadMagic is conservative on catch-all domains (many Google Workspace and corporate domains).
email_status: "invalid"with a populatedmx_record+mx_providerusually means “mailbox not provable,” not “does not deliver.” Don’t auto-discard these rows — fall back todeepline_nativevalidation or a second provider (zerobounce,bettercontact) before giving up on the lead. - If LeadMagic profile or phone quality is noisy on pilot rows, switch to quality-first enrichment (
crustdata_person_enrichment,peopledatalabs_enrich_contact) before scaling.
- Run 1-row pilots for identity + email candidates.
- Validate with
leadmagic_email_validationon every candidate. - Keep fallback chains explicit in your
--with-waterfallorder. - Promote only after pilot success and clear assumptions are set.