Provider: Azure OpenAI
Provider: Azure OpenAI
Use Respan Gateway to call Azure OpenAI deployments (gpt-5.5, gpt-5, gpt-5-mini, o3, and the rest) while keeping unified observability (logs, cost, latency, reliability) in Respan.
Quick setup
Add credits (recommended)
Top up credits to pay through Respan. No Azure resource required, Respan handles provider auth and billing.
Prefer to route through your own Azure OpenAI deployment? See Use your own Azure OpenAI key.
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. Use the azure/ prefix plus your deployment name (or any Azure-compatible model ID) as the model.
OpenAI SDK
Vercel AI SDK
Respan API
Point the standard OpenAI SDK at the Respan gateway. No Azure-specific client needed, Respan translates to your Azure deployment based on the model ID.
More integrations
Azure OpenAI 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/ prefix plus your Azure deployment name (or model ID) to disambiguate when routing across providers. Browse the full list on the Models page.
Use your own Azure OpenAI key (BYOK)
Credits are the default path. If you’d rather bill Azure directly, attach your own Azure OpenAI credentials.
Global (UI)
Per-request (Code)
Add Azure OpenAI
Select Azure OpenAI and fill in the required credential fields:
api_key(your Azure OpenAI API key)api_base(your Azure OpenAI resource endpoint, also called base URL)api_version(the Azure OpenAI API version to use)
Azure allows custom deployment names. Use the azure/{deployment-name} model ID format in gateway requests.
Override credentials per model (Optional)
Use credential_override when one model on a request should use a different Azure resource than the default.
Log without proxying (Optional)
Already calling Azure OpenAI directly? Send logs to Respan asynchronously to track cost, latency, and performance for those external calls.
See the logging guide for the full setup.