> ## 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 Upcell in Deepline

> Use contact existence first when you only need to check mobile availability for free; use contact enrichment to reveal matched mobile numbers.

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

## Provider-specific requirements

Use Upcell when the workflow needs mobile phone availability checks or matched
mobile phone reveal for a known person.

Prefer `upcell_contact_existence` first when the user only needs to know whether
a mobile exists, because it is free. Use `upcell_enrich_contact` when the mobile
number itself is needed.

For both actions, provide at least one strong matcher:

* `linkedinUrl`
* `email`
* `personalEmail`
* `firstName`, `lastName`, `title`, and `companyName`
* `firstName`, `lastName`, and either `companyDomain` or `companySocialUrl`

Only mobile workflows are currently enabled. Email, social URL, and usage stats
endpoints are intentionally not exposed until pricing and availability are
confirmed.

## 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 "Upcell" --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.