Skip to main content
Human guide: work with your agent → Inspect one FullEnrich action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

​
Key patterns

  • Async submit + async fetch. fullenrich_bulk_enrich and fullenrich_reverse_email start background jobs and return an enrichment_id. A Play waits synchronously for terminal data, prints the status command before polling, and reports progress about every 15 seconds. Status checks run every 15 seconds. If a run is canceled or reaches its wait limit, the provider job can continue and may still incur Deepline credits. Use the logged status command with fullenrich_get_result or fullenrich_get_reverse_result to check it.
  • Submit at most 50 contacts or emails per batch. Split larger inputs into multiple calls.
  • Use enrich_fields to control what’s enriched: contact.emails is the cheapest, contact.personal_emails costs more, and contact.phones is by far the most expensive.
  • LinkedIn URL improves accuracy significantly (5-20% for emails, 10-60% for phones).
  • Email status hierarchy: DELIVERABLE > HIGH_PROBABILITY > CATCH_ALL > INVALID. Use most_probable_work_email field for the best result.
  • Phone costs 10x email — use judiciously and only when explicitly needed.
  • Search is synchronous — use fullenrich_people_search or fullenrich_company_search for prospecting.
  • Status and result reads are free Deepline actions. The accepted batch’s Deepline charge settles once from its final usage. do not resubmit a batch that is already running.
  • forceResults=true on a direct get-result call returns partial results if enrichment is still running.

​
When to use

  • Best for high-quality email/phone waterfall enrichment with extensive provider coverage (20+ sources).
  • Search API is good for prospecting by job title, company, location, industry.
  • Reverse email lookup useful for identifying contacts from email addresses.

​
When NOT to use

  • Don’t use for email validation only — use a dedicated validator (ZeroBounce, LeadMagic validation).
  • Don’t use phone enrichment unless explicitly needed — it is the most expensive field.
  • For quick single-provider email lookups, LeadMagic or Prospeo are faster/cheaper.

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

​
Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow Write Plays. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.