Try Bifrost Enterprise free for 14 days. Explore now
A valid request URL is required to generate request examples{}Calls the upstream realtime provider’s client_secrets endpoint to mint a
short-lived ephemeral token (e.g. for browser-based WebRTC clients).
Bifrost selects a provider key, evaluates governance, and proxies the
response. The returned token is cached and mapped to the originating
virtual key for downstream attribution.
Request body must be JSON. session.model (or top-level model) must use
provider/model form.
A valid request URL is required to generate request examples{}Documentation Index
Fetch the complete documentation index at: https://docs.getbifrost.ai/llms.txt
Use this file to discover all available pages before exploring further.
Bearer token authentication. Use your provider API key or Bifrost authentication token.
Virtual keys (prefixed with sk-bf-) can also be passed here.
Provider-specific realtime client-secret payload (passthrough).
Upstream client-secret response (provider passthrough)
Provider-specific response body
Was this page helpful?