* Add keyword-based topic blocker implementation Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add embedding-based topic blocker using MiniLM Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add topic blocker package init with exports Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add synthetic engine eval set (34 cases) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add investment questions eval set (207 cases) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add engine eval synthetic policy config Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add engine keyword blocker eval results Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add investment keyword blocker eval results Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add investment embedding blocker eval results Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add investment embedding MiniLM eval results Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add investment embedding MPNet eval results (historical) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add investment TF-IDF eval results (historical) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add unified eval runner with confusion matrix reporting Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add benchmarks comparison table in markdown Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Clean up topic blocker: remove unused blockers, add phrase_patterns to content filter - Remove embedding_blocker.py, api_embedding_blocker.py, nli_blocker.py, tfidf_blocker.py, onnx_blocker.py (heavy deps not in Docker, inferior accuracy) - Remove airline_off_topic_restriction policy template and its test - Fix __init__.py to only export DeniedTopic and TopicBlocker (no eager import crash) - Add phrase_patterns support to ContentFilterGuardrail for regex-based paraphrase detection - Rewrite denied_financial_advice.yaml with conditional matching (identifier + block word), always-block keywords, phrase patterns, and exception phrases - Clean up test_eval.py: only keyword blocker + content filter tests remain (no network calls) - All 207 eval cases pass at 100% F1, 0 FP, 0 FN, <0.1ms latency Addresses all Greptile review comments: - Eager import crash (embedding deps) → fixed - Undeclared dependencies → fixed (files deleted) - lru_cache memory leak → fixed (file deleted) - Real network calls in tests → fixed (embedding tests removed) - Unused Dict import → already fixed Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add LLM-as-judge eval and update BENCHMARKS.md - Add TestInvestmentLlmJudgeGpt4oMini and TestInvestmentLlmJudgeClaude test classes that use litellm.completion() to classify messages - System prompt instructs LLM to act as airline chatbot content moderator - Tests skip gracefully when API keys aren't set - Update BENCHMARKS.md with production results table, historical comparison, and instructions for running LLM judge evals Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Move evals and benchmarks to guardrail_benchmarks folder Move eval runner, eval data (JSONL), and results from tests/test_litellm/.../topic_blocker/ into the guardrail implementation folder at litellm/.../litellm_content_filter/guardrail_benchmarks/. This keeps benchmarks co-located with the guardrail code they test. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Remove standalone topic_blocker package, consolidate into content_filter The standalone keyword_blocker.py was redundant with content_filter.py + denied_financial_advice.yaml. Removed the entire topic_blocker/ package, engine eval files, and old keyword blocker results. Simplified test_eval.py to only test ContentFilter + LLM judge baselines. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix compliance playground batch scoring bug, add display_name support The compliance playground was sending all texts in a single batch API call, but the content filter raises HTTPException on the first blocked text. This caused a single blocked/allowed result to be applied to all rows, producing incorrect scores (e.g. 41% instead of 100%). Fix by sending each text individually to get per-text results with progressive UI updates. Also add display_name field support for category YAML files so denied_financial_advice shows as "Denied Financial / Investment Advice" in the UI dropdown. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add block_investment CSV eval set and update benchmark result JSON Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * address greptile review feedback (greploop iteration 1) Fix stale test path in denied_financial_advice.yaml comment. Other comments were on files already deleted in prior commits. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
🚅 LiteLLM
Call 100+ LLMs in OpenAI format. [Bedrock, Azure, OpenAI, VertexAI, Anthropic, Groq, etc.]
LiteLLM Proxy Server (AI Gateway) | Hosted Proxy | Enterprise Tier
Use LiteLLM for
LLMs - Call 100+ LLMs (Python SDK + AI Gateway)
All Supported Endpoints - /chat/completions, /responses, /embeddings, /images, /audio, /batches, /rerank, /a2a, /messages and more.
Python SDK
pip install litellm
from litellm import completion
import os
os.environ["OPENAI_API_KEY"] = "your-openai-key"
os.environ["ANTHROPIC_API_KEY"] = "your-anthropic-key"
# OpenAI
response = completion(model="openai/gpt-4o", messages=[{"role": "user", "content": "Hello!"}])
# Anthropic
response = completion(model="anthropic/claude-sonnet-4-20250514", messages=[{"role": "user", "content": "Hello!"}])
AI Gateway (Proxy Server)
Getting Started - E2E Tutorial - Setup virtual keys, make your first request
pip install 'litellm[proxy]'
litellm --model gpt-4o
import openai
client = openai.OpenAI(api_key="anything", base_url="http://0.0.0.0:4000")
response = client.chat.completions.create(
model="gpt-4o",
messages=[{"role": "user", "content": "Hello!"}]
)
Agents - Invoke A2A Agents (Python SDK + AI Gateway)
Supported Providers - LangGraph, Vertex AI Agent Engine, Azure AI Foundry, Bedrock AgentCore, Pydantic AI
Python SDK - A2A Protocol
from litellm.a2a_protocol import A2AClient
from a2a.types import SendMessageRequest, MessageSendParams
from uuid import uuid4
client = A2AClient(base_url="http://localhost:10001")
request = SendMessageRequest(
id=str(uuid4()),
params=MessageSendParams(
message={
"role": "user",
"parts": [{"kind": "text", "text": "Hello!"}],
"messageId": uuid4().hex,
}
)
)
response = await client.send_message(request)
AI Gateway (Proxy Server)
Step 1. Add your Agent to the AI Gateway
Step 2. Call Agent via A2A SDK
from a2a.client import A2ACardResolver, A2AClient
from a2a.types import MessageSendParams, SendMessageRequest
from uuid import uuid4
import httpx
base_url = "http://localhost:4000/a2a/my-agent" # LiteLLM proxy + agent name
headers = {"Authorization": "Bearer sk-1234"} # LiteLLM Virtual Key
async with httpx.AsyncClient(headers=headers) as httpx_client:
resolver = A2ACardResolver(httpx_client=httpx_client, base_url=base_url)
agent_card = await resolver.get_agent_card()
client = A2AClient(httpx_client=httpx_client, agent_card=agent_card)
request = SendMessageRequest(
id=str(uuid4()),
params=MessageSendParams(
message={
"role": "user",
"parts": [{"kind": "text", "text": "Hello!"}],
"messageId": uuid4().hex,
}
)
)
response = await client.send_message(request)
MCP Tools - Connect MCP servers to any LLM (Python SDK + AI Gateway)
Python SDK - MCP Bridge
from mcp import ClientSession, StdioServerParameters
from mcp.client.stdio import stdio_client
from litellm import experimental_mcp_client
import litellm
server_params = StdioServerParameters(command="python", args=["mcp_server.py"])
async with stdio_client(server_params) as (read, write):
async with ClientSession(read, write) as session:
await session.initialize()
# Load MCP tools in OpenAI format
tools = await experimental_mcp_client.load_mcp_tools(session=session, format="openai")
# Use with any LiteLLM model
response = await litellm.acompletion(
model="gpt-4o",
messages=[{"role": "user", "content": "What's 3 + 5?"}],
tools=tools
)
AI Gateway - MCP Gateway
Step 1. Add your MCP Server to the AI Gateway
Step 2. Call MCP tools via /chat/completions
curl -X POST 'http://0.0.0.0:4000/v1/chat/completions' \
-H 'Authorization: Bearer sk-1234' \
-H 'Content-Type: application/json' \
-d '{
"model": "gpt-4o",
"messages": [{"role": "user", "content": "Summarize the latest open PR"}],
"tools": [{
"type": "mcp",
"server_url": "litellm_proxy/mcp/github",
"server_label": "github_mcp",
"require_approval": "never"
}]
}'
Use with Cursor IDE
{
"mcpServers": {
"LiteLLM": {
"url": "http://localhost:4000/mcp",
"headers": {
"x-litellm-api-key": "Bearer sk-1234"
}
}
}
}
How to use LiteLLM
You can use LiteLLM through either the Proxy Server or Python SDK. Both gives you a unified interface to access multiple LLMs (100+ LLMs). Choose the option that best fits your needs:
| LiteLLM AI Gateway | LiteLLM Python SDK | |
|---|---|---|
| Use Case | Central service (LLM Gateway) to access multiple LLMs | Use LiteLLM directly in your Python code |
| Who Uses It? | Gen AI Enablement / ML Platform Teams | Developers building LLM projects |
| Key Features | Centralized API gateway with authentication and authorization, multi-tenant cost tracking and spend management per project/user, per-project customization (logging, guardrails, caching), virtual keys for secure access control, admin dashboard UI for monitoring and management | Direct Python library integration in your codebase, Router with retry/fallback logic across multiple deployments (e.g. Azure/OpenAI) - Router, application-level load balancing and cost tracking, exception handling with OpenAI-compatible errors, observability callbacks (Lunary, MLflow, Langfuse, etc.) |
LiteLLM Performance: 8ms P95 latency at 1k RPS (See benchmarks here)
Jump to LiteLLM Proxy (LLM Gateway) Docs
Jump to Supported LLM Providers
Stable Release: Use docker images with the -stable tag. These have undergone 12 hour load tests, before being published. More information about the release cycle here
Support for more providers. Missing a provider or LLM Platform, raise a feature request.
OSS Adopters
Netflix |
Supported Providers (Website Supported Models | Docs)
Run in Developer mode
Services
- Setup .env file in root
- Run dependant services
docker-compose up db prometheus
Backend
- (In root) create virtual environment
python -m venv .venv - Activate virtual environment
source .venv/bin/activate - Install dependencies
pip install -e ".[all]" pip install prismaprisma generate- Start proxy backend
python litellm/proxy/proxy_cli.py
Frontend
- Navigate to
ui/litellm-dashboard - Install dependencies
npm install - Run
npm run devto start the dashboard
Enterprise
For companies that need better security, user management and professional support
This covers:
- ✅ Features under the LiteLLM Commercial License:
- ✅ Feature Prioritization
- ✅ Custom Integrations
- ✅ Professional Support - Dedicated discord + slack
- ✅ Custom SLAs
- ✅ Secure access with Single Sign-On
Contributing
We welcome contributions to LiteLLM! Whether you're fixing bugs, adding features, or improving documentation, we appreciate your help.
Quick Start for Contributors
This requires poetry to be installed.
git clone https://github.com/BerriAI/litellm.git
cd litellm
make install-dev # Install development dependencies
make format # Format your code
make lint # Run all linting checks
make test-unit # Run unit tests
make format-check # Check formatting only
For detailed contributing guidelines, see CONTRIBUTING.md.
Code Quality / Linting
LiteLLM follows the Google Python Style Guide.
Our automated checks include:
- Black for code formatting
- Ruff for linting and code quality
- MyPy for type checking
- Circular import detection
- Import safety checks
All these checks must pass before your PR can be merged.
Support / talk with founders
- Schedule Demo 👋
- Community Discord 💭
- Community Slack 💭
- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
Why did we build this
- Need for simplicity: Our code started to get extremely complicated managing & translating calls between Azure, OpenAI and Cohere.