xberg-io/liter-llm / plugin/.ai-rulez/skills/liter-llm-running-the-proxy
liter-llm-running-the-proxy
VerifiedUse when running the `liter-llm api` OpenAI-compatible gateway — virtual keys, per-key rate limits, budgets, cost tracking, and model routing. Covers the TOML config and the 22 REST endpoints.
Running the Proxy
liter-llm api is a drop-in OpenAI-compatible gateway: 22 REST endpoints that
route to 174 providers, with multi-tenant virtual keys, rate limits, budgets,
and cost tracking.
Start it
liter-llm api --config liter-llm-proxy.toml
The proxy auto-discovers liter-llm-proxy.toml in the current directory.
Configuration
[server]
host = "0.0.0.0"
port = 4000
[general]
master_key = "${LITER_LLM_MASTER_KEY}"
# Each [[models]] entry maps a routable name to a provider/model and its key.
[[models]]
name = "gpt-4o"
provider_model = "openai/gpt-4o"
api_key = "${OPENAI_API_KEY}"
[[models]]
name = "claude-sonnet"
provider_model = "anthropic/claude-sonnet-4-20250514"
api_key = "${ANTHROPIC_API_KEY}"
# Virtual keys scope which configured model names a caller may use.
[[keys]]
key = "sk-team-frontend"
models = ["gpt-4o", "claude-sonnet"]
rpm = 60
tpm = 100000
budget_limit = 50.0
${ENV_VAR} interpolation keeps secrets out of the file.
Call it like OpenAI
curl http://localhost:4000/v1/chat/completions \
-H "Authorization: Bearer sk-team-frontend" \
-d '{"model": "gpt-4o", "messages": [{"role": "user", "content": "Hello"}]}'
Notes
- Virtual keys scope which models a caller may use and carry their own RPM/TPM
and budget limits; the
master_keyadministers them. - The OpenAPI 3.1 spec is served at
/openapi.json. - Endpoints cover chat, embeddings, images, audio, moderations, files, batches, responses, and model listing.
- Docker:
docker run -p 4000:4000 -e LITER_LLM_MASTER_KEY=sk-key ghcr.io/xberg-io/liter-llm.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |