Provider: Azure DeepSeek
Use Respan Gateway to call Azure DeepSeek models while keeping unified observability (logs, cost, latency, reliability) in Respan.
Azure DeepSeek requires bring your own key (BYOK). Provider usage cannot be paid with Respan credits.
Quick setup
Add your Azure DeepSeek credentials
Configure your Azure DeepSeek credentials on the Providers page before using the examples below. See Use your own Azure DeepSeek key.
Send your first request
After configuring your Azure DeepSeek credentials in Respan, pick the integration that matches your stack. The base URL is https://api.respan.ai/api and your application authenticates with RESPAN_API_KEY.
OpenAI SDK
Vercel AI SDK
Respan API
The recommended path. Point the OpenAI SDK at the Respan gateway and call any Azure DeepSeek model.
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.
Use your own Azure DeepSeek key (BYOK)
Azure DeepSeek credentials are required. Configure them in Respan or pass them with each request using one of the options below.
Global (UI)
Per-request (Code)
Override credentials per model (Optional)
Use credential_override when one model on a request should use a different Azure deployment than the default.
Log without proxying (Optional)
Already calling Azure DeepSeek directly? Send logs to Respan asynchronously to track cost, latency, and performance for those external calls.
See the logging guide for the full setup.