Skip to main content

Overview

Passthrough integrations let you call provider-native API paths and payloads through Bifrost without route-level request/response conversion. When you use passthrough endpoints, the request still flows through Bifrost core logic. You keep Bifrost features such as logging and observability while sending provider-native paths and bodies.

Endpoints

  • /openai_passthrough Default provider: openai
  • /anthropic_passthrough Default provider: anthropic
  • /azure_passthrough Default provider: azure
  • /genai_passthrough Default provider: gemini (with automatic Vertex detection for clients configured to use Vertex)

How It Works

  1. Send your request to a passthrough endpoint (OpenAI, Anthropic, Azure, or GenAI passthrough).
  2. The integration strips the passthrough prefix and forwards the remaining provider-native path/body.
  3. Bifrost handles provider execution through core inference and plugin pipelines.
  4. Response status, headers, and body are returned as passthrough output (for both stream and non-stream requests).

Provider Selection Rules

OpenAI Passthrough

  • Uses openai as the default provider.

Anthropic Passthrough

  • Uses anthropic as the default provider.

Azure Passthrough

  • Uses azure as the default provider.
  • Requires an Azure key with endpoint configured.
  • api-version handling varies by route:
    • /openai/deployments/ routes: if the caller omits api-version, Bifrost injects a default (2025-04-01-preview). Pass your own api-version to override — for example, to pin to a GA version or use a specific preview version.

GenAI Passthrough

  • Uses gemini by default.
  • Automatically switches to vertex when Vertex patterns are detected, such as:
    • URL path containing /projects/{PROJECT_ID}/locations/{LOCATION}/
    • Request body model containing a Vertex resource path
    • OAuth token pattern typically used for Vertex (Bearer ya29...)

Usage Examples

OpenAI Passthrough

Anthropic Passthrough

Azure Passthrough

GenAI Passthrough (Gemini)

GenAI Passthrough (Vertex-style request)


Notes

  • Use passthrough when you need a provider endpoint that is not directly supported by Bifrost integration routes yet.
  • For Azure passthrough, auth headers (api-key, x-api-key, OAuth token) are always sourced from the Bifrost key config and never forwarded from the client request.
  • For Azure /openai/deployments/ routes, Bifrost injects api-version=2025-04-01-preview when the caller does not supply one. Supply your own api-version query parameter to use a different version (e.g. 2024-10-21 for the latest GA, or a newer preview).