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

​
Provider-specific requirements

Find a verified business email using trykitt_find_email with fullName and domain. Optional linkedinStandardProfileURL helps resolve names. Found emails are already verified. A completed miss returns email: null and is free. Use trykitt_verify_email for an existing address. Completed verifications are charged, including unknown/catch-all results. Both tools use synchronous results. realtime: false, callbacks, and legacy async job lookup are unavailable. Connect your own API key to use your TryKitt account without a Deepline provider charge, or use Deepline-managed credentials. Never pass API keys in tool payloads. Use the shared email_status getter for verification decisions. valid-risky and undocumented verdicts produce unknown/hold. inspect the preserved raw validity rather than assuming catch-all or confirmed deliverability.

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