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

​
Provider-specific requirements

Verify one email per call. Use Play rows for multiple emails. bulk operations are disabled pending file, tenant ownership, and billing contracts. Keep ok, invalid, disposable, catch_all, and unknown distinct. catch_all and unknown do not prove deliverability. A provider error or inconsistent verdict is a failed verification. Repeat verification can consume provider credits again. The free BYOK connection probe validates the connected customer’s key internally and returns status only. Account balances do not establish per-call usage and are not included in the public response.

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