Route inference requests and manage BitRouter Cloud through its public HTTP API.

The BitRouter API is in early beta. Pin your integration to the behavior you test and review release notes before upgrading.

Base URL: https://api.bitrouter.ai

Choose the API family that matches your task:

Need	Start with
Send a model request in an existing SDK format	One of the four inference APIs
Discover available models or providers	Models & providers
Manage Cloud accounts, keys, usage, billing, or policy	Cloud management
Check node health or scrape metrics	Health or Metrics

Route a request

Choose the protocol your client already speaks. BitRouter keeps the request and response shape for that protocol while routing the requested model to an eligible upstream.

OpenAI Chat Completions

POST /v1/chat/completions

OpenAI Responses

POST /v1/responses

Anthropic Messages

POST /v1/messages

Google GenerateContent

POST /v1beta/models/{model}:generateContent

Routing endpoints accept either:

Authorization: Bearer <api-key-or-JWT>
x-api-key: <api-key> for Anthropic-compatible clients

curl https://api.bitrouter.ai/v1/chat/completions \
  -H "Authorization: Bearer $BITROUTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "anthropic/claude-haiku-4.5",
    "messages": [{"role": "user", "content": "Hello"}]
  }'

Manage and inspect BitRouter

Discovery, BYOK encryption bootstrap, health, and metrics are public. Account-bound management endpoints require a credential with the scope named by that endpoint.

Models & providers

Inspect the public catalog and aggregate platform usage.

Cloud management

Manage namespaces, keys, billing, policy, presets, and OAuth clients.

BYOK encryption

Fetch the public key used for client-side provider-key encryption.

Health

Probe whether the Cloud node is alive.

This reference describes the hosted Cloud API. For the local daemon lifecycle, configuration, and virtual keys, use Self-hosting; for the generated CLI surface, use CLI.

Overview & authentication