mirror of
https://github.com/openclaw/openclaw.git
synced 2026-03-12 07:20:45 +00:00
* feat: add LiteLLM provider types, env var, credentials, and auth choice Add litellm-api-key auth choice, LITELLM_API_KEY env var mapping, setLitellmApiKey() credential storage, and LITELLM_DEFAULT_MODEL_REF. * feat: add LiteLLM onboarding handler and provider config Add applyLitellmProviderConfig which properly registers models.providers.litellm with baseUrl, api type, and model definitions. This fixes the critical bug from PR #6488 where the provider entry was never created, causing model resolution to fail at runtime. * docs: add LiteLLM provider documentation Add setup guide covering onboarding, manual config, virtual keys, model routing, and usage tracking. Link from provider index. * docs: add LiteLLM to sidebar navigation in docs.json Add providers/litellm to both English and Chinese provider page lists so the docs page appears in the sidebar navigation. * test: add LiteLLM non-interactive onboarding test Wire up litellmApiKey flag inference and auth-choice handler for the non-interactive onboarding path, and add an integration test covering profile, model default, and credential storage. * fix: register --litellm-api-key CLI flag and add preferred provider mapping Wire up the missing Commander CLI option, action handler mapping, and help text for --litellm-api-key. Add litellm-api-key to the preferred provider map for consistency with other providers. * fix: remove zh-CN sidebar entry for litellm (no localized page yet) * style: format buildLitellmModelDefinition return type * fix(onboarding): harden LiteLLM provider setup (#12823) * refactor(onboarding): keep auth-choice provider dispatcher under size limit --------- Co-authored-by: Peter Steinberger <steipete@gmail.com>
154 lines
3.5 KiB
Markdown
154 lines
3.5 KiB
Markdown
---
|
|
summary: "Run OpenClaw through LiteLLM Proxy for unified model access and cost tracking"
|
|
read_when:
|
|
- You want to route OpenClaw through a LiteLLM proxy
|
|
- You need cost tracking, logging, or model routing through LiteLLM
|
|
---
|
|
|
|
# LiteLLM
|
|
|
|
[LiteLLM](https://litellm.ai) is an open-source LLM gateway that provides a unified API to 100+ model providers. Route OpenClaw through LiteLLM to get centralized cost tracking, logging, and the flexibility to switch backends without changing your OpenClaw config.
|
|
|
|
## Why use LiteLLM with OpenClaw?
|
|
|
|
- **Cost tracking** — See exactly what OpenClaw spends across all models
|
|
- **Model routing** — Switch between Claude, GPT-4, Gemini, Bedrock without config changes
|
|
- **Virtual keys** — Create keys with spend limits for OpenClaw
|
|
- **Logging** — Full request/response logs for debugging
|
|
- **Fallbacks** — Automatic failover if your primary provider is down
|
|
|
|
## Quick start
|
|
|
|
### Via onboarding
|
|
|
|
```bash
|
|
openclaw onboard --auth-choice litellm-api-key
|
|
```
|
|
|
|
### Manual setup
|
|
|
|
1. Start LiteLLM Proxy:
|
|
|
|
```bash
|
|
pip install 'litellm[proxy]'
|
|
litellm --model claude-opus-4-6
|
|
```
|
|
|
|
2. Point OpenClaw to LiteLLM:
|
|
|
|
```bash
|
|
export LITELLM_API_KEY="your-litellm-key"
|
|
|
|
openclaw
|
|
```
|
|
|
|
That's it. OpenClaw now routes through LiteLLM.
|
|
|
|
## Configuration
|
|
|
|
### Environment variables
|
|
|
|
```bash
|
|
export LITELLM_API_KEY="sk-litellm-key"
|
|
```
|
|
|
|
### Config file
|
|
|
|
```json5
|
|
{
|
|
models: {
|
|
providers: {
|
|
litellm: {
|
|
baseUrl: "http://localhost:4000",
|
|
apiKey: "${LITELLM_API_KEY}",
|
|
api: "openai-completions",
|
|
models: [
|
|
{
|
|
id: "claude-opus-4-6",
|
|
name: "Claude Opus 4.6",
|
|
reasoning: true,
|
|
input: ["text", "image"],
|
|
contextWindow: 200000,
|
|
maxTokens: 64000,
|
|
},
|
|
{
|
|
id: "gpt-4o",
|
|
name: "GPT-4o",
|
|
reasoning: false,
|
|
input: ["text", "image"],
|
|
contextWindow: 128000,
|
|
maxTokens: 8192,
|
|
},
|
|
],
|
|
},
|
|
},
|
|
},
|
|
agents: {
|
|
defaults: {
|
|
model: { primary: "litellm/claude-opus-4-6" },
|
|
},
|
|
},
|
|
}
|
|
```
|
|
|
|
## Virtual keys
|
|
|
|
Create a dedicated key for OpenClaw with spend limits:
|
|
|
|
```bash
|
|
curl -X POST "http://localhost:4000/key/generate" \
|
|
-H "Authorization: Bearer $LITELLM_MASTER_KEY" \
|
|
-H "Content-Type: application/json" \
|
|
-d '{
|
|
"key_alias": "openclaw",
|
|
"max_budget": 50.00,
|
|
"budget_duration": "monthly"
|
|
}'
|
|
```
|
|
|
|
Use the generated key as `LITELLM_API_KEY`.
|
|
|
|
## Model routing
|
|
|
|
LiteLLM can route model requests to different backends. Configure in your LiteLLM `config.yaml`:
|
|
|
|
```yaml
|
|
model_list:
|
|
- model_name: claude-opus-4-6
|
|
litellm_params:
|
|
model: claude-opus-4-6
|
|
api_key: os.environ/ANTHROPIC_API_KEY
|
|
|
|
- model_name: gpt-4o
|
|
litellm_params:
|
|
model: gpt-4o
|
|
api_key: os.environ/OPENAI_API_KEY
|
|
```
|
|
|
|
OpenClaw keeps requesting `claude-opus-4-6` — LiteLLM handles the routing.
|
|
|
|
## Viewing usage
|
|
|
|
Check LiteLLM's dashboard or API:
|
|
|
|
```bash
|
|
# Key info
|
|
curl "http://localhost:4000/key/info" \
|
|
-H "Authorization: Bearer sk-litellm-key"
|
|
|
|
# Spend logs
|
|
curl "http://localhost:4000/spend/logs" \
|
|
-H "Authorization: Bearer $LITELLM_MASTER_KEY"
|
|
```
|
|
|
|
## Notes
|
|
|
|
- LiteLLM runs on `http://localhost:4000` by default
|
|
- OpenClaw connects via the OpenAI-compatible `/v1/chat/completions` endpoint
|
|
- All OpenClaw features work through LiteLLM — no limitations
|
|
|
|
## See also
|
|
|
|
- [LiteLLM Docs](https://docs.litellm.ai)
|
|
- [Model Providers](/concepts/model-providers)
|