Gateway overview
BetaWe just launched Apps: hosted models, actions and pages, on the same bill as your inference.Read the Apps docs
Gateway/Get started/Overview

Gateway

One inference API for every certified model, with a prepaid balance, budgets, routing rules, and a receipt for every request.

What it is

Inference Bureau sits between your application and the model providers. You call one endpoint, https://api.inferencebureau.com/v1, with the OpenAI SDK you already use. Model slugs match OpenRouter, so a slug like openai/gpt-4o-mini works as written. Models certified for the Anthropic Messages API (every Claude model, and others the gateway converts for) also answer at POST /v1/messages, so the Anthropic SDK works with a base URL change. Models certified for the OpenAI Responses API answer at POST /v1/responses, for responses.create and Codex. POST /v1/embeddings turns text into vectors in the OpenAI shape, and for classification and scoring, POST /v1/evaluate runs TypeSafe Jev.

Every request is checked against your team's Directives, rate limits, and balance before it reaches a provider. Afterwards you can look it up by id to see which provider served it, how many tokens it used, and what it cost.

How a request flows

  1. Authenticate. The key identifies the team, project, and environment.
  2. Admit. Directives decide which models and providers are allowed, rate limits are checked, and the worst-case cost is reserved from the team balance.
  3. Dispatch. A certified provider for the requested model is chosen. If it fails before answering, Dispatch may try another provider for the same model (see Routing).
  4. Settle. Actual usage replaces the reservation and the unused amount is released. The receipt in Logs shows the final charge.

Concepts

TermMeaning
TeamOwns the balance, members, and team-wide Directives.
ProjectGroups environments and keys for one application.
EnvironmentA stage within a project: production or development. Every key belongs to one.
DirectivesPolicy at team, project, environment, or key level: allowed models, limits, and budgets.
DispatchRouting: which providers may serve a model, and in what order.
LogsPer-request metadata, routing decisions, and costs. Prompts and responses are kept only when you turn on Log content.

Next steps