Provider: Azure DeepSeek

Call Azure DeepSeek models through Respan Gateway with unified logs, cost, and latency.
This page is for Respan LLM Gateway users.

Use Respan Gateway to call Azure DeepSeek models while keeping unified observability (logs, cost, latency, reliability) in Respan.

Quick setup

1

Get a Respan API key

Sign up and create a key on the API keys page.

Send your first request

Pick the integration that matches your stack. The base URL is https://api.respan.ai/api and the only key needed is your RESPAN_API_KEY.

The recommended path. Point the OpenAI SDK at the Respan gateway and call any Azure DeepSeek model.

1from openai import OpenAI
2
3client = OpenAI(
4 api_key="YOUR_RESPAN_API_KEY",
5 base_url="https://api.respan.ai/api",
6)
7
8response = client.chat.completions.create(
9 model="azure_deepseek/deepseek-chat",
10 messages=[{"role": "user", "content": "Hello, Azure DeepSeek!"}],
11)
12print(response.choices[0].message.content)

More integrations

Azure DeepSeek models work with every Respan gateway integration:

Switch models

Change the model parameter to call any supported model through the same client. Use the azure_deepseek/ prefix to disambiguate when routing across providers. Browse the full list on the Models page.

1client.chat.completions.create(model="azure_deepseek/deepseek-chat", messages=messages)
2client.chat.completions.create(model="azure_deepseek/deepseek-r1", messages=messages)
3client.chat.completions.create(model="openai/gpt-5.5", messages=messages)
4client.chat.completions.create(model="anthropic/claude-sonnet-4-5", messages=messages)

Use your own Azure DeepSeek key (BYOK)

Credits are the default path. If you’d rather bill Azure directly, attach your own deployment credentials.

1

Open Providers

Go to the Providers page.

2

Add Azure DeepSeek

Select Azure DeepSeek and paste your credentials:

  • azure_deepseek.api_key, your Azure AI Foundry API key
  • azure_deepseek.api_base, your Azure AI Foundry endpoint or Azure OpenAI-compatible base URL
3

Load balancing (Optional)

Add multiple credential sets and use Load balancing weight to distribute traffic across them.

Override credentials per model (Optional)

Use credential_override when one model on a request should use a different Azure deployment than the default.

1{
2 "customer_credentials": {
3 "azure_deepseek": {
4 "api_key": "YOUR_AZURE_DEEPSEEK_API_KEY",
5 "api_base": "https://your-resource.openai.azure.com/openai/v1/"
6 }
7 },
8 "credential_override": {
9 "azure_deepseek/deepseek-chat": {
10 "api_key": "ANOTHER_AZURE_DEEPSEEK_API_KEY",
11 "api_base": "https://another-resource.openai.azure.com/openai/v1/"
12 }
13 }
14}

Log without proxying (Optional)

Already calling Azure DeepSeek directly? Send logs to Respan asynchronously to track cost, latency, and performance for those external calls.

1import requests
2
3requests.post(
4 "https://api.respan.ai/api/request-logs/create/",
5 headers={
6 "Authorization": "Bearer YOUR_RESPAN_API_KEY",
7 "Content-Type": "application/json",
8 },
9 json={
10 "model": "azure_deepseek/deepseek-chat",
11 "prompt_messages": [{"role": "user", "content": "Hello, how are you?"}],
12 "completion_message": {"role": "assistant", "content": "Hello from Azure DeepSeek through Respan."},
13 "cost": 0.001,
14 "generation_time": 1.2,
15 "customer_params": {"customer_identifier": "user_123"},
16 },
17)

See the logging guide for the full setup.