> ## 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 WizLeads in Deepline

> Use direct email/company endpoints for synchronous enrichment and email verification. Includes inputs, outputs, SDK V2 examples, and Deepline cost.

[Human guide: work with your agent →](https://deepline.com/docs/human/providers/wizleads/guide.md)
Inspect one WizLeads action before starting provider-backed work. Your first result is a verified input and output contract.

## Provider-specific requirements

WizLeads is opt-in and fallback-only. Do not add it to a workflow unless the
user explicitly requests WizLeads or a preceding provider-specific step already
created a WizLeads task.

Preferred alternatives:

* Work-email recovery: use the name + domain work-email play.
* Email verification: use `leadmagic_email_validation`, then
  `zerobounce_validate`.
* LinkedIn company URL lookup: use a company identity resolver. Use
  `wizleads_get_company_linkedin_id` only when a downstream API needs the
  numeric LinkedIn company ID.
* Ordinary people or company discovery: use the dedicated discovery tools.

Use `wizleads_find_email`, `wizleads_verify_email`, and
`wizleads_get_company_linkedin_id` only within those endpoint-specific
boundaries.

WizLeads allows 10 requests per second across the provider account. Treat that as queue guidance when planning multi-step runs.

Use the public Deepline pricing summary returned by tools metadata when explaining cost.

The batch CSV endpoints are registered but disabled until shared multipart upload support exists.

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