DeepSeek - LangWatch

Add the credential

Open Settings > Model Providers, click Add Model Provider and select DeepSeek. Give the row a name, pick the organization, team or project it belongs to, and fill in:

Field	Value
`DEEPSEEK_API_KEY`	Your DeepSeek API key.

Save the row. Every virtual key whose scope can see the row can now dispatch to it, unless the key restricts its providers. See Virtual keys.

The DeepSeek model provider drawer with the DEEPSEEK_API_KEY field and the routing handle deepseek — The DeepSeek row: name, scope, DEEPSEEK_API_KEY and the routing handle deepseek.

The gateway calls https://api.deepseek.com as an OpenAI-compatible endpoint.

Model names

Write deepseek/<model>, for example deepseek/deepseek-chat. The gateway does not infer DeepSeek from a bare name.

Send a request

curl https://gateway.langwatch.ai/v1/chat/completions \
  -H "Authorization: Bearer $LANGWATCH_VIRTUAL_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "deepseek/deepseek-chat",
    "messages": [{"role": "user", "content": "Say hi in one word"}]
  }'

Endpoints

Endpoint	Served
`POST /v1/chat/completions`	Yes
`POST /v1/messages`	Yes, translated
`POST /v1/images/generations`, `POST /v1/images/edits`	No, rejected with HTTP 400. Image traffic needs a direct OpenAI, Azure OpenAI, Gemini, Vertex AI or Bedrock credential. See Images
`GET /v1/models`	Yes, from the DeepSeek catalog

Last modified on September 6, 2026