Model Access

Routing

When a task runs, the agent harness calls an LLM. How that call is routed depends on the executor and auth mode:

Agent harness
    ↓
┌─────────────────────────────────────────┐
│ Credits mode          │ BYOK mode       │
│                       │                 │
│ Rebyte Model Proxy    │ Direct to       │
│ (routes to any        │ provider API    │
│  provider)            │ (org's own key) │
└─────────────────────────────────────────┘
    ↓                       ↓
Anthropic / OpenAI / Google / OpenRouter

Credits mode — requests route through the Rebyte model proxy, which handles authentication with upstream providers. The claude executor can access models from any provider (Anthropic, OpenAI, Google, OpenRouter) through this proxy.

BYOK mode — requests go directly to the provider using the organization’s own API key. Each executor is restricted to its native provider’s models only (e.g., claude with BYOK can only use Anthropic models).

Available models

Model	Provider	Executors
`minimax-m2.7`	Open Source	claude, opencode
`kimi-k2.5`	Open Source	claude, opencode
`glm-5`	Open Source	claude, opencode
`gemini-3-flash`	Google	claude, opencode
`auto-gemini-3`	Google	gemini
`gemini-3.1-pro`	Google	claude, opencode
`claude-sonnet-4.6`	Anthropic	claude, opencode
`gpt-5.3-codex`	OpenAI	claude, codex, opencode
`gpt-5.4`	OpenAI	claude, codex, opencode
`claude-opus-4.6`	Anthropic	claude, opencode

Open Source models are routed via OpenRouter. All other models route directly to their provider’s API.

Defaults

Executor	Default model
`claude`	`claude-sonnet-4.6`
`codex`	`gpt-5.4`
`opencode`	`gemini-3.1-pro`
`gemini`	`auto-gemini-3`

Users can override the model per task.

Admin controls

Organization admins manage model access through Settings > Integrations > Code Agents.

Admins can:

Set BYOK keys per executor (claude, codex, gemini) — admin-only
Delete BYOK keys — immediately reverts the org to credits mode for that executor — admin-only

All org members can:

Test keys — verify a stored API key is valid
View key status — check which executors have active BYOK keys

BYOK (Bring Your Own Key)

BYOK lets an organization route LLM requests directly to the provider using their own API keys.

How it works

Admin stores an API key for an executor (claude, codex, or gemini) in Settings > Integrations > Code Agents
When a team member runs a task, the agent authenticates directly with the provider using the org’s key
No Rebyte credits are consumed — the org pays the provider directly
If no BYOK key is configured, the task routes through the Rebyte model proxy and consumes credits

BYOK model restrictions

With BYOK, each executor is restricted to its native provider’s models:

Executor	Provider	BYOK models
`claude`	Anthropic	`claude-sonnet-4.6`, `claude-opus-4.6`
`codex`	OpenAI	`gpt-5.4`, `gpt-5.3-codex`
`gemini`	Google	`auto-gemini-3`

opencode does not support BYOK — it routes through the model proxy only.

Without BYOK, the claude executor can access models from any provider through the model proxy. With BYOK, it is restricted to Anthropic models only, since the org’s Anthropic key cannot authenticate against other providers.