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

​
Provider-specific requirements

  • Start with hunter_discover and hunter_email_count to shape ICP and estimate reachable volume at zero credit cost.
  • Prefer hunter_domain_search when you need multiple contacts from one account. add department/seniority filters to keep recall high but usable.
  • Use hunter_email_finder for one named person after domain-level search is exhausted or too broad.
  • Always run hunter_email_verifier immediately before outbound send decisions. treat invalid, accept_all, webmail, and disposable as non-send states by default.
  • Use hunter_people_find and hunter_companies_find for enrichment context, not as your first discovery step.
  • Use hunter_combined_find only when person + company enrichment are both needed in one call and you already have a strong identity seed (email/LinkedIn/domain).

​
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.