Bifrost · Rate Limits

Bifrost Rate Limits

Bifrost is a self-hosted gateway, so there are no provider-imposed rate limits — limits are whatever the operator configures via virtual keys, budgets, and per-key rate-limit policies. Effective ceilings are governed by (1) the host's compute/network capacity and (2) the upstream LLM provider's own rate limits, which Bifrost surfaces via fallback and load-balancing logic.

Bifrost Rate Limits is the machine-readable rate-limit profile for Bifrost on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests_per_minute, spend_per_period, and varies.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include AI Gateway, LLM, Open Source, and Rate Limiting.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
AI GatewayLLMOpen SourceRate Limiting

Limits

Virtual Key Request Rate virtual-key
requests_per_minute
operator-configured
Bifrost virtual keys carry rate-limit policy set by the deploying operator.
Virtual Key Budget virtual-key
spend_per_period
operator-configured
Per-key budget policy enforces upstream-cost spend caps.
Upstream Provider Limits provider/model
varies
inherited from upstream provider (OpenAI, Anthropic, etc.)
Bifrost transparently respects and falls back across upstream provider rate limits.

Policies

Adaptive Load Balancing (Enterprise)
The Enterprise edition redistributes load across upstream providers based on observed latency and error rate.
Automatic Fallback
On 429 or 5xx from an upstream provider, Bifrost retries against a configured fallback provider/model.
Semantic Caching
Cache hits avoid upstream calls entirely, reducing effective rate-limit pressure.
Operator-Owned Configuration
Because Bifrost is self-hosted, all rate-limit thresholds are owned by the operator — not the project.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/bifrost-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.