Catalog
BerriAI/add-model

BerriAI

add-model

Add a new model to a live LiteLLM proxy. Walks the user through picking a provider, entering the deployment name and credentials, calls POST /model/new, then test-calls the model to confirm it routes correctly. Use when the user wants to add, register, deploy, or configure a new model on a LiteLLM proxy instance.

v1.0LATEST
NewUpdated Oct 12, 2026

Add Model

Add a new LLM to a live LiteLLM proxy.

Setup

Ask for these if not already known:

LITELLM_BASE_URL  — e.g. https://my-proxy.example.com
LITELLM_API_KEY   — proxy admin key

API reference: https://litellm.vercel.app/docs/proxy/model_management

Ask the user

  1. Public model name — what callers will send in "model": "..." (e.g. gpt-4o, my-claude, llama3)
  2. Provider — pick from the table below
  3. Credentials — whatever that provider needs

Provider table

Provider litellm_params.model Extra params
OpenAI openai/gpt-4o api_key
Azure OpenAI azure/<deployment-name> api_key, api_base, api_version
Anthropic anthropic/claude-3-5-sonnet-20241022 api_key
AWS Bedrock bedrock/anthropic.claude-3-5-sonnet-20241022-v2:0 AWS creds via env
Google Vertex vertex_ai/gemini-1.5-pro vertex_project, vertex_location
Ollama ollama/llama3 api_base (e.g. http://localhost:11434)
Groq groq/llama-3.3-70b-versatile api_key
Together AI together_ai/meta-llama/Llama-3-70b api_key
Mistral mistral/mistral-large-latest api_key

Full list: https://docs.litellm.ai/docs/providers

Run

curl -s -X POST "$BASE/model/new" \
  -H "Authorization: Bearer $KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model_name": "<public-name>",
    "litellm_params": {
      "model": "<provider/deployment>",
      "api_key": "<key>",
      "api_base": "<base_if_needed>",
      "api_version": "<version_if_azure>"
    }
  }'

Test it

After adding, verify it routes:

curl -s -X POST "$BASE/chat/completions" \
  -H "Authorization: Bearer $KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "<public-name>",
    "messages": [{"role": "user", "content": "say hi"}],
    "max_tokens": 10
  }'

Output

Show model_id from the response — needed to update or delete the model later. Report pass/fail from the test call.

Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

74/100

Grade

B

Good

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

72

Quality

75

Clarity

80

Completeness

68

Summary

This skill guides an agent through adding a new LLM model to a live LiteLLM proxy instance. It walks the user through selecting a provider, collecting necessary credentials, calling the proxy's `/model/new` API endpoint, and validating the model with a test request. The skill is scoped to proxy administration tasks and uses curl for HTTP operations.

Detected Capabilities

outbound HTTP requests (curl POST)credential handlingAPI authenticationresponse parsinguser input collection

Trigger Keywords

Phrases that agents use to match this skill to user intent.

add litellm modelregister proxy modeldeploy llm providerconfigure model routinglitellm proxy setupadd model to proxyregister new provider

Risk Signals

WARNING

Credential handling (api_key, AWS creds) passed as command-line arguments

Run section: curl -d with api_key in JSON payload
WARNING

API credentials transmitted in plaintext HTTP POST to proxy

Run section and Test section: curl requests
INFO

Environment variable assumption for AWS Bedrock credentials

Provider table: AWS creds via env
WARNING

User-provided credentials collected without explicit escaping guidance

Setup section: LITELLM_API_KEY collection

Referenced Domains

External domains referenced in skill content, detected by static analysis.

docs.litellm.ailitellm.vercel.applocalhostmy-proxy.example.com

Use Cases

  • Register a new OpenAI model on a LiteLLM proxy
  • Add Azure OpenAI deployment to proxy
  • Configure Anthropic Claude on a shared proxy
  • Set up local Ollama model via proxy
  • Add AWS Bedrock or Google Vertex model to proxy
  • Test model routing after registration

Quality Notes

  • Strength: Clear provider table with required parameters and model identifiers — reduces guessing
  • Strength: Explicit setup section captures required inputs before API calls
  • Strength: Test step validates registration and reports pass/fail with model_id output
  • Strength: Scope is well-defined (proxy admin tasks only)
  • Weakness: No error handling guidance — what if POST /model/new fails? What status codes indicate misconfiguration vs. network errors?
  • Weakness: No guidance on credential escaping for JSON payload — special characters in api_key or deployment name could break the curl command
  • Weakness: No security note about HTTPS/TLS for api_base parameter — localhost is shown but production should enforce HTTPS
  • Weakness: Missing guidance on updating or removing models (mentions 'needed to update or delete' but doesn't explain how)
  • Weakness: No mention of checking proxy logs if test call fails — leaves debugging path unclear
Model: claude-haiku-4-5-20251001Analyzed: Oct 12, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use BerriAI/add-model in your dev environment

Command Palette

Search for a command to run...