Overview
An integration is a protocol adapter that translates between Bifrost’s unified API and provider-specific API formats. Each integration handles request transformation, response normalization, and error mapping between the external API contract and Bifrost’s internal processing pipeline. Integrations enable you to utilize Bifrost’s features like governance, MCP tools, load balancing, semantic caching, multi-provider support, and more, all while preserving your existing SDK-based architecture. Bifrost handles all the overhead of structure conversion, requiring only a single URL change to switch from direct provider APIs to Bifrost’s gateway. Bifrost converts the request/response format of the provider API to the Bifrost API format based on the integration used, so you don’t have to.Quick Migration
Before (Direct Provider)
After (Bifrost)
Supported Integrations
Provider-Prefixed Models
Use multiple providers seamlessly by prefixing model names with the provider:- OpenAI
- Anthropic
- Azure
- Vertex
- Ollama
Direct API Usage
For custom HTTP clients or when you have existing provider-specific setup and want to use Bifrost gateway without restructuring your codebase:Listing Models
All integrations support listing available models through their respective list models endpoints (e.g.,/openai/v1/models, /anthropic/v1/models). By default, list models requests return models from all configured providers in Bifrost.
Filtering by Provider
You can control which provider’s models to list using thex-bf-list-models-provider header:
- Python
- JavaScript
- cURL
Header Behavior
| Header Value | Behavior |
|---|---|
| Not set (default) | Lists models from all configured providers |
all | Lists models from all configured providers |
openai | Lists models from OpenAI provider only |
anthropic | Lists models from Anthropic provider only |
vertex | Lists models from Vertex AI provider only |
| Any valid provider | Lists models from that specific provider |
Response Fields
When listing models from all providers, some provider-specific fields may be empty or contain default values if the information is not available from all providers. This is normal behavior as different providers expose different model metadata.Migration Strategies
Gradual Migration
- Start with development - Test Bifrost in dev environment
- Canary deployment - Route 5% of traffic through Bifrost
- Feature-by-feature - Migrate specific endpoints gradually
- Full migration - Switch all traffic to Bifrost
Blue-Green Migration
Feature Flag Integration
Next Steps
- HTTP Transport Overview - Main HTTP transport guide
- Endpoints - Complete API reference
- Configuration - Provider setup and config

