Provider-specific requirements
Use Versium for US consumer and business enrichment. If the workspace connects its own API key, that key takes precedence and Deepline does not bill the provider usage. Otherwise, actions with complete match-credit pricing use Deepline-managed access. Contact Append and Predictive Scores still require a workspace key because the supplied pricing table does not fully price them. Choose the narrowest action and output set that answers the request. Contact, demographic, audience, and predictive-score actions require at least one person identifier. Firmographic append requires a company identifier. Treat hashed email input as sensitive data even though it is not plaintext.Find an applicable action
Confirm your effective workspace, then search the live catalog:Inspect the selected contract
Replace<returned-tool-id> with the identifier returned by discovery:
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.