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

​
Provider-specific requirements

  • Use zerobounce_validate as the final email validation gate before any outbound send. Treat invalid, catch-all, spamtrap, abuse, and do_not_mail statuses as non-send by default.
  • Always inspect sub_status for granular failure reasons. status alone is not sufficient. For example, do_not_mail + role_based may still be acceptable for account-based campaigns whereas do_not_mail + disposable never is.
  • Use zerobounce_batch_validate for bulk verification of 1–100 emails. Play maps automatically batch zerobounce_validate calls. Results may take up to 70 seconds. An unknown verdict is not a validated email.
  • Use zerobounce_email_finder only for person-level lookups. domain is required, and at least one of first_name or last_name must be present.
  • Use zerobounce_domain_search for domain-only pattern discovery. It preserves the legacy Deepline public contract while mapping to the shared v2 guessformat endpoint.
  • Use zerobounce_activity_data to check recent engagement before re-engaging cold contacts. An active_in_days over 365 suggests the address may be abandoned.
  • When the did_you_mean field is non-empty, consider prompting the user or auto-correcting before sending.

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