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

​
Provider-specific requirements

Use searchbug_phone_validation for US and Canadian phone numbers when you need connection status, line type, carrier, porting, or DNC/TCPA fields. It is a validation/compliance check, not a person-to-phone identity match. The connector strips punctuation and a leading US/Canada country code before calling Searchbug’s api_lnp3 phone validator. The complete provider response is returned so newly added provider fields remain available without a Deepline release. Use Trestle when you need activity scoring or identity matching, and use IPQS for fraud-risk screening after ordinary phone validation.

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