Skip to main content
The bifrost.client block controls how Bifrost manages its internal worker pool, request logging, authentication enforcement, header policies, SDK compatibility shims, and MCP agent behaviour. All settings map directly to the client section of the rendered config.json.

Connection Pool

A larger pool reduces latency spikes under burst load at the cost of higher baseline memory. For production workloads with multiple providers, 1000 is a common starting point.

Request & Response Logging

Set disableContentLogging: true for HIPAA / PCI compliance workloads where message content must not be persisted.

Security & CORS


Header Filtering

Controls which x-bf-eh-* headers are forwarded to upstream LLM providers. When both lists are empty, all x-bf-eh-* headers pass through. Specifying an allowlist enables strict whitelist mode - only listed headers are forwarded.

Authentication


Encryption

Always use a Kubernetes Secret in production:

Async Jobs & Database Pings


Compat Shims

Compatibility flags that let Bifrost silently adapt request/response shapes for SDK integrations:

Prometheus Labels

Add custom labels to every Prometheus metric emitted by Bifrost:

MCP Agent Settings


Full Example