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

> Firmable provider guidance and usage best practices. Includes SDK V2 guidance, input constraints, response fields, and Deepline credit cost.

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

## Provider-specific requirements

Firmable supports either Deepline-managed access or a workspace-owned API key.
If a workspace connects its own key, that key is preferred for Firmable calls.

* Use `firmable_company_lookup` when you have a company identifier, domain, website, or LinkedIn profile.
* Use `firmable_person_lookup` when you have a Firmable person ID, LinkedIn profile, or email address.
* Use `firmable_people_search` to find people at a known Firmable company ID, then narrow by country, position, seniority, or department.
* Managed company and person lookups cost 3.57 Deepline credits per matched profile, including repeat lookups and profiles without contact details. Phone and email values are included.
* Managed people searches cost 3.57 Deepline credits per non-empty page, including masked rows and repeated searches. Empty searches and documented lookup misses are uncharged.
* These are Deepline data-access service charges. They do not infer Firmable credit consumption from a match. Firmable may make repeat unlocks free in its own account.
* Workspace-owned keys are not charged Deepline provider credits. Firmable manages the provider account's credits.

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