> ## 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 CrustData V2 in Deepline

> Use autocomplete endpoints before structured searches, prefer in-DB search for broad discovery, and use realtime enrichment only when fresh upstream data is.

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

## Provider-specific requirements

CrustData V2 is hidden from tool discovery: CrustData no longer serves Deepline's V2 API access, so every V2 call fails with a provider authorization error. Use the `crustdata_v3_*` tools for new workflows and migrate existing ones. confirm each V3 schema with `deepline describe <tool-id>`, since V3 uses its own filter vocabulary, not a renamed V2 payload.

Do not expose provider credit ladders to customers. Deepline tool pricing should remain Deepline-facing.

## 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 "CrustData V2" --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.