> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Versium in Deepline

> Use Versium for US consumer and business append workflows. Workspace API keys take precedence; otherwise priced actions use Deepline-managed access.

[Human guide: work with your agent →](https://deepline.com/docs/human/providers/versium/guide.md)
Inspect one Versium action before starting provider-backed work. Your first result is a verified input and output contract.

## 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:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline auth status --json
deepline search "Versium" --type tools --json
```

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:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline describe <returned-tool-id> --json
```

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](https://deepline.com/docs/sdk-v2/plays.md). For direct-call recovery, use [Tool execution recovery](https://deepline.com/docs/sdk-v2/tool-execution-recovery.md).

> [!TIP]
>
> Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.