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

# DeepSeek

> Use DeepSeek models in your Guild agents: supported models, inference providers, setup, and agent code.

Guild supports DeepSeek models. This page lists the models Guild recognizes, the inference providers that serve them, and how to call them from an agent.

| | |
| - | - |
| Name under **Models** in the credential form | DeepSeek |
| `provider` in `llmPreferences` | `"deepseek"` |
| Default model | `deepseek-v3.2` |
| Managed access | No. Add your own credential (BYOK). |

## Inference providers

DeepSeek models are served only through third-party inference providers, not a DeepSeek API.

| Provider | Notes |
| - | - |
| [AWS Bedrock](/platform/providers/aws-bedrock) | Serves `deepseek-v3.2` and `deepseek-r1`, except in `us-west-1`. |
| [OpenRouter](/platform/providers/openrouter) | Served under OpenRouter's `deepseek/` namespace. |
| [Fireworks AI](/platform/providers/fireworks) | Serves `deepseek-v4.1-flash` only. |

Write the canonical model name, such as `deepseek-v3.2`, everywhere in Guild. Guild maps it to each provider's own model ID.

## Models

Guild prices and recognizes these DeepSeek model IDs. A policy or preference can also name any other model your credential can reach. Third-party providers route more models than this list, and their catalogs change; see each provider's page for what it serves.

| Model | Notes |
| - | - |
| `deepseek-v3.2` | The default. |
| `deepseek-r1` | A reasoning model. |
| `deepseek-v4.1-flash` | Served by Fireworks AI. |

## Set up DeepSeek

Guild has no managed key for DeepSeek. To use DeepSeek models, add a credential for a provider that serves them. Adding your first credential switches the whole account to bring your own key (BYOK).

<Steps>
  <Step title="Open Models & providers">Click **Access & setup** in the left nav, then **Models & providers**. In an organization, only admins can open it.</Step>
  <Step title="Add a credential">Click **Add API key** and choose an inference provider from the table above.</Step>
  <Step title="Enter the provider's secret">Give the credential a **Name** and paste your provider's **API key**. [AWS Bedrock](/platform/providers/aws-bedrock) asks for an IAM role and region instead.</Step>
  <Step title="Choose DeepSeek">Under **Models**, check **DeepSeek**. Keep `deepseek-v3.2` as its default model or enter another from the list above. Then click **Add Key**. On [Fireworks AI](/platform/providers/fireworks), pick a model from its list, because the pre-filled default isn't available there.</Step>
</Steps>

To control which workspaces and agents can use DeepSeek models, add a [model policy](/platform/llm-settings#model-policies) for the credential. For example, `--models "deepseek-*"` limits a policy to matching models:

```bash theme={null}
guild llm policy create --credential <credential-id> --publisher DEEPSEEK --target-id <workspace-or-agent-id> --models "deepseek-*"
```

## Use it from an agent

Agent code never names a credential. Guild resolves the call against the workspace owner's settings. To ask for DeepSeek explicitly, put it in `llmPreferences`:

```typescript theme={null}
const result = await task.llm.generateText({
  prompt: "Summarize this text...",
  llmPreferences: [
    { provider: "deepseek", model: "deepseek-r1" },
    { provider: "deepseek" },
  ],
})
```

The first entry asks for `deepseek-r1`. The second falls back to the default model of the matching policy. Preferences are strict: if no credential or policy allows any of them, the call fails rather than using another publisher. See [LLM preferences](/guide/llms#llm-preferences).

## Related pages

* [Models & providers](/platform/llm-settings) for credentials, model policies, and the daily token limit
* [LLMs](/guide/llms) for `task.llm` and the unified LLM proxy
* [Usage](/insights/usage) for spend by model