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

# Use Hunter in Deepline

> Use discover for free ICP shaping first, then domain/email finder for credit-efficient contact discovery, and verifier as the final send gate.

[Human guide: work with your agent →](https://deepline.com/docs/human/providers/hunter/guide.md)
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:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline auth status --json
deepline search "Hunter" --type tools --json
```

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:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline describe <returned-tool-id> --json
```

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](https://deepline.com/docs/sdk-v2/plays.md). For direct-call recovery, use [Tool execution recovery](https://deepline.com/docs/sdk-v2/tool-execution-recovery.md).

> [!TIP]
>
> Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.