@@ -402,7 +403,7 @@ Support for more providers. Missing a provider or LLM Platform, raise a [feature
# Enterprise
For companies that need better security, user management and professional support
-[Talk to founders](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+[Talk to founders](https://enterprise.litellm.ai/demo)
This covers:
- ✅ **Features under the [LiteLLM Commercial License](https://docs.litellm.ai/docs/proxy/enterprise):**
@@ -452,7 +453,6 @@ All these checks must pass before your PR can be merged.
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
- [Community Slack 💭](https://www.litellm.ai/support)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
# Why did we build this
diff --git a/ci_cd/security_scans.sh b/ci_cd/security_scans.sh
index e0f370e0035..061e454465a 100755
--- a/ci_cd/security_scans.sh
+++ b/ci_cd/security_scans.sh
@@ -10,13 +10,13 @@ echo "Starting security scans for LiteLLM..."
# Function to install Trivy and required tools
install_trivy() {
echo "Installing Trivy and required tools..."
+ TRIVY_VERSION="0.35.0"
sudo apt-get update
- sudo apt-get install -y wget apt-transport-https gnupg lsb-release jq curl bsdmainutils
- wget -qO - https://aquasecurity.github.io/trivy-repo/deb/public.key | sudo apt-key add -
- echo "deb https://aquasecurity.github.io/trivy-repo/deb $(lsb_release -sc) main" | sudo tee -a /etc/apt/sources.list.d/trivy.list
- sudo apt-get update
- sudo apt-get install trivy
- echo "Trivy and required tools installed successfully"
+ sudo apt-get install -y wget jq curl bsdmainutils
+ wget -qO trivy.deb "https://github.com/aquasecurity/trivy/releases/download/v${TRIVY_VERSION}/trivy_${TRIVY_VERSION}_Linux-64bit.deb"
+ sudo dpkg -i trivy.deb
+ rm trivy.deb
+ echo "Trivy ${TRIVY_VERSION} installed successfully"
}
# Function to install Grype
@@ -163,6 +163,9 @@ run_grype_scans() {
"CVE-2026-25639" # axios - full fix requires 1.x major version bump; pinned to >=0.30.2 to clear other axios CVEs, upgrade to 1.x in follow-up
"CVE-2026-2297" # Python 3.13 SourcelessFileLoader audit hook bypass - no fix available in base image
"GHSA-qffp-2rhf-9h96" # tar hardlink path traversal - from nodejs_wheel bundled npm, not used in application runtime code
+ "CVE-2026-2673" # OpenSSL 3.6.1 TLS 1.3 key exchange group negotiation issue - no fix available yet
+ "CVE-2026-3644" # Python 3.13 vulnerability - no fix available in base image
+ "CVE-2026-4224" # Python 3.13 Expat parser stack overflow in ElementDeclHandler - no fix available in base image
)
# Build JSON array of allowlisted CVE IDs for jq
diff --git a/cookbook/benchmark/readme.md b/cookbook/benchmark/readme.md
index 57115eb96a9..afa59aa91ee 100644
--- a/cookbook/benchmark/readme.md
+++ b/cookbook/benchmark/readme.md
@@ -178,4 +178,4 @@ Benchmark Results for 'When will BerriAI IPO?':
```
## Support
-**🤝 Schedule a 1-on-1 Session:** Book a [1-on-1 session](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions) with Krrish and Ishaan, the founders, to discuss any issues, provide feedback, or explore how we can improve LiteLLM for you.
+**🤝 Schedule a 1-on-1 Session:** Book a [1-on-1 session](https://enterprise.litellm.ai/demo) with Krrish and Ishaan, the founders, to discuss any issues, provide feedback, or explore how we can improve LiteLLM for you.
diff --git a/cookbook/codellama-server/README.MD b/cookbook/codellama-server/README.MD
index b158bb083f2..82a7e62f40a 100644
--- a/cookbook/codellama-server/README.MD
+++ b/cookbook/codellama-server/README.MD
@@ -143,7 +143,6 @@ All responses from the server are returned in the following format (for all LLM
- [Our calendar 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
## Roadmap
diff --git a/cookbook/litellm_proxy_server/readme.md b/cookbook/litellm_proxy_server/readme.md
index d0b0592c433..2c1eab72c24 100644
--- a/cookbook/litellm_proxy_server/readme.md
+++ b/cookbook/litellm_proxy_server/readme.md
@@ -164,7 +164,6 @@ All responses from the server are returned in the following format (for all LLM
- [Our calendar 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
## Roadmap
diff --git a/docs/my-website/blog/anthropic_opus_4_5_and_advanced_features/index.md b/docs/my-website/blog/anthropic_opus_4_5_and_advanced_features/index.md
index 8a54426dfb0..21ba3d60790 100644
--- a/docs/my-website/blog/anthropic_opus_4_5_and_advanced_features/index.md
+++ b/docs/my-website/blog/anthropic_opus_4_5_and_advanced_features/index.md
@@ -3,18 +3,9 @@ slug: anthropic_advanced_features
title: "Day 0 Support: Claude 4.5 Opus (+Advanced Features)"
date: 2025-11-25T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - sameer
+ - krrish
+ - ishaan-alt
description: "Guide to Claude Opus 4.5 and advanced features in LiteLLM: Tool Search, Programmatic Tool Calling, and Effort Parameter."
tags: [anthropic, claude, tool search, programmatic tool calling, effort, advanced features]
hide_table_of_contents: false
@@ -25,6 +16,8 @@ import TabItem from '@theme/TabItem';
This guide covers Anthropic's latest model (Claude Opus 4.5) and its advanced features now available in LiteLLM: Tool Search, Programmatic Tool Calling, Tool Input Examples, and the Effort Parameter.
+{/* truncate */}
+
---
| Feature | Supported Models |
diff --git a/docs/my-website/blog/anthropic_wildcard_model_access_incident/index.md b/docs/my-website/blog/anthropic_wildcard_model_access_incident/index.md
index f6172cd6744..8d58e18e580 100644
--- a/docs/my-website/blog/anthropic_wildcard_model_access_incident/index.md
+++ b/docs/my-website/blog/anthropic_wildcard_model_access_incident/index.md
@@ -3,18 +3,9 @@ slug: anthropic-wildcard-model-access-incident
title: "Incident Report: Wildcard Blocking New Models After Cost Map Reload"
date: 2026-02-23T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - sameer
+ - krrish
+ - ishaan-alt
tags: [incident-report, proxy, auth, model-access]
hide_table_of_contents: false
---
diff --git a/docs/my-website/blog/authors.yml b/docs/my-website/blog/authors.yml
index 2a49a736333..1b1ef4d34c4 100644
--- a/docs/my-website/blog/authors.yml
+++ b/docs/my-website/blog/authors.yml
@@ -4,6 +4,12 @@ litellm:
url: https://github.com/BerriAI/litellm
image_url: https://github.com/BerriAI.png
+sameer:
+ name: Sameer Kankute
+ title: SWE @ LiteLLM (LLM Translation)
+ url: https://www.linkedin.com/in/sameer-kankute/
+ image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
+
krrish:
name: Krrish Dholakia
title: CEO, LiteLLM
@@ -22,3 +28,21 @@ ishaan-alt:
title: CTO, LiteLLM
url: https://www.linkedin.com/in/reffajnaahsi/
image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+
+ryan:
+ name: Ryan Crabbe
+ title: Performance Engineer, LiteLLM
+ url: https://www.linkedin.com/in/ryan-crabbe-0b9687214
+ image_url: https://media.licdn.com/dms/image/v2/D5603AQHt1t9Z4BJ6Gw/profile-displayphoto-shrink_400_400/profile-displayphoto-shrink_400_400/0/1724453682340?e=1772064000&v=beta&t=VXdmr13rsNB05wyA2F1TENOB5UuDHUZ0FCHTolNyR5M
+
+alexsander:
+ name: Alexsander Hamir
+ title: Performance Engineer, LiteLLM
+ url: https://www.linkedin.com/in/alexsander-baptista/
+ image_url: https://github.com/AlexsanderHamir.png
+
+yuneng:
+ name: Yuneng Jiang
+ title: SWE @ LiteLLM (Full Stack)
+ url: https://www.linkedin.com/in/yuneng-david-jiang-455676139/
+ image_url: https://avatars.githubusercontent.com/u/171294688?v=4
diff --git a/docs/my-website/blog/ci_cd_v2_improvements/index.md b/docs/my-website/blog/ci_cd_v2_improvements/index.md
new file mode 100644
index 00000000000..84f8f7bda6b
--- /dev/null
+++ b/docs/my-website/blog/ci_cd_v2_improvements/index.md
@@ -0,0 +1,55 @@
+---
+slug: ci-cd-v2-improvements
+title: "Announcing CI/CD v2 for LiteLLM"
+date: 2026-03-30T21:30:00
+authors:
+ - krrish
+description: "CI/CD v2 introduces isolated environments, stronger security gates, and safer release separation for LiteLLM."
+tags: [engineering, ci-cd, security]
+hide_table_of_contents: false
+---
+
+import Image from '@theme/IdealImage';
+
+The CI/CD v2 is now live for LiteLLM.
+
+
+
+
+Building on the roadmap from our [security incident](https://docs.litellm.ai/blog/security-townhall-updates#roadmap), CI/CD v2 introduces isolated environments, stronger security gates, and safer release separation for LiteLLM.
+
+## What changed
+
+- Security scans and unit tests run in isolated environments.
+- Validation and release are separated into different repositories, making it harder for an attacker to reach release credentials.
+- Trusted Publishing for PyPI releases - this means no long-lived credentials are used to publish releases.
+- Immutable Docker release tags - this means no tampering of Docker release tags after they are published [Learn more](https://docs.docker.com/docker-hub/repos/manage/hub-images/immutable-tags/). Note: work for GHCR docker releases is planned as well.
+
+## What's next
+
+Moving forward, we plan on:
+- Adopting OpenSSF (this is a set of security criteria that projects should meet to demonstrate a strong security posture - [Learn more](https://baseline.openssf.org/versions/2026-02-19.html))
+ - We've added Scorecard and Allstar to our Github
+
+- Adding SLSA Build Provenance to our CI/CD pipeline - this means we allow users to independently verify that a release came from us and prevent silent modifications of releases after they are published.
+
+
+We hope that this will mean you can be confident that the releases you are using are safe and from us.
+
+
+## The principle
+
+The new CI/CD pipeline reflects the principles, outlined below, and is designed to be more secure and reliable:
+
+- **Limit** what each package can access
+- **Reduce** the number of sensitive environment variables
+- **Avoid** compromised packages
+- **Prevent** release tampering
+
+
+## How to help:
+
+Help us plan April's stability sprint - https://github.com/BerriAI/litellm/issues/24825
\ No newline at end of file
diff --git a/docs/my-website/blog/claude_code_beta_headers/index.md b/docs/my-website/blog/claude_code_beta_headers/index.md
index 44567f616aa..ee07da79397 100644
--- a/docs/my-website/blog/claude_code_beta_headers/index.md
+++ b/docs/my-website/blog/claude_code_beta_headers/index.md
@@ -3,18 +3,9 @@ slug: claude-code-beta-headers-incident
title: "Incident Report: Invalid beta headers with Claude Code"
date: 2026-02-16T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
+ - sameer
+ - ishaan-alt
+ - krrish
tags: [incident-report, anthropic, stability]
hide_table_of_contents: false
---
@@ -173,5 +164,5 @@ curl -X POST "https://your-proxy-url/reload/anthropic_beta_headers" \
## Related documentation
-- [Managing Anthropic Beta Headers](../proxy/sync_anthropic_beta_headers.md) - Complete configuration guide
+- [Managing Anthropic Beta Headers](../../docs/proxy/sync_anthropic_beta_headers) - Complete configuration guide
- [`anthropic_beta_headers_config.json`](https://github.com/BerriAI/litellm/blob/main/litellm/anthropic_beta_headers_config.json) - Current configuration file
diff --git a/docs/my-website/blog/claude_opus_4_6/index.md b/docs/my-website/blog/claude_opus_4_6/index.md
index e44420bd570..eeb5d5ff2f8 100644
--- a/docs/my-website/blog/claude_opus_4_6/index.md
+++ b/docs/my-website/blog/claude_opus_4_6/index.md
@@ -3,18 +3,9 @@ slug: claude_opus_4_6
title: "Day 0 Support: Claude Opus 4.6"
date: 2026-02-05T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
+ - sameer
+ - ishaan-alt
+ - krrish
description: "Day 0 support for Claude Opus 4.6 on LiteLLM AI Gateway - use across Anthropic, Azure, Vertex AI, and Bedrock."
tags: [anthropic, claude, opus 4.6]
hide_table_of_contents: false
@@ -25,6 +16,8 @@ import TabItem from '@theme/TabItem';
LiteLLM now supports Claude Opus 4.6 on Day 0. Use it across Anthropic, Azure, Vertex AI, and Bedrock through the LiteLLM AI Gateway.
+{/* truncate */}
+
## Docker Image
```bash
diff --git a/docs/my-website/blog/claude_sonnet_4_6/index.md b/docs/my-website/blog/claude_sonnet_4_6/index.md
index df54fa09792..12446c82c60 100644
--- a/docs/my-website/blog/claude_sonnet_4_6/index.md
+++ b/docs/my-website/blog/claude_sonnet_4_6/index.md
@@ -3,14 +3,8 @@ slug: claude_sonnet_4_6
title: "Day 0 Support: Claude Sonnet 4.6"
date: 2026-02-17T10:00:00
authors:
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
+ - ishaan-alt
+ - krrish
description: "Day 0 support for Claude Sonnet 4.6 on LiteLLM AI Gateway - use across Anthropic, Azure, Vertex AI, and Bedrock."
tags: [anthropic, claude, sonnet 4.6]
hide_table_of_contents: false
@@ -21,6 +15,8 @@ import TabItem from '@theme/TabItem';
LiteLLM now supports Claude Sonnet 4.6 on Day 0. Use it across Anthropic, Azure, Vertex AI, and Bedrock through the LiteLLM AI Gateway.
+{/* truncate */}
+
## Docker Image
```bash
diff --git a/docs/my-website/blog/fastapi_middleware_performance/index.mdx b/docs/my-website/blog/fastapi_middleware_performance/index.mdx
index b0c5ba13634..e373326c071 100644
--- a/docs/my-website/blog/fastapi_middleware_performance/index.mdx
+++ b/docs/my-website/blog/fastapi_middleware_performance/index.mdx
@@ -3,18 +3,9 @@ slug: fastapi-middleware-performance
title: "Your Middleware Could Be a Bottleneck"
date: 2026-02-07T10:00:00
authors:
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
- - name: Ryan Crabbe
- title: "Performance Engineer, LiteLLM"
- url: https://www.linkedin.com/in/ryan-crabbe-0b9687214
- image_url: https://media.licdn.com/dms/image/v2/D5603AQHt1t9Z4BJ6Gw/profile-displayphoto-shrink_400_400/profile-displayphoto-shrink_400_400/0/1724453682340?e=1772064000&v=beta&t=VXdmr13rsNB05wyA2F1TENOB5UuDHUZ0FCHTolNyR5M
+ - krrish
+ - ishaan-alt
+ - ryan
description: "How we improved LiteLLM proxy latency and throughput by replacing a single middleware base class"
tags: [performance, fastapi, middleware]
hide_table_of_contents: false
diff --git a/docs/my-website/blog/gemin_3.1/index.md b/docs/my-website/blog/gemin_3.1/index.md
index b81595e4bd5..0afccb49d98 100644
--- a/docs/my-website/blog/gemin_3.1/index.md
+++ b/docs/my-website/blog/gemin_3.1/index.md
@@ -3,18 +3,9 @@ slug: gemini_3_1_pro
title: "DAY 0 Support: Gemini 3.1 Pro on LiteLLM"
date: 2026-02-19T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - sameer
+ - krrish
+ - ishaan-alt
description: "Guide to using Gemini 3.1 Pro on LiteLLM Proxy and SDK with day 0 support."
tags: [gemini, day 0 support, llms]
hide_table_of_contents: false
@@ -28,6 +19,8 @@ import TabItem from '@theme/TabItem';
LiteLLM now supports `gemini-3.1-pro-preview` and all the new API changes along with it.
+{/* truncate */}
+
## Deploy this version
@@ -67,7 +60,7 @@ LiteLLM provides **full end-to-end support** for Gemini 3.1 Pro on:
- ✅ `/v1/chat/completions` - OpenAI-compatible chat completions endpoint
- ✅ `/v1/responses` - OpenAI Responses API endpoint (streaming and non-streaming)
- ✅ [`/v1/messages`](../../docs/anthropic_unified) - Anthropic-compatible messages endpoint
-- ✅ `/v1/generateContent` – [Google Gemini API](../../docs/generateContent.md) compatible endpoint
+- ✅ `/v1/generateContent` – [Google Gemini API](../../docs/generateContent) compatible endpoint
All endpoints support:
- Streaming and non-streaming responses
@@ -147,4 +140,3 @@ curl -X POST http://localhost:4000/v1/chat/completions \
| `high` | `high` |
| `disable` | `minimal` |
| `none` | `minimal` |
-
diff --git a/docs/my-website/blog/gemini_3/index.md b/docs/my-website/blog/gemini_3/index.md
index 7263acc12c9..a5b94382b6f 100644
--- a/docs/my-website/blog/gemini_3/index.md
+++ b/docs/my-website/blog/gemini_3/index.md
@@ -3,18 +3,9 @@ slug: gemini_3
title: "DAY 0 Support: Gemini 3 on LiteLLM"
date: 2025-11-19T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - sameer
+ - krrish
+ - ishaan-alt
description: "Common questions and best practices for using gemini-3-pro-preview with LiteLLM Proxy and SDK."
tags: [gemini, day 0 support, llms]
hide_table_of_contents: false
@@ -29,6 +20,8 @@ This guide covers common questions and best practices for using `gemini-3-pro-pr
:::
+{/* truncate */}
+
## Quick Start
@@ -976,8 +969,7 @@ messages.append(response.choices[0].message) # ✅ Includes thought signatures
## Additional Resources
-- [Gemini Provider Documentation](../gemini.md)
-- [Thought Signatures Guide](../gemini.md#thought-signatures)
-- [Reasoning Content Documentation](../../reasoning_content.md)
-- [Function Calling Guide](../../function_calling.md)
-
+- [Gemini Provider Documentation](../../docs/providers/gemini)
+- [Thought Signatures Guide](../../docs/providers/gemini#thought-signatures)
+- [Reasoning Content Documentation](../../docs/reasoning_content)
+- [Function Calling Guide](../../docs/completion/function_call)
diff --git a/docs/my-website/blog/gemini_3_1_flash_lite/index.md b/docs/my-website/blog/gemini_3_1_flash_lite/index.md
index 9ef4bacb2ad..0ae79e5fa67 100644
--- a/docs/my-website/blog/gemini_3_1_flash_lite/index.md
+++ b/docs/my-website/blog/gemini_3_1_flash_lite/index.md
@@ -3,18 +3,9 @@ slug: gemini_3_1_flash_lite_preview
title: "DAY 0 Support: Gemini 3.1 Flash Lite Preview on LiteLLM"
date: 2026-03-03T08:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - sameer
+ - krrish
+ - ishaan-alt
description: "Guide to using Gemini 3.1 Flash Lite Preview on LiteLLM Proxy and SDK with day 0 support."
tags: [gemini, day 0 support, llms, supernova]
hide_table_of_contents: false
@@ -32,6 +23,8 @@ LiteLLM now supports `gemini-3.1-flash-lite-preview` with full day 0 support!
If you only want cost tracking, you need no change in your current Litellm version. But if you want the support for new features introduced along with it like thinking levels, you will need to use v1.80.8-stable.1 or above.
:::
+{/* truncate */}
+
## Deploy this version
@@ -150,7 +143,7 @@ LiteLLM provides **full end-to-end support** for Gemini 3.1 Flash Lite Preview o
- ✅ `/v1/chat/completions` - OpenAI-compatible chat completions endpoint
- ✅ `/v1/responses` - OpenAI Responses API endpoint (streaming and non-streaming)
- ✅ [`/v1/messages`](../../docs/anthropic_unified) - Anthropic-compatible messages endpoint
-- ✅ `/v1/generateContent` – [Google Gemini API](../../docs/generateContent.md) compatible endpoint
+- ✅ `/v1/generateContent` – [Google Gemini API](../../docs/generateContent) compatible endpoint
All endpoints support:
- Streaming and non-streaming responses
@@ -172,4 +165,4 @@ LiteLLM automatically maps OpenAI's `reasoning_effort` parameter to Gemini's `th
| `medium` | `medium` | Balanced reasoning for moderate complexity |
| `high` | `high` | Maximum reasoning depth, complex problems |
| `disable` | `minimal` | Disable extended reasoning |
-| `none` | `minimal` | No extended reasoning |
\ No newline at end of file
+| `none` | `minimal` | No extended reasoning |
diff --git a/docs/my-website/blog/gemini_3_flash/index.md b/docs/my-website/blog/gemini_3_flash/index.md
index 830c21e5f66..5e98d2136b4 100644
--- a/docs/my-website/blog/gemini_3_flash/index.md
+++ b/docs/my-website/blog/gemini_3_flash/index.md
@@ -3,18 +3,9 @@ slug: gemini_3_flash
title: "DAY 0 Support: Gemini 3 Flash on LiteLLM"
date: 2025-12-17T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - sameer
+ - krrish
+ - ishaan-alt
description: "Guide to using Gemini 3 Flash on LiteLLM Proxy and SDK with day 0 support."
tags: [gemini, day 0 support, llms]
hide_table_of_contents: false
@@ -32,6 +23,8 @@ LiteLLM now supports `gemini-3-flash-preview` and all the new API changes along
If you only want cost tracking, you need no change in your current Litellm version. But if you want the support for new features introduced along with it like thinking levels, you will need to use v1.80.8-stable.1 or above.
:::
+{/* truncate */}
+
## Deploy this version
@@ -80,7 +73,7 @@ LiteLLM provides **full end-to-end support** for Gemini 3 Flash on:
- ✅ `/v1/chat/completions` - OpenAI-compatible chat completions endpoint
- ✅ `/v1/responses` - OpenAI Responses API endpoint (streaming and non-streaming)
- ✅ [`/v1/messages`](../../docs/anthropic_unified) - Anthropic-compatible messages endpoint
-- ✅ `/v1/generateContent` – [Google Gemini API](../../docs/generateContent.md) compatible endpoint
+- ✅ `/v1/generateContent` – [Google Gemini API](../../docs/generateContent) compatible endpoint
All endpoints support:
- Streaming and non-streaming responses
- Function calling with thought signatures
@@ -252,4 +245,3 @@ If using this model via vertex_ai, keep the location as global as this is the on
| `high` | `high` |
| `disable` | `minimal` |
| `none` | `minimal` |
-
diff --git a/docs/my-website/blog/gemini_embedding_2_multimodal/index.md b/docs/my-website/blog/gemini_embedding_2_multimodal/index.md
index 8c09432e3b6..d66de1b6c79 100644
--- a/docs/my-website/blog/gemini_embedding_2_multimodal/index.md
+++ b/docs/my-website/blog/gemini_embedding_2_multimodal/index.md
@@ -3,10 +3,7 @@ slug: gemini_embedding_2_multimodal
title: "Gemini Embedding 2 Preview: Multimodal Embeddings on LiteLLM"
date: 2025-03-11T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
+ - sameer
description: "Generate embeddings from text, images, audio, video, and PDFs with gemini-embedding-2-preview on LiteLLM via Gemini API and Vertex AI."
tags: [gemini, embeddings, multimodal, vertex ai]
hide_table_of_contents: false
@@ -19,6 +16,8 @@ import TabItem from '@theme/TabItem';
LiteLLM now supports **multimodal embeddings** with `gemini-embedding-2-preview`—generating a single embedding from a mix of text, images, audio, video, and PDF content. Available via both the **Gemini API** (API key) and **Vertex AI** (GCP credentials).
+{/* truncate */}
+
## Supported Input Types
| Modality | Supported Formats |
diff --git a/docs/my-website/blog/gpt_5_3_codex/index.md b/docs/my-website/blog/gpt_5_3_codex/index.md
index 850586538f6..1dfab1f7ac7 100644
--- a/docs/my-website/blog/gpt_5_3_codex/index.md
+++ b/docs/my-website/blog/gpt_5_3_codex/index.md
@@ -3,18 +3,9 @@ slug: gpt_5_3_codex
title: "Day 0 Support: GPT-5.3-Codex"
date: 2026-02-24T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - sameer
+ - krrish
+ - ishaan-alt
description: "Day 0 support for GPT-5.3-Codex on LiteLLM, including phase parameter handling for Responses API."
tags: [openai, gpt-5.3-codex, codex, day 0 support]
hide_table_of_contents: false
@@ -25,6 +16,8 @@ import TabItem from '@theme/TabItem';
LiteLLM now supports GPT-5.3-Codex on Day 0, including support for the new assistant `phase` metadata on Responses API output items.
+{/* truncate */}
+
## Why `phase` matters for GPT-5.3-Codex
`phase` appears on assistant output items and helps distinguish preamble/commentary turns from final closeout responses.
diff --git a/docs/my-website/blog/gpt_5_4/index.md b/docs/my-website/blog/gpt_5_4/index.md
index de099736f00..4f7e4344157 100644
--- a/docs/my-website/blog/gpt_5_4/index.md
+++ b/docs/my-website/blog/gpt_5_4/index.md
@@ -3,18 +3,9 @@ slug: gpt_5_4
title: "Day 0 Support: GPT-5.4"
date: 2026-03-05T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - sameer
+ - krrish
+ - ishaan-alt
description: "GPT-5.4 model support in LiteLLM"
tags: [openai, gpt-5.4, completion]
hide_table_of_contents: false
@@ -25,6 +16,8 @@ import TabItem from '@theme/TabItem';
LiteLLM now supports fully GPT-5.4!
+{/* truncate */}
+
## Docker Image
```bash
diff --git a/docs/my-website/blog/gpt_5_4_mini_nano/index.md b/docs/my-website/blog/gpt_5_4_mini_nano/index.md
new file mode 100644
index 00000000000..6d7c2b33f72
--- /dev/null
+++ b/docs/my-website/blog/gpt_5_4_mini_nano/index.md
@@ -0,0 +1,106 @@
+---
+slug: gpt_5_4_mini_nano
+title: "Day 0 Support: GPT-5.4-mini and GPT-5.4-nano"
+date: 2026-03-17T10:00:00
+authors:
+ - name: Sameer Kankute
+ title: SWE @ LiteLLM (LLM Translation)
+ url: https://www.linkedin.com/in/sameer-kankute/
+ image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
+ - name: Krrish Dholakia
+ title: "CEO, LiteLLM"
+ url: https://www.linkedin.com/in/krish-d/
+ image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
+ - name: Ishaan Jaff
+ title: "CTO, LiteLLM"
+ url: https://www.linkedin.com/in/reffajnaahsi/
+ image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+description: "GPT-5.4-mini and GPT-5.4-nano model support in LiteLLM"
+tags: [openai, gpt-5.4-mini, gpt-5.4-nano, completion]
+hide_table_of_contents: false
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+LiteLLM now supports GPT-5.4-mini and GPT-5.4-nano — cost-effective models for simple completions and high-throughput workloads.
+
+:::note
+If you're on **v1.82.3-stable** or above, you don't need any update to use these models.
+:::
+
+## Usage
+
+
+
+
+**1. Setup config.yaml**
+
+```yaml
+model_list:
+ - model_name: gpt-5.4-mini
+ litellm_params:
+ model: openai/gpt-5.4-mini
+ api_key: os.environ/OPENAI_API_KEY
+ - model_name: gpt-5.4-nano
+ litellm_params:
+ model: openai/gpt-5.4-nano
+ api_key: os.environ/OPENAI_API_KEY
+```
+
+**2. Start the proxy**
+
+```bash
+litellm --config /path/to/config.yaml
+```
+
+**3. Test it**
+
+```bash
+# GPT-5.4-mini
+curl -X POST "http://localhost:4000/v1/chat/completions" \
+ -H "Content-Type: application/json" \
+ -H "Authorization: Bearer $LITELLM_KEY" \
+ -d '{
+ "model": "gpt-5.4-mini",
+ "messages": [{"role": "user", "content": "What is the capital of France?"}]
+ }'
+
+# GPT-5.4-nano
+curl -X POST "http://localhost:4000/v1/chat/completions" \
+ -H "Content-Type: application/json" \
+ -H "Authorization: Bearer $LITELLM_KEY" \
+ -d '{
+ "model": "gpt-5.4-nano",
+ "messages": [{"role": "user", "content": "What is 2 + 2?"}]
+ }'
+```
+
+
+
+
+```python
+from litellm import completion
+
+# GPT-5.4-mini
+response = completion(
+ model="openai/gpt-5.4-mini",
+ messages=[{"role": "user", "content": "What is the capital of France?"}],
+)
+print(response.choices[0].message.content)
+
+# GPT-5.4-nano
+response = completion(
+ model="openai/gpt-5.4-nano",
+ messages=[{"role": "user", "content": "What is 2 + 2?"}],
+)
+print(response.choices[0].message.content)
+```
+
+
+
+
+## Notes
+
+- Both models support function calling, vision, and tool-use — see the [OpenAI provider docs](../../docs/providers/openai) for advanced usage.
+- GPT-5.4-nano is the most cost-effective option for simple tasks; GPT-5.4-mini offers a balance of speed and capability.
diff --git a/docs/my-website/blog/guardrail_logging_secret_exposure_incident/index.md b/docs/my-website/blog/guardrail_logging_secret_exposure_incident/index.md
new file mode 100644
index 00000000000..71f9e3da011
--- /dev/null
+++ b/docs/my-website/blog/guardrail_logging_secret_exposure_incident/index.md
@@ -0,0 +1,78 @@
+---
+slug: guardrail-logging-secret-exposure-incident
+title: "Incident Report: Guardrail logging exposed secret headers in spend logs and traces"
+date: 2026-03-18T10:00:00
+authors:
+ - litellm
+tags: [incident-report, security, guardrails]
+hide_table_of_contents: false
+---
+
+**Date:** March 18, 2026
+**Duration:** Unknown
+**Severity:** High
+**Status:** Resolved
+
+## Summary
+
+When a custom guardrail returned the full LiteLLM request/data dictionary, the guardrail response logged by LiteLLM could include `secret_fields.raw_headers`, including plaintext `Authorization` headers containing API keys or other credentials.
+
+This information could then propagate to logging and observability surfaces that consume guardrail metadata, including:
+
+- **Spend logs in the LiteLLM UI:** visible to admins with access to spend-log data
+- **OpenTelemetry traces:** visible to anyone with access to the relevant telemetry backend
+
+LLM calls, proxy routing, and provider execution were not blocked by this bug. The impact was exposure of sensitive request headers in observability and logging paths.
+
+{/* truncate */}
+
+---
+
+## Background
+
+LiteLLM keeps internal request data (including request headers) for use during the call. That data is not meant to be written to logs or telemetry.
+
+When custom guardrails run, their outcomes are logged so they can appear in spend logs, OpenTelemetry traces, and other observability backends. If a guardrail returned the full request payload instead of a minimal result, that internal request data could be included in what was logged. Before the fix, the guardrail logging path did not strip that data before sending it to those systems.
+
+```mermaid
+flowchart TD
+ inboundRequest["1. Incoming proxy request"] --> storeSecrets["2. Store internal request data"]
+ storeSecrets --> guardrailRuns["3. Custom guardrail runs"]
+ guardrailRuns --> fullDataReturn["4. Guardrail returns full request payload"]
+ fullDataReturn --> loggingBuild["5. Build guardrail log payload"]
+ loggingBuild --> spendLogs["6a. Persist to spend logs / UI"]
+ loggingBuild --> otelTraces["6b. Attach to OTEL guardrail spans"]
+```
+
+---
+
+## Root Cause
+
+The root cause was incomplete sanitization in the guardrail logging path. When building the payload that gets sent to spend logs and traces, LiteLLM prepared guardrail responses for logging but did not strip internal request data (such as headers) from them. If a guardrail returned a response that included that data, it was passed through to the logging and observability systems unchanged.
+
+---
+
+## Impact
+
+This issue required all of the following:
+
+1. A custom guardrail returned the full LiteLLM request/data dictionary, or another response object containing `secret_fields`.
+2. LiteLLM logged that guardrail response through the standard guardrail logging path.
+3. An operator, admin, or telemetry consumer had access to the resulting logs or traces.
+
+When those conditions were met, sensitive values could become visible through:
+
+- **Spend logs / UI responses:** guardrail metadata could be included in spend-log payloads rendered in the admin UI.
+- **OpenTelemetry traces:** `guardrail_response` could be written as a span attribute on guardrail spans.
+- **Other downstream observability backends:** any integration consuming the same guardrail metadata could receive the leaked values.
+
+This was a logging and telemetry exposure bug. It did not let callers bypass auth, access other tenants directly, or change model behavior, but it could expose plaintext credentials to people with access to those observability systems.
+
+---
+
+## Guidance For Users
+
+- Upgrade to LiteLLM 1.82.3+.
+- If you operated custom guardrails that return the full request/data dict, review whether spend logs or telemetry traces were retained during the affected period.
+- Rotate any credentials that may have appeared in `Authorization` or other forwarded request headers in those systems.
+- Apply least-privilege access controls to spend-log views and telemetry backends that may contain request-derived metadata.
diff --git a/docs/my-website/blog/httpx_cache_eviction_incident/index.md b/docs/my-website/blog/httpx_cache_eviction_incident/index.md
index 9e6152d0e63..7fc3789a91d 100644
--- a/docs/my-website/blog/httpx_cache_eviction_incident/index.md
+++ b/docs/my-website/blog/httpx_cache_eviction_incident/index.md
@@ -3,17 +3,9 @@ slug: httpx-cache-eviction-incident
title: "Incident Report: Cache Eviction Closes In-Use httpx Clients"
date: 2026-02-27T10:00:00
authors:
- - name: Ryan Crabbe
- title: Performance Engineer, LiteLLM
- url: https://www.linkedin.com/in/ryan-crabbe-0b9687214
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
+ - ryan
+ - ishaan-alt
+ - krrish
tags: [incident-report, caching, stability]
hide_table_of_contents: false
---
@@ -31,6 +23,8 @@ A change to improve Redis connection pool cleanup introduced a regression that c
**Impact:** Any proxy instance that hit the cache TTL (default 10 minutes) or capacity limit (200 entries) would have its httpx clients closed out from under it, causing requests to LLM providers to fail with connection errors.
+{/* truncate */}
+
---
## Background
diff --git a/docs/my-website/blog/litellm_observatory/index.md b/docs/my-website/blog/litellm_observatory/index.md
index 4554f77fb85..36366e5de22 100644
--- a/docs/my-website/blog/litellm_observatory/index.md
+++ b/docs/my-website/blog/litellm_observatory/index.md
@@ -3,18 +3,9 @@ slug: litellm-observatory
title: "Improve release stability with 24 hour load tests"
date: 2026-02-06T10:00:00
authors:
- - name: Alexsander Hamir
- title: "Performance Engineer, LiteLLM"
- url: https://www.linkedin.com/in/alexsander-baptista/
- image_url: https://github.com/AlexsanderHamir.png
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - alexsander
+ - krrish
+ - ishaan-alt
description: "How we built a long-running, release-validation system to catch regressions before they reach users."
tags: [testing, observability, reliability, releases]
hide_table_of_contents: false
@@ -28,6 +19,8 @@ As LiteLLM adoption has grown, so have expectations around reliability, performa
This post introduces **LiteLLM Observatory**, a long-running release-validation system we built to catch regressions before they reach users.
+{/* truncate */}
+
---
## Why We Built the Observatory
@@ -133,4 +126,3 @@ Reliability is an ongoing investment.
LiteLLM Observatory is one of several systems we’re building to continuously raise the bar on release quality and operational safety. As LiteLLM evolves, so will our validation tooling, informed by real-world usage and lessons learned.
We’ll continue to share those improvements openly as we go.
-
diff --git a/docs/my-website/blog/minimax_m2_5/index.md b/docs/my-website/blog/minimax_m2_5/index.md
index 50084fcc1e5..9bccbdf7979 100644
--- a/docs/my-website/blog/minimax_m2_5/index.md
+++ b/docs/my-website/blog/minimax_m2_5/index.md
@@ -3,18 +3,9 @@ slug: minimax_m2_5
title: "Day 0 Support: MiniMax-M2.5"
date: 2026-02-12T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - sameer
+ - krrish
+ - ishaan-alt
description: "Day 0 support for MiniMax-M2.5 on LiteLLM"
tags: [minimax, M2.5, llm]
hide_table_of_contents: false
@@ -25,6 +16,8 @@ import TabItem from '@theme/TabItem';
LiteLLM now supports MiniMax-M2.5 on Day 0. Use it across OpenAI-compatible and Anthropic-compatible APIs through the LiteLLM AI Gateway.
+{/* truncate */}
+
## Supported Models
LiteLLM supports the following MiniMax models:
diff --git a/docs/my-website/blog/model_cost_map_incident/index.md b/docs/my-website/blog/model_cost_map_incident/index.md
index b9ff20e4128..5b4499cc31c 100644
--- a/docs/my-website/blog/model_cost_map_incident/index.md
+++ b/docs/my-website/blog/model_cost_map_incident/index.md
@@ -3,10 +3,7 @@ slug: model-cost-map-incident
title: "Incident Report: Invalid model cost map on main"
date: 2026-02-10T10:00:00
authors:
- - name: Ishaan Jaffer
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/ishaanjaffer/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - ishaan
tags: [incident-report, stability]
hide_table_of_contents: false
---
diff --git a/docs/my-website/blog/realtime_webrtc_http_endpoints/index.md b/docs/my-website/blog/realtime_webrtc_http_endpoints/index.md
index 04c3d3c9097..70fc5b2c48e 100644
--- a/docs/my-website/blog/realtime_webrtc_http_endpoints/index.md
+++ b/docs/my-website/blog/realtime_webrtc_http_endpoints/index.md
@@ -3,18 +3,9 @@ slug: realtime_webrtc_http_endpoints
title: "Realtime WebRTC HTTP Endpoints"
date: 2026-03-12T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - sameer
+ - krrish
+ - ishaan-alt
description: "Use the LiteLLM proxy to route OpenAI-style WebRTC realtime via HTTP: client_secrets and SDP exchange."
tags: [realtime, webrtc, proxy, openai]
hide_table_of_contents: false
@@ -24,6 +15,8 @@ import WebRTCTester from '@site/src/components/WebRTCTester';
Connect to the Realtime API via WebRTC from browser/mobile clients. LiteLLM handles auth and key management.
+{/* truncate */}
+
## How it works

@@ -116,4 +109,3 @@ A: Set the correct `api_version` in `litellm_params` (or via the `AZURE_API_VERS
**Q: What if I get no audio?**
A: Make sure you grant microphone permission, ensure `pc.ontrack` assigns the audio element with `autoplay` enabled, check your network/firewall for WebRTC traffic, and inspect the browser console for ICE or SDP errors.
-
diff --git a/docs/my-website/blog/responses_api_encrypted_content_incident/index.md b/docs/my-website/blog/responses_api_encrypted_content_incident/index.md
index 19b55898caa..fd5a9e76c42 100644
--- a/docs/my-website/blog/responses_api_encrypted_content_incident/index.md
+++ b/docs/my-website/blog/responses_api_encrypted_content_incident/index.md
@@ -3,18 +3,9 @@ slug: responses-api-encrypted-content-incident
title: "Incident Report: Encrypted Content Failures in Multi-Region Responses API Load Balancing"
date: 2026-02-24T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - sameer
+ - krrish
+ - ishaan-alt
tags: [incident-report, proxy, responses-api, load-balancing]
hide_table_of_contents: false
---
diff --git a/docs/my-website/blog/security_townhall_updates/index.md b/docs/my-website/blog/security_townhall_updates/index.md
new file mode 100644
index 00000000000..b997de9c185
--- /dev/null
+++ b/docs/my-website/blog/security_townhall_updates/index.md
@@ -0,0 +1,190 @@
+---
+slug: security-townhall-updates
+title: "Security Townhall Updates"
+date: 2026-03-27T12:00:00
+authors:
+ - krrish
+ - ishaan-alt
+description: "What happened, what we've done, and what comes next for LiteLLM's release and security processes."
+tags: [security, incident-report]
+hide_table_of_contents: false
+---
+
+import Image from '@theme/IdealImage';
+
+Thank you to everyone who joined our town hall.
+
+We wanted to use that time to walk through what we know, what we've done so far, and how we're improving LiteLLM's release and security processes going forward. This post is a written version of that update. [Slides available here](https://drive.google.com/file/d/17hsSG7nk-OYL7VRCTbTa7McrWREtS9OO/view?usp=sharing)
+
+{/* truncate */}
+
+## What happened
+
+On March 24, 2026 at 10:39 UTC, LiteLLM v1.82.7 was pushed to PyPI. Version v1.82.8 was published soon after. Those packages were live for about 40 minutes before being quarantined by PyPI. By 16:00 UTC, the LiteLLM team had worked with PyPI to delete the affected packages.
+
+At this point, our understanding is that this was a supply-chain incident affecting those two published versions.
+
+## How did this happen?
+
+Our understanding is that the issue came from the [compromised Trivy security scanner](https://www.aquasec.com/blog/trivy-supply-chain-attack-what-you-need-to-know/) dependency in our CI/CD pipeline.
+
+
+
+There were three major contributing factors:
+
+### 1. Shared CI/CD environment
+
+At the time, everything was running on CircleCI, and all steps shared a common environment. That increased blast radius: if one component was compromised, it could potentially access credentials or context intended for other parts of the pipeline.
+
+### 2. Static credentials in environment variables
+
+Release credentials, including credentials for PyPI, GHCR, and Docker publishing, were available as static secrets in the environment. That meant a compromised step could access long-lived release credentials.
+
+### 3. Unpinned Trivy dependency
+
+In our security scanning component, we had an unpinned Trivy dependency. Our present understanding is that a compromised Trivy package ran during the scan, had access to environment variables, and enabled attackers to obtain those credentials.
+
+**In summary:** a compromised package in CI had access to secrets it should not have had, and those secrets were then used in the release path.
+
+## What we've already done
+
+
+In the last 3 days, we've taken the following steps:
+
+### 1. Minimize Scope of Impact
+
+#### Prevented further key abuse
+
+We deleted or rotated all impacted or adjacent secret keys, including PyPI, GitHub, Docker, and related credentials. Out of an abundance of caution, we've also rotated LiteLLM maintainer accounts.
+
+#### Prevent branch attacks
+
+We removed roughly 6,000 open branches and added an auto-deletion policy for branches merged into `main`. This reduces the surface area for branch-based abuse.
+
+#### Pinned CI/CD dependencies
+
+We've pinned all Github Actions, and are working on pinning all CircleCI dependencies as well.
+
+#### Paused releases
+
+We've paused new releases until we've confirmed codebase security and put stronger release controls in place.
+
+### 2. Secured LiteLLM
+
+#### Forensic analysis
+
+We are working with Google's Mandiant cybersecurity team to confirm the source of the attack and verify the security of the codebase. We also confirmed that no malicious code was pushed to `main`.
+
+#### Confirm Application Security
+
+In parallel, we are working with whitehat hackers at [Veria Labs](https://verialabs.com/) to verify application security and review improvements to our CI/CD process.
+
+We have also confirmed that the last 20 LiteLLM releases contain no indicators of compromise, and that no unauthenticated attacks can be made against LiteLLM Proxy based on our current investigation. [Check Security Blog for release verification.](https://docs.litellm.ai/blog/security-update-march-2026#verified-safe-versions)
+
+#### Created a security working group
+
+We created a new security working group inside LiteLLM focused on:
+
+- Building threat models
+- Auditing the build process and dependencies
+
+If you're interested in joining the security working group, please file an issue [here](https://github.com/BerriAI/litellm-security-wg).
+
+### 3. Improved CI/CD
+
+We've already begun making structural changes to how releases are built and published. These align with our goals (covered in the next section) around isolated environments, ephemeral credentials, and release auditing.
+
+## Roadmap
+
+We plan on following 4 guiding principles for our new CI/CD pipeline:
+
+1. **Limit** what each package can access
+2. **Reduce** the number of sensitive environment variables
+3. **Avoid** compromised packages
+4. **Prevent** release tampering
+
+
+### Isolated environments
+
+
+
+We are breaking our CI/CD into 4 semantic concepts:
+
+1. Unit tests
+2. Integration tests
+3. Security scans
+4. Release publishing
+
+And will be running each of these in isolated environments.
+
+This will limit the damage that any single compromised component can cause.
+
+### Ephemeral credentials
+
+We plan to move to ephemeral credentials for PyPI (Trusted Publisher) and GHCR (Token-based authentication) releases. This will reduce the risk of credentials being leaked or compromised.
+
+We have already begun doing this:
+
+- PyPI Trusted Publisher on GitHub Actions [PR](https://github.com/BerriAI/litellm/pull/24654)
+- GHCR Token-based authentication on GitHub Actions [PR](https://github.com/BerriAI/litellm/pull/24683)
+
+### Release auditing
+
+Our goal is to allow users to independently verify that a release came from us and prevent silent modifications of releases after they are published.
+
+This will ensure, your releases are safe, even when:
+- Stolen PyPI/GHCR credentials are used to publish malicious releases
+- Tampered registry artifacts are published
+- Tag mutations are made after the release is published
+
+We believe that [Cosign](https://github.com/sigstore/cosign) is a good fit for this, and have already begun working on it [PR](https://github.com/BerriAI/litellm/pull/24683).
+
+
+### Avoid Compromised Packages
+
+- Move to pinned, verified SHAs for packages and actions used in CI/CD, avoiding `latest` wherever possible.
+- Add a cooldown period before upgrading to a new version of a package - allows more time to investigate and verify the new version.
+
+We've added zizmor to help us catch issues such as unpinned dependencies and credential leakage. [commit](https://github.com/BerriAI/litellm/commit/a671275f5c5b0e1fb1adacdf3b6ef779aaa5d56c).
+
+
+## Frequently Asked Questions
+
+**Q: Did you observe any lateral movement into your corporate environment during this incident?**
+
+A: No. Our investigation to date, conducted in coordination with external security experts, has found no evidence of lateral movement into our internal corporate systems. The incident was isolated to the CI/CD pipeline and the release path for specific versions (v1.82.7 and v1.82.8). As a proactive measure, we have rotated all potentially impacted or adjacent secrets—including PyPI, GitHub, and Docker credentials—and updated maintainer account security to ensure continued isolation.
+
+**Q: Do you expect delays in future product releases due to these new security measures?**
+
+A: We are committed to balancing security with speed. While we have temporarily paused releases to implement stronger controls, we are moving quickly to automate our new security protocols. We are currently implementing isolated CI/CD environments, ephemeral credentials (via Trusted Publishers), and release auditing with Cosign. These improvements are designed to be integrated into our automated pipeline, allowing us to maintain a fast release cadence while ensuring every package is verified and secure.
+
+**Q: Were older packages impacted?**
+
+Our current findings show no indicators of compromise in the last 20 versions of LiteLLM. This was manually verified by our team and independently reviewed by Veria Labs.
+
+We have also published the verified versions for users to use. [Check Security Blog for release verification.](https://docs.litellm.ai/blog/security-update-march-2026#verified-safe-versions)
+
+
+
+## Questions & Support
+
+If you believe your systems may be affected, contact us immediately:
+
+- **Security:** security@berri.ai
+- **Support:** support@berri.ai
+- **Slack:** Reach out to the LiteLLM team directly [here](https://join.slack.com/t/litellmossslack/shared_invite/zt-3o7nkuyfr-p_kbNJj8taRfXGgQI1~YyA)
+
+## Hiring
+
+We are currently hiring for:
+
+- DevOps Engineer - to keep ci/cd secure and running smoothly
+- Security Engineer - to keep the application secure
+
+If you're interest in joining, please apply [here](https://jobs.ashbyhq.com/litellm)
\ No newline at end of file
diff --git a/docs/my-website/blog/security_townhall_updates/shared_ci_cd_environment.png b/docs/my-website/blog/security_townhall_updates/shared_ci_cd_environment.png
new file mode 100644
index 00000000000..29ec195b7fb
Binary files /dev/null and b/docs/my-website/blog/security_townhall_updates/shared_ci_cd_environment.png differ
diff --git a/docs/my-website/blog/security_update_march_2026/index.md b/docs/my-website/blog/security_update_march_2026/index.md
new file mode 100644
index 00000000000..1c298fe372f
--- /dev/null
+++ b/docs/my-website/blog/security_update_march_2026/index.md
@@ -0,0 +1,786 @@
+---
+slug: security-update-march-2026
+title: "Security Update: Suspected Supply Chain Incident"
+date: 2026-03-24T14:00:00
+authors:
+ - krrish
+ - ishaan-alt
+description: "As of 2:00 PM ET on March 24, 2026"
+tags: [security, incident-report]
+hide_table_of_contents: false
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+import VersionVerificationTable from '@site/src/components/VersionVerificationTable';
+
+> **Status:** Active investigation
+> **Last updated:** March 27, 2026
+
+> **Update (March 30):** A new **clean** version of LiteLLM is now available (v1.83.0). This was released by our new [CI/CD v2](https://docs.litellm.ai/blog/ci-cd-v2-improvements) pipeline which added isolated environments, stronger security gates, and safer release separation for LiteLLM.
+
+> **Update (March 27):** Review Townhall updates, including explanation of the incident, what we've done, and what comes next. [Learn more](https://docs.litellm.ai/blog/security-townhall-updates)
+
+> **Update (March 27):** Added [Verified safe versions](#verified-safe-versions) section with SHA-256 checksums for all audited PyPI and Docker releases.
+
+> **Update (March 26):** Added `checkmarx[.]zone` to [Indicators of compromise](#indicators-of-compromise-iocs)
+
+> **Update (March 25):** Added community-contributed scripts for scanning GitHub Actions and GitLab CI pipelines for the compromised versions. See [How to check if you are affected](#how-to-check-if-you-are-affected). s/o [@Zach Fury](https://www.linkedin.com/in/fryware/) for these scripts.
+
+
+## TLDR;
+- The compromised PyPI packages were **litellm==1.82.7** and **litellm==1.82.8**. Those packages were live on March 24, 2026 from 10:39 UTC for about 40 minutes before being quarantined by PyPI.
+- We believe that the compromise originated from the [Trivy dependency](https://www.aquasec.com/blog/trivy-supply-chain-attack-what-you-need-to-know/) used in our CI/CD security scanning workflow.
+- Customers running the official LiteLLM Proxy Docker image were not impacted. That deployment path pins dependencies in requirements.txt and does not rely on the compromised PyPI packages.
+- ~~We have paused all new LiteLLM releases until we complete a broader supply-chain review and confirm the release path is safe.~~ **Updated:** We have now released a new **safe** version of LiteLLM (v1.83.0) by our new [CI/CD v2](https://docs.litellm.ai/blog/ci-cd-v2-improvements) pipeline which added isolated environments, stronger security gates, and safer release separation for LiteLLM. We have also verified the codebase is safe and no malicious code was pushed to `main`.
+
+
+## Overview
+
+LiteLLM AI Gateway is investigating a suspected supply chain attack involving unauthorized PyPI package publishes. Current evidence suggests a maintainer's PyPI account may have been compromised and used to distribute malicious code.
+
+At this time, we believe this incident may be linked to the broader [Trivy security compromise](https://www.aquasec.com/blog/trivy-supply-chain-attack-what-you-need-to-know/), in which stolen credentials were reportedly used to gain unauthorized access to the LiteLLM publishing pipeline.
+
+This investigation is ongoing. Details below may change as we confirm additional findings.
+
+## Confirmed affected versions
+
+The following LiteLLM versions published to PyPI were impacted:
+
+- **v1.82.7**: contained a malicious payload in the LiteLLM AI Gateway `proxy_server.py`
+- **v1.82.8**: contained `litellm_init.pth` and a malicious payload in the LiteLLM AI Gateway `proxy_server.py`
+
+If you installed or ran either of these versions, review the recommendations below immediately.
+
+Note: These versions have already been removed from PyPI.
+
+## What happened
+
+Initial evidence suggests the attacker bypassed official CI/CD workflows and uploaded malicious packages directly to PyPI.
+
+These compromised versions appear to have included a credential stealer designed to:
+
+- Harvest secrets by scanning for:
+ - environment variables
+ - SSH keys
+ - cloud provider credentials (AWS, GCP, Azure)
+ - Kubernetes tokens
+ - database passwords
+- Encrypt and exfiltrate data via a `POST` request to `models.litellm.cloud`, which is **not** an official BerriAI / LiteLLM domain
+
+## Who is affected
+
+You may be affected if **any** of the following are true:
+
+- You installed or upgraded LiteLLM via `pip` on **March 24, 2026**, between **10:39 UTC and 16:00 UTC**
+- You ran `pip install litellm` without pinning a version and received **v1.82.7** or **v1.82.8**
+- You built a Docker image during this window that included `pip install litellm` without a pinned version
+- A dependency in your project pulled in LiteLLM as a transitive, unpinned dependency
+ (for example through AI agent frameworks, MCP servers, or LLM orchestration tools)
+
+You are **not** affected if any of the following are true:
+
+**LiteLLM AI Gateway/Proxy users:** Customers running the official LiteLLM Proxy Docker image were not impacted. That deployment path pins dependencies in requirements.txt and does not rely on the compromised PyPI packages.
+
+- You are using **LiteLLM Cloud**
+- You are using the official LiteLLM AI Gateway Docker image: `ghcr.io/berriai/litellm`
+- You are on **v1.82.6 or earlier** and did not upgrade during the affected window
+- You installed LiteLLM from source via the GitHub repository, which was **not** compromised
+
+
+### How to check if you are affected
+
+
+
+
+```bash
+pip show litellm
+```
+
+
+
+Go to the proxy base url, and check the version of the installed LiteLLM.
+
+
+
+
+
+Scans all repositories in a GitHub organization for workflow jobs that installed the compromised versions.
+
+**Requirements:** Python 3 and `requests` (`pip install requests`).
+
+**Setup:**
+
+```bash
+export GITHUB_TOKEN="your-github-pat"
+```
+
+**Run:**
+
+```bash
+python find_litellm_github.py
+```
+
+Set the `ORG` variable in the script to your GitHub organization name.
+
+Both scripts default to scanning jobs from **today**. Adjust the `WINDOW_START` and `WINDOW_END` constants to cover **March 24, 2026** (the incident date) if running on a different day.
+
+
+View full script (find_litellm_github.py)
+
+```python
+#!/usr/bin/env python3
+"""
+Scan all GitHub Actions jobs in a GitHub org that ran between
+0800-1244 UTC today and identify any that installed litellm 1.82.7 or 1.82.8.
+
+Adjust WINDOW_START / WINDOW_END to cover March 24, 2026 if running later.
+"""
+
+import io
+import os
+import re
+import sys
+import zipfile
+from concurrent.futures import ThreadPoolExecutor, as_completed
+from datetime import datetime, timezone
+
+import requests
+
+GITHUB_URL = "https://api.github.com"
+ORG = "your-org" # <-- set to your GitHub organization
+TOKEN = os.environ.get("GITHUB_TOKEN", "")
+
+TODAY = datetime.now(timezone.utc).date()
+WINDOW_START = datetime(TODAY.year, TODAY.month, TODAY.day, 8, 0, 0, tzinfo=timezone.utc)
+WINDOW_END = datetime(TODAY.year, TODAY.month, TODAY.day, 12, 44, 0, tzinfo=timezone.utc)
+
+TARGET_VERSIONS = {"1.82.7", "1.82.8"}
+VERSION_PATTERN = re.compile(r"litellm[=\-](\d+\.\d+\.\d+)", re.IGNORECASE)
+
+SESSION = requests.Session()
+SESSION.headers.update({
+ "Authorization": f"Bearer {TOKEN}",
+ "Accept": "application/vnd.github+json",
+ "X-GitHub-Api-Version": "2022-11-28",
+})
+
+
+def get_paginated(url, params=None):
+ params = dict(params or {})
+ params.setdefault("per_page", 100)
+ page = 1
+ while True:
+ params["page"] = page
+ resp = SESSION.get(url, params=params, timeout=30)
+ if resp.status_code == 404:
+ return
+ resp.raise_for_status()
+ data = resp.json()
+ if isinstance(data, dict):
+ items = next((v for v in data.values() if isinstance(v, list)), [])
+ else:
+ items = data
+ if not items:
+ break
+ yield from items
+ if len(items) < params["per_page"]:
+ break
+ page += 1
+
+
+def parse_ts(ts_str):
+ if not ts_str:
+ return None
+ return datetime.fromisoformat(ts_str.replace("Z", "+00:00"))
+
+
+def get_repos():
+ repos = []
+ for r in get_paginated(f"{GITHUB_URL}/orgs/{ORG}/repos", {"type": "all"}):
+ repos.append({"id": r["id"], "name": r["name"], "full_name": r["full_name"]})
+ return repos
+
+
+def get_runs_in_window(repo_full_name):
+ created_filter = (
+ f"{WINDOW_START.strftime('%Y-%m-%dT%H:%M:%SZ')}"
+ f"..{WINDOW_END.strftime('%Y-%m-%dT%H:%M:%SZ')}"
+ )
+ url = f"{GITHUB_URL}/repos/{repo_full_name}/actions/runs"
+ runs = []
+ for run in get_paginated(url, {"created": created_filter, "per_page": 100}):
+ ts = parse_ts(run.get("run_started_at") or run.get("created_at"))
+ if ts and WINDOW_START <= ts <= WINDOW_END:
+ runs.append(run)
+ return runs
+
+
+def get_jobs_for_run(repo_full_name, run_id):
+ url = f"{GITHUB_URL}/repos/{repo_full_name}/actions/runs/{run_id}/jobs"
+ jobs = []
+ for job in get_paginated(url, {"filter": "all"}):
+ ts = parse_ts(job.get("started_at"))
+ if ts and WINDOW_START <= ts <= WINDOW_END:
+ jobs.append(job)
+ return jobs
+
+
+def fetch_job_log(repo_full_name, job_id):
+ url = f"{GITHUB_URL}/repos/{repo_full_name}/actions/jobs/{job_id}/logs"
+ resp = SESSION.get(url, timeout=60, allow_redirects=True)
+ if resp.status_code in (403, 404, 410):
+ return ""
+ resp.raise_for_status()
+
+ content_type = resp.headers.get("Content-Type", "")
+ if "zip" in content_type or resp.content[:2] == b"PK":
+ try:
+ with zipfile.ZipFile(io.BytesIO(resp.content)) as zf:
+ parts = []
+ for name in sorted(zf.namelist()):
+ with zf.open(name) as f:
+ parts.append(f.read().decode("utf-8", errors="replace"))
+ return "\n".join(parts)
+ except zipfile.BadZipFile:
+ pass
+ return resp.text
+
+
+def check_job(repo_full_name, job):
+ job_id = job["id"]
+ job_name = job["name"]
+ run_id = job["run_id"]
+ started = job.get("started_at", "")
+
+ log_text = fetch_job_log(repo_full_name, job_id)
+ if not log_text:
+ return None
+
+ found_versions = set()
+ context_lines = []
+ for line in log_text.splitlines():
+ m = VERSION_PATTERN.search(line)
+ if m:
+ ver = m.group(1)
+ if ver in TARGET_VERSIONS:
+ found_versions.add(ver)
+ context_lines.append(line.strip())
+
+ if not found_versions:
+ return None
+
+ return {
+ "repo": repo_full_name,
+ "run_id": run_id,
+ "job_id": job_id,
+ "job_name": job_name,
+ "started_at": started,
+ "versions": sorted(found_versions),
+ "context": context_lines[:10],
+ "job_url": job.get("html_url", f"https://github.com/{repo_full_name}/actions/runs/{run_id}"),
+ }
+
+
+def main():
+ if not TOKEN:
+ print("ERROR: Set GITHUB_TOKEN environment variable.", file=sys.stderr)
+ sys.exit(1)
+
+ print(f"Time window : {WINDOW_START.isoformat()} -> {WINDOW_END.isoformat()}")
+ print(f"Hunting for : litellm {', '.join(sorted(TARGET_VERSIONS))}")
+ print()
+
+ print(f"Fetching repositories for org '{ORG}'...")
+ repos = get_repos()
+ print(f" Found {len(repos)} repositories")
+ print()
+
+ jobs_to_check = []
+
+ print("Scanning workflow runs for time window...")
+ for repo in repos:
+ full_name = repo["full_name"]
+ try:
+ runs = get_runs_in_window(full_name)
+ except requests.HTTPError as e:
+ print(f" WARN: {full_name} - {e}", file=sys.stderr)
+ continue
+ if not runs:
+ continue
+ print(f" {full_name}: {len(runs)} run(s) in window")
+ for run in runs:
+ try:
+ jobs = get_jobs_for_run(full_name, run["id"])
+ except requests.HTTPError as e:
+ print(f" WARN: run {run['id']} - {e}", file=sys.stderr)
+ continue
+ for job in jobs:
+ jobs_to_check.append((full_name, job))
+
+ total = len(jobs_to_check)
+ print(f"\nFetching logs for {total} job(s)...")
+ print()
+
+ hits = []
+ with ThreadPoolExecutor(max_workers=8) as pool:
+ futures = {
+ pool.submit(check_job, full_name, job): (full_name, job["id"])
+ for full_name, job in jobs_to_check
+ }
+ done = 0
+ for future in as_completed(futures):
+ done += 1
+ full_name, jid = futures[future]
+ try:
+ result = future.result()
+ except Exception as e:
+ print(f" ERROR {full_name} job {jid}: {e}", file=sys.stderr)
+ continue
+ if result:
+ hits.append(result)
+ print(
+ f" [{done}/{total}] {full_name} job {jid}" +
+ (f" *** HIT: litellm {result['versions']} ***" if result else ""),
+ flush=True,
+ )
+
+ print()
+ print("=" * 72)
+ print(f"RESULTS: {len(hits)} job(s) installed litellm {' or '.join(sorted(TARGET_VERSIONS))}")
+ print("=" * 72)
+
+ if not hits:
+ print("No matches found.")
+ return
+
+ for h in sorted(hits, key=lambda x: x["started_at"]):
+ print()
+ print(f" Repo : {h['repo']}")
+ print(f" Job : {h['job_name']} (#{h['job_id']})")
+ print(f" Run ID : {h['run_id']}")
+ print(f" Started : {h['started_at']}")
+ print(f" Versions : litellm {', '.join(h['versions'])}")
+ print(f" URL : {h['job_url']}")
+ print(f" Log lines :")
+ for line in h["context"]:
+ print(f" {line}")
+
+
+if __name__ == "__main__":
+ main()
+```
+
+
+
+
+
+
+Scans all projects in a GitLab group (including subgroups) for CI/CD jobs that installed the compromised versions.
+
+**Requirements:** Python 3 and `requests` (`pip install requests`).
+
+**Setup:**
+
+```bash
+export GITLAB_TOKEN="your-gitlab-pat"
+```
+
+**Run:**
+
+```bash
+python find_litellm_jobs.py
+```
+
+Set the `GROUP_NAME` variable in the script to your GitLab group name.
+
+Both scripts default to scanning jobs from **today**. Adjust the `WINDOW_START` and `WINDOW_END` constants to cover **March 24, 2026** (the incident date) if running on a different day.
+
+
+View full script (find_litellm_jobs.py)
+
+```python
+#!/usr/bin/env python3
+"""
+Scan all GitLab CI/CD jobs in a GitLab group that ran between
+0800-1244 UTC today and identify any that installed litellm 1.82.7 or 1.82.8.
+
+Adjust WINDOW_START / WINDOW_END to cover March 24, 2026 if running later.
+"""
+
+import os
+import re
+import sys
+from concurrent.futures import ThreadPoolExecutor, as_completed
+from datetime import datetime, timezone
+
+import requests
+
+GITLAB_URL = "https://gitlab.com"
+GROUP_NAME = "YourGroup" # <-- set to your GitLab group name
+TOKEN = os.environ.get("GITLAB_TOKEN", "")
+
+TODAY = datetime.now(timezone.utc).date()
+WINDOW_START = datetime(TODAY.year, TODAY.month, TODAY.day, 8, 0, 0, tzinfo=timezone.utc)
+WINDOW_END = datetime(TODAY.year, TODAY.month, TODAY.day, 12, 44, 0, tzinfo=timezone.utc)
+
+TARGET_VERSIONS = {"1.82.7", "1.82.8"}
+VERSION_PATTERN = re.compile(r"litellm[=\-](\d+\.\d+\.\d+)", re.IGNORECASE)
+
+HEADERS = {"PRIVATE-TOKEN": TOKEN}
+SESSION = requests.Session()
+SESSION.headers.update(HEADERS)
+
+
+def get_paginated(url, params=None):
+ params = dict(params or {})
+ params.setdefault("per_page", 100)
+ page = 1
+ while True:
+ params["page"] = page
+ resp = SESSION.get(url, params=params, timeout=30)
+ resp.raise_for_status()
+ data = resp.json()
+ if not data:
+ break
+ yield from data
+ if len(data) < params["per_page"]:
+ break
+ page += 1
+
+
+def get_group_id(group_name):
+ resp = SESSION.get(f"{GITLAB_URL}/api/v4/groups/{group_name}", timeout=30)
+ resp.raise_for_status()
+ return resp.json()["id"]
+
+
+def get_all_projects(group_id):
+ projects = []
+ for p in get_paginated(
+ f"{GITLAB_URL}/api/v4/groups/{group_id}/projects",
+ {"include_subgroups": "true", "archived": "false"},
+ ):
+ projects.append({"id": p["id"], "name": p["path_with_namespace"]})
+ return projects
+
+
+def parse_ts(ts_str):
+ if not ts_str:
+ return None
+ ts_str = ts_str.replace("Z", "+00:00")
+ return datetime.fromisoformat(ts_str)
+
+
+def jobs_in_window(project_id):
+ matching = []
+ url = f"{GITLAB_URL}/api/v4/projects/{project_id}/jobs"
+ params = {"per_page": 100, "scope[]": ["success", "failed", "canceled", "running"]}
+
+ page = 1
+ while True:
+ params["page"] = page
+ resp = SESSION.get(url, params=params, timeout=30)
+ if resp.status_code == 403:
+ return matching
+ resp.raise_for_status()
+ jobs = resp.json()
+ if not jobs:
+ break
+
+ stop_early = False
+ for job in jobs:
+ ts = parse_ts(job.get("started_at") or job.get("created_at"))
+ if ts is None:
+ continue
+ if ts > WINDOW_END:
+ continue
+ if ts < WINDOW_START:
+ stop_early = True
+ continue
+ matching.append(job)
+
+ if stop_early or len(jobs) < 100:
+ break
+ page += 1
+
+ return matching
+
+
+def fetch_trace(project_id, job_id):
+ url = f"{GITLAB_URL}/api/v4/projects/{project_id}/jobs/{job_id}/trace"
+ resp = SESSION.get(url, timeout=60)
+ if resp.status_code in (403, 404):
+ return ""
+ resp.raise_for_status()
+ return resp.text
+
+
+def check_job(project_name, project_id, job):
+ job_id = job["id"]
+ job_name = job["name"]
+ ref = job.get("ref", "")
+ started = job.get("started_at", job.get("created_at", ""))
+
+ trace = fetch_trace(project_id, job_id)
+ if not trace:
+ return None
+
+ found_versions = set()
+ for match in VERSION_PATTERN.finditer(trace):
+ ver = match.group(1)
+ if ver in TARGET_VERSIONS:
+ found_versions.add(ver)
+
+ if not found_versions:
+ return None
+
+ context_lines = []
+ for line in trace.splitlines():
+ if VERSION_PATTERN.search(line):
+ ver_match = VERSION_PATTERN.search(line)
+ if ver_match and ver_match.group(1) in TARGET_VERSIONS:
+ context_lines.append(line.strip())
+
+ return {
+ "project": project_name,
+ "project_id": project_id,
+ "job_id": job_id,
+ "job_name": job_name,
+ "ref": ref,
+ "started_at": started,
+ "versions": sorted(found_versions),
+ "context": context_lines[:10],
+ "job_url": f"{GITLAB_URL}/{project_name}/-/jobs/{job_id}",
+ }
+
+
+def main():
+ if not TOKEN:
+ print("ERROR: Set GITLAB_TOKEN environment variable.", file=sys.stderr)
+ sys.exit(1)
+
+ print(f"Time window : {WINDOW_START.isoformat()} -> {WINDOW_END.isoformat()}")
+ print(f"Hunting for : litellm {', '.join(sorted(TARGET_VERSIONS))}")
+ print()
+
+ print(f"Resolving group '{GROUP_NAME}'...")
+ group_id = get_group_id(GROUP_NAME)
+
+ print("Fetching projects...")
+ projects = get_all_projects(group_id)
+ print(f" Found {len(projects)} projects")
+ print()
+
+ all_jobs_to_check = []
+
+ print("Scanning job listings for time window...")
+ for proj in projects:
+ try:
+ jobs = jobs_in_window(proj["id"])
+ except requests.HTTPError as e:
+ print(f" WARN: {proj['name']} - {e}", file=sys.stderr)
+ continue
+ if jobs:
+ print(f" {proj['name']}: {len(jobs)} job(s) in window")
+ for j in jobs:
+ all_jobs_to_check.append((proj["name"], proj["id"], j))
+
+ total = len(all_jobs_to_check)
+ print(f"\nFetching traces for {total} job(s)...")
+ print()
+
+ hits = []
+ with ThreadPoolExecutor(max_workers=10) as pool:
+ futures = {
+ pool.submit(check_job, pname, pid, job): (pname, job["id"])
+ for pname, pid, job in all_jobs_to_check
+ }
+ done = 0
+ for future in as_completed(futures):
+ done += 1
+ pname, jid = futures[future]
+ try:
+ result = future.result()
+ except Exception as e:
+ print(f" ERROR checking {pname} job {jid}: {e}", file=sys.stderr)
+ continue
+ if result:
+ hits.append(result)
+ print(f" [{done}/{total}] checked {pname} job {jid}" +
+ (f" *** HIT: litellm {result['versions']} ***" if result else ""),
+ flush=True)
+
+ print()
+ print("=" * 72)
+ print(f"RESULTS: {len(hits)} job(s) installed litellm {' or '.join(sorted(TARGET_VERSIONS))}")
+ print("=" * 72)
+
+ if not hits:
+ print("No matches found.")
+ return
+
+ for h in sorted(hits, key=lambda x: x["started_at"]):
+ print()
+ print(f" Project : {h['project']}")
+ print(f" Job : {h['job_name']} (#{h['job_id']})")
+ print(f" Branch/tag: {h['ref']}")
+ print(f" Started : {h['started_at']}")
+ print(f" Versions : litellm {', '.join(h['versions'])}")
+ print(f" URL : {h['job_url']}")
+ print(f" Log lines :")
+ for line in h["context"]:
+ print(f" {line}")
+
+
+if __name__ == "__main__":
+ main()
+```
+
+
+
+
+
+
+*CI/CD scripts contributed by the community ([original gist](https://gist.github.com/fryz/93ec8d4898ffe5b5ac5706a208823ef3)). Review before running.*
+
+
+## Indicators of compromise (IoCs)
+
+Review affected systems for the following indicators:
+
+- `litellm_init.pth` present in your `site-packages`
+- Outbound traffic or requests to `models.litellm[.]cloud`
+ This domain is **not** affiliated with LiteLLM
+- Outbound traffic or requests to `checkmarx[.]zone`
+ This domain is **not** affiliated with LiteLLM
+
+
+## Immediate actions for affected users
+
+If you installed or ran **v1.82.7** or **v1.82.8**, take the following actions immediately.
+
+### 1. Rotate all secrets
+
+Treat any credentials present on the affected systems as compromised, including:
+
+- API keys
+- Cloud access keys
+- Database passwords
+- SSH keys
+- Kubernetes tokens
+- Any secrets stored in environment variables or configuration files
+
+### 2. Inspect your filesystem
+
+Check your `site-packages` directory for a file named `litellm_init.pth`:
+
+```bash
+find /usr/lib/python3.13/site-packages/ -name "litellm_init.pth"
+```
+
+If present:
+
+- remove it immediately
+- investigate the host for further compromise
+- preserve relevant artifacts if your security team is performing forensics
+
+### 3. Audit version history
+
+Review your:
+
+- Local environments
+- CI/CD pipelines
+- Docker builds
+- Deployment logs
+
+Confirm whether **v1.82.7** or **v1.82.8** was installed anywhere.
+
+Pin LiteLLM to a known safe version such as **v1.82.6 or earlier**, or to a later verified release once announced.
+
+
+## Response and remediation
+
+The LiteLLM AI Gateway team has already taken the following steps:
+
+- Removed compromised packages from PyPI
+- Rotated maintainer credentials and established new authorized maintainers
+- Engaged Google's Mandiant security team to assist with forensic analysis of the build and publishing chain
+
+
+## Verified safe versions
+
+We have audited every LiteLLM release published between v1.78.0 and v1.82.6 across both PyPI and Docker. Each artifact was verified by:
+
+1. Downloading the published artifact and computing its SHA-256 digest
+2. Scanning for the known [indicators of compromise](#indicators-of-compromise-iocs) (IOCs)
+3. Comparing the artifact contents against the corresponding Git commit in the BerriAI/litellm repository
+
+**All versions listed below are confirmed clean.**
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## Questions and support
+
+If you believe your systems may be affected, contact us immediately:
+
+- **Security:** `security@berri.ai`
+- **Support:** `support@berri.ai`
+- **Slack:** Reach out to the LiteLLM team directly
+
+For real-time updates, follow [LiteLLM (YC W23) on X](https://x.com/LiteLLM).
+
diff --git a/docs/my-website/blog/server_root_path/index.md b/docs/my-website/blog/server_root_path/index.md
index d7925baf6b4..13b7365cc9e 100644
--- a/docs/my-website/blog/server_root_path/index.md
+++ b/docs/my-website/blog/server_root_path/index.md
@@ -3,17 +3,9 @@ slug: server-root-path-incident
title: "Incident Report: SERVER_ROOT_PATH regression broke UI routing"
date: 2026-02-21T10:00:00
authors:
- - name: Yuneng Jiang
- title: SWE @ LiteLLM (Full Stack)
- url: https://www.linkedin.com/in/yunengjiang/
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
+ - yuneng
+ - ishaan-alt
+ - krrish
tags: [incident-report, ui, stability]
hide_table_of_contents: false
---
diff --git a/docs/my-website/blog/sub_millisecond_proxy_overhead/index.md b/docs/my-website/blog/sub_millisecond_proxy_overhead/index.md
index 1857383363c..7f8ac086a21 100644
--- a/docs/my-website/blog/sub_millisecond_proxy_overhead/index.md
+++ b/docs/my-website/blog/sub_millisecond_proxy_overhead/index.md
@@ -3,18 +3,9 @@ slug: sub-millisecond-proxy-overhead
title: "Achieving Sub-Millisecond Proxy Overhead"
date: 2026-02-02T10:00:00
authors:
- - name: Alexsander Hamir
- title: "Performance Engineer, LiteLLM"
- url: https://www.linkedin.com/in/alexsander-baptista/
- image_url: https://github.com/AlexsanderHamir.png
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - alexsander
+ - krrish
+ - ishaan-alt
description: "Our Q1 performance target and architectural direction for achieving sub-millisecond proxy overhead on modest hardware."
tags: [performance, architecture]
hide_table_of_contents: false
@@ -32,6 +23,8 @@ Proxy overhead refers to the latency introduced by LiteLLM itself, independent o
To measure it, we run the same workload directly against the provider and through LiteLLM at identical QPS (for example, 1,000 QPS) and compare the latency delta. To reduce noise, the load generator, LiteLLM, and a mock LLM endpoint all run on the same machine, ensuring the difference reflects proxy overhead rather than network latency.
+{/* truncate */}
+
---
## Where We're Coming From
diff --git a/docs/my-website/blog/vanta_compliance_recertification/index.md b/docs/my-website/blog/vanta_compliance_recertification/index.md
new file mode 100644
index 00000000000..d05c113967f
--- /dev/null
+++ b/docs/my-website/blog/vanta_compliance_recertification/index.md
@@ -0,0 +1,18 @@
+---
+slug: vanta-compliance-recertification
+title: "LiteLLM + Vanta: SOC 2 Type 2 and ISO 27001 Recertification"
+date: 2026-03-30T10:00:00
+authors:
+ - krrish
+description: "LiteLLM is partnering with Vanta on SOC 2 Type 2 and ISO 27001 recertification and engaging independent auditors for verification."
+tags: [security, compliance]
+hide_table_of_contents: true
+---
+
+
+
+We are partnering with [Vanta](https://www.vanta.com/) to recertify LiteLLM's compliance for SOC 2 Type 2 and ISO 27001.
+
+As part of this process, we are also identifying independent auditors to validate and verify our compliance posture.
+
+This is part of our commitment to being the most secure and transparent AI Gateway possible.
diff --git a/docs/my-website/blog/video_characters_litellm/index.md b/docs/my-website/blog/video_characters_litellm/index.md
index 263a17d7191..a0f87385d81 100644
--- a/docs/my-website/blog/video_characters_litellm/index.md
+++ b/docs/my-website/blog/video_characters_litellm/index.md
@@ -3,18 +3,9 @@ slug: video_characters_api
title: "New Video Characters, Edit and Extension API support"
date: 2026-03-16T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - sameer
+ - krrish
+ - ishaan-alt
description: "LiteLLM now supports creating, retrieving, and managing reusable video characters across multiple video generations."
tags: [videos, characters, proxy, routing]
hide_table_of_contents: false
@@ -22,6 +13,8 @@ hide_table_of_contents: false
LiteLLM now supoports videos character, edit and extension apis.
+{/* truncate */}
+
## What's New
Four new endpoints for video character operations:
@@ -125,4 +118,4 @@ Router knows exactly which deployment to use
**Behind the scenes:**
- Character ID format: `character_`
- Metadata includes: provider, model_id, original_character_id
-- Transparent to you - just use the ID, LiteLLM handles routing
\ No newline at end of file
+- Transparent to you - just use the ID, LiteLLM handles routing
diff --git a/docs/my-website/blog/vllm_embeddings_incident/index.md b/docs/my-website/blog/vllm_embeddings_incident/index.md
index a1ce8152857..26387e66dd0 100644
--- a/docs/my-website/blog/vllm_embeddings_incident/index.md
+++ b/docs/my-website/blog/vllm_embeddings_incident/index.md
@@ -3,18 +3,9 @@ slug: vllm-embeddings-incident
title: "Incident Report: vLLM Embeddings Broken by encoding_format Parameter"
date: 2026-02-18T10:00:00
authors:
- - name: Sameer Kankute
- title: SWE @ LiteLLM (LLM Translation)
- url: https://www.linkedin.com/in/sameer-kankute/
- image_url: https://pbs.twimg.com/profile_images/2001352686994907136/ONgNuSk5_400x400.jpg
- - name: Krrish Dholakia
- title: "CEO, LiteLLM"
- url: https://www.linkedin.com/in/krish-d/
- image_url: https://pbs.twimg.com/profile_images/1298587542745358340/DZv3Oj-h_400x400.jpg
- - name: Ishaan Jaff
- title: "CTO, LiteLLM"
- url: https://www.linkedin.com/in/reffajnaahsi/
- image_url: https://pbs.twimg.com/profile_images/1613813310264340481/lz54oEiB_400x400.jpg
+ - sameer
+ - krrish
+ - ishaan-alt
tags: [incident-report, embeddings, vllm]
hide_table_of_contents: false
---
diff --git a/docs/my-website/docs/anthropic_unified/index.md b/docs/my-website/docs/anthropic_unified/index.md
index 9981547ce1f..f8a50e14da5 100644
--- a/docs/my-website/docs/anthropic_unified/index.md
+++ b/docs/my-website/docs/anthropic_unified/index.md
@@ -506,12 +506,15 @@ Request body will be in the Anthropic messages API format. **litellm follows the
A system prompt providing context or specific instructions to the model.
- **temperature** (number):
Controls randomness in the model's responses. Valid range: `0 < temperature < 1`.
-- **thinking** (object):
+- **thinking** (object):
Configuration for enabling extended thinking. If enabled, it includes:
- - **budget_tokens** (integer):
+ - **budget_tokens** (integer):
Minimum of 1024 tokens (and less than `max_tokens`).
- - **type** (enum):
+ - **type** (enum):
E.g., `"enabled"`.
+ - **summary** (string, optional):
+ Enables the summary style for thinking blocks. Possible values: `"auto"`, `"concise"`, `"detailed"`, `"disabled"`.
+ When routing to non-Anthropic providers (e.g., `openai/gpt-5.1`), the `summary` value is preserved and forwarded to the downstream API.
- **tool_choice** (object):
Instructs how the model should utilize any provided tools.
- **tools** (array of objects):
diff --git a/docs/my-website/docs/completion/prompt_caching.md b/docs/my-website/docs/completion/prompt_caching.md
index dca5f5c0cff..402c7b9f4c7 100644
--- a/docs/my-website/docs/completion/prompt_caching.md
+++ b/docs/my-website/docs/completion/prompt_caching.md
@@ -6,6 +6,8 @@ import TabItem from '@theme/TabItem';
Supported Providers:
- OpenAI (`openai/`)
- Anthropic API (`anthropic/`)
+- Google AI Studio (`gemini/`)
+- Vertex AI (`vertex_ai/`, `vertex_ai_beta/`)
- Bedrock (`bedrock/`, `bedrock/invoke/`, `bedrock/converse`) ([All models bedrock supports prompt caching on](https://docs.aws.amazon.com/bedrock/latest/userguide/prompt-caching.html))
- Deepseek API (`deepseek/`)
@@ -257,7 +259,7 @@ Anthropic charges for cache writes.
Specify the content to cache with `"cache_control": {"type": "ephemeral"}`.
-If you pass that in for any other llm provider, it will be ignored.
+This same format also works for [Gemini / Vertex AI](#google-ai-studio--vertex-ai-gemini-example). For other providers, it will be ignored.
@@ -356,6 +358,208 @@ print(response.usage)
+### Google AI Studio / Vertex AI (Gemini) Example
+
+Use the same Anthropic-style `cache_control` format — LiteLLM automatically translates it to Google's [context caching API](https://ai.google.dev/api/caching).
+
+**How it works under the hood:**
+1. Messages with `cache_control` are separated and sent to Google's `cachedContents` API
+2. The cached content ID is then passed as `cachedContent` in the Gemini request body
+3. Works across all three providers: `gemini/` (Google AI Studio), `vertex_ai/`, and `vertex_ai_beta/`
+4. Requires a minimum of **1024 tokens** in the cached content — below that, caching is silently skipped
+
+
+
+
+```python
+from litellm import completion
+import os
+
+os.environ["GEMINI_API_KEY"] = ""
+
+response = completion(
+ model="gemini/gemini-2.5-flash",
+ messages=[
+ {
+ "role": "system",
+ "content": [
+ {
+ "type": "text",
+ "text": "You are an AI assistant tasked with analyzing legal documents.",
+ },
+ {
+ "type": "text",
+ "text": "Here is the full text of a complex legal agreement" * 400,
+ "cache_control": {"type": "ephemeral"},
+ },
+ ],
+ },
+ {
+ "role": "user",
+ "content": "what are the key terms and conditions in this agreement?",
+ },
+ ],
+)
+
+print(response.usage)
+```
+
+
+
+1. Setup config.yaml
+
+```yaml
+model_list:
+ - model_name: gemini-2.5-flash
+ litellm_params:
+ model: gemini/gemini-2.5-flash
+ api_key: os.environ/GEMINI_API_KEY
+```
+
+2. Start proxy
+
+```bash
+litellm --config /path/to/config.yaml
+```
+
+3. Test it!
+
+```python
+from openai import OpenAI
+
+client = OpenAI(
+ api_key="LITELLM_PROXY_KEY", # sk-1234
+ base_url="LITELLM_PROXY_BASE", # http://0.0.0.0:4000
+)
+
+response = client.chat.completions.create(
+ model="gemini-2.5-flash",
+ messages=[
+ {
+ "role": "system",
+ "content": [
+ {
+ "type": "text",
+ "text": "You are an AI assistant tasked with analyzing legal documents.",
+ },
+ {
+ "type": "text",
+ "text": "Here is the full text of a complex legal agreement" * 400,
+ "cache_control": {"type": "ephemeral"},
+ },
+ ],
+ },
+ {
+ "role": "user",
+ "content": "what are the key terms and conditions in this agreement?",
+ },
+ ],
+)
+
+print(response.usage)
+```
+
+
+
+
+#### Vertex AI
+
+For Vertex AI, use `vertex_ai/` prefix:
+
+
+
+
+```python
+from litellm import completion
+
+response = completion(
+ model="vertex_ai/gemini-2.5-flash",
+ vertex_project="my-gcp-project",
+ vertex_location="us-central1",
+ messages=[
+ {
+ "role": "system",
+ "content": [
+ {
+ "type": "text",
+ "text": "You are an AI assistant tasked with analyzing legal documents.",
+ },
+ {
+ "type": "text",
+ "text": "Here is the full text of a complex legal agreement" * 400,
+ "cache_control": {"type": "ephemeral"},
+ },
+ ],
+ },
+ {
+ "role": "user",
+ "content": "what are the key terms and conditions in this agreement?",
+ },
+ ],
+)
+
+print(response.usage)
+```
+
+
+
+1. Setup config.yaml
+
+```yaml
+model_list:
+ - model_name: gemini-2.5-flash
+ litellm_params:
+ model: vertex_ai/gemini-2.5-flash
+ vertex_project: my-gcp-project
+ vertex_location: us-central1
+```
+
+2. Start proxy
+
+```bash
+litellm --config /path/to/config.yaml
+```
+
+3. Test it!
+
+```python
+from openai import OpenAI
+
+client = OpenAI(
+ api_key="LITELLM_PROXY_KEY", # sk-1234
+ base_url="LITELLM_PROXY_BASE", # http://0.0.0.0:4000
+)
+
+response = client.chat.completions.create(
+ model="gemini-2.5-flash",
+ messages=[
+ {
+ "role": "system",
+ "content": [
+ {
+ "type": "text",
+ "text": "You are an AI assistant tasked with analyzing legal documents.",
+ },
+ {
+ "type": "text",
+ "text": "Here is the full text of a complex legal agreement" * 400,
+ "cache_control": {"type": "ephemeral"},
+ },
+ ],
+ },
+ {
+ "role": "user",
+ "content": "what are the key terms and conditions in this agreement?",
+ },
+ ],
+)
+
+print(response.usage)
+```
+
+
+
+
### Deepeek Example
Works the same as OpenAI.
diff --git a/docs/my-website/docs/data_security.md b/docs/my-website/docs/data_security.md
index 2c4b1247e2b..d93d17aa0de 100644
--- a/docs/my-website/docs/data_security.md
+++ b/docs/my-website/docs/data_security.md
@@ -128,8 +128,6 @@ We'll review all reports promptly. Note that we don't currently offer a bug boun
Legal Entity Name: Berrie AI Incorporated
-Company Phone Number: 7708783106
-
Point of contact email address for security incidents: krrish@berri.ai
Point of contact email address for general security-related questions: krrish@berri.ai
diff --git a/docs/my-website/docs/debugging/local_debugging.md b/docs/my-website/docs/debugging/local_debugging.md
index 8a56d6c34a0..53daa4e366b 100644
--- a/docs/my-website/docs/debugging/local_debugging.md
+++ b/docs/my-website/docs/debugging/local_debugging.md
@@ -67,6 +67,6 @@ response = completion("command-nightly", messages, logger_fn=my_custom_logging_f
## Still Seeing Issues?
-Text us @ +17708783106 or Join the [Discord](https://discord.com/invite/wuPM9dRgDw).
+Join the [Discord](https://discord.com/invite/wuPM9dRgDw).
We promise to help you in `lite`ning speed ❤️
diff --git a/docs/my-website/docs/enterprise.md b/docs/my-website/docs/enterprise.md
index 6dccf7ff4e7..a3fc9e38b6e 100644
--- a/docs/my-website/docs/enterprise.md
+++ b/docs/my-website/docs/enterprise.md
@@ -4,7 +4,7 @@ import Image from '@theme/IdealImage';
:::info
- ✨ SSO is free for up to 5 users. After that, an enterprise license is required. [Get Started with Enterprise here](https://www.litellm.ai/enterprise)
-- Who is Enterprise for? Companies giving access to 100+ users **OR** 10+ AI use-cases. If you're not sure, [get in touch with us](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions) to discuss your needs.
+- Who is Enterprise for? Companies giving access to 100+ users **OR** 10+ AI use-cases. If you're not sure, [get in touch with us](https://enterprise.litellm.ai/demo) to discuss your needs.
:::
For companies that need SSO, user management and professional support for LiteLLM Proxy
@@ -36,7 +36,7 @@ Manage Yourself - you can deploy our Docker Image or build a custom image from o
### What’s the cost of the Self-Managed Enterprise edition?
-Self-Managed Enterprise deployments require our team to understand your exact needs. [Get in touch with us to learn more](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+Self-Managed Enterprise deployments require our team to understand your exact needs. [Get in touch with us to learn more](https://enterprise.litellm.ai/demo)
### How does deployment with Enterprise License work?
@@ -106,7 +106,7 @@ Professional Support can assist with LLM/Provider integrations, deployment, upgr
Pricing is based on usage. We can figure out a price that works for your team, on the call.
-[**Contact Us to learn more**](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+[**Contact Us to learn more**](https://enterprise.litellm.ai/demo)
diff --git a/docs/my-website/docs/fine_tuning.md b/docs/my-website/docs/fine_tuning.md
index d0bd98a76f9..52e96f28688 100644
--- a/docs/my-website/docs/fine_tuning.md
+++ b/docs/my-website/docs/fine_tuning.md
@@ -6,7 +6,7 @@ import TabItem from '@theme/TabItem';
:::info
-This is an Enterprise only endpoint [Get Started with Enterprise here](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+This is an Enterprise only endpoint [Get Started with Enterprise here](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/guides/index.md b/docs/my-website/docs/guides/index.md
new file mode 100644
index 00000000000..1641600dab2
--- /dev/null
+++ b/docs/my-website/docs/guides/index.md
@@ -0,0 +1,78 @@
+---
+title: Guides
+sidebar_label: Overview
+---
+
+import NavigationCards from '@site/src/components/NavigationCards';
+
+**Guides** are focused references organized by the job you are trying to do with LiteLLM: make requests, use tools, handle media, manage context, or operate the gateway safely.
+
+> New to LiteLLM or not sure whether you need the SDK or Gateway path first? Start at [Learn →](/docs/learn)
+
+---
+
+## Build With LiteLLM
+
+
+
+---
+
+## Operate & Extend
+
+
diff --git a/docs/my-website/docs/index.md b/docs/my-website/docs/index.md
index ba605e316d3..ca63c9e39ff 100644
--- a/docs/my-website/docs/index.md
+++ b/docs/my-website/docs/index.md
@@ -1,689 +1,462 @@
+---
+id: index
+title: Getting Started
+sidebar_label: Quickstart
+---
+
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
+import NavigationCards from '@site/src/components/NavigationCards';
+import Image from '@theme/IdealImage';
-# LiteLLM - Getting Started
+
-https://github.com/BerriAI/litellm
+**LiteLLM** is an open-source library that gives you a single, unified interface to call 100+ LLMs — OpenAI, Anthropic, Vertex AI, Bedrock, and more — using the OpenAI format.
-## **Call 100+ LLMs using the OpenAI Input/Output Format**
+- Call any provider using the same `completion()` interface — no re-learning the API for each one
+- Consistent output format regardless of which provider or model you use
+- Built-in retry / fallback logic across multiple deployments via the [Router](./routing.md)
+- Self-hosted [LLM Gateway (Proxy)](./simple_proxy) with virtual keys, cost tracking, and an admin UI
-- Translate inputs to provider's endpoints (`/chat/completions`, `/responses`, `/embeddings`, `/images`, `/audio`, `/batches`, and more)
-- [Consistent output](https://docs.litellm.ai/docs/supported_endpoints) - same response format regardless of which provider you use
-- Retry/fallback logic across multiple deployments (e.g. Azure/OpenAI) - [Router](https://docs.litellm.ai/docs/routing)
-- Track spend & set budgets per project [LiteLLM Proxy Server](https://docs.litellm.ai/docs/simple_proxy)
+[](https://pypi.org/project/litellm/)
+[](https://github.com/BerriAI/litellm)
-## 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:
-
-
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 & 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 Python SDK**
-
-### Basic usage
-
-
-
-
+## Installation
```shell
pip install litellm
```
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables
-os.environ["OPENAI_API_KEY"] = "your-api-key"
-
-response = completion(
- model="openai/gpt-4o",
- messages=[{ "content": "Hello, how are you?","role": "user"}]
-)
-```
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables
-os.environ["ANTHROPIC_API_KEY"] = "your-api-key"
-
-response = completion(
- model="anthropic/claude-3-sonnet-20240229",
- messages=[{ "content": "Hello, how are you?","role": "user"}]
-)
-```
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables
-os.environ["XAI_API_KEY"] = "your-api-key"
-
-response = completion(
- model="xai/grok-2-latest",
- messages=[{ "content": "Hello, how are you?","role": "user"}]
-)
-```
-
-
-
-```python
-from litellm import completion
-import os
-
-# auth: run 'gcloud auth application-default'
-os.environ["VERTEXAI_PROJECT"] = "hardy-device-386718"
-os.environ["VERTEXAI_LOCATION"] = "us-central1"
-
-response = completion(
- model="vertex_ai/gemini-1.5-pro",
- messages=[{ "content": "Hello, how are you?","role": "user"}]
-)
-```
-
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables
-os.environ["NVIDIA_NIM_API_KEY"] = "nvidia_api_key"
-os.environ["NVIDIA_NIM_API_BASE"] = "nvidia_nim_endpoint_url"
-
-response = completion(
- model="nvidia_nim/",
- messages=[{ "content": "Hello, how are you?","role": "user"}]
-)
-```
-
-
-
-
-
-```python
-from litellm import completion
-import os
-
-os.environ["HUGGINGFACE_API_KEY"] = "huggingface_api_key"
-
-# e.g. Call 'WizardLM/WizardCoder-Python-34B-V1.0' hosted on HF Inference endpoints
-response = completion(
- model="huggingface/WizardLM/WizardCoder-Python-34B-V1.0",
- messages=[{ "content": "Hello, how are you?","role": "user"}],
- api_base="https://my-endpoint.huggingface.cloud"
-)
-
-print(response)
-```
-
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables
-os.environ["AZURE_API_KEY"] = ""
-os.environ["AZURE_API_BASE"] = ""
-os.environ["AZURE_API_VERSION"] = ""
-
-# azure call
-response = completion(
- "azure/",
- messages = [{ "content": "Hello, how are you?","role": "user"}]
-)
-```
-
-
-
-
-
-```python
-from litellm import completion
-
-response = completion(
- model="ollama/llama2",
- messages = [{ "content": "Hello, how are you?","role": "user"}],
- api_base="http://localhost:11434"
-)
-```
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables
-os.environ["OPENROUTER_API_KEY"] = "openrouter_api_key"
-
-response = completion(
- model="openrouter/google/palm-2-chat-bison",
- messages = [{ "content": "Hello, how are you?","role": "user"}],
-)
-```
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables. Visit https://novita.ai/settings/key-management to get your API key
-os.environ["NOVITA_API_KEY"] = "novita-api-key"
-
-response = completion(
- model="novita/deepseek/deepseek-r1",
- messages=[{ "content": "Hello, how are you?","role": "user"}]
-)
-```
-
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables. Visit https://vercel.com/docs/ai-gateway#using-the-ai-gateway-with-an-api-key for insturctions on obtaining a key
-os.environ["VERCEL_AI_GATEWAY_API_KEY"] = "your-vercel-api-key"
-
-response = completion(
- model="vercel_ai_gateway/openai/gpt-4o",
- messages=[{ "content": "Hello, how are you?","role": "user"}]
-)
-```
-
-
-
-
-
-### Response Format (OpenAI Chat Completions Format)
-
-```json
-{
- "id": "chatcmpl-565d891b-a42e-4c39-8d14-82a1f5208885",
- "created": 1734366691,
- "model": "gpt-4o-2024-08-06",
- "object": "chat.completion",
- "system_fingerprint": null,
- "choices": [
- {
- "finish_reason": "stop",
- "index": 0,
- "message": {
- "content": "Hello! As an AI language model, I don't have feelings, but I'm operating properly and ready to assist you with any questions or tasks you may have. How can I help you today?",
- "role": "assistant",
- "tool_calls": null,
- "function_call": null
- }
- }
- ],
- "usage": {
- "completion_tokens": 43,
- "prompt_tokens": 13,
- "total_tokens": 56,
- "completion_tokens_details": null,
- "prompt_tokens_details": {
- "audio_tokens": null,
- "cached_tokens": 0
- },
- "cache_creation_input_tokens": 0,
- "cache_read_input_tokens": 0
- }
-}
-```
-
-### Streaming
-Set `stream=True` in the `completion` args.
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables
-os.environ["OPENAI_API_KEY"] = "your-api-key"
-
-response = completion(
- model="openai/gpt-4o",
- messages=[{ "content": "Hello, how are you?","role": "user"}],
- stream=True,
-)
-```
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables
-os.environ["ANTHROPIC_API_KEY"] = "your-api-key"
-
-response = completion(
- model="anthropic/claude-3-sonnet-20240229",
- messages=[{ "content": "Hello, how are you?","role": "user"}],
- stream=True,
-)
-```
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables
-os.environ["XAI_API_KEY"] = "your-api-key"
-
-response = completion(
- model="xai/grok-2-latest",
- messages=[{ "content": "Hello, how are you?","role": "user"}],
- stream=True,
-)
-```
-
-
-
-```python
-from litellm import completion
-import os
-
-# auth: run 'gcloud auth application-default'
-os.environ["VERTEX_PROJECT"] = "hardy-device-386718"
-os.environ["VERTEX_LOCATION"] = "us-central1"
-
-response = completion(
- model="vertex_ai/gemini-1.5-pro",
- messages=[{ "content": "Hello, how are you?","role": "user"}],
- stream=True,
-)
-```
-
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables
-os.environ["NVIDIA_NIM_API_KEY"] = "nvidia_api_key"
-os.environ["NVIDIA_NIM_API_BASE"] = "nvidia_nim_endpoint_url"
-
-response = completion(
- model="nvidia_nim/",
- messages=[{ "content": "Hello, how are you?","role": "user"}]
- stream=True,
-)
-```
-
-
-
-
-```python
-from litellm import completion
-import os
-
-os.environ["HUGGINGFACE_API_KEY"] = "huggingface_api_key"
-
-# e.g. Call 'WizardLM/WizardCoder-Python-34B-V1.0' hosted on HF Inference endpoints
-response = completion(
- model="huggingface/WizardLM/WizardCoder-Python-34B-V1.0",
- messages=[{ "content": "Hello, how are you?","role": "user"}],
- api_base="https://my-endpoint.huggingface.cloud",
- stream=True,
-)
-
-print(response)
-```
-
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables
-os.environ["AZURE_API_KEY"] = ""
-os.environ["AZURE_API_BASE"] = ""
-os.environ["AZURE_API_VERSION"] = ""
-
-# azure call
-response = completion(
- "azure/",
- messages = [{ "content": "Hello, how are you?","role": "user"}],
- stream=True,
-)
-```
-
-
-
-
-
-```python
-from litellm import completion
-
-response = completion(
- model="ollama/llama2",
- messages = [{ "content": "Hello, how are you?","role": "user"}],
- api_base="http://localhost:11434",
- stream=True,
-)
-```
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables
-os.environ["OPENROUTER_API_KEY"] = "openrouter_api_key"
-
-response = completion(
- model="openrouter/google/palm-2-chat-bison",
- messages = [{ "content": "Hello, how are you?","role": "user"}],
- stream=True,
-)
-```
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables. Visit https://novita.ai/settings/key-management to get your API key
-os.environ["NOVITA_API_KEY"] = "novita_api_key"
-
-response = completion(
- model="novita/deepseek/deepseek-r1",
- messages = [{ "content": "Hello, how are you?","role": "user"}],
- stream=True,
-)
-```
-
-
-
-
-
-```python
-from litellm import completion
-import os
-
-## set ENV variables. Visit https://vercel.com/docs/ai-gateway#using-the-ai-gateway-with-an-api-key for insturctions on obtaining a key
-os.environ["VERCEL_AI_GATEWAY_API_KEY"] = "your-vercel-api-key"
-
-response = completion(
- model="vercel_ai_gateway/openai/gpt-4o",
- messages = [{ "content": "Hello, how are you?","role": "user"}],
- stream=True,
-)
-```
-
-
-
-
-
-### Streaming Response Format (OpenAI Format)
-
-```json
-{
- "id": "chatcmpl-2be06597-eb60-4c70-9ec5-8cd2ab1b4697",
- "created": 1734366925,
- "model": "claude-3-sonnet-20240229",
- "object": "chat.completion.chunk",
- "system_fingerprint": null,
- "choices": [
- {
- "finish_reason": null,
- "index": 0,
- "delta": {
- "content": "Hello",
- "role": "assistant",
- "function_call": null,
- "tool_calls": null,
- "audio": null
- },
- "logprobs": null
- }
- ]
-}
-```
-
-### Exception handling
-
-LiteLLM maps exceptions across all supported providers to the OpenAI exceptions. All our exceptions inherit from OpenAI's exception types, so any error-handling you have for that, should work out of the box with LiteLLM.
-
-```python
-import litellm
-from litellm import completion
-import os
-
-os.environ["ANTHROPIC_API_KEY"] = "bad-key"
-try:
- completion(model="anthropic/claude-instant-1", messages=[{"role": "user", "content": "Hey, how's it going?"}])
-except litellm.AuthenticationError as e:
- # Thrown when the API key is invalid
- print(f"Authentication failed: {e}")
-except litellm.RateLimitError as e:
- # Thrown when you've exceeded your rate limit
- print(f"Rate limited: {e}")
-except litellm.APIError as e:
- # Thrown for general API errors
- print(f"API error: {e}")
-```
-### See How LiteLLM Transforms Your Requests
-
-Want to understand how LiteLLM parses and normalizes your LLM API requests? Use the `/utils/transform_request` endpoint to see exactly how your request is transformed internally.
-
-You can try it out now directly on our Demo App!
-Go to the [LiteLLM API docs for transform_request](https://litellm-api.up.railway.app/#/llm%20utils/transform_request_utils_transform_request_post)
-
-LiteLLM will show you the normalized, provider-agnostic version of your request. This is useful for debugging, learning, and understanding how LiteLLM handles different providers and options.
-
-
-### Logging Observability - Log LLM Input/Output ([Docs](https://docs.litellm.ai/docs/observability/callbacks))
-LiteLLM exposes pre defined callbacks to send data to Lunary, MLflow, Langfuse, Helicone, Promptlayer, Traceloop, Slack
-
-```python
-from litellm import completion
-
-## set env variables for logging tools (API key set up is not required when using MLflow)
-os.environ["LUNARY_PUBLIC_KEY"] = "your-lunary-public-key" # get your public key at https://app.lunary.ai/settings
-os.environ["HELICONE_API_KEY"] = "your-helicone-key"
-os.environ["LANGFUSE_PUBLIC_KEY"] = ""
-os.environ["LANGFUSE_SECRET_KEY"] = ""
-
-os.environ["OPENAI_API_KEY"]
-
-# set callbacks
-litellm.success_callback = ["lunary", "mlflow", "langfuse", "helicone"] # log input/output to lunary, mlflow, langfuse, helicone
-
-#openai call
-response = completion(model="gpt-3.5-turbo", messages=[{"role": "user", "content": "Hi 👋 - i'm openai"}])
-```
-
-### Track Costs, Usage, Latency for streaming
-Use a callback function for this - more info on custom callbacks: https://docs.litellm.ai/docs/observability/custom_callback
-
-```python
-import litellm
-
-# track_cost_callback
-def track_cost_callback(
- kwargs, # kwargs to completion
- completion_response, # response from completion
- start_time, end_time # start/end time
-):
- try:
- response_cost = kwargs.get("response_cost", 0)
- print("streaming response_cost", response_cost)
- except:
- pass
-# set callback
-litellm.success_callback = [track_cost_callback] # set custom callback function
-
-# litellm.completion() call
-response = completion(
- model="gpt-3.5-turbo",
- messages=[
- {
- "role": "user",
- "content": "Hi 👋 - i'm openai"
- }
- ],
- stream=True
-)
-```
-
-## **LiteLLM Proxy Server (LLM Gateway)**
-
-Track spend across multiple projects/people
-
-
-
-The proxy provides:
-
-1. [Hooks for auth](https://docs.litellm.ai/docs/proxy/virtual_keys#custom-auth)
-2. [Hooks for logging](https://docs.litellm.ai/docs/proxy/logging#step-1---create-your-custom-litellm-callback-class)
-3. [Cost tracking](https://docs.litellm.ai/docs/proxy/virtual_keys#tracking-spend)
-4. [Rate Limiting](https://docs.litellm.ai/docs/proxy/users#set-rate-limits)
-
-### 📖 Proxy Endpoints - [Swagger Docs](https://litellm-api.up.railway.app/)
-
-Go here for a complete tutorial with keys + rate limits - [**here**](./proxy/docker_quick_start.md)
-
-### Quick Start Proxy - CLI
+To run the full Proxy Server (LLM Gateway):
```shell
pip install 'litellm[proxy]'
```
-#### Step 1: Start litellm proxy
+---
+
+## Quick Start
+
+Make your first LLM call using the provider of your choice:
+
-
+```python
+from litellm import completion
+import os
-```shell
-$ litellm --model huggingface/bigcode/starcoder
+os.environ["OPENAI_API_KEY"] = "your-api-key"
-#INFO: Proxy running on http://0.0.0.0:4000
+response = completion(
+ model="openai/gpt-4o",
+ messages=[{"role": "user", "content": "Hello, how are you?"}]
+)
+print(response.choices[0].message.content)
```
+
-
+```python
+from litellm import completion
+import os
+os.environ["ANTHROPIC_API_KEY"] = "your-api-key"
-Step 1. CREATE config.yaml
+response = completion(
+ model="anthropic/claude-3-5-sonnet-20241022",
+ messages=[{"role": "user", "content": "Hello, how are you?"}]
+)
+print(response.choices[0].message.content)
+```
-Example `litellm_config.yaml`
+
+
-```yaml
+```python
+from litellm import completion
+import os
+
+# auth: run 'gcloud auth application-default login'
+os.environ["VERTEXAI_PROJECT"] = "your-project-id"
+os.environ["VERTEXAI_LOCATION"] = "us-central1"
+
+response = completion(
+ model="vertex_ai/gemini-1.5-pro",
+ messages=[{"role": "user", "content": "Hello, how are you?"}]
+)
+print(response.choices[0].message.content)
+```
+
+
+
+
+```python
+from litellm import completion
+import os
+
+os.environ["AWS_ACCESS_KEY_ID"] = "your-key"
+os.environ["AWS_SECRET_ACCESS_KEY"] = "your-secret"
+os.environ["AWS_REGION_NAME"] = "us-east-1"
+
+response = completion(
+ model="bedrock/anthropic.claude-3-5-sonnet-20241022-v2:0",
+ messages=[{"role": "user", "content": "Hello, how are you?"}]
+)
+print(response.choices[0].message.content)
+```
+
+
+
+
+```python
+from litellm import completion
+
+response = completion(
+ model="ollama/llama3",
+ messages=[{"role": "user", "content": "Hello, how are you?"}],
+ api_base="http://localhost:11434"
+)
+print(response.choices[0].message.content)
+```
+
+
+
+
+```python
+from litellm import completion
+import os
+
+os.environ["AZURE_API_KEY"] = "your-key"
+os.environ["AZURE_API_BASE"] = "https://your-resource.openai.azure.com"
+os.environ["AZURE_API_VERSION"] = "2024-02-01"
+
+response = completion(
+ model="azure/your-deployment-name",
+ messages=[{"role": "user", "content": "Hello, how are you?"}]
+)
+print(response.choices[0].message.content)
+```
+
+
+
+
+Every response follows the OpenAI Chat Completions format, regardless of provider. ✅
+
+### Response Format
+
+Non-streaming responses return a `ModelResponse` object:
+
+```json
+{
+ "id": "chatcmpl-abc123",
+ "object": "chat.completion",
+ "created": 1677858242,
+ "model": "gpt-4o",
+ "choices": [
+ {
+ "index": 0,
+ "message": {
+ "role": "assistant",
+ "content": "Hello! I'm doing well, thanks for asking."
+ },
+ "finish_reason": "stop"
+ }
+ ],
+ "usage": {
+ "prompt_tokens": 13,
+ "completion_tokens": 12,
+ "total_tokens": 25
+ }
+}
+```
+
+Streaming responses (`stream=True`) yield `ModelResponseStream` chunks:
+
+```json
+{
+ "id": "chatcmpl-abc123",
+ "object": "chat.completion.chunk",
+ "created": 1677858242,
+ "model": "gpt-4o",
+ "choices": [
+ {
+ "index": 0,
+ "delta": {
+ "role": "assistant",
+ "content": "Hello"
+ },
+ "finish_reason": null
+ }
+ ]
+}
+```
+
+📖 [Full output format reference →](./completion/output)
+
+:::tip Open in Colab
+
+
+
+:::
+
+---
+
+## New to LiteLLM?
+
+**Want to get started fast?** Head to [Tutorials](/docs/tutorials) for step-by-step walkthroughs — AI coding tools, agent SDKs, proxy setup, and more.
+
+**Need to understand a specific feature?** Check [Guides](/docs/guides) for streaming, function calling, prompt caching, and other how-tos.
+
+---
+
+## Choose Your Path
+
+
+
+---
+
+## LiteLLM Python SDK
+
+### Streaming
+
+Add `stream=True` to receive chunks as they are generated:
+
+```python
+from litellm import completion
+import os
+
+os.environ["OPENAI_API_KEY"] = "your-api-key"
+
+for chunk in completion(
+ model="openai/gpt-4o",
+ messages=[{"role": "user", "content": "Write a short poem"}],
+ stream=True,
+):
+ print(chunk.choices[0].delta.content or "", end="")
+```
+
+### Exception Handling
+
+LiteLLM maps every provider's errors to the OpenAI exception types — your existing error handling works out of the box:
+
+```python
+import litellm
+
+try:
+ litellm.completion(
+ model="anthropic/claude-instant-1",
+ messages=[{"role": "user", "content": "Hey!"}]
+ )
+except litellm.AuthenticationError as e:
+ print(f"Bad API key: {e}")
+except litellm.RateLimitError as e:
+ print(f"Rate limited: {e}")
+except litellm.APIError as e:
+ print(f"API error: {e}")
+```
+
+### Logging & Observability
+
+Send input/output to Langfuse, MLflow, Helicone, Lunary, and more with a single line:
+
+```python
+import litellm
+
+litellm.success_callback = ["langfuse", "mlflow", "helicone"]
+
+response = litellm.completion(
+ model="gpt-4o",
+ messages=[{"role": "user", "content": "Hi!"}]
+)
+```
+
+📖 [See all observability integrations →](/docs/observability/agentops_integration)
+
+### Track Costs & Usage
+
+Use a callback to capture cost per response:
+
+```python
+import litellm
+
+def track_cost(kwargs, completion_response, start_time, end_time):
+ print("Cost:", kwargs.get("response_cost", 0))
+
+litellm.success_callback = [track_cost]
+
+litellm.completion(
+ model="gpt-4o",
+ messages=[{"role": "user", "content": "Hello!"}],
+ stream=True
+)
+```
+
+📖 [Custom callback docs →](./observability/custom_callback)
+
+---
+
+## LiteLLM Proxy Server (LLM Gateway)
+
+The proxy is a self-hosted OpenAI-compatible gateway. Any client that works with OpenAI works with the proxy — no code changes needed.
+
+
+
+#### Step 1 — Start the proxy
+
+
+
+
+```shell
+litellm --model huggingface/bigcode/starcoder
+# Proxy running on http://0.0.0.0:4000
+```
+
+
+
+
+```yaml title="litellm_config.yaml"
model_list:
- model_name: gpt-3.5-turbo
litellm_params:
- model: azure/
- api_base: os.environ/AZURE_API_BASE # runs os.getenv("AZURE_API_BASE")
- api_key: os.environ/AZURE_API_KEY # runs os.getenv("AZURE_API_KEY")
+ model: azure/your-deployment
+ api_base: os.environ/AZURE_API_BASE
+ api_key: os.environ/AZURE_API_KEY
api_version: "2023-07-01-preview"
```
-Step 2. RUN Docker Image
-
```shell
docker run \
- -v $(pwd)/litellm_config.yaml:/app/config.yaml \
- -e AZURE_API_KEY=d6*********** \
- -e AZURE_API_BASE=https://openai-***********/ \
- -p 4000:4000 \
- docker.litellm.ai/berriai/litellm:main-latest \
- --config /app/config.yaml --detailed_debug
+ -v $(pwd)/litellm_config.yaml:/app/config.yaml \
+ -e AZURE_API_KEY=your-key \
+ -e AZURE_API_BASE=https://your-resource.openai.azure.com/ \
+ -p 4000:4000 \
+ docker.litellm.ai/berriai/litellm:main-latest \
+ --config /app/config.yaml --detailed_debug
```
-
-#### Step 2: Make ChatCompletions Request to Proxy
+#### Step 2 — Call it with the OpenAI client
```python
-import openai # openai v1.0.0+
-client = openai.OpenAI(api_key="anything",base_url="http://0.0.0.0:4000") # set proxy to base_url
-# request sent to model set on litellm proxy, `litellm --model`
-response = client.chat.completions.create(model="gpt-3.5-turbo", messages = [
- {
- "role": "user",
- "content": "this is a test request, write a short poem"
- }
-])
+import openai
-print(response)
+client = openai.OpenAI(api_key="anything", base_url="http://0.0.0.0:4000")
+
+response = client.chat.completions.create(
+ model="gpt-3.5-turbo",
+ messages=[{"role": "user", "content": "Write a short poem"}]
+)
+print(response.choices[0].message.content)
```
-## More details
+👉 [Full proxy quickstart with Docker →](./proxy/docker_quick_start)
-- [exception mapping](./exception_mapping.md)
-- [retries + model fallbacks for completion()](./completion/reliable_completions.md)
-- [proxy virtual keys & spend management](./proxy/virtual_keys.md)
-- [E2E Tutorial for LiteLLM Proxy Server](./proxy/docker_quick_start.md)
+:::tip Debugging tool
+Use [**`/utils/transform_request`**](./utils/transform_request) to inspect exactly what LiteLLM sends to any provider — useful for debugging prompt formatting, header issues, and provider-specific parameters.
+:::
+
+🔗 [Interactive API explorer (Swagger) →](https://litellm-api.up.railway.app/)
+
+---
+
+## Agent & MCP Gateway
+
+LiteLLM is a unified gateway for **LLMs, agents, and MCP** — you don't need a separate agent or MCP gateway. One endpoint for 100+ models, A2A agents, and MCP tools.
+
+
+
+---
+
+## What to Explore Next
+
+
diff --git a/docs/my-website/docs/integrations/index.md b/docs/my-website/docs/integrations/index.md
index 95c922cce89..0ad934d5b41 100644
--- a/docs/my-website/docs/integrations/index.md
+++ b/docs/my-website/docs/integrations/index.md
@@ -1,18 +1,336 @@
-# Integrations
+---
+title: Integrations
+sidebar_label: Overview
+---
+
+import NavigationCards from '@site/src/components/NavigationCards';
This section covers integrations with various tools and services that can be used with LiteLLM (either Proxy or SDK).
-## AI Agent Frameworks
-- **[Letta](./letta.md)** - Build stateful LLM agents with persistent memory using LiteLLM Proxy
+---
-## Development Tools
-- **[OpenWebUI](../tutorials/openweb_ui.md)** - Self-hosted ChatGPT-style interface
+## Observability
-## Observability & Monitoring
-- **[Langfuse](../observability/langfuse_integration.md)** - LLM observability and analytics
-- **[Prometheus](../proxy/prometheus.md)** - Metrics collection and monitoring
-- **[PagerDuty](../proxy/pagerduty.md)** - Incident response and alerting
-- **[Datadog](../observability/datadog.md)**
+Track, debug, and analyze LLM calls with observability platforms.
+
-Click into each section to learn more about the integrations.
\ No newline at end of file
+[View all observability integrations →](/docs/integrations/observability_integrations)
+
+---
+
+## Alerting & Monitoring
+
+Set up alerts, metrics collection, and infrastructure monitoring.
+
+
+
+---
+
+## Guardrail Providers
+
+Add safety and content filtering to LLM calls.
+
+
+
+[View all guardrail providers →](/docs/guardrail_providers)
+
+---
+
+## Policies
+
+Define and enforce usage policies across your LLM deployment.
+
+
+
+---
+
+## AI Tools
+
+Connect LiteLLM to AI-powered coding and productivity tools.
+
+
+
+---
+
+## Agent SDKs
+
+Use LiteLLM with agent frameworks and SDKs.
+
+
+
+---
+
+## Prompt Management
+
+Manage, version, and deploy prompts.
+
+
+
+---
+
+## Manage with AI Agents
+
+Use AI agents to manage your LiteLLM deployment — create users, teams, keys, models, and more via natural language.
+
+
diff --git a/docs/my-website/docs/integrations/letta.md b/docs/my-website/docs/integrations/letta.md
index 2afb82542f2..9711999df5e 100644
--- a/docs/my-website/docs/integrations/letta.md
+++ b/docs/my-website/docs/integrations/letta.md
@@ -920,9 +920,9 @@ for model in models:
## Resources
-- [Letta Documentation](https://docs.letta.ai/)
-- [LiteLLM Proxy Documentation](../proxy/quick_start.md)
-- [LiteLLM SDK Documentation](../completion/input.md)
-- [Function Calling Guide](../completion/function_call.md)
-- [Observability Setup](../observability/langfuse_integration.md)
-- [Router Configuration](../routing.md)
\ No newline at end of file
+- [Letta Documentation](https://docs.letta.com/)
+- [LiteLLM Proxy Documentation](/docs/simple_proxy)
+- [LiteLLM SDK Documentation](/docs/#litellm-python-sdk)
+- [Function Calling Guide](/docs/completion/function_call)
+- [Observability Setup](/docs/integrations/observability_integrations)
+- [Router Configuration](/docs/routing)
\ No newline at end of file
diff --git a/docs/my-website/docs/integrations/observability_index.md b/docs/my-website/docs/integrations/observability_index.md
new file mode 100644
index 00000000000..8ab83950cdc
--- /dev/null
+++ b/docs/my-website/docs/integrations/observability_index.md
@@ -0,0 +1,28 @@
+---
+title: Observability
+sidebar_label: Overview
+slug: observability_integrations
+---
+
+Track, debug, and analyze LLM calls with observability platforms.
+
+import NavigationCards from '@site/src/components/NavigationCards';
+
+## Observability Integrations
+
+
+
+[View all observability integrations →](/docs/observability/callbacks)
diff --git a/docs/my-website/docs/integrations/websearch_interception.md b/docs/my-website/docs/integrations/websearch_interception.md
index 0c5d8927013..bc5e8ec0b39 100644
--- a/docs/my-website/docs/integrations/websearch_interception.md
+++ b/docs/my-website/docs/integrations/websearch_interception.md
@@ -375,7 +375,7 @@ search_tools:
- [Search Providers](../search/index.md) - Detailed search provider setup
- [Claude Code WebSearch](../tutorials/claude_code_websearch.md) - Using with Claude Code
- [Tool Calling](../completion/function_call.md) - General tool calling documentation
-- [Callbacks](./custom_callback.md) - Custom callback documentation
+- [Callbacks](../observability/custom_callback.md) - Custom callback documentation
## Technical Details
diff --git a/docs/my-website/docs/learn/gateway_quickstart.md b/docs/my-website/docs/learn/gateway_quickstart.md
new file mode 100644
index 00000000000..acec259758c
--- /dev/null
+++ b/docs/my-website/docs/learn/gateway_quickstart.md
@@ -0,0 +1,174 @@
+---
+title: Gateway Quickstart
+sidebar_label: Gateway Quickstart
+description: Start LiteLLM Gateway, add models and keys, then connect applications and SDKs to one shared endpoint.
+---
+
+import NavigationCards from '@site/src/components/NavigationCards';
+
+Use this path if you need one shared OpenAI-compatible endpoint for a team or platform.
+
+If you need a Docker or database-first setup, use the [Docker + Database tutorial](/docs/proxy/docker_quick_start). Otherwise, use the steps below to get to a working request fast.
+
+## 1. Install The Gateway
+
+```bash
+pip install 'litellm[proxy]'
+```
+
+## 2. Set One Provider Key
+
+```bash
+export OPENAI_API_KEY="your-api-key"
+```
+
+## 3. Create `config.yaml`
+
+```yaml
+model_list:
+ - model_name: gpt-4o-mini
+ litellm_params:
+ model: openai/gpt-4o-mini
+ api_key: os.environ/OPENAI_API_KEY
+
+general_settings:
+ master_key: sk-1234
+```
+
+## 4. Start The Gateway
+
+```bash
+litellm --config config.yaml
+```
+
+You should see the proxy start on `http://0.0.0.0:4000`.
+
+## 5. Send Your First Request
+
+```bash
+curl -X POST 'http://0.0.0.0:4000/chat/completions' \
+ -H 'Content-Type: application/json' \
+ -H 'Authorization: Bearer sk-1234' \
+ -d '{
+ "model": "gpt-4o-mini",
+ "messages": [
+ {"role": "user", "content": "Hello from LiteLLM Gateway"}
+ ]
+ }'
+```
+
+## 6. Check The Response
+
+If the request succeeds, the proxy returns `200 OK` with an OpenAI-style response.
+
+The assistant text will be in:
+
+```json
+choices[0].message.content
+```
+
+If your gateway is routing to OpenAI, a real response can look like this:
+
+```json
+{
+ "id": "chatcmpl-abc123",
+ "created": 1677858242,
+ "model": "gpt-4o-mini-2024-07-18",
+ "object": "chat.completion",
+ "system_fingerprint": "fp_406d6473f8",
+ "choices": [
+ {
+ "finish_reason": "stop",
+ "index": 0,
+ "message": {
+ "role": "assistant",
+ "content": "Hello! How can I assist you today?",
+ "tool_calls": null,
+ "function_call": null,
+ "annotations": []
+ }
+ }
+ ],
+ "usage": {
+ "completion_tokens": 9,
+ "prompt_tokens": 13,
+ "total_tokens": 22,
+ "completion_tokens_details": {
+ "accepted_prediction_tokens": 0,
+ "audio_tokens": 0,
+ "reasoning_tokens": 0,
+ "rejected_prediction_tokens": 0
+ },
+ "prompt_tokens_details": {
+ "audio_tokens": 0,
+ "cached_tokens": 0
+ }
+ },
+ "service_tier": "default"
+}
+```
+
+`id`, `created`, the resolved model version, token counts, and message text will vary by request. Other providers may return a smaller or slightly different set of fields, but `choices[0].message.content` is the main field to read.
+
+## 7. Add Keys And The UI
+
+If you need virtual keys, spend tracking, or the admin UI, add a database next.
+
+- Add `database_url` under `general_settings`
+- Use [Virtual keys](/docs/proxy/virtual_keys) for key creation and budgets
+- Use [Admin UI](/docs/proxy/ui) to manage models and keys
+- Use the [Docker + Database tutorial](/docs/proxy/docker_quick_start) if you want a fuller setup
+
+## 8. Pick Your Next Step
+
+
+
+## When To Use The SDK Path Instead
+
+If you only need to call models from one application and do not need centralized auth or shared infrastructure, start with the [SDK Quickstart](/docs/learn/sdk_quickstart) instead.
diff --git a/docs/my-website/docs/learn/index.md b/docs/my-website/docs/learn/index.md
new file mode 100644
index 00000000000..018aec5af00
--- /dev/null
+++ b/docs/my-website/docs/learn/index.md
@@ -0,0 +1,117 @@
+---
+title: Learn LiteLLM
+sidebar_label: Learn
+slug: /learn
+---
+
+import NavigationCards from '@site/src/components/NavigationCards';
+
+LiteLLM gives you one OpenAI-compatible interface for 100+ LLM providers. Start with the path that matches your setup.
+
+---
+
+## Start Here
+
+Pick one path first.
+
+
+
+---
+
+## Common Tasks
+
+Jump to a specific task.
+
+
+
+---
+
+## Docs Map
+
+Use these when you already know the type of doc you want.
+
+
+
+Not sure where to start? Use [SDK Quickstart](/docs/learn/sdk_quickstart) for app code or [Gateway Quickstart](/docs/learn/gateway_quickstart) for shared infrastructure.
diff --git a/docs/my-website/docs/learn/sdk_quickstart.md b/docs/my-website/docs/learn/sdk_quickstart.md
new file mode 100644
index 00000000000..0fb8c3f02a5
--- /dev/null
+++ b/docs/my-website/docs/learn/sdk_quickstart.md
@@ -0,0 +1,174 @@
+---
+title: SDK Quickstart
+sidebar_label: SDK Quickstart
+description: Make your first LiteLLM SDK call, then jump to the right docs for the next feature you need.
+---
+
+import NavigationCards from '@site/src/components/NavigationCards';
+
+Use this path if you are integrating LiteLLM directly into application code.
+
+## 1. Install LiteLLM
+
+```bash
+pip install litellm==1.82.6
+```
+
+## 2. Set Provider Credentials
+
+Start with one provider and set its environment variables.
+
+- OpenAI: `OPENAI_API_KEY`
+- Anthropic: `ANTHROPIC_API_KEY`
+- Azure OpenAI: `AZURE_API_KEY`, `AZURE_API_BASE`, `AZURE_API_VERSION`
+- Bedrock: standard AWS credentials
+- Vertex AI: `VERTEXAI_PROJECT`, `VERTEXAI_LOCATION`
+
+If you have not picked a provider yet, browse [all supported providers](/docs/providers).
+
+## 3. Make Your First Call
+
+```python
+from litellm import completion
+import os
+
+os.environ["OPENAI_API_KEY"] = "your-api-key"
+
+response = completion(
+ model="openai/gpt-4o",
+ messages=[{"role": "user", "content": "Hello, how are you?"}],
+)
+
+print(response.choices[0].message.content)
+```
+
+## 4. Check The Response
+
+The line below:
+
+```python
+print(response.choices[0].message.content)
+```
+
+prints the assistant text, for example:
+
+```text
+Hello! I'm doing well, thanks for asking.
+```
+
+If you print the full object with:
+
+```python
+print(response)
+```
+
+you will see a Python `ModelResponse(...)` object. For an OpenAI-backed model, it can look like this:
+
+```python
+ModelResponse(
+ id='chatcmpl-abc123',
+ created=1773782130,
+ model='gpt-4o-2024-08-06',
+ object='chat.completion',
+ system_fingerprint='fp_4ff89bf575',
+ choices=[
+ Choices(
+ finish_reason='stop',
+ index=0,
+ message=Message(
+ content="Hello! I'm just a program, but I'm here to help you. How can I assist you today?",
+ role='assistant',
+ tool_calls=None,
+ function_call=None,
+ provider_specific_fields={'refusal': None},
+ annotations=[]
+ ),
+ provider_specific_fields={}
+ )
+ ],
+ usage=Usage(
+ completion_tokens=21,
+ prompt_tokens=13,
+ total_tokens=34,
+ completion_tokens_details=CompletionTokensDetailsWrapper(...),
+ prompt_tokens_details=PromptTokensDetailsWrapper(...)
+ ),
+ service_tier='default'
+)
+```
+
+The same response follows an OpenAI-style shape. Conceptually, it looks like this:
+
+```json
+{
+ "id": "chatcmpl-abc123",
+ "object": "chat.completion",
+ "created": 1677858242,
+ "model": "gpt-4o",
+ "choices": [
+ {
+ "index": 0,
+ "message": {
+ "role": "assistant",
+ "content": "Hello! I'm doing well, thanks for asking."
+ },
+ "finish_reason": "stop"
+ }
+ ],
+ "usage": {
+ "prompt_tokens": 13,
+ "completion_tokens": 12,
+ "total_tokens": 25
+ }
+}
+```
+
+`id`, `created`, token counts, and message text will vary by request.
+
+If you call an OpenAI-backed model, you may also see extra fields such as `system_fingerprint`, `service_tier`, `tool_calls`, `function_call`, `annotations`, `provider_specific_fields`, and detailed token usage. For the full output reference, see [completion output](/docs/completion/output).
+
+Need more provider examples? See the main [Getting Started](/docs/#quick-start) page.
+
+## 5. Pick Your Next Step
+
+
+
+## When To Use Gateway Instead
+
+Use LiteLLM Gateway if you need centralized auth, virtual keys, spend tracking, shared logging, or one OpenAI-compatible endpoint for multiple apps.
+
+[Go to Gateway Quickstart →](/docs/learn/gateway_quickstart)
diff --git a/docs/my-website/docs/load_test_advanced.md b/docs/my-website/docs/load_test_advanced.md
index d35b5f74784..d7bc35e74e0 100644
--- a/docs/my-website/docs/load_test_advanced.md
+++ b/docs/my-website/docs/load_test_advanced.md
@@ -11,7 +11,7 @@ Tutorial on how to get to 1K+ RPS with LiteLLM Proxy on locust
- [Github releases](https://github.com/BerriAI/litellm/releases)
- [litellm docker containers](https://github.com/BerriAI/litellm/pkgs/container/litellm)
- [litellm database docker container](https://github.com/BerriAI/litellm/pkgs/container/litellm-database)
-- [ ] Ensure you're following **ALL** [best practices for production](./proxy/production_setup.md)
+- [ ] Ensure you're following **ALL** [best practices for production](./proxy/prod.md)
- [ ] Locust - Ensure you're Locust instance can create 1K+ requests per second
- 👉 You can use our **[maintained locust instance here](https://locust-load-tester-production.up.railway.app/)**
- If you're self hosting locust
@@ -222,4 +222,4 @@ class MyUser(HttpUser):
def on_start(self):
self.api_key = os.getenv('API_KEY', 'sk-1234')
self.client.headers.update({'Authorization': f'Bearer {self.api_key}'})
-```
\ No newline at end of file
+```
diff --git a/docs/my-website/docs/migration.md b/docs/my-website/docs/migration.md
index e1af07d4684..fda1155905d 100644
--- a/docs/my-website/docs/migration.md
+++ b/docs/my-website/docs/migration.md
@@ -31,5 +31,4 @@ When we have breaking changes (i.e. going from 1.x.x to 2.x.x), we will document
**How can we communicate changes better?**
Tell us
- [Discord](https://discord.com/invite/wuPM9dRgDw)
-- Email (krrish@berri.ai/ishaan@berri.ai)
-- Text us (+17708783106)
+- Email (support@berri.ai)
diff --git a/docs/my-website/docs/observability/arize_integration.md b/docs/my-website/docs/observability/arize_integration.md
index b3ccf98ea3b..4486fb2b718 100644
--- a/docs/my-website/docs/observability/arize_integration.md
+++ b/docs/my-website/docs/observability/arize_integration.md
@@ -194,5 +194,4 @@ print(response)
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/observability/gcs_bucket_integration.md b/docs/my-website/docs/observability/gcs_bucket_integration.md
index 69b956950e5..5f8d42508ae 100644
--- a/docs/my-website/docs/observability/gcs_bucket_integration.md
+++ b/docs/my-website/docs/observability/gcs_bucket_integration.md
@@ -6,7 +6,7 @@ Log LLM Logs to [Google Cloud Storage Buckets](https://cloud.google.com/storage?
:::info
-✨ This is an Enterprise only feature [Get Started with Enterprise here](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+✨ This is an Enterprise only feature [Get Started with Enterprise here](https://enterprise.litellm.ai/demo)
:::
@@ -79,5 +79,4 @@ curl --location 'http://0.0.0.0:4000/chat/completions' \
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/observability/langfuse_integration.md b/docs/my-website/docs/observability/langfuse_integration.md
index d3c5a44d481..32849ebdb92 100644
--- a/docs/my-website/docs/observability/langfuse_integration.md
+++ b/docs/my-website/docs/observability/langfuse_integration.md
@@ -342,5 +342,4 @@ Be aware that if you are continuing an existing trace, and you set `update_trace
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/observability/langfuse_otel_integration.md b/docs/my-website/docs/observability/langfuse_otel_integration.md
index b4c9a2bd1ad..79ad2f6f75d 100644
--- a/docs/my-website/docs/observability/langfuse_otel_integration.md
+++ b/docs/my-website/docs/observability/langfuse_otel_integration.md
@@ -83,6 +83,9 @@ os.environ["LANGFUSE_OTEL_HOST"] = "https://cloud.langfuse.com" # EU region
# Or use self-hosted instance
# os.environ["LANGFUSE_OTEL_HOST"] = "https://my-langfuse.company.com"
+# Optional: Ignore otel context propagation to prevent parent-child relationships with spans from other providers
+# os.environ["OTEL_IGNORE_CONTEXT_PROPAGATION"] = "true"
+
litellm.callbacks = ["langfuse_otel"]
```
@@ -124,6 +127,9 @@ export LANGFUSE_PUBLIC_KEY="pk-lf-..."
export LANGFUSE_SECRET_KEY="sk-lf-..."
export LANGFUSE_OTEL_HOST="https://us.cloud.langfuse.com" # Default US region
# export LANGFUSE_OTEL_HOST="https://otel.my-langfuse.company.com" # custom OTEL endpoint
+
+# Optional: Ignore otel context propagation to prevent parent-child relationships with spans from other providers
+# export OTEL_IGNORE_CONTEXT_PROPAGATION="true"
```
2. Setup config.yaml
diff --git a/docs/my-website/docs/observability/langsmith_integration.md b/docs/my-website/docs/observability/langsmith_integration.md
index cada4122b20..bf867319de8 100644
--- a/docs/my-website/docs/observability/langsmith_integration.md
+++ b/docs/my-website/docs/observability/langsmith_integration.md
@@ -225,5 +225,4 @@ environment_variables:
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/observability/logfire_integration.md b/docs/my-website/docs/observability/logfire_integration.md
index a1bd43a4bc4..00652c0f1a1 100644
--- a/docs/my-website/docs/observability/logfire_integration.md
+++ b/docs/my-website/docs/observability/logfire_integration.md
@@ -63,5 +63,4 @@ response = litellm.completion(
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/observability/lunary_integration.md b/docs/my-website/docs/observability/lunary_integration.md
index 8d28321c807..4f1dca9d4af 100644
--- a/docs/my-website/docs/observability/lunary_integration.md
+++ b/docs/my-website/docs/observability/lunary_integration.md
@@ -176,5 +176,4 @@ You can find more details about the different ways of making requests to the Lit
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/observability/opik_integration.md b/docs/my-website/docs/observability/opik_integration.md
index d28c46f0b4b..5b5cbe0f185 100644
--- a/docs/my-website/docs/observability/opik_integration.md
+++ b/docs/my-website/docs/observability/opik_integration.md
@@ -261,5 +261,4 @@ All requests made with this key will automatically be tracked in the "TestProjec
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/observability/phoenix_integration.md b/docs/my-website/docs/observability/phoenix_integration.md
index 191f1f8044a..67ba815557e 100644
--- a/docs/my-website/docs/observability/phoenix_integration.md
+++ b/docs/my-website/docs/observability/phoenix_integration.md
@@ -127,5 +127,4 @@ Depending on which Phoenix Cloud version or deployment you are using, you should
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/observability/promptlayer_integration.md b/docs/my-website/docs/observability/promptlayer_integration.md
index 7f62a316972..9462e755f74 100644
--- a/docs/my-website/docs/observability/promptlayer_integration.md
+++ b/docs/my-website/docs/observability/promptlayer_integration.md
@@ -84,5 +84,4 @@ Credits to [Nick Bradford](https://github.com/nsbradford), from [Vim-GPT](https:
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
\ No newline at end of file
diff --git a/docs/my-website/docs/observability/slack_integration.md b/docs/my-website/docs/observability/slack_integration.md
index 0ca7f616683..468d8b5945c 100644
--- a/docs/my-website/docs/observability/slack_integration.md
+++ b/docs/my-website/docs/observability/slack_integration.md
@@ -101,5 +101,4 @@ response = litellm.completion(
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/observability/sumologic_integration.md b/docs/my-website/docs/observability/sumologic_integration.md
index c30ee94dad4..87e20ca57ed 100644
--- a/docs/my-website/docs/observability/sumologic_integration.md
+++ b/docs/my-website/docs/observability/sumologic_integration.md
@@ -328,5 +328,4 @@ If you get authentication errors, regenerate the HTTP Source URL in Sumo Logic:
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/observability/supabase_integration.md b/docs/my-website/docs/observability/supabase_integration.md
index fd3f1c3d5a0..c29871d752f 100644
--- a/docs/my-website/docs/observability/supabase_integration.md
+++ b/docs/my-website/docs/observability/supabase_integration.md
@@ -105,5 +105,4 @@ litellm.modify_integration("supabase",{"table_name": "litellm_logs"})
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/observability/wandb_integration.md b/docs/my-website/docs/observability/wandb_integration.md
index 37057f43db5..3c1a3363957 100644
--- a/docs/my-website/docs/observability/wandb_integration.md
+++ b/docs/my-website/docs/observability/wandb_integration.md
@@ -57,5 +57,4 @@ response = litellm.completion(
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
\ No newline at end of file
diff --git a/docs/my-website/docs/prompt_management.md b/docs/my-website/docs/prompt_management.md
new file mode 100644
index 00000000000..c4e606674b1
--- /dev/null
+++ b/docs/my-website/docs/prompt_management.md
@@ -0,0 +1,48 @@
+---
+title: Prompt Management with Responses API
+---
+
+# Prompt Management with Responses API
+
+Use LiteLLM Prompt Management with `/v1/responses` by passing `prompt_id` and optional `prompt_variables`.
+
+## Basic Usage
+
+```bash
+curl -X POST "http://localhost:4000/v1/responses" \
+ -H "Authorization: Bearer sk-1234" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "model": "gpt-4o",
+ "prompt_id": "my-responses-prompt",
+ "prompt_variables": {"topic": "large language models"},
+ "input": []
+ }'
+```
+
+## Multi-turn Follow-up in `input`
+
+To send follow-up turns in one request, pass message history in `input`.
+
+```bash
+curl -X POST "http://localhost:4000/v1/responses" \
+ -H "Authorization: Bearer sk-1234" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "model": "gpt-4o",
+ "prompt_id": "my-responses-prompt",
+ "prompt_variables": {"topic": "large language models"},
+ "input": [
+ {"role": "user", "content": "Topic is LLMs. Start short."},
+ {"role": "assistant", "content": "Sure, go ahead."},
+ {"role": "user", "content": "Now give me 3 bullets and include pricing caveat."}
+ ]
+ }'
+```
+
+## Notes
+
+- Prompt template messages are merged with your `input` messages.
+- Prompt variable substitution applies to prompt message content.
+- Tool call payload fields are not substituted by prompt variables.
+- For follow-ups with `previous_response_id`, include `prompt_id` again if you want prompt management applied on that turn.
diff --git a/docs/my-website/docs/providers/azure/azure.md b/docs/my-website/docs/providers/azure/azure.md
index 12ddc1bd98e..682f263c108 100644
--- a/docs/my-website/docs/providers/azure/azure.md
+++ b/docs/my-website/docs/providers/azure/azure.md
@@ -1032,7 +1032,7 @@ print("list_batches_response=", list_batches_response)
-### [Health Check Azure Batch models](./proxy/health.md#batch-models-azure-only)
+### [Health Check Azure Batch models](../../proxy/health.md#batch-models-azure-only)
### [BETA] Loadbalance Multiple Azure Deployments
diff --git a/docs/my-website/docs/providers/azure/azure_anthropic.md b/docs/my-website/docs/providers/azure/azure_anthropic.md
index 4c722b30397..e7cd8fffbf0 100644
--- a/docs/my-website/docs/providers/azure/azure_anthropic.md
+++ b/docs/my-website/docs/providers/azure/azure_anthropic.md
@@ -372,7 +372,6 @@ response = completion(
## Related Documentation
-- [Anthropic Provider Documentation](./anthropic.md) - For standard Anthropic API usage
+- [Anthropic Provider Documentation](../anthropic.md) - For standard Anthropic API usage
- [Azure OpenAI Documentation](./azure.md) - For Azure OpenAI models
-- [Azure Authentication Guide](../secret_managers/azure_key_vault.md) - For Azure AD token setup
-
+- [Azure Authentication Guide](../../secret_managers/azure_key_vault.md) - For Azure AD token setup
diff --git a/docs/my-website/docs/providers/gemini.md b/docs/my-website/docs/providers/gemini.md
index 0aaf3d5ae81..87ab5ad40f4 100644
--- a/docs/my-website/docs/providers/gemini.md
+++ b/docs/my-website/docs/providers/gemini.md
@@ -11,6 +11,7 @@ import TabItem from '@theme/TabItem';
| Provider Doc | [Google AI Studio ↗](https://aistudio.google.com/) |
| API Endpoint for Provider | https://generativelanguage.googleapis.com |
| Supported OpenAI Endpoints | `/chat/completions`, [`/embeddings`](../embedding/supported_embedding#gemini-ai-embedding-models), `/completions`, [`/videos`](./gemini/videos.md), [`/images/edits`](../image_edits.md) |
+| Lyria (music) | [Cost map & notes](./gemini/music.md) |
| Pass-through Endpoint | [Supported](../pass_through/google_ai_studio.md) |
@@ -54,6 +55,7 @@ response = completion(
- stream
- tools
- tool_choice
+- include_server_side_tool_invocations
- functions
- response_format
- n
@@ -856,7 +858,112 @@ curl -X POST 'http://0.0.0.0:4000/chat/completions' \
-### URL Context
+### Context Circulation (Server-Side Tool Combination)
+
+Context circulation allows Gemini 3+ models to combine **built-in tools** (like Google Search) with **your custom functions** in the same request. Without it, Gemini returns an error if you try to use both.
+
+When enabled, Gemini can execute Google Search server-side, use those results to decide whether to call your custom functions, and return the full chain of reasoning.
+
+**How it works:**
+1. You pass `include_server_side_tool_invocations=True` along with both Google Search and your function tools
+2. Gemini executes server-side tools internally and returns `toolCall`/`toolResponse` parts alongside any `functionCall` parts
+3. LiteLLM extracts the server-side invocations into `provider_specific_fields["server_side_tool_invocations"]`
+4. On subsequent turns, include the full assistant message in your conversation history — LiteLLM re-injects the server-side parts automatically
+
+
+
+
+```python
+from litellm import completion
+
+response = completion(
+ model="gemini/gemini-3-flash-preview",
+ messages=[{"role": "user", "content": "What's the weather in Buenos Aires? If it's raining, schedule a meeting."}],
+ tools=[
+ {"type": "web_search_preview"}, # Google Search (server-side)
+ {
+ "type": "function",
+ "function": {
+ "name": "schedule_meeting",
+ "description": "Schedule a meeting",
+ "parameters": {
+ "type": "object",
+ "properties": {"reason": {"type": "string"}},
+ "required": ["reason"],
+ },
+ },
+ },
+ ],
+ include_server_side_tool_invocations=True,
+)
+
+msg = response.choices[0].message
+
+# Server-side tool results are in provider_specific_fields
+psf = msg.provider_specific_fields or {}
+for invocation in psf.get("server_side_tool_invocations", []):
+ print(invocation["tool_type"]) # e.g. "GOOGLE_SEARCH_WEB"
+ print(invocation["id"])
+ print(invocation["args"]) # e.g. {"queries": ["weather Buenos Aires"]}
+ print(invocation["response"]) # Search results from Google
+
+# For multi-turn: just append the full message to history
+messages.append(msg)
+messages.append({"role": "user", "content": "Thanks!"})
+# LiteLLM automatically re-injects the server-side parts + thought signatures
+response2 = completion(
+ model="gemini/gemini-3-flash-preview",
+ messages=messages,
+ tools=tools,
+ include_server_side_tool_invocations=True,
+)
+```
+
+
+
+
+1. Setup config.yaml
+```yaml
+model_list:
+ - model_name: gemini-3-flash
+ litellm_params:
+ model: gemini/gemini-3-flash-preview
+ api_key: os.environ/GEMINI_API_KEY
+```
+
+2. Start Proxy
+```bash
+$ litellm --config /path/to/config.yaml
+```
+
+3. Make Request
+```bash
+curl -X POST 'http://0.0.0.0:4000/chat/completions' \
+-H 'Content-Type: application/json' \
+-H 'Authorization: Bearer sk-1234' \
+-d '{
+ "model": "gemini-3-flash",
+ "messages": [{"role": "user", "content": "What is the weather in Buenos Aires?"}],
+ "tools": [
+ {"type": "web_search_preview"},
+ {"type": "function", "function": {"name": "schedule_meeting", "description": "Schedule a meeting", "parameters": {"type": "object", "properties": {"reason": {"type": "string"}}}}}
+ ],
+ "include_server_side_tool_invocations": true
+}'
+```
+
+
+
+
+:::info
+
+- Context circulation requires **Gemini 3+** models
+- Server-side tool invocations (`toolCall`/`toolResponse`) are **not** included in `tool_calls` — they are in `provider_specific_fields["server_side_tool_invocations"]` because they were already executed by Google, not by your code
+- `thought_signatures` are automatically preserved alongside server-side invocations for multi-turn coherence
+
+:::
+
+### URL Context
diff --git a/docs/my-website/docs/providers/gemini/music.md b/docs/my-website/docs/providers/gemini/music.md
new file mode 100644
index 00000000000..f3968f2db39
--- /dev/null
+++ b/docs/my-website/docs/providers/gemini/music.md
@@ -0,0 +1,28 @@
+# Gemini — Lyria (music generation)
+
+Google Lyria 3 preview models are listed in LiteLLM’s [model cost map](https://github.com/BerriAI/litellm/blob/main/model_prices_and_context_window.json) under the `gemini/` provider for metadata and spend tracking.
+
+| Property | Details |
+|----------|---------|
+| Provider route | `gemini/` |
+| Models | `gemini/lyria-3-clip-preview`, `gemini/lyria-3-pro-preview` |
+| Provider docs | [Gemini API pricing / models ↗](https://ai.google.dev/gemini-api/docs/pricing) |
+
+## Models
+
+| Model | Notes |
+|-------|--------|
+| `gemini/lyria-3-clip-preview` | ~30s clip; paid tier listed as per generated song in Google’s pricing |
+| `gemini/lyria-3-pro-preview` | Full song; paid tier listed as per generated song in Google’s pricing |
+
+Input context limit in the cost map: **131,072** tokens. For modalities, limits, and features, see [Google’s Gemini API docs ↗](https://ai.google.dev/gemini-api/docs/models).
+
+## LiteLLM behavior
+
+- **Cost map**: Per-song paid pricing is stored as `output_cost_per_image` on those entries (flat per generation unit). Token-based completion cost may not reflect music billing until a dedicated path exists.
+- **API calls**: Use the Gemini API as documented by Google. LiteLLM does not ship a separate `music_generation` helper like Veo’s `video_generation`.
+
+## Auth
+
+Same as other Gemini API models: `GEMINI_API_KEY` or `GOOGLE_API_KEY`.
+
diff --git a/docs/my-website/docs/providers/openai.md b/docs/my-website/docs/providers/openai.md
index 80931ad8217..1f4a1687e8b 100644
--- a/docs/my-website/docs/providers/openai.md
+++ b/docs/my-website/docs/providers/openai.md
@@ -581,6 +581,90 @@ curl -X POST 'http://0.0.0.0:4000/chat/completions' \
See [OpenAI Reasoning documentation](https://platform.openai.com/docs/guides/reasoning) for more details on organization verification requirements.
+### Multi-turn Conversations with `reasoning_items`
+
+For multi-turn conversations you need `reasoning_items`: structured blocks that include the `encrypted_content` token OpenAI uses to restore reasoning state on the next request. Pass `include=["reasoning.encrypted_content"]` on every call where you want that token returned.
+
+
+
+
+```python showLineNumbers title="Non-streaming: round-trip reasoning_items"
+import litellm
+
+messages = [{"role": "user", "content": "Solve this step by step: 2 + 2"}]
+
+# Turn 1 — get reasoning_items (encrypted_content);
+response = litellm.completion(
+ model="openai/responses/gpt-5-mini",
+ messages=messages,
+ reasoning_effort="low",
+ include=["reasoning.encrypted_content"],
+)
+
+assistant_msg = response.choices[0].message
+
+# Turn 2 — pass reasoning_items back; LiteLLM converts to the correct Responses API format
+messages.append({
+ "role": "assistant",
+ "content": assistant_msg.content,
+ "reasoning_items": assistant_msg.reasoning_items,
+})
+messages.append({"role": "user", "content": "Now summarize your reasoning."})
+
+response2 = litellm.completion(
+ model="openai/responses/gpt-5-mini",
+ messages=messages,
+ reasoning_effort="low",
+ include=["reasoning.encrypted_content"],
+)
+```
+
+
+
+
+`reasoning_items` (with `encrypted_content`) arrive on the final chunk when the full response completes:
+
+```python showLineNumbers title="Streaming: collect and round-trip reasoning_items"
+import litellm
+
+messages = [{"role": "user", "content": "Solve this step by step: 2 + 2"}]
+
+collected_content = []
+collected_reasoning_items = []
+
+stream = litellm.completion(
+ model="openai/responses/gpt-5-mini",
+ messages=messages,
+ stream=True,
+ reasoning_effort="low",
+ include=["reasoning.encrypted_content"],
+)
+
+for chunk in stream:
+ delta = chunk.choices[0].delta
+ if delta.content:
+ collected_content.append(delta.content)
+ if getattr(delta, "reasoning_items", None):
+ collected_reasoning_items.extend(delta.reasoning_items)
+
+messages.append({
+ "role": "assistant",
+ "content": "".join(collected_content),
+ "reasoning_items": collected_reasoning_items or None,
+})
+messages.append({"role": "user", "content": "Continue the conversation."})
+
+response2 = litellm.completion(
+ model="openai/responses/gpt-5-mini",
+ messages=messages,
+ reasoning_effort="low",
+ include=["reasoning.encrypted_content"],
+)
+```
+
+
+
+
### Verbosity Control for GPT-5 Models
The `verbosity` parameter controls the length and detail of responses from GPT-5 family models. It accepts three values: `"low"`, `"medium"`, or `"high"`.
@@ -1153,4 +1237,4 @@ response = completion(
LiteLLM supports OpenAI's video generation models including Sora.
-For detailed documentation on video generation, see [OpenAI Video Generation →](./openai/video_generation.md)
+For detailed documentation on video generation, see [OpenAI Video Generation →](./openai/videos.md)
diff --git a/docs/my-website/docs/proxy/call_hooks.md b/docs/my-website/docs/proxy/call_hooks.md
index 17354725fd5..5935a29c50b 100644
--- a/docs/my-website/docs/proxy/call_hooks.md
+++ b/docs/my-website/docs/proxy/call_hooks.md
@@ -7,7 +7,7 @@ import Image from '@theme/IdealImage';
- Enforce 'user' param for all openai endpoint calls
:::tip
-**Understanding Callback Hooks?** Check out our [Callback Management Guide](../observability/callback_management.md) to understand the differences between proxy-specific hooks like `async_pre_call_hook` and general logging hooks like `async_log_success_event`.
+**Understanding Callback Hooks?** Check out our [Callback Guide](../observability/callbacks.md) to understand the differences between proxy-specific hooks like `async_pre_call_hook` and general logging hooks like `async_log_success_event`.
:::
## Which Hook Should I Use?
diff --git a/docs/my-website/docs/proxy/config_settings.md b/docs/my-website/docs/proxy/config_settings.md
index a0e404e3a18..cc9090c2de6 100644
--- a/docs/my-website/docs/proxy/config_settings.md
+++ b/docs/my-website/docs/proxy/config_settings.md
@@ -206,7 +206,7 @@ router_settings:
| Name | Type | Description |
|------|------|-------------|
-| completion_model | string | The default model to use for completions when `model` is not specified in the request |
+| completion_model | string | The model to use for all completions, overriding any `model` specified in the request |
| disable_spend_logs | boolean | If true, turns off writing each transaction to the database |
| disable_spend_updates | boolean | If true, turns off all spend updates to the DB. Including key/user/team spend updates. |
| disable_master_key_return | boolean | If true, turns off returning master key on UI. (checked on '/user/info' endpoint) |
@@ -279,6 +279,33 @@ router_settings:
| forward_client_headers_to_llm_api | boolean | If true, forwards the client headers (any `x-` headers and `anthropic-beta` headers) to the backend LLM call |
| maximum_spend_logs_retention_period | str | Used to set the max retention time for spend logs in the db, after which they will be auto-purged |
| maximum_spend_logs_retention_interval | str | Used to set the interval in which the spend log cleanup task should run in. |
+| alert_type_config | dict | Configuration mapping alert types to their handler settings |
+| always_include_stream_usage | boolean | If true, includes usage metrics in every streaming response chunk |
+| auto_redirect_ui_login_to_sso | boolean | If true, automatically redirects UI login page to SSO provider |
+| control_plane_url | string | URL of the control plane for cross-instance state sharing |
+| custom_auth_run_common_checks | boolean | If true, runs standard auth validation checks alongside custom auth handlers |
+| custom_ui_sso_sign_in_handler | string | Custom handler for SSO sign-in logic in the UI |
+| database_connection_pool_timeout | integer | Database connection pool timeout in seconds |
+| disable_error_logs | boolean | If true, suppresses error tracking and storage in the database |
+| enable_health_check_routing | boolean | If true, enables health check-driven request routing to avoid unhealthy deployments |
+| enable_mcp_registry | boolean | If true, enables access to the centralized MCP server registry |
+| enforce_rbac | boolean | If true, enables role-based access control (RBAC) for all proxy operations |
+| forward_llm_provider_auth_headers | boolean | If true, forwards provider-specific auth headers to LLM API calls |
+| health_check_concurrency | integer | Maximum number of concurrent health check operations |
+| health_check_staleness_threshold | integer | Maximum age in seconds for health check results before marking deployments as stale |
+| maximum_spend_logs_cleanup_cron | string | Cron expression for scheduling automatic spend log cleanup tasks |
+| mcp_client_side_auth_header_name | string | HTTP header name for client-side MCP server credentials |
+| mcp_internal_ip_ranges | list | CIDR ranges considered internal for non-public MCP server access control |
+| mcp_required_fields | list | List of required field names for MCP server submissions |
+| mcp_trusted_proxy_ranges | list | CIDR ranges of proxies trusted to forward X-Forwarded-For headers for MCP |
+| require_end_user_mcp_access_defined | boolean | If true, requires end users to have explicit MCP access permissions defined |
+| role_permissions | list | List of role-based permission configurations |
+| search_tools | list | List of search tool configurations for enabling web search capabilities |
+| token_rate_limit_type | string | Rate limit counting method: "total", "output", or "input" tokens |
+| use_redis_transaction_buffer | boolean | If true, buffers database transactions in Redis before writing |
+| use_shared_health_check | boolean | If true, uses Redis-backed shared health check state across multiple proxy instances |
+| user_header_mappings | dict | Map custom request headers to user IDs using lookup rules |
+| user_header_name | string | HTTP header name to extract user identity from requests |
### router_settings - Reference
@@ -361,11 +388,14 @@ router_settings:
| redis_url | str | URL for Redis server. **Known performance issue with Redis URL.** |
| cache_responses | boolean | Flag to enable caching LLM Responses, if cache set under `router_settings`. If true, caches responses. Defaults to False. |
| router_general_settings | RouterGeneralSettings | [SDK-Only] Router general settings - contains optimizations like 'async_only_mode'. [Docs](../routing.md#router-general-settings) |
-| optional_pre_call_checks | List[str] | List of pre-call checks to add to the router. Supported: `router_budget_limiting`, `prompt_caching`, `responses_api_deployment_check`, `encrypted_content_affinity`, `deployment_affinity`, `session_affinity`, `forward_client_headers_by_model_group` |
+| optional_pre_call_checks | List[str] | List of pre-call checks to add to the router. Supported: `router_budget_limiting`, `prompt_caching`, `responses_api_deployment_check`, `encrypted_content_affinity` (requires LiteLLM >= 1.82.3), `deployment_affinity`, `session_affinity`, `forward_client_headers_by_model_group` |
| deployment_affinity_ttl_seconds | int | TTL (seconds) for user-key → deployment affinity mapping when `deployment_affinity` is enabled (configured at Router init / proxy startup). Defaults to `3600` (1 hour). |
+| model_group_affinity_config | Dict[str, List[str]] | Per-model-group affinity flags. Keys are model group names; values are lists of checks to enable (`deployment_affinity`, `responses_api_deployment_check`, `session_affinity`). Groups not listed fall back to the global `optional_pre_call_checks`. [Docs](../response_api.md#per-model-group-affinity-configuration) |
| ignore_invalid_deployments | boolean | If true, ignores invalid deployments. Default for proxy is True - to prevent invalid models from blocking other models from being loaded. |
-| search_tools | List[SearchToolTypedDict] | List of search tool configurations for Search API integration. Each tool specifies a search_tool_name and litellm_params with search_provider, api_key, api_base, etc. [Further Docs](../search.md) |
+| search_tools | List[SearchToolTypedDict] | List of search tool configurations for Search API integration. Each tool specifies a search_tool_name and litellm_params with search_provider, api_key, api_base, etc. [Further Docs](../search/index.md) |
| guardrail_list | List[GuardrailTypedDict] | List of guardrail configurations for guardrail load balancing. Enables load balancing across multiple guardrail deployments with the same guardrail_name. [Further Docs](./guardrails/guardrail_load_balancing.md) |
+| enable_health_check_routing | boolean | If true, enables health check-driven deployment filtering to avoid routing requests to unhealthy deployments |
+| health_check_staleness_threshold | integer | Maximum age in seconds for cached health check results before marking deployments as stale |
### environment variables - Reference
@@ -401,8 +431,10 @@ router_settings:
| AUTH_STRATEGY | Strategy used for authentication (e.g., OAuth, API key)
| AUTO_REDIRECT_UI_LOGIN_TO_SSO | Flag to enable automatic redirect of UI login page to SSO when SSO is configured. Default is **false**
| AUDIO_SPEECH_CHUNK_SIZE | Chunk size for audio speech processing. Default is 1024
-| ANTHROPIC_API_KEY | API key for Anthropic service
+| ANTHROPIC_API_KEY | API key for Anthropic service. Uses `x-api-key` header for authentication.
+| ANTHROPIC_AUTH_TOKEN | Alternative auth token for Anthropic service. Uses `Authorization: Bearer` header instead of `x-api-key`. Used as fallback when `ANTHROPIC_API_KEY` is not set.
| ANTHROPIC_API_BASE | Base URL for Anthropic API. Default is https://api.anthropic.com
+| ANTHROPIC_BASE_URL | Alternative to `ANTHROPIC_API_BASE` for setting the Anthropic API base URL. Used as fallback when `ANTHROPIC_API_BASE` is not set.
| ANTHROPIC_TOKEN_COUNTING_BETA_VERSION | Beta version header for Anthropic token counting API. Default is `token-counting-2024-11-01`
| AWS_ACCESS_KEY_ID | Access Key ID for AWS services
| AWS_BATCH_ROLE_ARN | ARN of the AWS IAM role for batch operations
@@ -801,6 +833,7 @@ router_settings:
| LITELLM_OTEL_INTEGRATION_ENABLE_EVENTS | Optionally enable semantic logs for OTEL
| LITELLM_OTEL_INTEGRATION_ENABLE_METRICS | Optionally enable emantic metrics for OTEL
| LITELLM_ENABLE_PYROSCOPE | If true, enables Pyroscope CPU profiling. Profiles are sent to PYROSCOPE_SERVER_ADDRESS. Off by default. See [Pyroscope profiling](/proxy/pyroscope_profiling).
+| LITELLM_ENABLE_TEAM_STALE_ALIAS_BYPASS | When `true`, if a team's legacy `model_aliases` entry maps a public model name to an internal `model_name__` deployment, pre-call handling can skip that rewrite when team-scoped sibling deployments exist for the public name—so load balancing / `order` apply across siblings. Default is `false` for backwards compatibility. See [Team-scoped models and legacy aliases](./load_balancing#team-scoped-models-and-legacy-model_aliases). When stale aliases are detected and this flag is off, the proxy may log a one-time warning.
| PYROSCOPE_APP_NAME | Application name reported to Pyroscope. Required when LITELLM_ENABLE_PYROSCOPE is true. No default.
| PYROSCOPE_SERVER_ADDRESS | Pyroscope server URL to send profiles to. Required when LITELLM_ENABLE_PYROSCOPE is true. No default.
| PYROSCOPE_SAMPLE_RATE | Optional. Sample rate for Pyroscope profiling (integer). No default; when unset, the pyroscope-io library default is used.
@@ -811,7 +844,7 @@ router_settings:
| LITELLM_MODE | Operating mode for LiteLLM (e.g., production, development)
| LITELLM_NON_ROOT | Flag to run LiteLLM in non-root mode for enhanced security in Docker containers
| LITELLM_RATE_LIMIT_WINDOW_SIZE | Rate limit window size for LiteLLM. Default is 60
-| LITELLM_REASONING_AUTO_SUMMARY | If set to "true", automatically enables detailed reasoning summaries for reasoning models (e.g., o1, o3-mini, deepseek-reasoner). When enabled, adds `summary: "detailed"` to reasoning effort configurations. Default is "false"
+| LITELLM_REASONING_AUTO_SUMMARY | If set to "true", automatically enables detailed reasoning summaries (`summary: "detailed"`) for reasoning models across all translation paths (Anthropic adapter, Responses API, etc.). Default is "false"
| LITELLM_SALT_KEY | Salt key for encryption in LiteLLM
| LITELLM_SSL_CIPHERS | SSL/TLS cipher configuration for faster handshakes. Controls cipher suite preferences for OpenSSL connections.
| LITELLM_SECRET_AWS_KMS_LITELLM_LICENSE | AWS KMS encrypted license for LiteLLM
@@ -902,6 +935,7 @@ router_settings:
| OTEL_SERVICE_NAME | Service name identifier for OpenTelemetry
| OTEL_TRACER_NAME | Tracer name for OpenTelemetry tracing
| OTEL_LOGS_EXPORTER | Exporter type for OpenTelemetry logs (e.g., console)
+| OTEL_IGNORE_CONTEXT_PROPAGATION | When true, ignore parent span context propagation in OpenTelemetry callbacks
| PAGERDUTY_API_KEY | API key for PagerDuty Alerting
| PANW_PRISMA_AIRS_API_KEY | API key for PANW Prisma AIRS service
| PANW_PRISMA_AIRS_API_BASE | Base URL for PANW Prisma AIRS service
@@ -949,6 +983,8 @@ router_settings:
| QDRANT_URL | Connection URL for Qdrant database
| QDRANT_VECTOR_SIZE | Vector size for Qdrant operations. Default is 1536
| REDIS_CONNECTION_POOL_TIMEOUT | Timeout in seconds for Redis connection pool. Default is 5
+| REDIS_CIRCUIT_BREAKER_FAILURE_THRESHOLD | Number of consecutive failures before the Redis circuit breaker opens. Default is 5
+| REDIS_CIRCUIT_BREAKER_RECOVERY_TIMEOUT | Time in seconds before the Redis circuit breaker attempts recovery after opening. Default is 60
| REDIS_CLUSTER_NODES | JSON-formatted list of Redis cluster startup nodes for Redis Cluster mode. Example: `[{"host": "node1", "port": 6379}]`
| REDIS_HOST | Hostname for Redis server
| REDIS_PASSWORD | Password for Redis service
diff --git a/docs/my-website/docs/proxy/configs.md b/docs/my-website/docs/proxy/configs.md
index 56a8b9566db..84a6fac1210 100644
--- a/docs/my-website/docs/proxy/configs.md
+++ b/docs/my-website/docs/proxy/configs.md
@@ -602,6 +602,22 @@ Since you shouldn't use 12.5, round down to **10** to leave a safety buffer. Thi
- Total maximum connections: 8 workers × 10 connections = 80 connections
- This stays safely under your database's 100 connection limit
+## LiteLLM License Key (Enterprise)
+
+To enable [LiteLLM Enterprise features](https://docs.litellm.ai/docs/proxy/enterprise), set your license key as an environment variable:
+
+```bash
+export LITELLM_LICENSE="eyJ..."
+```
+
+The license key is a JWT token provided when you purchase a LiteLLM Enterprise license. Once set, LiteLLM will automatically detect and activate enterprise features.
+
+You can also add it to your `.env` file:
+
+```env
+LITELLM_LICENSE="eyJ..."
+```
+
## Extras
diff --git a/docs/my-website/docs/proxy/cost_tracking.md b/docs/my-website/docs/proxy/cost_tracking.md
index f28eec287d4..f9e22cfecd3 100644
--- a/docs/my-website/docs/proxy/cost_tracking.md
+++ b/docs/my-website/docs/proxy/cost_tracking.md
@@ -163,7 +163,7 @@ Use this when you want non-proxy admins to access `/spend` endpoints
:::info
-Schedule a [meeting with us to get your Enterprise License](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+Schedule a [meeting with us to get your Enterprise License](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/proxy/docker_quick_start.md b/docs/my-website/docs/proxy/docker_quick_start.md
index efdc73de43e..58a56604751 100644
--- a/docs/my-website/docs/proxy/docker_quick_start.md
+++ b/docs/my-website/docs/proxy/docker_quick_start.md
@@ -1,25 +1,90 @@
-
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
+import Image from '@theme/IdealImage';
# Getting Started Tutorial
End-to-End tutorial for LiteLLM Proxy to:
-- Add an Azure OpenAI model
-- Make a successful /chat/completion call
-- Generate a virtual key
-- Set RPM limit on virtual key
+- Add an Azure OpenAI model
+- Make a successful /chat/completion call
+- Generate a virtual key
+- Set RPM limit on virtual key
+## Quick Install (Recommended for local / beginners)
+
+New to LiteLLM? This is the easiest way to get started locally. One command installs LiteLLM and walks you through setup interactively — no config files to write by hand.
+
+### 1. Install
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/BerriAI/litellm/main/scripts/install.sh | sh
+```
+
+This detects your OS, installs `litellm[proxy]`, and drops you straight into the setup wizard.
+
+### 2. Follow the wizard
+
+```
+$ litellm --setup
+
+ Welcome to LiteLLM
+
+ Choose your LLM providers
+ ○ 1. OpenAI GPT-4o, GPT-4o-mini, o1
+ ○ 2. Anthropic Claude Opus, Sonnet, Haiku
+ ○ 3. Azure OpenAI GPT-4o via Azure
+ ○ 4. Google Gemini Gemini 2.0 Flash, 1.5 Pro
+ ○ 5. AWS Bedrock Claude, Llama via AWS
+ ○ 6. Ollama Local models
+
+ ❯ Provider(s): 1,2
+
+ ❯ OpenAI API key: sk-...
+ ❯ Anthropic API key: sk-ant-...
+
+ ❯ Port [4000]:
+ ❯ Master key [auto-generate]:
+
+ ✔ Config saved → ./litellm_config.yaml
+
+ ❯ Start the proxy now? (Y/n):
+```
+
+The wizard walks you through:
+1. Pick your LLM providers (OpenAI, Anthropic, Azure, Bedrock, Gemini, Ollama)
+2. Enter API keys for each provider
+3. Set a port and master key (or accept the defaults)
+4. Config is saved to `./litellm_config.yaml` and the proxy starts immediately
+
+### 3. Make a call
+
+Your proxy is running on `http://0.0.0.0:4000`. Test it:
+
+```bash
+curl -X POST 'http://0.0.0.0:4000/chat/completions' \
+-H 'Content-Type: application/json' \
+-H 'Authorization: Bearer ' \
+-d '{
+ "model": "gpt-4o",
+ "messages": [{"role": "user", "content": "Hello!"}]
+}'
+```
+
+:::tip Already have pip installed?
+You can skip the curl install and run `litellm --setup` directly after `pip install 'litellm[proxy]'`.
+:::
+
+---
## Pre-Requisites
-- Install LiteLLM Docker Image **OR** LiteLLM CLI (pip package)
+Choose your install method. **Docker Compose** users complete their full setup inside the tab and are done. **Docker** and **pip** users continue with the steps below the tabs.
-```
+```bash
docker pull docker.litellm.ai/berriai/litellm:main-latest
```
@@ -37,7 +102,25 @@ $ pip install 'litellm[proxy]'
-Use this docker compose to spin up the proxy with a postgres database running locally.
+Docker Compose bundles LiteLLM with a Postgres database. Follow the steps below — the proxy will be fully running by the end.
+
+### Step 1 — Pull the LiteLLM database image
+
+LiteLLM provides a dedicated `litellm-database` image for proxy deployments that connect to Postgres.
+
+```bash
+docker pull ghcr.io/berriai/litellm-database:main-latest
+```
+
+See all available tags on the [GitHub Container Registry](https://github.com/BerriAI/litellm/pkgs/container/litellm-database).
+
+---
+
+### Step 2 — Set up a database
+
+Complete all three config files **before** running `docker compose up`. The proxy server will not start correctly if any of these are missing.
+
+#### 2.1 — Get `docker-compose.yml` and create `.env`
```bash
# Get the docker compose file
@@ -46,26 +129,154 @@ curl -O https://raw.githubusercontent.com/BerriAI/litellm/main/docker-compose.ym
# Add the master key - you can change this after setup
echo 'LITELLM_MASTER_KEY="sk-1234"' > .env
-# Add the litellm salt key - you cannot change this after adding a model
-# It is used to encrypt / decrypt your LLM API Key credentials
-# We recommend - https://1password.com/password-generator/
-# password generator to get a random hash for litellm salt key
+# Add the litellm salt key — cannot be changed after adding a model
+# Used to encrypt/decrypt your LLM API key credentials
+# Generate a strong random value: https://1password.com/password-generator/
echo 'LITELLM_SALT_KEY="sk-1234"' >> .env
-# Start
+# Add your model credentials
+echo 'AZURE_API_BASE="https://openai-***********/"' >> .env
+echo 'AZURE_API_KEY="your-azure-api-key"' >> .env
+```
+
+#### 2.2 — Create `config.yaml`
+
+The default `docker-compose.yml` starts a Postgres container at `db:5432`. Your `config.yaml` must include `database_url` pointing to it:
+
+```yaml
+model_list:
+ - model_name: gpt-4o
+ litellm_params:
+ model: azure/my_azure_deployment
+ api_base: os.environ/AZURE_API_BASE
+ api_key: os.environ/AZURE_API_KEY
+ api_version: "2025-01-01-preview"
+
+general_settings:
+ master_key: sk-1234 # 🔑 your proxy admin key (must start with sk-)
+ database_url: "postgresql://llmproxy:dbpassword9090@db:5432/litellm"
+```
+
+:::tip
+`database_url` enables virtual keys, spend tracking, and the UI. Replace it with your [Supabase](https://supabase.com/) or [Neon](https://neon.tech/) connection string if you prefer a managed database.
+:::
+
+#### 2.3 — Create `prometheus.yml`
+
+This file **must exist as a file** before `docker compose up`. If it is missing, Docker auto-creates it as an empty directory and the Prometheus container fails to start.
+
+```yaml
+global:
+ scrape_interval: 15s
+ evaluation_interval: 15s
+
+scrape_configs:
+ - job_name: "litellm"
+ static_configs:
+ - targets: ["litellm:4000"]
+```
+
+Also verify that the `config.yaml` volume mount and `--config` flag are **not commented out** in `docker-compose.yml`:
+
+```yaml
+services:
+ litellm:
+ volumes:
+ - ./config.yaml:/app/config.yaml # ✅ must be uncommented
+ command:
+ - "--config=/app/config.yaml" # ✅ must be uncommented
+```
+
+:::warning
+All three files (`.env`, `config.yaml`, `prometheus.yml`) must be present before running `docker compose up`. See [Troubleshooting](#troubleshooting) if you run into issues.
+:::
+
+---
+
+### Step 3 — Start the proxy server and test it
+
+After `config.yaml`, `prometheus.yml`, and `.env` are complete, start the proxy:
+
+```bash
docker compose up
```
+Once running, test it with a curl request:
+
+```bash
+curl -X POST 'http://0.0.0.0:4000/chat/completions' \
+ -H 'Content-Type: application/json' \
+ -H 'Authorization: Bearer sk-1234' \
+ -d '{
+ "model": "gpt-4o",
+ "messages": [{"role": "user", "content": "Hello!"}]
+ }'
+```
+
+**Expected response:**
+
+```json
+{
+ "id": "chatcmpl-abcd",
+ "created": 1773817678,
+ "model": "gpt-4o",
+ "object": "chat.completion",
+ "system_fingerprint": "fp_6b1ef07cda",
+ "choices": [
+ {
+ "finish_reason": "stop",
+ "index": 0,
+ "message": {
+ "content": "Hello! How can I assist you today?",
+ "role": "assistant",
+ "annotations": []
+ }
+ }
+ ],
+ "usage": {
+ "completion_tokens": 9,
+ "prompt_tokens": 9,
+ "total_tokens": 18,
+ "completion_tokens_details": {
+ "accepted_prediction_tokens": 0,
+ "audio_tokens": 0,
+ "reasoning_tokens": 0,
+ "rejected_prediction_tokens": 0
+ },
+ "prompt_tokens_details": {
+ "audio_tokens": 0,
+ "cached_tokens": 0
+ }
+ },
+ "service_tier": "default"
+}
+```
+
+---
+
+### Optional — Navigate to the LiteLLM UI and generate a virtual key
+
+Open [http://localhost:4000/ui](http://localhost:4000/ui) in your browser and log in with your master key (`sk-1234`).
+
+Navigate to **Virtual Keys** and click **+ Create New Key**:
+
+
+
+Virtual keys let you track spend, set rate limits, and control model access per user or team.
+
+
-## 1. Add a model
+:::note Docker Compose users
+Your setup is complete — the steps below are for **Docker** and **pip** users only.
+:::
-Control LiteLLM Proxy with a config.yaml file.
+---
-Setup your config.yaml with your azure model.
+## Step 1 — Add a model
-Note: When using the proxy with a database, you can also **just add models via UI** (UI is available on `/ui` route).
+Control LiteLLM Proxy with a `config.yaml` file. Create one with your Azure model:
```yaml
model_list:
@@ -89,8 +300,6 @@ You can read more about how model resolution works in the [Model Configuration](
- **`api_base`** (`str`) - The API base for your azure deployment.
- **`api_version`** (`str`) - The API Version to use when calling Azure's OpenAI API. Get the latest Inference API version [here](https://learn.microsoft.com/en-us/azure/ai-services/openai/api-version-deprecation?source=recommendations#latest-preview-api-releases).
----
-
---
@@ -138,19 +347,19 @@ $ litellm --config /app/config.yaml --detailed_debug
+Confirm your config was loaded correctly — you should see this in the logs:
-Confirm your config.yaml got mounted correctly
-
-```bash
+```
Loaded config YAML (api_key and environment_variables are not shown):
{
-"model_list": [
-{
-"model_name ...
+ "model_list": [
+ {
+ "model_name": ...
```
### 2.2 Make Call
+LiteLLM Proxy is 100% OpenAI-compatible. Test your model via `/chat/completions`:
```bash
curl -X POST 'http://0.0.0.0:4000/chat/completions' \
@@ -244,15 +453,17 @@ curl -X POST 'http://0.0.0.0:4000/chat/completions' \
- [Other/Non-Chat Completion Endpoints](../embedding/supported_embedding.md)
- [Pass-through for VertexAI, Bedrock, etc.](../pass_through/vertex_ai.md)
-## 3. Generate a virtual key
+## Optional: Generate a virtual key
-Track Spend, and control model access via virtual keys for the proxy
+Track spend and control model access via virtual keys for the proxy.
-### 3.1 Set up a Database
+### Prerequisite — Set up a database
-**Requirements**
-- Need a postgres database (e.g. [Supabase](https://supabase.com/), [Neon](https://neon.tech/), etc)
+:::note Docker Compose users
+Your Postgres container is already running — skip ahead to [Create Key w/ RPM Limit](#create-key-w-rpm-limit) below.
+:::
+**Docker / pip users** — you need a Postgres database (e.g. [Supabase](https://supabase.com/), [Neon](https://neon.tech/), or self-hosted). Add `general_settings` to your `config.yaml`:
```yaml
model_list:
@@ -268,7 +479,9 @@ general_settings:
database_url: "postgresql://:@:/" # 👈 KEY CHANGE
```
-Save config.yaml as `litellm_config.yaml` (used in 3.2).
+Save config.yaml as `litellm_config.yaml` before continuing.
+
+You must finish this setup before starting the proxy server.
---
@@ -294,7 +507,7 @@ See All General Settings [here](http://localhost:3000/docs/proxy/configs#all-set
`database_url: "postgresql://..."`
- Set `DATABASE_URL=postgresql://:@:/` in your env
-### 3.2 Start Proxy
+### Start Proxy
```bash
docker run \
@@ -302,12 +515,11 @@ docker run \
-e AZURE_API_KEY=d6*********** \
-e AZURE_API_BASE=https://openai-***********/ \
-p 4000:4000 \
- docker.litellm.ai/berriai/litellm:main-latest \
+ ghcr.io/berriai/litellm-database:main-latest \
--config /app/config.yaml --detailed_debug
```
-
-### 3.3 Create Key w/ RPM Limit
+### Create Key w/ RPM Limit
Create a key with `rpm_limit: 1`. This will only allow 1 request per minute for calls to proxy with this key.
@@ -330,9 +542,9 @@ curl -L -X POST 'http://0.0.0.0:4000/key/generate' \
}
```
-### 3.4 Test it!
+### Test it!
-**Use your virtual key from step 3.3**
+**Use the virtual key you just created.**
1st call - Expect to work!
@@ -546,6 +758,24 @@ model_list:
## Troubleshooting
+### `prometheus.yml` mount error — "not a directory"
+
+If you see:
+
+```bash
+Error: cannot create subdirectories in ".../prometheus.yml": not a directory
+```
+
+Docker created `prometheus.yml` as an **empty directory** instead of a file. This happens when the file is missing at `docker compose up` time.
+
+Fix it:
+Then create the file (see [Step 2.3 — Create `prometheus.yml`](#23--create-prometheusyml)) and run `docker compose up` again.
+```bash
+rm -rf prometheus.yml
+```
+
+Then create the file (see [Step 2.4](#step-24--create-prometheusyml)) and run `docker compose up` again.
+
### Non-root docker image?
If you need to run the docker image as a non-root user, use [this](https://github.com/BerriAI/litellm/pkgs/container/litellm-non_root).
@@ -645,6 +875,3 @@ LiteLLM Proxy uses the [LiteLLM Python SDK](https://docs.litellm.ai/docs/routing
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
[](https://wa.link/huol9n) [](https://discord.gg/wuPM9dRgDw)
-
-
-
diff --git a/docs/my-website/docs/proxy/email.md b/docs/my-website/docs/proxy/email.md
index 86a79cbcfc8..ba737c6782c 100644
--- a/docs/my-website/docs/proxy/email.md
+++ b/docs/my-website/docs/proxy/email.md
@@ -203,7 +203,7 @@ After regenerating the key, the user will receive an email notification with:
:::info
-Customizing Email Branding is an Enterprise Feature [Get in touch with us for a Free Trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+Customizing Email Branding is an Enterprise Feature [Get in touch with us for a Free Trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/proxy/endpoint_activity.md b/docs/my-website/docs/proxy/endpoint_activity.md
index a66c0f7a5e5..d06727ce4b4 100644
--- a/docs/my-website/docs/proxy/endpoint_activity.md
+++ b/docs/my-website/docs/proxy/endpoint_activity.md
@@ -114,4 +114,4 @@ Understand spend distribution across endpoints:
- [Customer Usage](./customer_usage.md) - Track spend and usage for individual customers
- [Cost Tracking](./cost_tracking.md) - Comprehensive cost tracking and analytics
-- [Spend Logs](./spend_logs.md) - Detailed request-level spend logs
+- [Spend Logs](./cost_tracking.md#-spend-logs-api---individual-transaction-logs) - Detailed request-level spend logs
diff --git a/docs/my-website/docs/proxy/enterprise.md b/docs/my-website/docs/proxy/enterprise.md
index 4b525837a20..09b103ca4a0 100644
--- a/docs/my-website/docs/proxy/enterprise.md
+++ b/docs/my-website/docs/proxy/enterprise.md
@@ -5,7 +5,7 @@ import TabItem from '@theme/TabItem';
# ✨ Enterprise Features
:::tip
-To get a license, get in touch with us [here](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+To get a license, get in touch with us [here](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/proxy/guardrails/akto.md b/docs/my-website/docs/proxy/guardrails/akto.md
new file mode 100644
index 00000000000..67ae741d11e
--- /dev/null
+++ b/docs/my-website/docs/proxy/guardrails/akto.md
@@ -0,0 +1,139 @@
+# Akto
+
+## Overview
+[Akto](https://www.akto.io/) provides API security guardrails and data ingestion for LLM traffic.
+
+Akto now uses a **two-entry guardrail pattern** in LiteLLM:
+- `akto-validate` (`pre_call`) for request validation
+- `akto-ingest` (`post_call`) for request/response ingestion
+
+There is no `on_flagged` setting anymore.
+
+Use these as two separate guardrails in `config.yaml`:
+- `guardrail_name: "akto-validate"`
+- `guardrail_name: "akto-ingest"`
+
+## 1. Get Your Akto Credentials
+
+Set up the Akto Guardrail API Service and grab:
+- `AKTO_GUARDRAIL_API_BASE` — your Guardrail API Base URL
+- `AKTO_API_KEY` — your API key
+
+## 2. Configure in `config.yaml`
+
+### Block + Ingest (recommended)
+
+Use both entries below. This gives you:
+- pre-call block decision
+- post-call ingestion for allowed traffic
+
+Keep these as two separate entries (`akto-validate` and `akto-ingest`).
+
+```yaml
+guardrails:
+ - guardrail_name: "akto-validate"
+ litellm_params:
+ guardrail: akto
+ mode: pre_call
+ akto_base_url: os.environ/AKTO_GUARDRAIL_API_BASE
+ akto_api_key: os.environ/AKTO_API_KEY
+ default_on: true
+ unreachable_fallback: fail_closed # optional: fail_open | fail_closed (default: fail_closed)
+ guardrail_timeout: 5 # optional, default: 5
+ akto_account_id: "1000000" # optional, env fallback: AKTO_ACCOUNT_ID
+ akto_vxlan_id: "0" # optional, env fallback: AKTO_VXLAN_ID
+
+ - guardrail_name: "akto-ingest"
+ litellm_params:
+ guardrail: akto
+ mode: post_call
+ akto_base_url: os.environ/AKTO_GUARDRAIL_API_BASE
+ akto_api_key: os.environ/AKTO_API_KEY
+ default_on: true
+```
+
+### Monitor-only mode
+
+If you only want logging/ingestion and no blocking, keep only `akto-ingest`.
+
+```yaml
+guardrails:
+ - guardrail_name: "akto-ingest"
+ litellm_params:
+ guardrail: akto
+ mode: post_call
+ akto_base_url: os.environ/AKTO_GUARDRAIL_API_BASE
+ akto_api_key: os.environ/AKTO_API_KEY
+ default_on: true
+```
+
+## 3. Test It
+
+```shell
+curl -i http://localhost:4000/v1/chat/completions \
+ -H "Content-Type: application/json" \
+ -H "Authorization: Bearer " \
+ -d '{
+ "model": "gpt-3.5-turbo",
+ "messages": [
+ {"role": "user", "content": "Hello, how are you?"}
+ ]
+ }'
+```
+
+If a request gets blocked:
+
+```json
+{
+ "error": {
+ "message": "Prompt injection detected",
+ "type": "None",
+ "param": "None",
+ "code": "403"
+ }
+}
+```
+
+## 4. How It Works
+
+**Block + Ingest mode:**
+```
+Request → LiteLLM → Akto guardrail check
+ → Allowed → forward to LLM → ingest response
+ → Blocked → ingest blocked marker → 403 error
+```
+
+**Monitor-only mode:**
+```
+Request → LiteLLM → forward to LLM → get response
+ → Send to Akto (guardrails + ingest) → log only
+```
+
+## 5. Event behavior
+
+| Entry | LiteLLM hook | Akto call behavior |
+|------|---|---|
+| `akto-validate` | `pre_call` | Awaited call with `guardrails=true`, `ingest_data=false` |
+| `akto-ingest` | `post_call` | Fire-and-forget call with `guardrails=true`, `ingest_data=true` |
+
+When blocked in `pre_call`, LiteLLM sends one fire-and-forget ingest payload with blocked metadata and returns `403`.
+
+## 6. Parameters
+
+| Parameter | Env Variable | Default | Description |
+|-----------|-------------|---------|-------------|
+| `akto_base_url` | `AKTO_GUARDRAIL_API_BASE` | *required* | Akto Guardrail API Base URL |
+| `akto_api_key` | `AKTO_API_KEY` | *required* | API key (sent as `Authorization` header) |
+| `akto_account_id` | `AKTO_ACCOUNT_ID` | `1000000` | Akto account id included in payload |
+| `akto_vxlan_id` | `AKTO_VXLAN_ID` | `0` | Akto vxlan id included in payload |
+| `unreachable_fallback` | — | `fail_closed` | `fail_open` or `fail_closed` |
+| `guardrail_timeout` | — | `5` | Timeout in seconds |
+| `default_on` | — | `true` (recommended) | Enables the guardrail entry by default |
+
+## 7. Error Handling
+
+| Scenario | `fail_closed` (default) | `fail_open` |
+|----------|------------------------|-------------|
+| Akto unreachable | ❌ Blocked (503) | ✅ Passes through |
+| Akto returns error | ❌ Blocked (503) | ✅ Passes through |
+| Guardrail says no | ❌ Blocked (403) | ❌ Blocked (403) |
diff --git a/docs/my-website/docs/proxy/guardrails/aporia_api.md b/docs/my-website/docs/proxy/guardrails/aporia_api.md
index ceafc19a1cc..e6ff0d5fed3 100644
--- a/docs/my-website/docs/proxy/guardrails/aporia_api.md
+++ b/docs/my-website/docs/proxy/guardrails/aporia_api.md
@@ -139,7 +139,7 @@ curl -i http://localhost:4000/v1/chat/completions \
:::info
-✨ This is an Enterprise only feature [Contact us to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+✨ This is an Enterprise only feature [Contact us to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/proxy/guardrails/custom_guardrail.md b/docs/my-website/docs/proxy/guardrails/custom_guardrail.md
index c9115cf8265..37579ad870d 100644
--- a/docs/my-website/docs/proxy/guardrails/custom_guardrail.md
+++ b/docs/my-website/docs/proxy/guardrails/custom_guardrail.md
@@ -117,6 +117,14 @@ guardrails:
:::
+:::note Streaming and post_call guardrails
+
+For **streaming responses**, `post_call` guardrails run on the fully assembled response **after** all chunks have been delivered to the client. This means `post_call` guardrails on streaming are **audit-only** — they can inspect and log the complete response, but cannot block content delivery. Guardrail results are recorded in `guardrail_information` within the logging payload for compliance and auditing.
+
+To filter or block streaming content in real-time, use `async_post_call_streaming_iterator_hook` instead, which processes chunks as they arrive.
+
+:::
+
Advanced: Multiple modes with individual event hooks
@@ -409,7 +417,7 @@ curl -i -X POST http://localhost:4000/v1/chat/completions \
:::info
-✨ This is an Enterprise only feature [Contact us to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+✨ This is an Enterprise only feature [Contact us to get a free trial](https://enterprise.litellm.ai/demo)
:::
@@ -655,8 +663,8 @@ class myCustomGuardrail(CustomGuardrail):
| `apply_guardrail` | Simple method to check and optionally modify text | ✅ | INPUT or OUTPUT | ✅ | ✅ | ✅ |
| `async_pre_call_hook` | A hook that runs before the LLM API call | ✅ | INPUT | ✅ | ❌ | ✅ |
| `async_moderation_hook` | A hook that runs during the LLM API call| ✅ | INPUT | ❌ | ❌ | ✅ |
-| `async_post_call_success_hook` | A hook that runs after a successful LLM API call| ✅ | INPUT, OUTPUT | ❌ | ✅ | ✅ |
-| `async_post_call_streaming_iterator_hook` | A hook that processes streaming responses | ✅ | OUTPUT | ❌ | ✅ | ✅ |
+| `async_post_call_success_hook` | A hook that runs after a successful LLM API call. For streaming, runs on the assembled response after delivery (audit-only, cannot block). | ✅ | INPUT, OUTPUT | ❌ | ✅ | ✅ (non-streaming only) |
+| `async_post_call_streaming_iterator_hook` | A hook that processes streaming responses in real-time (can filter/block chunks) | ✅ | OUTPUT | ❌ | ✅ | ✅ |
## Frequently Asked Questions
diff --git a/docs/my-website/docs/proxy/guardrails/guardrails_ai.md b/docs/my-website/docs/proxy/guardrails/guardrails_ai.md
index 55d586aee7b..19ae34014a4 100644
--- a/docs/my-website/docs/proxy/guardrails/guardrails_ai.md
+++ b/docs/my-website/docs/proxy/guardrails/guardrails_ai.md
@@ -59,7 +59,7 @@ curl -i http://localhost:4000/v1/chat/completions \
:::info
-✨ This is an Enterprise only feature [Contact us to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+✨ This is an Enterprise only feature [Contact us to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/proxy/health.md b/docs/my-website/docs/proxy/health.md
index 2764a6f0d4f..530bea3d06b 100644
--- a/docs/my-website/docs/proxy/health.md
+++ b/docs/my-website/docs/proxy/health.md
@@ -314,6 +314,89 @@ general_settings:
health_check_details: False
```
+## Health Check Driven Routing
+
+By default, background health checks are observability-only — they populate the `/health` endpoint but don't affect routing. Unhealthy deployments still receive traffic until request failures trigger cooldown.
+
+With `enable_health_check_routing: true`, the router **excludes deployments that failed their last background health check** before selecting a candidate. This gives you proactive failover instead of reactive cooldown.
+
+### How it works
+
+1. Background health checks run on their configured interval
+2. After each cycle, every deployment is marked healthy or unhealthy
+3. On each incoming request, the router filters out unhealthy deployments **before** cooldown filtering and load balancing
+4. If all deployments are unhealthy, the filter is bypassed (safety net — never causes a total outage)
+5. If health state is stale (older than `health_check_staleness_threshold`), it is ignored
+
+### Quick start
+
+```yaml
+model_list:
+ - model_name: gpt-4
+ litellm_params:
+ model: openai/gpt-4
+ api_key: os.environ/OPENAI_API_KEY
+ - model_name: gpt-4
+ litellm_params:
+ model: openai/gpt-4
+ api_key: os.environ/OPENAI_API_KEY_SECONDARY
+
+general_settings:
+ background_health_checks: true
+ health_check_interval: 60
+ enable_health_check_routing: true
+```
+
+### Configuration
+
+| Setting | Where | Default | Description |
+|---------|-------|---------|-------------|
+| `enable_health_check_routing` | `general_settings` | `false` | Enable/disable health-check-driven routing |
+| `health_check_staleness_threshold` | `general_settings` | `health_check_interval * 2` | Seconds before health state is considered stale and ignored |
+| `background_health_checks` | `general_settings` | `false` | Must be `true` for health check routing to work |
+| `health_check_interval` | `general_settings` | `300` | Seconds between health check cycles |
+
+### Interaction with cooldown
+
+Health check filtering and cooldown are **additive**. A deployment can be excluded by either mechanism:
+
+- **Health check filter** — proactive, runs on the configured interval, excludes deployments that failed the last check
+- **Cooldown** — reactive, triggered by request failures, excludes deployments for a short TTL
+
+This means request failures still provide fast detection between health check intervals.
+
+### Staleness
+
+If a health check result is older than `health_check_staleness_threshold`, it is ignored and the deployment is treated as eligible. This prevents stale data from permanently excluding a deployment if the health check loop stops or slows down.
+
+The default staleness threshold is `health_check_interval * 2`. For a 60s interval, health state expires after 120s.
+
+### Example: custom staleness
+
+```yaml
+general_settings:
+ background_health_checks: true
+ health_check_interval: 30
+ enable_health_check_routing: true
+ health_check_staleness_threshold: 90 # ignore health state older than 90s
+```
+
+### Debugging
+
+Run the proxy with `--detailed_debug` and look for:
+
+```
+health_check_routing_state_updated healthy=3 unhealthy=1
+```
+
+This is logged after each health check cycle when routing state is written.
+
+If the safety net triggers (all deployments unhealthy), you'll see:
+
+```
+All deployments marked unhealthy by health checks, bypassing health filter
+```
+
## Health Check Timeout
The health check timeout is set in `litellm/constants.py` and defaults to 60 seconds.
diff --git a/docs/my-website/docs/proxy/high_availability_control_plane.md b/docs/my-website/docs/proxy/high_availability_control_plane.md
new file mode 100644
index 00000000000..324fba3a180
--- /dev/null
+++ b/docs/my-website/docs/proxy/high_availability_control_plane.md
@@ -0,0 +1,190 @@
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+import { ControlPlaneArchitecture } from '@site/src/components/ControlPlaneArchitecture';
+
+# [BETA] High Availability Control Plane
+
+Deploy a single LiteLLM UI that manages multiple independent LiteLLM proxy instances, each with its own database, Redis, and master key.
+
+:::info
+
+This is an Enterprise feature.
+
+[Enterprise Pricing](https://www.litellm.ai/#pricing)
+
+[Get free 7-day trial key](https://www.litellm.ai/enterprise#trial)
+
+:::
+
+## Why This Architecture?
+
+In the [standard multi-region setup](./control_plane_and_data_plane.md), all instances share a single database and master key. This works, but introduces a shared dependency. If the database goes down, every instance is affected.
+
+The **High Availability Control Plane** takes a different approach:
+
+| | Shared Database (Standard) | High Availability Control Plane |
+|---|---|---|
+| **Database** | Single shared DB for all instances | Each instance has its own DB |
+| **Redis** | Shared Redis | Each instance has its own Redis |
+| **Master Key** | Same key across all instances | Each instance has its own key |
+| **Failure isolation** | DB outage affects all instances | Failure is isolated to one instance |
+| **User management** | Centralized, one user table | Independent, each worker manages its own users |
+| **UI** | One UI per admin instance | Single control plane UI manages all workers |
+
+### Benefits
+
+- **True high availability**: no shared infrastructure means no single point of failure
+- **Blast radius containment**: a misconfiguration or outage on one worker doesn't affect others
+- **Regional isolation**: workers can run in different regions with data residency requirements
+- **Simpler operations**: each worker is a self-contained LiteLLM deployment
+
+## Architecture
+
+
+
+The **control plane** is a LiteLLM instance that serves the admin UI and knows about all the workers. It does not proxy LLM requests, it is purely for administration.
+
+Each **worker** is a fully independent LiteLLM proxy that handles LLM requests for its region or team. Workers have their own users, keys, teams, and budgets.
+
+## Setup
+
+### 1. Control Plane Configuration
+
+The control plane needs a `worker_registry` that lists all worker instances.
+
+```yaml title="cp_config.yaml"
+model_list: []
+
+general_settings:
+ master_key: sk-1234
+ database_url: os.environ/DATABASE_URL
+
+worker_registry:
+ - worker_id: "worker-a"
+ name: "Worker A"
+ url: "http://localhost:4001"
+ - worker_id: "worker-b"
+ name: "Worker B"
+ url: "http://localhost:4002"
+```
+
+Start the control plane:
+
+```bash
+litellm --config cp_config.yaml --port 4000
+```
+
+### 2. Worker Configuration
+
+Each worker needs `control_plane_url` in its `general_settings` to enable cross-origin authentication from the control plane UI.
+
+`PROXY_BASE_URL` must also be set for each worker so that SSO callback redirects resolve correctly.
+
+
+
+
+```yaml title="worker_a_config.yaml"
+model_list: []
+
+general_settings:
+ master_key: sk-worker-a-1234
+ database_url: os.environ/WORKER_A_DATABASE_URL
+ control_plane_url: "http://localhost:4000"
+```
+
+```bash
+PROXY_BASE_URL=http://localhost:4001 litellm --config worker_a_config.yaml --port 4001
+```
+
+
+
+
+```yaml title="worker_b_config.yaml"
+model_list: []
+
+general_settings:
+ master_key: sk-worker-b-1234
+ database_url: os.environ/WORKER_B_DATABASE_URL
+ control_plane_url: "http://localhost:4000"
+```
+
+```bash
+PROXY_BASE_URL=http://localhost:4002 litellm --config worker_b_config.yaml --port 4002
+```
+
+
+
+
+:::important
+Each worker must have its own `master_key` and `database_url`. The whole point of this architecture is that workers are independent.
+:::
+
+### 3. SSO Configuration (Optional)
+
+SSO is configured on the **control plane** instance the same way as a standard LiteLLM proxy. See the [SSO setup guide](./admin_ui_sso.md) for full instructions.
+
+If using SSO, make sure to register each worker URL and the control plane URL as allowed callback URLs in your SSO provider's dashboard.
+
+## How It Works
+
+### Login Flow
+
+1. User visits the control plane UI (`http://localhost:4000/ui`)
+2. The login page shows a **worker selector** dropdown listing all registered workers
+3. User selects a worker (e.g. "Worker A") and logs in with username/password or SSO
+4. The UI authenticates against the **selected worker** using the `/v3/login` endpoint
+5. On success, the UI stores the worker's JWT and points all subsequent API calls at the worker
+6. The user can now manage keys, teams, models, and budgets on that worker, all from the control plane UI
+
+### Switching Workers
+
+Once logged in, users can switch workers from the **navbar dropdown** without leaving the UI. Switching redirects back to the login page to authenticate against the new worker.
+
+### Discovery
+
+The control plane exposes a `/.well-known/litellm-ui-config` endpoint that the UI reads on load. This endpoint returns:
+- `is_control_plane: true`
+- The list of workers with their IDs, names, and URLs
+
+This is how the login page knows to show the worker selector.
+
+## Local Testing
+
+To try this out locally, start each instance in a separate terminal:
+
+```bash
+# Terminal 1: Control Plane
+litellm --config cp_config.yaml --port 4000
+
+# Terminal 2: Worker A
+PROXY_BASE_URL=http://localhost:4001 litellm --config worker_a_config.yaml --port 4001
+
+# Terminal 3: Worker B
+PROXY_BASE_URL=http://localhost:4002 litellm --config worker_b_config.yaml --port 4002
+```
+
+Then open `http://localhost:4000/ui`. You should see the worker selector on the login page.
+
+## Configuration Reference
+
+### Control Plane Settings
+
+| Field | Location | Description |
+|---|---|---|
+| `worker_registry` | Top-level config | List of worker instances |
+| `worker_registry[].worker_id` | Required | Unique identifier for the worker |
+| `worker_registry[].name` | Required | Display name shown in the UI |
+| `worker_registry[].url` | Required | Full URL of the worker instance |
+
+### Worker Settings
+
+| Field | Location | Description |
+|---|---|---|
+| `general_settings.control_plane_url` | Required | URL of the control plane instance. Enables `/v3/login` and `/v3/login/exchange` endpoints on this worker. |
+| `PROXY_BASE_URL` | Environment variable | The worker's own external URL. Required for SSO callback redirects. |
+
+## Related Documentation
+
+- [Standard Multi-Region Setup](./control_plane_and_data_plane.md) - shared-database architecture for admin/worker split
+- [SSO Setup](./admin_ui_sso.md) - configuring SSO for the admin UI
+- [Production Deployment](./prod.md) - production best practices
diff --git a/docs/my-website/docs/proxy/ip_address.md b/docs/my-website/docs/proxy/ip_address.md
index 8f042d9f183..4c469b81e0b 100644
--- a/docs/my-website/docs/proxy/ip_address.md
+++ b/docs/my-website/docs/proxy/ip_address.md
@@ -3,7 +3,7 @@
:::info
-You need a LiteLLM License to unlock this feature. [Grab time](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions), to get one today!
+You need a LiteLLM License to unlock this feature. [Grab time](https://enterprise.litellm.ai/demo), to get one today!
:::
diff --git a/docs/my-website/docs/proxy/keys_teams_router_settings.md b/docs/my-website/docs/proxy/keys_teams_router_settings.md
index ec59e8f271b..6a1744ca951 100644
--- a/docs/my-website/docs/proxy/keys_teams_router_settings.md
+++ b/docs/my-website/docs/proxy/keys_teams_router_settings.md
@@ -146,5 +146,5 @@ Test new router settings on specific keys or teams before applying globally:
- [Router Settings Reference](./config_settings.md#router_settings---reference) - Complete reference of all router settings
- [Load Balancing](./load_balancing.md) - Learn about routing strategies and load balancing
- [Reliability](./reliability.md) - Configure fallbacks, retries, and error handling
-- [Keys](./keys.md) - Manage API keys and their settings
-- [Teams](./teams.md) - Organize keys into teams
+- [Keys](./virtual_keys.md) - Manage API keys and their settings
+- [Teams](./multi_tenant_architecture.md) - Organize keys into teams
diff --git a/docs/my-website/docs/proxy/load_balancing.md b/docs/my-website/docs/proxy/load_balancing.md
index 5bf39d179f6..93f3d944340 100644
--- a/docs/my-website/docs/proxy/load_balancing.md
+++ b/docs/my-website/docs/proxy/load_balancing.md
@@ -324,17 +324,58 @@ model_list:
litellm_params:
model: azure/gpt-4-fallback
api_key: os.environ/AZURE_API_KEY_2
- order: 2 # 👈 Used when order=1 is unavailable
-
-router_settings:
- enable_pre_call_checks: true # 👈 Required for 'order' to work
+ order: 2 # 👈 Used when order=1 fails
```
-:::important
-The `order` parameter requires `enable_pre_call_checks: true` in `router_settings`.
-:::
+### How order-based fallback works
-If `order=1` deployment is unavailable (e.g., rate-limited), the router falls back to `order=2` deployments.
+When a request to an `order=1` deployment fails (connection error, 404, 429, etc.), the router automatically tries `order=2` deployments, then `order=3`, and so on. Each order level gets its own set of retries before escalating to the next.
+
+If all order levels are exhausted, the router falls through to any configured [model-level fallbacks](#fallbacks).
+
+```yaml
+model_list:
+ - model_name: gpt-4
+ litellm_params:
+ model: azure/gpt-4-primary
+ api_key: os.environ/AZURE_API_KEY
+ order: 1
+
+ - model_name: gpt-4
+ litellm_params:
+ model: azure/gpt-4-secondary
+ api_key: os.environ/AZURE_API_KEY_2
+ order: 2
+
+ - model_name: gpt-4-fallback
+ litellm_params:
+ model: openai/gpt-4
+ api_key: os.environ/OPENAI_API_KEY
+
+router_settings:
+ fallbacks:
+ - gpt-4:
+ - gpt-4-fallback # tried after all order levels fail
+```
+
+The fallback chain for the above config: `order=1` → `order=2` → `gpt-4-fallback`.
+
+For 429 (rate limit) errors specifically, the failed deployment is immediately placed on cooldown. If all `order=1` deployments are on cooldown, the router picks `order=2` deployments directly during retries without waiting for the fallback path.
+
+### Team-scoped models and legacy `model_aliases` {#team-scoped-models-and-legacy-model_aliases}
+
+Team-scoped deployments are identified by `model_info.team_id` and `model_info.team_public_model_name`. Requests should use the **public** model name; the router resolves all sibling deployments (same public name, different `api_base` / `order`, etc.) for routing, failover, and deployment `order`.
+
+For router internals: when a `team_id` is in scope, optimized lookups key off `(team_id, team_public_model_name)`. If code passes an internal deployment id (e.g. `model_name__`) instead of the public name, routing still works via the usual deployment-name paths, but the team-specific fast path applies only to the public name.
+
+**Legacy teams:** Older proxy versions could persist `model_aliases` on the team row mapping a public name to a single internal deployment id (`model_name__`). On each request, pre-call logic may still rewrite `model` to that internal name **before** routing, which collapses to one deployment and can make newer sibling deployments unreachable.
+
+**Migration options:**
+
+1. **Recommended for upgrades:** Set environment variable `LITELLM_ENABLE_TEAM_STALE_ALIAS_BYPASS=true` so that when sibling team deployments exist for the public name, the stale alias rewrite is skipped and team-scoped routing (including `order` and failover) applies. See the [Environment variables](./config_settings) table in the proxy settings doc.
+2. **Data cleanup:** Remove obsolete `model_aliases` entries for team public names from the team record in the database so only `team_public_model_name` + team model list drive access.
+
+If a stale alias is detected and the bypass is **not** enabled, the proxy may emit a **one-time** warning in logs explaining that sibling deployments may be unreachable until the flag is set or aliases are cleaned up.
### When You'll See Load Balancing in Action
@@ -352,7 +393,7 @@ If `order=1` deployment is unavailable (e.g., rate-limited), the router falls ba
When load balancing OpenAI's Responses API across deployments with **different API keys** (e.g., different Azure regions or organizations), encrypted content items (like `rs_...` reasoning items) can only be decrypted by the originating API key.
-**Solution:** Use the `encrypted_content_affinity` pre-call check to automatically route follow-up requests containing encrypted items to the correct deployment:
+**Solution:** Use the `encrypted_content_affinity` pre-call check (requires LiteLLM >= 1.82.3) to automatically route follow-up requests containing encrypted items to the correct deployment:
```yaml
model_list:
diff --git a/docs/my-website/docs/proxy/logging.md b/docs/my-website/docs/proxy/logging.md
index 74a79776fbd..2f81498799a 100644
--- a/docs/my-website/docs/proxy/logging.md
+++ b/docs/my-website/docs/proxy/logging.md
@@ -1109,7 +1109,7 @@ Log LLM Logs to [Google Cloud Storage Buckets](https://cloud.google.com/storage?
:::info
-✨ This is an Enterprise only feature [Get Started with Enterprise here](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+✨ This is an Enterprise only feature [Get Started with Enterprise here](https://enterprise.litellm.ai/demo)
:::
@@ -1194,7 +1194,7 @@ Log LLM Logs/SpendLogs to [Google Cloud Storage PubSub Topic](https://cloud.goog
:::info
-✨ This is an Enterprise only feature [Get Started with Enterprise here](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+✨ This is an Enterprise only feature [Get Started with Enterprise here](https://enterprise.litellm.ai/demo)
:::
@@ -1497,7 +1497,7 @@ Log LLM Logs to [Azure Data Lake Storage](https://learn.microsoft.com/en-us/azur
:::info
-✨ This is an Enterprise only feature [Get Started with Enterprise here](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+✨ This is an Enterprise only feature [Get Started with Enterprise here](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/proxy/model_compare_ui.md b/docs/my-website/docs/proxy/model_compare_ui.md
index bd6f5414224..ee0376ed2fa 100644
--- a/docs/my-website/docs/proxy/model_compare_ui.md
+++ b/docs/my-website/docs/proxy/model_compare_ui.md
@@ -187,7 +187,7 @@ Use tags and multiple comparisons to run structured A/B tests:
## Related Features
-- [Playground Chat UI](./playground.md) - Single model testing interface
+- [Playground Chat UI](./ui.md) - Single model testing interface
- [Model Management](./model_management.md) - Configure and manage models
-- [Guardrails](./guardrails.md) - Set up safety filters
+- [Guardrails](./guardrails/quick_start.md) - Set up safety filters
- [AI Hub](./ai_hub.md) - Share models and agents with your organization
diff --git a/docs/my-website/docs/proxy/multiple_admins.md b/docs/my-website/docs/proxy/multiple_admins.md
index 8d39674df19..83d0c5863df 100644
--- a/docs/my-website/docs/proxy/multiple_admins.md
+++ b/docs/my-website/docs/proxy/multiple_admins.md
@@ -20,7 +20,7 @@ LiteLLM tracks changes to the following entities and actions:
:::tip
-Requires Enterprise License, Get in touch with us [here](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+Requires Enterprise License, Get in touch with us [here](https://enterprise.litellm.ai/demo)
:::
@@ -56,6 +56,40 @@ On the LiteLLM UI, navigate to Logs -> Audit Logs. You should see the audit log
/>
+## Export Audit Logs to External Storage
+
+You can export audit logs to an external storage backend (e.g. S3) in addition to storing them in the database. Logs are batched and uploaded asynchronously, so they do not block your proxy requests.
+
+### S3 Example
+
+Add `audit_log_callbacks` and `s3_callback_params` to your `litellm_settings`:
+
+```yaml
+litellm_settings:
+ store_audit_logs: true
+ audit_log_callbacks: ["s3_v2"]
+ s3_callback_params:
+ s3_bucket_name: my-audit-logs-bucket # AWS Bucket Name
+ s3_region_name: us-west-2 # AWS Region
+ s3_aws_access_key_id: os.environ/AWS_ACCESS_KEY_ID
+ s3_aws_secret_access_key: os.environ/AWS_SECRET_ACCESS_KEY
+ s3_path: litellm-audit # [OPTIONAL] prefix path in the bucket
+```
+
+Audit logs are written as JSON files to:
+
+```
+s3:///audit_logs//_.json
+# or, when s3_path is set:
+s3:////audit_logs//_.json
+```
+
+:::info
+
+Both `store_audit_logs: true` and `audit_log_callbacks` must be set. If `store_audit_logs` is not enabled, the callbacks will not fire.
+
+:::
+
## Advanced
### Attribute Management changes to Users
diff --git a/docs/my-website/docs/proxy/oauth2.md b/docs/my-website/docs/proxy/oauth2.md
index 41c4110e447..204a01538cc 100644
--- a/docs/my-website/docs/proxy/oauth2.md
+++ b/docs/my-website/docs/proxy/oauth2.md
@@ -4,7 +4,7 @@ Use this if you want to use an Oauth2.0 token to make `/chat`, `/embeddings` req
:::info
-This is an Enterprise Feature - [get in touch with us if you want a free trial to test if this feature meets your needs]((https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions))
+This is an Enterprise Feature - [get in touch with us if you want a free trial to test if this feature meets your needs]((https://enterprise.litellm.ai/demo))
:::
diff --git a/docs/my-website/docs/proxy/pass_through.md b/docs/my-website/docs/proxy/pass_through.md
index f47d7064140..700bfb0831d 100644
--- a/docs/my-website/docs/proxy/pass_through.md
+++ b/docs/my-website/docs/proxy/pass_through.md
@@ -422,6 +422,5 @@ general_settings:
[Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/proxy/prod.md b/docs/my-website/docs/proxy/prod.md
index 26cb484cbe9..d40a0343106 100644
--- a/docs/my-website/docs/proxy/prod.md
+++ b/docs/my-website/docs/proxy/prod.md
@@ -47,7 +47,7 @@ export LITELLM_LOG="ERROR"
:::info
-Need Help or want dedicated support ? Talk to a founder [here]: (https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+Need Help or want dedicated support ? Talk to a founder [here]: (https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/proxy/prompt_management.md b/docs/my-website/docs/proxy/prompt_management.md
index 08307ba99ec..5a3e411e984 100644
--- a/docs/my-website/docs/proxy/prompt_management.md
+++ b/docs/my-website/docs/proxy/prompt_management.md
@@ -311,7 +311,7 @@ litellm_settings:
1. **At Startup**: When the proxy starts, it reads the `prompts` field from `config.yaml`
2. **Initialization**: Each prompt is initialized based on its `prompt_integration` type
3. **In-Memory Storage**: Prompts are stored in the `IN_MEMORY_PROMPT_REGISTRY`
-4. **Access**: Use these prompts via the `/v1/chat/completions` endpoint with `prompt_id` in the request
+4. **Access**: Use these prompts via `/v1/chat/completions` or `/v1/responses` with `prompt_id` in the request
### Using Config-Loaded Prompts
@@ -331,6 +331,23 @@ curl -L -X POST 'http://0.0.0.0:4000/v1/chat/completions' \
}'
```
+You can also use the same `prompt_id` with the Responses API:
+
+```bash
+curl -L -X POST 'http://0.0.0.0:4000/v1/responses' \
+-H 'Content-Type: application/json' \
+-H 'Authorization: Bearer sk-1234' \
+-d '{
+ "model": "gpt-4o",
+ "prompt_id": "coding_assistant",
+ "prompt_variables": {
+ "language": "python",
+ "task": "create a web scraper"
+ },
+ "input": []
+}'
+```
+
### Prompt Schema Reference
Each prompt in the `prompts` list requires:
diff --git a/docs/my-website/docs/proxy/public_routes.md b/docs/my-website/docs/proxy/public_routes.md
index d5f3941751f..e53548349dc 100644
--- a/docs/my-website/docs/proxy/public_routes.md
+++ b/docs/my-website/docs/proxy/public_routes.md
@@ -5,7 +5,7 @@ import TabItem from '@theme/TabItem';
:::info
-Requires a LiteLLM Enterprise License. [Get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions).
+Requires a LiteLLM Enterprise License. [Get a free trial](https://enterprise.litellm.ai/demo).
:::
diff --git a/docs/my-website/docs/proxy/sync_anthropic_beta_headers.md b/docs/my-website/docs/proxy/sync_anthropic_beta_headers.md
index e1645082d97..0373d20c879 100644
--- a/docs/my-website/docs/proxy/sync_anthropic_beta_headers.md
+++ b/docs/my-website/docs/proxy/sync_anthropic_beta_headers.md
@@ -125,4 +125,4 @@ curl -X DELETE "https://your-proxy-url/schedule/anthropic_beta_headers_reload" \
## Related
- [Model Cost Map Sync](./sync_models_github.md) - Auto-sync model pricing data
-- [Anthropic Beta Headers](../completion/anthropic.md#beta-features) - Using Anthropic beta features
+- [Anthropic Beta Headers](../providers/anthropic.md) - Using Anthropic beta features
diff --git a/docs/my-website/docs/proxy/tag_routing.md b/docs/my-website/docs/proxy/tag_routing.md
index a1ae52e5e45..57d16a59b54 100644
--- a/docs/my-website/docs/proxy/tag_routing.md
+++ b/docs/my-website/docs/proxy/tag_routing.md
@@ -315,7 +315,7 @@ LiteLLM Proxy supports team-based tag routing, allowing you to associate specifi
:::info
-This is an enterprise feature, [Contact us here to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+This is an enterprise feature, [Contact us here to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/proxy/team_logging.md b/docs/my-website/docs/proxy/team_logging.md
index 2ad7e2a4a8e..3f57d0d6d8b 100644
--- a/docs/my-website/docs/proxy/team_logging.md
+++ b/docs/my-website/docs/proxy/team_logging.md
@@ -26,7 +26,7 @@ Team 3 -> Disabled Logging (for GDPR compliance)
:::info
-✨ This is an Enterprise only feature [Get Started with Enterprise here](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+✨ This is an Enterprise only feature [Get Started with Enterprise here](https://enterprise.litellm.ai/demo)
:::
@@ -248,7 +248,7 @@ Use the `/key/generate` or `/key/update` endpoints to add logging callbacks to a
:::info
-✨ This is an Enterprise only feature [Get Started with Enterprise here](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+✨ This is an Enterprise only feature [Get Started with Enterprise here](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/proxy/team_model_add.md b/docs/my-website/docs/proxy/team_model_add.md
index 7db59a3300e..bb4238055b5 100644
--- a/docs/my-website/docs/proxy/team_model_add.md
+++ b/docs/my-website/docs/proxy/team_model_add.md
@@ -5,7 +5,7 @@
This is an Enterprise feature.
[Enterprise Pricing](https://www.litellm.ai/#pricing)
-[Contact us here to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+[Contact us here to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/proxy/token_auth.md b/docs/my-website/docs/proxy/token_auth.md
index 7364ae0fb56..bc6fde7c840 100644
--- a/docs/my-website/docs/proxy/token_auth.md
+++ b/docs/my-website/docs/proxy/token_auth.md
@@ -11,7 +11,7 @@ Use JWT's to auth admins / users / projects into the proxy.
[Enterprise Pricing](https://www.litellm.ai/#pricing)
-[Contact us here to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+[Contact us here to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/proxy/ui_store_model_db_setting.md b/docs/my-website/docs/proxy/ui_store_model_db_setting.md
index 5f860137d0f..4b0bc690f9a 100644
--- a/docs/my-website/docs/proxy/ui_store_model_db_setting.md
+++ b/docs/my-website/docs/proxy/ui_store_model_db_setting.md
@@ -87,6 +87,6 @@ Change the setting from the UI and have it take effect immediately—perfect for
## Related Documentation
-- [Admin UI Overview](./ui_overview.md) – General guide to the LiteLLM Admin UI
-- [Models and Endpoints](./models_and_endpoints.md) – Managing models and API endpoints
+- [Admin UI Overview](./ui.md) – General guide to the LiteLLM Admin UI
+- [Models and Endpoints](./model_management.md) – Managing models and API endpoints
- [Config Settings](./config_settings.md) – `store_model_in_db` in `general_settings`
diff --git a/docs/my-website/docs/proxy/user_onboarding.md b/docs/my-website/docs/proxy/user_onboarding.md
index baa241d6cdf..ecbdc11db43 100644
--- a/docs/my-website/docs/proxy/user_onboarding.md
+++ b/docs/my-website/docs/proxy/user_onboarding.md
@@ -79,4 +79,4 @@ curl -X POST http://localhost:4000/v1/chat/completions \
## See Also
- [Proxy Quick Start](./quick_start.md)
- [User Management](./users.md)
-- [Key Management](./key_management.md)
+- [Key Management](./virtual_keys.md)
diff --git a/docs/my-website/docs/proxy_server.md b/docs/my-website/docs/proxy_server.md
index e23d64e443b..7b6f15a604b 100644
--- a/docs/my-website/docs/proxy_server.md
+++ b/docs/my-website/docs/proxy_server.md
@@ -813,5 +813,4 @@ Thread Stats Avg Stdev Max +/- Stdev
- [Schedule Demo 👋](https://calendly.com/d/4mp-gd3-k5k/berriai-1-1-onboarding-litellm-hosted-version)
- [Community Discord 💭](https://discord.gg/wuPM9dRgDw)
-- Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
- Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/reasoning_content.md b/docs/my-website/docs/reasoning_content.md
index 8bf59f66a33..6e6a30cdb49 100644
--- a/docs/my-website/docs/reasoning_content.md
+++ b/docs/my-website/docs/reasoning_content.md
@@ -13,6 +13,7 @@ Supported Providers:
- Deepseek (`deepseek/`)
- Anthropic API (`anthropic/`)
- Bedrock (Anthropic + Deepseek + GPT-OSS) (`bedrock/`)
+- OpenAI Responses API (`openai/responses/`)
- Vertex AI (Anthropic) (`vertexai/`)
- OpenRouter (`openrouter/`)
- XAI (`xai/`)
@@ -594,9 +595,26 @@ Expected Response
:::tip gpt-5.4: reasoning_effort + function tools
-LiteLLM drops `reasoning_effort` from `gpt-5.4` requests to `litellm.completion()` that include tools, since that combination is supported in the Responses API.
+When `gpt-5.4+` requests to `litellm.completion()` include both `reasoning_effort` and `tools`, LiteLLM **automatically routes** the request through the Responses API bridge. This works for both **OpenAI** (`openai/gpt-5.4`) and **Azure** (`azure/gpt-5.4`) providers — no extra configuration needed.
-If you need reasoning **and** tools together, use `openai/responses/gpt-5.4` to route through the Responses API instead. See [Responses API Bridge](/docs/providers/openai#openai-chat-completion-to-responses-api-bridge) for details.
+You can also route explicitly via `openai/responses/gpt-5.4` or `azure/responses/gpt-5.4`. See [Responses API Bridge](/docs/providers/openai#openai-chat-completion-to-responses-api-bridge) for details.
+
+**Azure custom deployment names:** Auto-routing relies on the deployment name matching the `gpt-5.4*` pattern. If you use a custom deployment name (e.g. `"my-reasoning-model"`), enable routing via:
+
+**SDK:**
+```python
+litellm.completion(model="azure/responses/my-reasoning-model", ...)
+```
+
+**Proxy config:**
+```yaml
+model_list:
+ - model_name: my-reasoning-model
+ litellm_params:
+ model: azure/my-reasoning-model
+ model_info:
+ mode: responses
+```
:::
@@ -683,3 +701,69 @@ response = litellm.completion(
reasoning_effort={"effort": "low", "summary": "detailed"}, # Explicit control
)
```
+
+### Summary Preservation via `/v1/messages` Adapter
+
+When using the Anthropic `/v1/messages` adapter to route non-Claude models (e.g., `openai/gpt-5.1`), the `thinking.summary` value is preserved and forwarded to the downstream provider. For example:
+
+```python
+import litellm
+
+response = await litellm.anthropic.messages.acreate(
+ model="openai/gpt-5.1",
+ messages=[{"role": "user", "content": "Hello"}],
+ max_tokens=8096,
+ thinking={"type": "enabled", "budget_tokens": 5000, "summary": "concise"},
+)
+# The summary="concise" is preserved when routing to OpenAI's Responses API
+```
+
+### Enabling Default Summary Injection for `/v1/messages` Adapter
+
+When the Anthropic `/v1/messages` adapter translates `thinking` parameters to OpenAI `reasoning_effort` for non-Claude models, you can opt-in to automatic `summary="detailed"` injection using the `reasoning_auto_summary` flag. This ensures that reasoning text is returned in the response (matching the Anthropic thinking behavior).
+
+To **enable** this default injection, use the `reasoning_auto_summary` flag:
+
+
+
+
+```python
+import litellm
+
+# Enable default summary="detailed" injection
+litellm.reasoning_auto_summary = True
+
+response = await litellm.anthropic.messages.acreate(
+ model="openai/gpt-5.1",
+ messages=[{"role": "user", "content": "Hello"}],
+ max_tokens=8096,
+ thinking={"type": "enabled", "budget_tokens": 5000},
+)
+# summary="detailed" will be automatically added to reasoning_effort
+```
+
+
+
+
+
+```bash
+export LITELLM_REASONING_AUTO_SUMMARY=true
+```
+
+
+
+
+
+```yaml
+litellm_settings:
+ reasoning_auto_summary: true
+```
+
+
+
+
+:::info
+
+This flag only affects the automatic injection of `summary="detailed"` when no user-provided summary is present. If you explicitly pass `thinking.summary` (e.g., `"concise"` or `"auto"`), your value is always preserved regardless of this flag.
+
+:::
diff --git a/docs/my-website/docs/response_api.md b/docs/my-website/docs/response_api.md
index fb55ae9f9d0..0c428000c72 100644
--- a/docs/my-website/docs/response_api.md
+++ b/docs/my-website/docs/response_api.md
@@ -1160,12 +1160,12 @@ follow_up = await router.aresponses(
To enable session continuity for Responses API in your LiteLLM proxy, set `optional_pre_call_checks` in your proxy config.yaml.
- `responses_api_deployment_check`: high priority routing when `previous_response_id` is provided
-- `encrypted_content_affinity`: **[Recommended]** content-aware routing for encrypted items (e.g., `rs_...` reasoning items)
+- `encrypted_content_affinity`: **[Recommended]** content-aware routing for encrypted items (e.g., `rs_...` reasoning items) (**requires LiteLLM >= 1.82.3**)
- `session_affinity`: sticky sessions based on session id (takes priority over `deployment_affinity`)
- `deployment_affinity`: sticky sessions based on user key (applies even without `previous_response_id`)
:::tip Recommended: Use `encrypted_content_affinity`
-For Responses API with load balancing across deployments with **different API keys**, use `encrypted_content_affinity` instead of `deployment_affinity`. It only pins requests that contain encrypted content, avoiding quota reduction while preventing `invalid_encrypted_content` errors.
+For Responses API with load balancing across deployments with **different API keys**, use `encrypted_content_affinity` instead of `deployment_affinity`. It only pins requests that contain encrypted content, avoiding quota reduction while preventing `invalid_encrypted_content` errors. (Requires LiteLLM >= 1.82.3.)
:::
Notes:
@@ -1364,6 +1364,85 @@ litellm --config config.yaml
| `deployment_affinity` | Simple sticky sessions | All requests from same API key | ❌ Reduces quota by # of users |
+## Per-Model-Group Affinity Configuration
+
+By default, `optional_pre_call_checks` applies globally to all model groups. Use `model_group_affinity_config` when you want different affinity behavior per model group — for example, enabling stickiness only for models spread across providers (Azure + Bedrock) while leaving single-provider groups free to load-balance.
+
+Groups not listed fall back to the global `optional_pre_call_checks` settings.
+
+
+
+
+```python
+router = litellm.Router(
+ model_list=[
+ {
+ "model_name": "gpt-4",
+ "litellm_params": {"model": "azure/gpt-4", "api_key": "...", "api_base": "https://endpoint1.openai.azure.com"},
+ },
+ {
+ "model_name": "gpt-4",
+ "litellm_params": {"model": "bedrock/anthropic.claude-v2", "aws_region_name": "us-east-1"},
+ },
+ {
+ "model_name": "text-embedding-ada-002",
+ "litellm_params": {"model": "azure/text-embedding-ada-002", "api_key": "...", "api_base": "https://endpoint1.openai.azure.com"},
+ },
+ {
+ "model_name": "text-embedding-ada-002",
+ "litellm_params": {"model": "azure/text-embedding-ada-002", "api_key": "...", "api_base": "https://endpoint2.openai.azure.com"},
+ },
+ ],
+ # gpt-4: cross-provider (Azure + Bedrock) — enable deployment affinity
+ # text-embedding-ada-002: same provider — no affinity, let it load balance freely
+ model_group_affinity_config={
+ "gpt-4": ["deployment_affinity", "responses_api_deployment_check"],
+ },
+)
+```
+
+
+
+
+```yaml title="config.yaml"
+model_list:
+ - model_name: gpt-4
+ litellm_params:
+ model: azure/gpt-4
+ api_key: os.environ/AZURE_API_KEY_1
+ api_base: https://endpoint1.openai.azure.com
+
+ - model_name: gpt-4
+ litellm_params:
+ model: bedrock/anthropic.claude-v2
+ aws_region_name: us-east-1
+
+ - model_name: text-embedding-ada-002
+ litellm_params:
+ model: azure/text-embedding-ada-002
+ api_key: os.environ/AZURE_API_KEY_1
+ api_base: https://endpoint1.openai.azure.com
+
+ - model_name: text-embedding-ada-002
+ litellm_params:
+ model: azure/text-embedding-ada-002
+ api_key: os.environ/AZURE_API_KEY_2
+ api_base: https://endpoint2.openai.azure.com
+
+router_settings:
+ # gpt-4: cross-provider — enable stickiness
+ # text-embedding-ada-002: not listed — load balances freely
+ model_group_affinity_config:
+ "gpt-4":
+ - deployment_affinity
+ - responses_api_deployment_check
+```
+
+
+
+
+**Supported values:** `deployment_affinity`, `responses_api_deployment_check`, `session_affinity`
+
## Calling non-Responses API endpoints (`/responses` to `/chat/completions` Bridge)
LiteLLM allows you to call non-Responses API models via a bridge to LiteLLM's `/chat/completions` endpoint. This is useful for calling Anthropic, Gemini and even non-Responses API OpenAI models.
@@ -1556,6 +1635,12 @@ curl -X POST "http://localhost:4000/v1/responses" \
}'
```
+## File Search (Vector Stores)
+
+For full `file_search` usage (native + emulated fallback), SDK/Proxy examples, architecture diagram, and Q&A, see:
+
+- [`File Search in the Responses API — E2E Testing Guide`](/docs/tutorials/file_search_responses_api)
+
## Session Management
LiteLLM Proxy supports session management for all supported models. This allows you to store and fetch conversation history (state) in LiteLLM Proxy.
diff --git a/docs/my-website/docs/routing.md b/docs/my-website/docs/routing.md
index 67e7f681147..5aa655ae212 100644
--- a/docs/my-website/docs/routing.md
+++ b/docs/my-website/docs/routing.md
@@ -842,6 +842,8 @@ Traffic mirroring allows you to "mimic" production traffic to a secondary (silen
Set `order` in `litellm_params` to prioritize deployments. Lower values = higher priority. When multiple deployments share the same `order`, the routing strategy picks among them.
+When a request to an `order=1` deployment fails (connection error, 404, 429, etc.), the router automatically tries `order=2` deployments, then `order=3`, and so on. Each order level gets its own set of retries before escalating to the next. If all order levels are exhausted, the router falls through to any configured [fallbacks](#fallbacks).
+
@@ -862,18 +864,14 @@ model_list = [
"litellm_params": {
"model": "azure/gpt-4-fallback",
"api_key": os.getenv("AZURE_API_KEY_2"),
- "order": 2, # 👈 Used when order=1 is unavailable
+ "order": 2, # 👈 Tried when order=1 fails
},
},
]
-router = Router(model_list=model_list, enable_pre_call_checks=True) # 👈 Required for 'order' to work
+router = Router(model_list=model_list)
```
-:::important
-The `order` parameter requires `enable_pre_call_checks=True` to be set on the Router.
-:::
-
@@ -889,10 +887,7 @@ model_list:
litellm_params:
model: azure/gpt-4-fallback
api_key: os.environ/AZURE_API_KEY_2
- order: 2 # 👈 Used when order=1 is unavailable
-
-router_settings:
- enable_pre_call_checks: true # 👈 Required for 'order' to work
+ order: 2 # 👈 Tried when order=1 fails
```
diff --git a/docs/my-website/docs/secret.md b/docs/my-website/docs/secret.md
index c5c80311475..57f576fd56a 100644
--- a/docs/my-website/docs/secret.md
+++ b/docs/my-website/docs/secret.md
@@ -6,7 +6,7 @@
[Enterprise Pricing](https://www.litellm.ai/#pricing)
-[Contact us here to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+[Contact us here to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/secret_managers/aws_kms.md b/docs/my-website/docs/secret_managers/aws_kms.md
index 7f69d91fe87..806223a2539 100644
--- a/docs/my-website/docs/secret_managers/aws_kms.md
+++ b/docs/my-website/docs/secret_managers/aws_kms.md
@@ -6,7 +6,7 @@
[Enterprise Pricing](https://www.litellm.ai/#pricing)
-[Contact us here to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+[Contact us here to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/secret_managers/aws_secret_manager.md b/docs/my-website/docs/secret_managers/aws_secret_manager.md
index c49797a15dd..a7e24ea69ae 100644
--- a/docs/my-website/docs/secret_managers/aws_secret_manager.md
+++ b/docs/my-website/docs/secret_managers/aws_secret_manager.md
@@ -9,7 +9,7 @@ import TabItem from '@theme/TabItem';
[Enterprise Pricing](https://www.litellm.ai/#pricing)
-[Contact us here to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+[Contact us here to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/secret_managers/azure_key_vault.md b/docs/my-website/docs/secret_managers/azure_key_vault.md
index 81aeaa32159..4ea53d2ea9e 100644
--- a/docs/my-website/docs/secret_managers/azure_key_vault.md
+++ b/docs/my-website/docs/secret_managers/azure_key_vault.md
@@ -6,7 +6,7 @@
[Enterprise Pricing](https://www.litellm.ai/#pricing)
-[Contact us here to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+[Contact us here to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/secret_managers/cyberark.md b/docs/my-website/docs/secret_managers/cyberark.md
index 0a17c0afc30..cd7c0ea5d25 100644
--- a/docs/my-website/docs/secret_managers/cyberark.md
+++ b/docs/my-website/docs/secret_managers/cyberark.md
@@ -8,7 +8,7 @@ import Image from '@theme/IdealImage';
[Enterprise Pricing](https://www.litellm.ai/#pricing)
-[Contact us here to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+[Contact us here to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/secret_managers/google_kms.md b/docs/my-website/docs/secret_managers/google_kms.md
index 31fd6195bdb..152ecbaae80 100644
--- a/docs/my-website/docs/secret_managers/google_kms.md
+++ b/docs/my-website/docs/secret_managers/google_kms.md
@@ -6,7 +6,7 @@
[Enterprise Pricing](https://www.litellm.ai/#pricing)
-[Contact us here to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+[Contact us here to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/secret_managers/google_secret_manager.md b/docs/my-website/docs/secret_managers/google_secret_manager.md
index 81878b7e398..f3e7367e8a4 100644
--- a/docs/my-website/docs/secret_managers/google_secret_manager.md
+++ b/docs/my-website/docs/secret_managers/google_secret_manager.md
@@ -6,7 +6,7 @@
[Enterprise Pricing](https://www.litellm.ai/#pricing)
-[Contact us here to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+[Contact us here to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/secret_managers/hashicorp_vault.md b/docs/my-website/docs/secret_managers/hashicorp_vault.md
index 52d9b556200..11e25e88a7d 100644
--- a/docs/my-website/docs/secret_managers/hashicorp_vault.md
+++ b/docs/my-website/docs/secret_managers/hashicorp_vault.md
@@ -8,7 +8,7 @@ import Image from '@theme/IdealImage';
[Enterprise Pricing](https://www.litellm.ai/#pricing)
-[Contact us here to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+[Contact us here to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/secret_managers/overview.md b/docs/my-website/docs/secret_managers/overview.md
index bf7386ab89c..f02362f4932 100644
--- a/docs/my-website/docs/secret_managers/overview.md
+++ b/docs/my-website/docs/secret_managers/overview.md
@@ -8,7 +8,7 @@ import Image from '@theme/IdealImage';
[Enterprise Pricing](https://www.litellm.ai/#pricing)
-[Contact us here to get a free trial](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions)
+[Contact us here to get a free trial](https://enterprise.litellm.ai/demo)
:::
diff --git a/docs/my-website/docs/troubleshoot.md b/docs/my-website/docs/troubleshoot.md
index 1539e1959f7..1afa35df8e4 100644
--- a/docs/my-website/docs/troubleshoot.md
+++ b/docs/my-website/docs/troubleshoot.md
@@ -50,7 +50,6 @@ Full error logs, stack traces, and any images from service metrics (CPU, memory,
[Community Discord 💭](https://discord.gg/wuPM9dRgDw)
[Community Slack 💭](https://www.litellm.ai/support)
-Our numbers 📞 +1 (770) 8783-106 / +1 (412) 618-6238
Our emails ✉️ ishaan@berri.ai / krrish@berri.ai
diff --git a/docs/my-website/docs/tutorials/claude_code_plugin_marketplace.md b/docs/my-website/docs/tutorials/claude_code_plugin_marketplace.md
index 9d93c717c4f..d8175f51aca 100644
--- a/docs/my-website/docs/tutorials/claude_code_plugin_marketplace.md
+++ b/docs/my-website/docs/tutorials/claude_code_plugin_marketplace.md
@@ -37,7 +37,7 @@ Click **+ Add New Plugin** to register a plugin in your marketplace.
Enter the plugin information:
- **Name**: Plugin identifier (kebab-case, e.g., `my-plugin`)
-- **Source Type**: Choose GitHub or URL
+- **Source Type**: Choose GitHub, Git URL, or Git Subdir
- **Repository/URL**: The git source (e.g., `org/repo` for GitHub)
- **Version**: Semantic version (optional)
- **Description**: What the plugin does
@@ -216,6 +216,22 @@ curl -X DELETE http://localhost:4000/claude-code/plugins/my-plugin \
Use this format for GitLab, Bitbucket, or self-hosted git repositories.
+
+
+
+```json
+{
+ "name": "my-plugin",
+ "source": {
+ "source": "git-subdir",
+ "url": "https://github.com/org/repo.git",
+ "path": "plugins/my-plugin"
+ }
+}
+```
+
+Use this format when your plugin lives in a subdirectory of a git repository. The `path` field must be a relative path of slash-separated segments (alphanumeric, dots, hyphens, underscores only).
+
diff --git a/docs/my-website/docs/tutorials/compare_llms.md b/docs/my-website/docs/tutorials/compare_llms.md
index 02877b46607..0252263a16e 100644
--- a/docs/my-website/docs/tutorials/compare_llms.md
+++ b/docs/my-website/docs/tutorials/compare_llms.md
@@ -82,7 +82,7 @@ Benchmark Results for 'When will BerriAI IPO?':
+-----------------+----------------------------------------------------------------------------------+---------------------------+------------+
```
## Support
-**🤝 Schedule a 1-on-1 Session:** Book a [1-on-1 session](https://calendly.com/d/cx9p-5yf-2nm/litellm-introductions) with Krrish and Ishaan, the founders, to discuss any issues, provide feedback, or explore how we can improve LiteLLM for you.
+**🤝 Schedule a 1-on-1 Session:** Book a [1-on-1 session](https://enterprise.litellm.ai/demo) with Krrish and Ishaan, the founders, to discuss any issues, provide feedback, or explore how we can improve LiteLLM for you.
B[LiteLLM Responses API]
+ B --> C{Provider supports native file_search?}
+
+ C -->|Yes| D[Native passthrough path]
+ D --> D1[Decode unified vector_store_id if needed]
+ D1 --> D2[Forward request to provider unchanged]
+ D2 --> D3[Provider performs file_search]
+ D3 --> Z[OpenAI-compatible output]
+
+ C -->|No| E[Emulated fallback path]
+ E --> E1[Convert file_search to litellm_file_search function tool]
+ E1 --> E2[First model call returns tool call with one or more queries]
+ E2 --> E3[LiteLLM executes vector search for each query]
+ E3 --> E4[Second model call with tool_result context]
+ E4 --> E5[Synthesize file_search_call + message + citations]
+ E5 --> Z[OpenAI-compatible output]
+```
+
+
+
+## Prerequisites
+
+```bash
+pip install 'litellm[proxy]'
+export OPENAI_API_KEY="sk-..." # for native path
+export ANTHROPIC_API_KEY="sk-ant-..." # for emulated path
+```
+
+
+
+## Example response shape
+
+## Validating the Output Format
+
+Regardless of which path ran, the response always follows the OpenAI Responses API format:
+
+```json
+{
+ "output": [
+ {
+ "type": "file_search_call",
+ "id": "fs_abc123",
+ "status": "completed",
+ "queries": ["What does LiteLLM support?"],
+ "search_results": null
+ },
+ {
+ "type": "message",
+ "role": "assistant",
+ "content": [
+ {
+ "type": "output_text",
+ "text": "LiteLLM is a unified interface...",
+ "annotations": [
+ {
+ "type": "file_citation",
+ "index": 150,
+ "file_id": "file-xxxx",
+ "filename": "knowledge.txt"
+ }
+ ]
+ }
+ ]
+ }
+ ]
+}
+```
+
+**Validation script:**
+
+```python showLineNumbers title="Validate response structure"
+def validate_file_search_response(response):
+ """Assert that response follows OpenAI file_search output format."""
+ output = response.output
+ assert len(output) >= 2, "Expected at least 2 output items"
+
+ # First item: file_search_call
+ fs_call = output[0]
+ fs_type = fs_call["type"] if isinstance(fs_call, dict) else fs_call.type
+ assert fs_type == "file_search_call", f"Expected file_search_call, got {fs_type}"
+
+ fs_status = fs_call["status"] if isinstance(fs_call, dict) else fs_call.status
+ assert fs_status == "completed"
+
+ # Second item: message
+ msg = output[1]
+ msg_type = msg["type"] if isinstance(msg, dict) else msg.type
+ assert msg_type == "message"
+
+ content = msg["content"] if isinstance(msg, dict) else msg.content
+ assert len(content) > 0
+ text_block = content[0]
+ text = text_block["text"] if isinstance(text_block, dict) else text_block.text
+ assert isinstance(text, str) and len(text) > 0
+
+ print("✅ Response structure valid")
+ print(f" Queries: {fs_call['queries'] if isinstance(fs_call, dict) else fs_call.queries}")
+ print(f" Answer length: {len(text)} chars")
+ annotations = text_block["annotations"] if isinstance(text_block, dict) else text_block.annotations
+ print(f" Citations: {len(annotations)}")
+
+validate_file_search_response(response)
+```
+
+
+
+## Q&A
+
+- **Why do I see `UnsupportedParamsError`?** This usually means `file_search` was passed to a provider that does not support it natively and emulation could not route correctly. Check:
+ - The model string is valid (for example, `anthropic/claude-sonnet-4-5`).
+ - `custom_llm_provider` resolves correctly so LiteLLM can load the provider config.
+- **Why does vector search return no results?** Common causes:
+ - The vector store ID is wrong or has no files attached.
+ - In LiteLLM-managed stores, file ingestion is not complete (`status != completed`).
+ - The query is too narrow; try a broader query.
+- **Why am I getting `403 Access denied` on vector store calls?** The caller does not have access to that vector store.
+ - The store may belong to another team.
+ - Use an admin/proxy key if your setup requires cross-team access.
+- **Why are `annotations` empty in emulated mode?** `file_citation` annotations require `file_id` metadata in search results. If your vector backend does not return file-level metadata, the answer text is still generated but citations can be empty.
+
+
+
+## What to check next
+
+- [File Search reference in Responses API docs](/docs/response_api#file-search-vector-stores) — full API reference
+- [Vector Store management](/docs/vector_store_files) — create and manage vector stores
+- [Managed vector stores](/docs/providers/bedrock_vector_store) — provider-specific setup
diff --git a/docs/my-website/docs/tutorials/index.md b/docs/my-website/docs/tutorials/index.md
new file mode 100644
index 00000000000..7f80cc760ee
--- /dev/null
+++ b/docs/my-website/docs/tutorials/index.md
@@ -0,0 +1,98 @@
+---
+title: Tutorials
+sidebar_label: Overview
+---
+
+import NavigationCards from '@site/src/components/NavigationCards';
+
+**Tutorials** are step-by-step walkthroughs for integrating LiteLLM with external tools, frameworks, and services — or building complete end-to-end workflows.
+
+> Need help choosing the right path before you start? See [Learn →](/docs/learn)
+
+---
+
+## Getting Started
+
+
+
+---
+
+## Integrations
+
+
+
+---
+
+## Proxy
+
+
+
+---
+
+## Observability & Evaluation
+
+
diff --git a/docs/my-website/docs/tutorials/installation.md b/docs/my-website/docs/tutorials/installation.md
index ecaed0bec9d..cf39c55bee6 100644
--- a/docs/my-website/docs/tutorials/installation.md
+++ b/docs/my-website/docs/tutorials/installation.md
@@ -1,7 +1,3 @@
----
-displayed_sidebar: tutorialSidebar
----
-
# Set up environment
Let's get the necessary keys to set up our demo environment.
@@ -11,7 +7,5 @@ Every LLM provider needs API keys (e.g. `OPENAI_API_KEY`). You can get API keys
Let's get them for our demo!
**OpenAI**: https://platform.openai.com/account/api-keys
-**Cohere**: https://dashboard.cohere.com/welcome/login?redirect_uri=%2Fapi-keys (no credit card required)
+**Cohere**: https://dashboard.cohere.com/welcome/login?redirect_uri=%2Fapi-keys (no credit card required)
**AI21**: https://studio.ai21.com/account/api-key (no credit card required)
-
-
diff --git a/docs/my-website/docs/tutorials/opencode_integration.md b/docs/my-website/docs/tutorials/opencode_integration.md
index e55367833f2..35e00a1de50 100644
--- a/docs/my-website/docs/tutorials/opencode_integration.md
+++ b/docs/my-website/docs/tutorials/opencode_integration.md
@@ -253,7 +253,7 @@ model_list:
litellm_params:
model: openai/gpt-4
api_key: os.environ/OPENAI_API_KEY
-
+
- model_name: gpt-4o
litellm_params:
model: openai/gpt-4o
@@ -264,7 +264,7 @@ model_list:
litellm_params:
model: anthropic/claude-3-5-sonnet-20241022
api_key: os.environ/ANTHROPIC_API_KEY
-
+
# DeepSeek models
- model_name: deepseek-chat
litellm_params:
@@ -272,6 +272,19 @@ model_list:
api_key: os.environ/DEEPSEEK_API_KEY
```
+### Dropping OpenCode-specific parameters
+
+OpenCode sends a `reasoningSummary` parameter with reasoning-capable models such as `gpt-5`. This parameter is not supported by the Chat Completions API and will cause errors. Add `additional_drop_params` to every model entry in your `model_list` that will receive requests from OpenCode with reasoning enabled:
+
+```yaml
+model_list:
+ - model_name: gpt-5
+ litellm_params:
+ model: openai/gpt-5
+ api_key: os.environ/OPENAI_API_KEY
+ additional_drop_params: ["reasoningSummary"]
+```
+
## Troubleshooting
**OpenCode not connecting:**
@@ -294,6 +307,16 @@ model_list:
- Validate JSON syntax using a JSON validator
- Ensure the `$schema` URL is accessible
+**`Unknown parameter: 'reasoningSummary'` error:**
+- OpenCode sends a `reasoningSummary` parameter that is not supported by the Chat Completions API. Add `additional_drop_params: ["reasoningSummary"]` to each affected model entry in your `litellm_params`:
+ ```yaml
+ - model_name: gpt-5
+ litellm_params:
+ model: openai/gpt-5
+ api_key: os.environ/OPENAI_API_KEY
+ additional_drop_params: ["reasoningSummary"]
+ ```
+
## Tips
- Add more models to the config as needed - they'll appear in `/models`
diff --git a/docs/my-website/docs/tutorials/vertex_ai_pay_go.md b/docs/my-website/docs/tutorials/vertex_ai_pay_go.md
new file mode 100644
index 00000000000..87197e5bad5
--- /dev/null
+++ b/docs/my-website/docs/tutorials/vertex_ai_pay_go.md
@@ -0,0 +1,151 @@
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+# Vertex AI PayGo and Priority
+
+## Priority PayGo
+
+LiteLLM supports Priority PayGo.
+Send a priority header, get priority queueing, and pay priority token rates.
+
+:::info Which models support Priority PayGo?
+As of this writing: `gemini/gemini-2.5-pro`, `vertex_ai/gemini-3-pro-preview`, `vertex_ai/gemini-3.1-pro-preview`, `vertex_ai/gemini-3-flash-preview`, and their variants.
+Check `supports_service_tier: true` in LiteLLM's [model pricing JSON](https://github.com/BerriAI/litellm/blob/main/model_prices_and_context_window.json).
+:::
+
+### Send a priority request
+
+Use this header:
+
+`X-Vertex-AI-LLM-Shared-Request-Type: priority`
+
+
+
+
+```python
+import litellm
+
+response = litellm.completion(
+ model="vertex_ai/gemini-3-pro-preview",
+ messages=[{"role": "user", "content": "Summarize the Gettysburg Address."}],
+ vertex_project="YOUR_PROJECT_ID",
+ vertex_location="us-central1",
+ extra_headers={"X-Vertex-AI-LLM-Shared-Request-Type": "priority"},
+)
+
+print(response.choices[0].message.content)
+```
+
+
+
+
+```yaml title="config.yaml"
+model_list:
+ - model_name: gemini-priority
+ litellm_params:
+ model: vertex_ai/gemini-3-pro-preview
+ vertex_project: "YOUR_PROJECT_ID"
+ vertex_location: "us-central1"
+ vertex_credentials: os.environ/GOOGLE_APPLICATION_CREDENTIALS
+ extra_headers:
+ X-Vertex-AI-LLM-Shared-Request-Type: priority
+```
+
+```bash
+curl http://localhost:4000/v1/chat/completions \
+ -H "Authorization: Bearer sk-your-key" \
+ -H "Content-Type: application/json" \
+ -d '{"model": "gemini-priority", "messages": [{"role": "user", "content": "Hello"}]}'
+```
+
+
+
+
+Use `x-pass-` so LiteLLM forwards provider-specific headers.
+
+```bash
+MODEL_ID="gemini-3-pro-preview-0325"
+PROJECT_ID="YOUR_PROJECT_ID"
+
+curl -X POST \
+ "${LITELLM_PROXY_BASE_URL}/vertex_ai/v1/projects/${PROJECT_ID}/locations/global/publishers/google/models/${MODEL_ID}:generateContent" \
+ -H "Authorization: Bearer sk-your-litellm-key" \
+ -H "Content-Type: application/json" \
+ -H "x-pass-X-Vertex-AI-LLM-Shared-Request-Type: priority" \
+ -d '{"contents": [{"role": "user", "parts": [{"text": "Hello!"}]}]}'
+```
+
+
+
+
+### How cost tracking works
+
+
+
+**`trafficType` → `service_tier` mapping**
+
+| `usageMetadata.trafficType` | `service_tier` | Pricing keys used |
+|---|---|---|
+| `ON_DEMAND` | `None` | `input_cost_per_token` |
+| `ON_DEMAND_PRIORITY` | `"priority"` | `input_cost_per_token_priority` |
+| `FLEX` / `BATCH` | `"flex"` | `input_cost_per_token_flex` |
+
+If a tier-specific key is missing, LiteLLM falls back to standard pricing keys.
+
+---
+
+## Standard PayGo vs Provisioned Throughput
+
+This is a different header from priority routing:
+
+| Header value | Behavior |
+|---|---|
+| `X-Vertex-AI-LLM-Request-Type: shared` | Force standard PayGo (bypass PT) |
+| `X-Vertex-AI-LLM-Request-Type: dedicated` | Force Provisioned Throughput only (`429` if exhausted) |
+
+### Native route example
+
+```python
+import litellm
+
+response = litellm.completion(
+ model="vertex_ai/gemini-2.0-flash",
+ messages=[{"role": "user", "content": "Hello!"}],
+ vertex_project="YOUR_PROJECT_ID",
+ vertex_location="us-central1",
+ extra_headers={"X-Vertex-AI-LLM-Request-Type": "shared"},
+)
+```
+
+### Pass-through example
+
+```bash
+MODEL_ID="gemini-2.0-flash-001"
+PROJECT_ID="YOUR_PROJECT_ID"
+
+curl -X POST \
+ "${LITELLM_PROXY_BASE_URL}/vertex_ai/v1/projects/${PROJECT_ID}/locations/global/publishers/google/models/${MODEL_ID}:generateContent" \
+ -H "Authorization: Bearer sk-your-litellm-key" \
+ -H "Content-Type: application/json" \
+ -H "x-pass-X-Vertex-AI-LLM-Request-Type: shared" \
+ -d '{
+ "contents": [{"role": "user", "parts": [{"text": "Hello!"}]}]
+ }'
+```
+
+---
+
+## Troubleshooting
+
+**Q: What does `403 Permission denied` or `IAM_PERMISSION_DENIED` mean?**
+A: The service account or Application Default Credentials (ADC) user does not have the `roles/aiplatform.user` role. To resolve this, re-run the `gcloud projects add-iam-policy-binding`.
+
+**Q: What should I do if I get a `429 Quota exceeded` error?**
+A: This means you've hit the per-region QPM (queries per minute) or TPM (tokens per minute) quota. You can:
+- Request a quota increase from the [GCP Quotas console](https://console.cloud.google.com/iam-admin/quotas)
+- Add more regions to your LiteLLM configuration for load balancing
+- Upgrade to [Provisioned Throughput](https://cloud.google.com/vertex-ai/generative-ai/docs/provisioned-throughput) for guaranteed capacity
+
+**Q: How do I fix the `VERTEXAI_PROJECT not set` error?**
+A: Either pass the `vertex_project` parameter explicitly in your LiteLLM call, or set the `VERTEXAI_PROJECT` environment variable before running your code.
+
diff --git a/docs/my-website/docs/vertex_batch_passthrough.md b/docs/my-website/docs/vertex_batch_passthrough.md
index 3203d7d792a..17ffc1e6dbc 100644
--- a/docs/my-website/docs/vertex_batch_passthrough.md
+++ b/docs/my-website/docs/vertex_batch_passthrough.md
@@ -155,6 +155,6 @@ Common error scenarios and their solutions:
## Related Documentation
-- [Vertex AI Provider Documentation](./vertex.md)
-- [General Batches API Documentation](../batches.md)
-- [Cost Tracking and Monitoring](../observability/telemetry.md)
+- [Vertex AI Provider Documentation](./providers/vertex.md)
+- [General Batches API Documentation](./batches.md)
+- [Cost Tracking and Monitoring](./observability/telemetry.md)
diff --git a/docs/my-website/docusaurus.config.js b/docs/my-website/docusaurus.config.js
index 32d5d800b71..9e1fae6a34f 100644
--- a/docs/my-website/docusaurus.config.js
+++ b/docs/my-website/docusaurus.config.js
@@ -2,9 +2,9 @@
// Note: type annotations allow type checking and IDEs autocompletion
// @ts-ignore
-const lightCodeTheme = require('prism-react-renderer/themes/github');
+const lightCodeTheme = require('prism-react-renderer/themes/vsLight');
// @ts-ignore
-const darkCodeTheme = require('prism-react-renderer/themes/dracula');
+const darkCodeTheme = require('prism-react-renderer/themes/nightOwl');
const inkeepConfig = {
baseSettings: {
@@ -87,18 +87,88 @@ const config = {
},
],
[
- '@docusaurus/plugin-content-blog',
+ '@docusaurus/plugin-content-docs',
{
- id: 'release_notes',
+ id: 'release-notes',
path: './release_notes',
routeBasePath: 'release_notes',
- blogTitle: 'Release Notes',
- blogSidebarTitle: 'Releases',
- blogSidebarCount: 'ALL',
- postsPerPage: 'ALL',
- showReadingTime: false,
- sortPosts: 'descending',
- include: ['**/*.{md,mdx}'],
+ sidebarPath: require.resolve('./sidebars-release-notes.js'),
+ async sidebarItemsGenerator({defaultSidebarItemsGenerator, docs, ...args}) {
+ const items = await defaultSidebarItemsGenerator({docs, ...args});
+
+ // Build map of doc id -> year from frontmatter date
+ const docYearMap = {};
+ for (const doc of docs) {
+ const date = doc.frontMatter && doc.frontMatter.date;
+ if (date) {
+ const year = new Date(date).getFullYear();
+ docYearMap[doc.id] = year;
+ }
+ }
+
+ function parseVersion(str) {
+ const match = (str || '').match(/v?(\d+)\.(\d+)\.(\d+)/);
+ if (!match) return [0, 0, 0];
+ return [parseInt(match[1]), parseInt(match[2]), parseInt(match[3])];
+ }
+ function compareVersionsDesc(a, b) {
+ const [aMaj, aMin, aPatch] = parseVersion(a.label || a.id || '');
+ const [bMaj, bMin, bPatch] = parseVersion(b.label || b.id || '');
+ if (bMaj !== aMaj) return bMaj - aMaj;
+ if (bMin !== aMin) return bMin - aMin;
+ return bPatch - aPatch;
+ }
+
+ // Flatten and transform doc items (filter index, shorten labels)
+ function flattenDocs(list) {
+ const result = [];
+ for (const item of list) {
+ if (item.type === 'doc' && item.id === 'index') continue;
+ if (item.type === 'doc') {
+ const label = item.id.replace(/\/index$/, '');
+ result.push({...item, label});
+ } else if (item.type === 'category') {
+ if (item.link && item.link.type === 'doc' && item.link.id !== 'index') {
+ const id = item.link.id;
+ const label = id.replace(/\/index$/, '');
+ result.push({type: 'doc', id, label});
+ } else {
+ result.push(...flattenDocs(item.items));
+ }
+ }
+ }
+ return result;
+ }
+
+ const docItems = flattenDocs(items);
+
+ // Group by year
+ const byYear = {};
+ for (const item of docItems) {
+ const year = docYearMap[item.id] || 'Other';
+ if (!byYear[year]) byYear[year] = [];
+ byYear[year].push(item);
+ }
+
+ // Sort each year's items by version descending
+ for (const year of Object.keys(byYear)) {
+ byYear[year].sort(compareVersionsDesc);
+ }
+
+ // Build categories sorted by year descending
+ const years = Object.keys(byYear).sort((a, b) => {
+ // Object.keys() returns strings; avoid numeric subtraction type errors.
+ const na = Number.parseInt(a, 10);
+ const nb = Number.parseInt(b, 10);
+ return nb - na;
+ });
+ return years.map(year => ({
+ type: 'category',
+ label: String(year),
+ collapsed: year !== String(years[0]),
+ items: byYear[year],
+ }));
+ },
},
],
[
@@ -130,6 +200,20 @@ const config = {
};
},
}),
+ // Ensure gtag exists before the GA script loads.
+ () => ({
+ name: 'gtag-shim',
+ injectHtmlTags() {
+ return {
+ headTags: [
+ {
+ tagName: 'script',
+ innerHTML: `window.dataLayer=window.dataLayer||[];function gtag(){dataLayer.push(arguments);}if(!window.gtag){window.gtag=gtag;}`,
+ },
+ ],
+ };
+ },
+ }),
],
presets: [
@@ -137,10 +221,13 @@ const config = {
'classic',
/** @type {import('@docusaurus/preset-classic').Options} */
({
- gtag: {
- trackingID: 'G-K7K215ZVNC',
- anonymizeIP: true,
- },
+ gtag:
+ process.env.NODE_ENV === 'production'
+ ? {
+ trackingID: 'G-K7K215ZVNC',
+ anonymizeIP: true,
+ }
+ : undefined,
docs: {
sidebarPath: require.resolve('./sidebars.js'),
},
@@ -181,34 +268,39 @@ const config = {
label: 'Docs',
},
{
+ type: 'docSidebar',
+ sidebarId: 'learnSidebar',
+ position: 'left',
+ label: 'Learn',
+ },
+ {
+ type: 'docSidebar',
sidebarId: 'integrationsSidebar',
position: 'left',
label: 'Integrations',
- to: "docs/integrations"
},
{
- sidebarId: 'tutorialSidebar',
position: 'left',
label: 'Enterprise',
to: "docs/enterprise"
},
- { to: '/release_notes', label: 'Release Notes', position: 'left' },
{ to: '/blog', label: 'Blog', position: 'left' },
- {
- href: 'https://models.litellm.ai/',
- label: '💸 LLM Model Cost Map',
- position: 'right',
- },
{
href: 'https://github.com/BerriAI/litellm',
- label: 'GitHub',
position: 'right',
+ className: 'header-github-link',
+ 'aria-label': 'GitHub repository',
},
{
href: 'https://www.litellm.ai/support',
- label: 'Slack/Discord',
position: 'right',
- }
+ className: 'header-discord-link',
+ 'aria-label': 'Discord / Slack community',
+ },
+ {
+ type: 'search',
+ position: 'right',
+ },
],
},
footer: {
diff --git a/docs/my-website/img/ci_cd_architecture.png b/docs/my-website/img/ci_cd_architecture.png
new file mode 100644
index 00000000000..111567c11b0
Binary files /dev/null and b/docs/my-website/img/ci_cd_architecture.png differ
diff --git a/docs/my-website/img/hero.png b/docs/my-website/img/hero.png
new file mode 100644
index 00000000000..9f77a28d718
Binary files /dev/null and b/docs/my-website/img/hero.png differ
diff --git a/docs/my-website/img/isolated_ci_cd_environments.png b/docs/my-website/img/isolated_ci_cd_environments.png
new file mode 100644
index 00000000000..347523f0fab
Binary files /dev/null and b/docs/my-website/img/isolated_ci_cd_environments.png differ
diff --git a/docs/my-website/img/mcp_zero_trust_gateway.png b/docs/my-website/img/mcp_zero_trust_gateway.png
new file mode 100644
index 00000000000..3955cef0553
Binary files /dev/null and b/docs/my-website/img/mcp_zero_trust_gateway.png differ
diff --git a/docs/my-website/img/security_update_march_2026/proxy_version.png b/docs/my-website/img/security_update_march_2026/proxy_version.png
new file mode 100644
index 00000000000..c5d03d6a636
Binary files /dev/null and b/docs/my-website/img/security_update_march_2026/proxy_version.png differ
diff --git a/docs/my-website/img/shared_ci_cd_environment.png b/docs/my-website/img/shared_ci_cd_environment.png
new file mode 100644
index 00000000000..e54e11faa85
Binary files /dev/null and b/docs/my-website/img/shared_ci_cd_environment.png differ
diff --git a/docs/my-website/package.json b/docs/my-website/package.json
index 20462de2dd7..4b41a7ef46a 100644
--- a/docs/my-website/package.json
+++ b/docs/my-website/package.json
@@ -90,7 +90,7 @@
"tar-fs": ">=2.1.4",
"webpack-dev-middleware": ">=5.3.4",
"braces": ">=3.0.3",
- "axios": ">=0.30.2",
+ "axios": "1.13.6",
"webpack": ">=5.94.0",
"serve-static": ">=1.16.0",
"path-to-regexp": ">=0.1.12",
diff --git a/docs/my-website/release_notes/index.md b/docs/my-website/release_notes/index.md
new file mode 100644
index 00000000000..e2b7edf3222
--- /dev/null
+++ b/docs/my-website/release_notes/index.md
@@ -0,0 +1,52 @@
+---
+title: Release Notes
+sidebar_label: Overview
+slug: /
+---
+
+# Release Notes
+
+LiteLLM ships new releases regularly with new provider support, performance improvements, and enterprise features. Use the sidebar to browse all releases.
+
+## Latest Release
+
+### [v1.82.3 — Nebius AI, gpt-5.4, Gemini 3.x, FLUX Kontext, and 116 New Models](/release_notes/v1.82.3/v1-82-3)
+
+_March 16, 2026_
+
+116 new models including Nebius AI, gpt-5.4, Gemini 3.x, and FLUX Kontext.
+
+---
+
+## Recent Releases
+
+| Version | Date | Highlights |
+| ----------------------------------- | ------------ | ---------------------------------------------------------- |
+| [v1.82.0](/release_notes/v1.82.0/v1-82-0) | Feb 28, 2026 | Realtime Guardrails, Projects Management, and 10+ Performance Optimizations |
+| [v1.81.14](/release_notes/v1.81.14/v1-81-14) | Feb 21, 2026 | New Gateway Level Guardrails & Compliance Playground |
+| [v1.81.12](/release_notes/v1.81.12/v1-81-12) | Feb 14, 2026 | Guardrail Policy Templates & Action Builder |
+| [v1.81.9](/release_notes/v1.81.9/v1-81-9) | Feb 7, 2026 | Control which MCP Servers are exposed on the Internet |
+| [v1.81.6](/release_notes/v1.81.6/v1-81-6) | Jan 31, 2026 | Logs v2 with Tool Call Tracing |
+| [v1.81.3](/release_notes/v1.81.3-stable/v1-81-3) | Jan 26, 2026 | Performance — 25% CPU Usage Reduction |
+| [v1.81.0](/release_notes/v1.81.0/v1-81-0) | Jan 18, 2026 | Claude Code — Web Search Across All Providers |
+| [v1.80.15](/release_notes/v1.80.15/v1-80-15) | Jan 10, 2026 | Manus API Support |
+| [v1.80.8](/release_notes/v1.80.8-stable/v1-80-8) | Dec 6, 2025 | Introducing A2A Agent Gateway |
+| [v1.80.5](/release_notes/v1.80.5-stable/v1-80-5) | Nov 22, 2025 | Gemini 3.0 Support |
+| [v1.80.0](/release_notes/v1.80.0-stable/v1-80-0) | Nov 15, 2025 | Introducing Agent Hub: Register, Publish, and Share Agents |
+| [v1.79.3](/release_notes/v1.79.3-stable/v1-79-3) | Nov 8, 2025 | Built-in Guardrails on AI Gateway |
+| [v1.79.0](/release_notes/v1.79.0-stable/v1-79-0) | Oct 26, 2025 | Search APIs |
+| [v1.78.5](/release_notes/v1.78.5-stable/v1-78-5) | Oct 18, 2025 | Native OCR Support |
+| [v1.78.0](/release_notes/v1.78.0-stable/v1-78-0) | Oct 11, 2025 | MCP Gateway: Control Tool Access by Team, Key |
+| [v1.77.7](/release_notes/v1.77.7-stable/v1-77-7) | Oct 4, 2025 | 2.9x Lower Median Latency |
+| [v1.77.5](/release_notes/v1.77.5-stable/v1-77-5) | Sep 29, 2025 | MCP OAuth 2.0 Support |
+| [v1.77.3](/release_notes/v1.77.3-stable/v1-77-3) | Sep 21, 2025 | Priority Based Rate Limiting |
+
+---
+
+## Stay Updated
+
+- **GitHub**: Watch the [BerriAI/litellm](https://github.com/BerriAI/litellm) repository for release notifications
+- **Discord**: Join our [community](https://discord.com/invite/wuPM9dRgDw) for announcements
+- **Twitter**: Follow [@LiteLLM](https://twitter.com/LiteLLM)
+
+Use the sidebar to browse the full release history.
diff --git a/docs/my-website/release_notes/v1.63.14/index.md b/docs/my-website/release_notes/v1.63.14/index.md
index 1ac713fc2d5..d34b2c7b335 100644
--- a/docs/my-website/release_notes/v1.63.14/index.md
+++ b/docs/my-website/release_notes/v1.63.14/index.md
@@ -62,10 +62,10 @@ Here's a Demo Instance to test changes:
- Infer aws region from bedrock application profile id - (`arn:aws:bedrock:us-east-1:...`)
- Ollama - support calling via `/v1/completions` [Get Started](../../docs/providers/ollama#using-ollama-fim-on-v1completions)
- Bedrock - support `us.deepseek.r1-v1:0` model name [Docs](../../docs/providers/bedrock#supported-aws-bedrock-models)
-- OpenRouter - `OPENROUTER_API_BASE` env var support [Docs](../../docs/providers/openrouter.md)
+- OpenRouter - `OPENROUTER_API_BASE` env var support [Docs](../../docs/providers/openrouter)
- Azure - add audio model parameter support - [Docs](../../docs/providers/azure#azure-audio-model)
- OpenAI - PDF File support [Docs](../../docs/completion/document_understanding#openai-file-message-type)
-- OpenAI - o1-pro Responses API streaming support [Docs](../../docs/response_api.md#streaming)
+- OpenAI - o1-pro Responses API streaming support [Docs](../../docs/response_api#streaming)
- [BETA] MCP - Use MCP Tools with LiteLLM SDK [Docs](../../docs/mcp)
2. **Bug Fixes**
@@ -102,7 +102,7 @@ Here's a Demo Instance to test changes:
- fix logging to just log the LLM I/O [PR](https://github.com/BerriAI/litellm/pull/9353)
- Dynamic API Key/Space param support [Get Started](../../docs/observability/arize_integration#pass-arize-spacekey-per-request)
- StandardLoggingPayload - Log litellm_model_name in payload. Allows knowing what the model sent to API provider was [Get Started](../../docs/proxy/logging_spec#standardlogginghiddenparams)
-- Prompt Management - Allow building custom prompt management integration [Get Started](../../docs/proxy/custom_prompt_management.md)
+- Prompt Management - Allow building custom prompt management integration [Get Started](../../docs/proxy/custom_prompt_management)
## Performance / Reliability improvements
@@ -128,4 +128,4 @@ Here's a Demo Instance to test changes:
## Complete Git Diff
-[Here's the complete git diff](https://github.com/BerriAI/litellm/compare/v1.63.11-stable...v1.63.14.rc)
\ No newline at end of file
+[Here's the complete git diff](https://github.com/BerriAI/litellm/compare/v1.63.11-stable...v1.63.14.rc)
diff --git a/docs/my-website/release_notes/v1.63.2-stable/index.md b/docs/my-website/release_notes/v1.63.2-stable/index.md
index a248aa94342..18233f25c21 100644
--- a/docs/my-website/release_notes/v1.63.2-stable/index.md
+++ b/docs/my-website/release_notes/v1.63.2-stable/index.md
@@ -64,15 +64,15 @@ Here's a Demo Instance to test changes:
9. Bedrock - handle thinking blocks in assistant message. [Get Started](https://docs.litellm.ai/docs/providers/bedrock#usage---thinking--reasoning-content)
10. Anthropic - Return `signature` on streaming. [Get Started](https://docs.litellm.ai/docs/providers/bedrock#usage---thinking--reasoning-content)
- Note: We've also migrated from `signature_delta` to `signature`. [Read more](https://docs.litellm.ai/release_notes/v1.63.0)
-11. Support format param for specifying image type. [Get Started](../../docs/completion/vision.md#explicitly-specify-image-type)
-12. Anthropic - `/v1/messages` endpoint - `thinking` param support. [Get Started](../../docs/anthropic_unified.md)
+11. Support format param for specifying image type. [Get Started](../../docs/completion/vision#explicitly-specify-image-type)
+12. Anthropic - `/v1/messages` endpoint - `thinking` param support. [Get Started](../../docs/anthropic_unified)
- Note: this refactors the [BETA] unified `/v1/messages` endpoint, to just work for the Anthropic API.
13. Vertex AI - handle $id in response schema when calling vertex ai. [Get Started](https://docs.litellm.ai/docs/providers/vertex#json-schema)
## Spend Tracking Improvements
1. Batches API - Fix cost calculation to run on retrieve_batch. [Get Started](https://docs.litellm.ai/docs/batches)
-2. Batches API - Log batch models in spend logs / standard logging payload. [Get Started](../../docs/proxy/logging_spec.md#standardlogginghiddenparams)
+2. Batches API - Log batch models in spend logs / standard logging payload. [Get Started](../../docs/proxy/logging_spec#standardlogginghiddenparams)
## Management Endpoints / UI
@@ -109,4 +109,4 @@ Here's a Demo Instance to test changes:
## Complete Git Diff
-[Here's the complete git diff](https://github.com/BerriAI/litellm/compare/v1.61.20-stable...v1.63.2-stable)
\ No newline at end of file
+[Here's the complete git diff](https://github.com/BerriAI/litellm/compare/v1.61.20-stable...v1.63.2-stable)
diff --git a/docs/my-website/release_notes/v1.80.15/index.md b/docs/my-website/release_notes/v1.80.15/index.md
index 4037a0d9b5d..15b49822965 100644
--- a/docs/my-website/release_notes/v1.80.15/index.md
+++ b/docs/my-website/release_notes/v1.80.15/index.md
@@ -53,7 +53,7 @@ pip install litellm==1.80.15
- **MCP Global Mode** - [Configure MCP servers globally with visibility controls](../../docs/mcp)
- **Interactions API Bridge** - [Use all LiteLLM providers with the Interactions API](../../docs/interactions)
- **RAG Query Endpoint** - [New RAG Search/Query endpoint for retrieval-augmented generation](../../docs/search/index)
-- **UI Usage - Endpoint Activity** - [Users can now see Endpoint Activity Metrics in the UI](../../docs/proxy/endpoint_activity.md)
+- **UI Usage - Endpoint Activity** - [Users can now see Endpoint Activity Metrics in the UI](../../docs/proxy/endpoint_activity)
- **50% Overhead Reduction** - LiteLLM now sends 2.5× more requests to LLM providers
@@ -640,4 +640,3 @@ Users can now see Endpoint Activity Metrics in the UI.
**[View complete changelog on GitHub](https://github.com/BerriAI/litellm/compare/v1.80.11.rc.1...v1.80.15-stable.1)**
-
diff --git a/docs/my-website/release_notes/v1.81.0/index.md b/docs/my-website/release_notes/v1.81.0/index.md
index e61d7d2d593..5953c572a7a 100644
--- a/docs/my-website/release_notes/v1.81.0/index.md
+++ b/docs/my-website/release_notes/v1.81.0/index.md
@@ -48,7 +48,7 @@ pip install litellm==1.81.0
- **Claude Code** - Support for using web search across Bedrock, Vertex AI, and all LiteLLM providers
- **Major Change** - [50MB limit on image URL downloads](#major-change---chatcompletions-image-url-download-size-limit) to improve reliability
- **Performance** - [25% CPU Usage Reduction](#performance---25-cpu-usage-reduction) by removing premature model.dump() calls from the hot path
-- **Deleted Keys Audit Table on UI** - [View deleted keys and teams for audit purposes](../../docs/proxy/deleted_keys_teams.md) with spend and budget information at the time of deletion
+- **Deleted Keys Audit Table on UI** - [View deleted keys and teams for audit purposes](../../docs/proxy/deleted_keys_teams) with spend and budget information at the time of deletion
---
@@ -166,7 +166,7 @@ LiteLLM now reduces CPU usage by removing premature `model.dump()` calls from th
-LiteLLM now provides a comprehensive audit table for deleted API keys and teams directly in the UI. This feature allows you to easily track the spend of deleted keys, view their associated team information, and maintain accurate financial records for auditing and compliance purposes. The table displays key details including key aliases, team associations, and spend information captured at the time of deletion. For more information on how to use this feature, see the [Deleted Keys & Teams documentation](../../docs/proxy/deleted_keys_teams.md).
+LiteLLM now provides a comprehensive audit table for deleted API keys and teams directly in the UI. This feature allows you to easily track the spend of deleted keys, view their associated team information, and maintain accurate financial records for auditing and compliance purposes. The table displays key details including key aliases, team associations, and spend information captured at the time of deletion. For more information on how to use this feature, see the [Deleted Keys & Teams documentation](../../docs/proxy/deleted_keys_teams).
---
diff --git a/docs/my-website/release_notes/v1.81.12.md b/docs/my-website/release_notes/v1.81.12/index.md
similarity index 99%
rename from docs/my-website/release_notes/v1.81.12.md
rename to docs/my-website/release_notes/v1.81.12/index.md
index 0b7c1e146ab..1bbea5b82bc 100644
--- a/docs/my-website/release_notes/v1.81.12.md
+++ b/docs/my-website/release_notes/v1.81.12/index.md
@@ -62,13 +62,13 @@ This release fixes out-of-memory (OOM) risks from unbounded `asyncio.Queue()` us
This release adds a visual action builder for guardrail policies with conditional execution support. You can now chain guardrails into multi-step pipelines — if a simple guardrail fails, route to an advanced one instead of immediately blocking. Each step has configurable ON PASS and ON FAIL actions (Next Step, Block, or Allow), and you can test the full pipeline with a sample message before saving.
-
+
### Access Groups
Access Groups simplify defining resource access across your organization. One group can grant access to models, MCP servers, and agents—simply attach it to a key or team. Create groups in the Admin UI, define which resources each group includes, then assign the group when creating keys or teams. Updates to a group apply automatically to all attached keys and teams.
-
+
## New Providers and Endpoints
diff --git a/docs/my-website/release_notes/v1.81.14.md b/docs/my-website/release_notes/v1.81.14/index.md
similarity index 99%
rename from docs/my-website/release_notes/v1.81.14.md
rename to docs/my-website/release_notes/v1.81.14/index.md
index c342bc47ee9..92c22bc0ea3 100644
--- a/docs/my-website/release_notes/v1.81.14.md
+++ b/docs/my-website/release_notes/v1.81.14/index.md
@@ -56,7 +56,7 @@ pip install litellm==1.81.14
AI Platform Admins can now browse built-in and partner guardrails from the Guardrail Garden. Guardrails are organized by use case — blocking financial advice, filtering insults, detecting competitor mentions, and more — so you can find the right one and deploy it in a few clicks.
-
+
### 3 New Built-in Guardrails
@@ -72,7 +72,7 @@ These guardrails are built for production and on our benchmarks had a 100% Recal
Previously, the `store_model_in_db` setting could only be configured in `proxy_config.yaml` under `general_settings`, requiring a proxy restart to take effect. Now you can enable or disable this setting directly from the Admin UI without any restarts. This is especially useful for cloud deployments where you don't have direct access to config files or want to avoid downtime. Enable `store_model_in_db` to move model definitions from your YAML into the database—reducing config complexity, improving scalability, and enabling dynamic model management across multiple proxy instances.
-
+
#### Eval results
@@ -91,14 +91,14 @@ We benchmarked our new built-in guardrails against labeled datasets before shipp
The Compliance Playground lets you test any guardrail against our pre-built eval datasets or your own custom datasets, so you can see precision, recall, and false positive rate before rolling it out to production.
-
+
---
## Performance & Reliability — Up to 13% Lower Latency
-
+
This release cuts latency across all percentiles through 20+ micro-optimizations across logging, cost calculation, routing, and connection management. See [benchmarking](../../docs/benchmarks) for more info about how to benchmark yourself.
diff --git a/docs/my-website/release_notes/v1.81.6.md b/docs/my-website/release_notes/v1.81.6/index.md
similarity index 100%
rename from docs/my-website/release_notes/v1.81.6.md
rename to docs/my-website/release_notes/v1.81.6/index.md
diff --git a/docs/my-website/release_notes/v1.81.9.md b/docs/my-website/release_notes/v1.81.9/index.md
similarity index 99%
rename from docs/my-website/release_notes/v1.81.9.md
rename to docs/my-website/release_notes/v1.81.9/index.md
index 80be4179b46..d11b52e892c 100644
--- a/docs/my-website/release_notes/v1.81.9.md
+++ b/docs/my-website/release_notes/v1.81.9/index.md
@@ -81,7 +81,7 @@ This release makes it safe to expose MCP servers on the public internet by addin
[Get started](../../docs/mcp_public_internet)
@@ -92,7 +92,7 @@ Set a soft budget on any team to receive email alerts when spending crosses the
[Get started](../../docs/proxy/ui_team_soft_budget_alerts)
diff --git a/docs/my-website/release_notes/v1.82.0.md b/docs/my-website/release_notes/v1.82.0/index.md
similarity index 100%
rename from docs/my-website/release_notes/v1.82.0.md
rename to docs/my-website/release_notes/v1.82.0/index.md
diff --git a/docs/my-website/release_notes/v1.82.3.md b/docs/my-website/release_notes/v1.82.3/index.md
similarity index 58%
rename from docs/my-website/release_notes/v1.82.3.md
rename to docs/my-website/release_notes/v1.82.3/index.md
index 15df33fdb80..20be8826718 100644
--- a/docs/my-website/release_notes/v1.82.3.md
+++ b/docs/my-website/release_notes/v1.82.3/index.md
@@ -47,6 +47,10 @@ pip install litellm==1.82.3
- **FLUX Kontext image editing** — `flux-kontext-pro` and `flux-kontext-max` added to Black Forest Labs, alongside `flux-pro-1.0-fill` and `flux-pro-1.0-expand` for inpainting and outpainting
- **116 new models, 132 deprecated models cleaned up** — Major model map refresh including Mistral Magistral, Dashscope Qwen3 VL, xAI Grok via Azure AI, ZAI GLM-5, Serper Search; removal of OpenAI GPT-3.5/GPT-4 legacy variants, Gemini 1.5, and Vertex AI PaLM2
- **SageMaker Nova provider** — [New `sagemaker_nova` provider for Amazon Nova models on SageMaker](../../docs/providers/aws_sagemaker) - [PR #21542](https://github.com/BerriAI/litellm/pull/21542)
+- **Hashicorp Vault secret manager** — Config override backend powered by Hashicorp Vault, with full UI for managing vault-sourced credentials - [PR #22939](https://github.com/BerriAI/litellm/pull/22939), [PR #23036](https://github.com/BerriAI/litellm/pull/23036)
+- **Responses API WebSocket streaming** — Real-time WebSocket streaming for the Responses API, including support across all providers - [PR #22559](https://github.com/BerriAI/litellm/pull/22559), [PR #22771](https://github.com/BerriAI/litellm/pull/22771)
+- **Org Admin RBAC expansion** — Org Admins can now access team management endpoints, view and invite internal users, and manage team membership without requiring a global admin role - [PR #23085](https://github.com/BerriAI/litellm/pull/23085), [PR #23080](https://github.com/BerriAI/litellm/pull/23080)
+- **Guardrail mode defaults and tag-based modes** — Set a default guardrail mode list globally, and specify a list of modes in tag-based guardrail configs - [PR #22676](https://github.com/BerriAI/litellm/pull/22676), [PR #23020](https://github.com/BerriAI/litellm/pull/23020)
- **Secret redaction in logs** — API keys, tokens, and credentials automatically scrubbed from all proxy log output. Enabled by default; opt out with `LITELLM_DISABLE_REDACT_SECRETS=true` - [PR #23668](https://github.com/BerriAI/litellm/pull/23668)
- **Streaming stability fix** — Critical fix for `RuntimeError: Cannot send a request, as the client has been closed.` crashes after ~1 hour in production - [PR #22926](https://github.com/BerriAI/litellm/pull/22926)
@@ -54,7 +58,7 @@ pip install litellm==1.82.3
## New Providers and Endpoints
-### New Providers (5 new providers)
+### New Providers (7 new providers)
| Provider | Supported LiteLLM Endpoints | Description |
| -------- | --------------------------- | ----------- |
@@ -63,6 +67,8 @@ pip install litellm==1.82.3
| [Black Forest Labs](../../docs/providers/black_forest_labs) (`black_forest_labs/`) | `/images/generations`, `/images/edits` | FLUX image generation and editing — Kontext Pro/Max, Pro 1.0 Fill/Expand |
| [Serper](../../docs/providers/serper) (`serper/`) | `/search` | Web search via Serper API |
| [SageMaker Nova](../../docs/providers/aws_sagemaker) (`sagemaker_nova/`) | `/chat/completions` | Amazon Nova models via SageMaker endpoint |
+| [Google Search API](../../docs/providers/google_search) (`google_search/`) | `/search` | Google Search API integration - [PR #22752](https://github.com/BerriAI/litellm/pull/22752) |
+| [Bedrock Mantle](../../docs/providers/bedrock) (`bedrock_mantle/`) | `/chat/completions` | Amazon Bedrock via Mantle — alternative auth and routing path for Bedrock models - [PR #22866](https://github.com/BerriAI/litellm/pull/22866) |
---
@@ -238,22 +244,92 @@ pip install litellm==1.82.3
- **[Responses API](../../docs/response_api)**
- Handle `response.failed`, `response.incomplete`, and `response.cancelled` terminal event types in background streaming — previously only `response.completed` was handled - [PR #23492](https://github.com/BerriAI/litellm/pull/23492)
+ - WebSocket streaming support for Responses API — real-time streaming via WebSocket for all providers - [PR #22559](https://github.com/BerriAI/litellm/pull/22559), [PR #22771](https://github.com/BerriAI/litellm/pull/22771)
+ - WebRTC support for real-time audio/video communication - [PR #23446](https://github.com/BerriAI/litellm/pull/23446)
+ - Responses API support for OpenAI-compatible JSON providers (`openai_like`) - [PR #21398](https://github.com/BerriAI/litellm/pull/21398)
+ - Route `gpt-5.4+` calls using both tools and reasoning to the Responses API automatically - [PR #23577](https://github.com/BerriAI/litellm/pull/23577)
-#### Bug Fixes
+- **[Anthropic Files API](../../docs/providers/anthropic)**
+ - Full Anthropic Files API support — upload, retrieve, list, and delete files; use file references in messages - [PR #16594](https://github.com/BerriAI/litellm/pull/16594)
+
+- **[Mistral](../../docs/providers/mistral)**
+ - Voxtral audio transcription support — `mistral/voxtral-mini-*` and `mistral/voxtral-*` for audio transcription via Mistral - [PR #22801](https://github.com/BerriAI/litellm/pull/22801)
+
+- **[OpenAI](../../docs/providers/openai)**
+ - `litellm.acount_tokens()` public API — async token counting with full OpenAI provider support - [PR #22809](https://github.com/BerriAI/litellm/pull/22809)
+ - Normalize `reasoning_effort` dict to string for chat completion API - [PR #22981](https://github.com/BerriAI/litellm/pull/22981)
+
+- **[OpenRouter](../../docs/providers/openrouter)**
+ - Image edit support for OpenRouter models - [PR #22403](https://github.com/BerriAI/litellm/pull/22403)
+
+- **[Google Vertex AI](../../docs/providers/vertex)**
+ - VIDEO modality token usage tracking in `completion_tokens_details` - [PR #22550](https://github.com/BerriAI/litellm/pull/22550)
+
+- **Images API**
+ - `input_fidelity` parameter for image edit API - [PR #23201](https://github.com/BerriAI/litellm/pull/23201)
+
+- **General**
+ - Per-request `enable_json_schema_validation` flag for thread-safe JSON schema validation - [PR #21233](https://github.com/BerriAI/litellm/pull/21233)
+ - Model cost aliases expansion — define aliases in the cost map that inherit pricing from a parent model - [PR #23314](https://github.com/BerriAI/litellm/pull/23314), [PR #23457](https://github.com/BerriAI/litellm/pull/23457)
+ - Wildcards model support for the Files API - [PR #22740](https://github.com/BerriAI/litellm/pull/22740)
+
+#### Bugs
- **[Anthropic](../../docs/providers/anthropic)**
- Preserve native tool format (web_search, bash, tool_search, etc.) when guardrails convert tools for the Anthropic Messages API - [PR #23526](https://github.com/BerriAI/litellm/pull/23526)
+ - Enforce `type: "object"` on tool input schemas in `_map_tool_helper` — fixes tool call failures for strict-schema providers - [PR #23103](https://github.com/BerriAI/litellm/pull/23103)
+ - Deduplicate `tool_result` messages by `tool_call_id` — prevents duplicate tool result errors in multi-turn conversations - [PR #23104](https://github.com/BerriAI/litellm/pull/23104)
+ - Map `reasoning_effort` to `output_config` for Claude 4.6 models - [PR #22220](https://github.com/BerriAI/litellm/pull/22220)
+
+- **[Google Gemini](../../docs/providers/gemini)**
+ - Correct streaming `finish_reason` for tool calls — was incorrectly returning `null` instead of `tool_calls` - [PR #21577](https://github.com/BerriAI/litellm/pull/21577)
+ - Preserve `$ref` in JSON Schema for Gemini 2.0+ — schema references were being stripped, breaking structured output - [PR #21597](https://github.com/BerriAI/litellm/pull/21597)
+ - Handle `minimal` `reasoning_effort` param for Gemini 3.1 models - [PR #22920](https://github.com/BerriAI/litellm/pull/22920)
+
+- **[Google Vertex AI](../../docs/providers/vertex)**
+ - Pass through native Gemini `imageConfig` params for image generation - [PR #21585](https://github.com/BerriAI/litellm/pull/21585)
+ - Prevent content truncation when `finish_reason` races ahead of content chunks in streaming - [PR #22692](https://github.com/BerriAI/litellm/pull/22692)
+ - Strip LiteLLM-internal keys from `extra_body` before merging to Gemini request body - [PR #23131](https://github.com/BerriAI/litellm/pull/23131)
+ - Drop unsupported `output_config` parameter from all Vertex AI requests - [PR #22884](https://github.com/BerriAI/litellm/pull/22884)
+ - Skip schema transforms for Gemini 2.0+ tool parameters — avoids breaking native Gemini schema handling - [PR #23265](https://github.com/BerriAI/litellm/pull/23265)
+
+- **[OpenRouter](../../docs/providers/openrouter)**
+ - Pattern-based fix for native model double-stripping when provider prefix matches model name - [PR #22320](https://github.com/BerriAI/litellm/pull/22320)
+ - Use provider-reported usage in streaming responses when `stream_options` is not set - [PR #21592](https://github.com/BerriAI/litellm/pull/21592)
+
+- **[AWS Bedrock](../../docs/providers/bedrock)**
+ - Extract region and model ID from `bedrock/{region}/{model}` path format - [PR #22546](https://github.com/BerriAI/litellm/pull/22546)
+ - Strip `scope` from `cache_control` for Anthropic messages on Bedrock and Azure AI - [PR #22867](https://github.com/BerriAI/litellm/pull/22867)
+ - Populate `completion_tokens_details` in Responses API responses - [PR #23243](https://github.com/BerriAI/litellm/pull/23243)
+
+- **[Azure AI](../../docs/providers/azure_ai)**
+ - Resolve `api_base` from environment variable in Document Intelligence OCR - [PR #21581](https://github.com/BerriAI/litellm/pull/21581)
- **[Moonshot / Kimi](../../docs/providers/openai_compatible)**
- Auto-fill `reasoning_content` for Moonshot Kimi reasoning models - [PR #23580](https://github.com/BerriAI/litellm/pull/23580)
+ - Preserve `image_url` blocks in multimodal messages for Moonshot - [PR #21595](https://github.com/BerriAI/litellm/pull/21595)
- **[HuggingFace](../../docs/providers/huggingface)**
- Forward `extra_headers` to HuggingFace embedding API - [PR #23525](https://github.com/BerriAI/litellm/pull/23525)
+- **Token Counting / Cost**
+ - Fix `count_tokens` to include system prompts and tools in token counting API requests - [PR #22301](https://github.com/BerriAI/litellm/pull/22301)
+ - Pass all custom pricing fields to `register_model` in `completion()` and `embedding()` - [PR #22552](https://github.com/BerriAI/litellm/pull/22552)
+
+- **Tools / Function Calling**
+ - Gracefully repair truncated JSON in tool call arguments — prevents crashes on malformed tool responses - [PR #22503](https://github.com/BerriAI/litellm/pull/22503)
+ - Fix `output_item.done` for function calls not emitting `finish_reason` in streaming - [PR #22553](https://github.com/BerriAI/litellm/pull/22553)
+ - Preserve thinking block order with multiple web searches - [PR #23093](https://github.com/BerriAI/litellm/pull/23093)
+
- **General**
- Normalize `content_filtered` finish reason across providers - [PR #23564](https://github.com/BerriAI/litellm/pull/23564)
+ - Unify `finish_reason` mapping to OpenAI-compatible values across all providers - [PR #22138](https://github.com/BerriAI/litellm/pull/22138)
- Fix custom cost tracking on deployments for `/v1/messages` and `/v1/responses` - [PR #23647](https://github.com/BerriAI/litellm/pull/23647)
- Fix per-request custom pricing when `router_model_id` has no pricing data — now falls back to model name
+ - Fix batch list showing stale `validating` status after completion - [PR #22982](https://github.com/BerriAI/litellm/pull/22982)
+ - Fix batch retrieve returning raw `output_file_id` when `model_id` is missing - [PR #23194](https://github.com/BerriAI/litellm/pull/23194)
+ - Encode batch IDs when `x-litellm-model` header is used - [PR #22653](https://github.com/BerriAI/litellm/pull/22653)
+ - Map `reasoning` to `reasoning_content` in streaming Delta for gpt-oss providers - [PR #22803](https://github.com/BerriAI/litellm/pull/22803)
---
@@ -264,10 +340,31 @@ pip install litellm==1.82.3
- **Virtual Keys**
- Add Organization dropdown to Create/Edit Key form — `organization_id` is now a first-class field in Key Ownership - [PR #23595](https://github.com/BerriAI/litellm/pull/23595)
- Allow setting `organization_id` on `/key/update` — keys can be assigned or moved to a different organization after creation - [PR #23557](https://github.com/BerriAI/litellm/pull/23557)
+ - Manual Spend Reset for virtual keys from the UI — admins can reset key spend to zero on demand - [PR #22715](https://github.com/BerriAI/litellm/pull/22715)
+ - BYOK (Bring Your Own Key) — client-side provider API key takes precedence over proxy key for Anthropic `/v1/messages` - [PR #22964](https://github.com/BerriAI/litellm/pull/22964)
+ - UI login session duration configurable via `LITELLM_UI_SESSION_DURATION` environment variable - [PR #22182](https://github.com/BerriAI/litellm/pull/22182)
+ - Auto-redirect UI login to SSO via `auto_redirect_ui_login_to_sso: true` in config.yaml - [PR #23367](https://github.com/BerriAI/litellm/pull/23367)
+
+- **Access Control (RBAC)**
+ - Org Admins can now access team management endpoints — `/team/new`, `/team/update`, `/team/delete`, `/team/member_add`, `/team/member_delete` - [PR #23085](https://github.com/BerriAI/litellm/pull/23085), [PR #23095](https://github.com/BerriAI/litellm/pull/23095)
+ - Org Admins can view and invite internal users — full user management without requiring global admin role - [PR #23080](https://github.com/BerriAI/litellm/pull/23080)
+ - Allow Admin Viewers to access Audit Logs — view-only admin role now includes audit log access - [PR #23419](https://github.com/BerriAI/litellm/pull/23419)
+ - RBAC for Vector Stores and Agents — key/team-level access control for vector store and agent resources - [PR #22858](https://github.com/BerriAI/litellm/pull/22858)
+ - User filter scope (`scope_user_search_to_org`) is now opt-in — previously default-on, causing unintended restriction - [PR #23057](https://github.com/BerriAI/litellm/pull/23057)
+
+- **Vector Stores**
+ - Vector Store management endpoints — retrieve, list, update, and delete vector stores via `/v1/vector_stores/*` - [PR #23435](https://github.com/BerriAI/litellm/pull/23435)
+
+- **Teams**
+ - Batch expiry setting for teams — configure a default expiry duration for all team keys - [PR #22705](https://github.com/BerriAI/litellm/pull/22705)
+ - Team Admin can reset key spend - [PR #22725](https://github.com/BerriAI/litellm/pull/22725)
- **Internal Users**
- Add/Remove Team Membership directly from the Internal Users info page — includes searchable dropdown and role selector; no longer requires navigating to each team - [PR #23638](https://github.com/BerriAI/litellm/pull/23638)
+- **Models**
+ - Attach knowledge base to model via UI - [PR #22656](https://github.com/BerriAI/litellm/pull/22656)
+
- **Default Team Settings**
- Modernize page to antd (consistent with rest of app) - [PR #23614](https://github.com/BerriAI/litellm/pull/23614)
- Fix: default team params (budget, duration, tpm, rpm, permissions) now correctly applied on `/team/new` - [PR #23614](https://github.com/BerriAI/litellm/pull/23614)
@@ -290,6 +387,13 @@ pip install litellm==1.82.3
- Fix Public Model Hub not showing config-defined models after save - [PR #23501](https://github.com/BerriAI/litellm/pull/23501)
- Fix fallback popup model dropdown z-index issue - [PR #23516](https://github.com/BerriAI/litellm/pull/23516)
- Fix double-counting bug in org/team key limit checks on `/key/update`
+- Fix invite link allowing multiple password resets for the same link - [PR #22462](https://github.com/BerriAI/litellm/pull/22462)
+- Fix key expiry default duration not being applied when `duration` is not set - [PR #22956](https://github.com/BerriAI/litellm/pull/22956)
+- Fix all proxy models not including model access groups in key creation - [PR #23236](https://github.com/BerriAI/litellm/pull/23236)
+- Fix admin viewers unable to see all organizations - [PR #22940](https://github.com/BerriAI/litellm/pull/22940)
+- Fix Audit Logs UI: added server-side pagination, filtering, and drawer view - [PR #22476](https://github.com/BerriAI/litellm/pull/22476)
+- Fix virtual keys in teams view not applying the team filter correctly - [PR #23065](https://github.com/BerriAI/litellm/pull/23065)
+- Fix team expiry enforcement validation - [PR #22728](https://github.com/BerriAI/litellm/pull/22728)
---
@@ -297,6 +401,13 @@ pip install litellm==1.82.3
### Logging
+- **[Helicone](../../docs/observability/helicone_integration)**
+ - Add Gemini and Vertex AI support to HeliconeLogger — routes Gemini and Vertex AI requests through the correct Helicone provider URL - [PR #19288](https://github.com/BerriAI/litellm/pull/19288)
+ - Fix correct provider URL for Vertex AI Gemini models - [PR #22603](https://github.com/BerriAI/litellm/pull/22603)
+
+- **[Langfuse](../../docs/proxy/logging#langfuse)**
+ - Fix failure path kwargs inconsistency causing dropped traces on failed requests - [PR #22390](https://github.com/BerriAI/litellm/pull/22390)
+
- **[Vantage](https://vantage.sh)**
- Add Vantage integration for FOCUS 1.2 CSV export — export LiteLLM proxy spend data as FinOps Open Cost & Usage Specification reports, with time-windowed filenames to prevent overwrites - [PR #23333](https://github.com/BerriAI/litellm/pull/23333)
@@ -305,7 +416,10 @@ pip install litellm==1.82.3
### Guardrails
-No major guardrail changes in this release.
+- **Guardrail mode default list** — Configure a default list of guardrail modes applied globally when no per-request mode is specified - [PR #22676](https://github.com/BerriAI/litellm/pull/22676)
+- **Tag-based guardrail mode lists** — Specify a list of modes in tag-based guardrail configs instead of a single mode - [PR #23020](https://github.com/BerriAI/litellm/pull/23020)
+- **Fix presidio PII token leak** — Edge case where Anthropic handle in Presidio caused PII data exposure in token response - [PR #22627](https://github.com/BerriAI/litellm/pull/22627)
+- **Fix OTEL orphaned guardrail traces** — Span redundancy and missing response IDs in OpenTelemetry guardrail traces - [PR #23001](https://github.com/BerriAI/litellm/pull/23001)
### Prompt Management
@@ -313,7 +427,32 @@ No major prompt management changes in this release.
### Secret Managers
-No major secret manager changes in this release.
+- **[Hashicorp Vault](../../docs/secret_managers)** — Full Hashicorp Vault integration as a config override backend — secrets defined in Vault are fetched at startup and override `config.yaml` values. UI support for managing vault-sourced credentials included - [PR #22939](https://github.com/BerriAI/litellm/pull/22939), [PR #23036](https://github.com/BerriAI/litellm/pull/23036)
+
+---
+
+## MCP Gateway
+
+#### Features
+
+- **Token authentication for MCP servers** — configure `auth_type: "bearer"` per MCP server to require token-based auth on tool calls - [PR #23260](https://github.com/BerriAI/litellm/pull/23260)
+- **Team-scoped MCP server filtering** — keys created under a team only see MCP servers available to that team - [PR #23323](https://github.com/BerriAI/litellm/pull/23323)
+- **Per-server health recheck in UI** — trigger a health check for individual MCP servers without reloading all servers - [PR #23328](https://github.com/BerriAI/litellm/pull/23328)
+
+#### Bugs
+
+- Fix MCP server URL and tools management issues causing tool discovery to fail - [PR #22751](https://github.com/BerriAI/litellm/pull/22751)
+- Fix MCP server health checks triggering on server deletion - [PR #23063](https://github.com/BerriAI/litellm/pull/23063)
+
+---
+
+## Spend Tracking, Budgets and Rate Limiting
+
+- **Fix budget-linked keys never having spend reset** — Keys linked to budget objects were not having their spend reset on the configured reset interval - [PR #20688](https://github.com/BerriAI/litellm/pull/20688)
+- **Flex pricing support** — Add `flex_pricing` field to cost map for providers that offer dynamic pricing tiers - [PR #22992](https://github.com/BerriAI/litellm/pull/22992)
+- **Fix spend log cleanup** — Resolved lock tracking, integer retention, and skip-log-level issues in spend log cleanup job - [PR #22687](https://github.com/BerriAI/litellm/pull/22687)
+- **Fix WebSearch spend log deduplication** — WebSearch interception was failing with thinking enabled; fixed along with spend log dedup - [PR #22679](https://github.com/BerriAI/litellm/pull/22679)
+- **Fix TypeError when request has no API key** — Spend tracking was throwing unhandled exception when API key was absent from request - [PR #23363](https://github.com/BerriAI/litellm/pull/23363)
---
@@ -323,6 +462,10 @@ No major secret manager changes in this release.
- **Fix OOM / Prisma connection loss** on large installs — unbounded managed-object poll was exhausting Prisma connections after ~60–70 minutes on instances with 336K+ queued response rows - [PR #23472](https://github.com/BerriAI/litellm/pull/23472)
- **Centralize logging kwarg updates** — root cause fix migrating all logging updates to a single function, eliminating kwarg inconsistencies across logging paths - [PR #23659](https://github.com/BerriAI/litellm/pull/23659)
- **Fix tiktoken cache for non-root offline containers** — tiktoken cache now works correctly in offline environments running as non-root users - [PR #23498](https://github.com/BerriAI/litellm/pull/23498)
+- **Block proxy startup when Redis transaction buffer has no Redis** — prevents silent data loss when `use_redis_transaction_buffer: true` is set without a Redis connection - [PR #23019](https://github.com/BerriAI/litellm/pull/23019)
+- **Fix `InFlightRequestsMiddleware` crash** — undefined kwargs in middleware were causing request failures - [PR #22523](https://github.com/BerriAI/litellm/pull/22523)
+- **Fix `BaseModelResponseIterator` crash on non-string stream chunks** — streaming was crashing when providers returned non-string chunk data - [PR #23497](https://github.com/BerriAI/litellm/pull/23497)
+- **Fix `SERVER_ROOT_PATH` prefix handling** — strip prefix before checking mapped pass-through routes to prevent double-prefix issues - [PR #23414](https://github.com/BerriAI/litellm/pull/23414)
- **Add CodSpeed continuous performance benchmarks** — automated performance regression tracking on CI - [PR #23676](https://github.com/BerriAI/litellm/pull/23676)
---
@@ -342,6 +485,16 @@ No major secret manager changes in this release.
---
+## Documentation Updates
+
+- Add Anthropic `/v1/messages` → `/responses` parameter mapping reference - [PR #22893](https://github.com/BerriAI/litellm/pull/22893)
+- Update Okta SSO docs and custom SSO handler example - [PR #22786](https://github.com/BerriAI/litellm/pull/22786)
+- Add `LITELLM_MAX_BUDGET_PER_SESSION_TTL` to environment variables reference - [PR #23186](https://github.com/BerriAI/litellm/pull/23186)
+- Add DB query performance guidelines to `CLAUDE.md` - [PR #23196](https://github.com/BerriAI/litellm/pull/23196)
+- Add Gemini Vertex AI PayGo/priority cost tracking docs - [PR #22948](https://github.com/BerriAI/litellm/pull/22948)
+
+---
+
## New Contributors
* @ryanh-ai made their first contribution in [PR #21542](https://github.com/BerriAI/litellm/pull/21542)
@@ -359,14 +512,17 @@ No major secret manager changes in this release.
## Diff Summary
## 03/16/2026
-* New Providers: 5
+* New Providers: 7
* New Models / Updated Models: 116 new, 132 removed
-* LLM API Endpoints: 5
-* Management Endpoints / UI: 11
-* AI Integrations: 2
-* Performance / Reliability: 5
+* LLM API Endpoints: 37
+* Management Endpoints / UI: 31
+* AI Integrations: 8
+* MCP Gateway: 5
+* Spend Tracking, Budgets and Rate Limiting: 5
+* Performance / Loadbalancing / Reliability improvements: 9
* Security: 3
* Database / Proxy Operations: 2
+* Documentation Updates: 5
---
diff --git a/docs/my-website/sidebars-release-notes.js b/docs/my-website/sidebars-release-notes.js
new file mode 100644
index 00000000000..6ed29003ce1
--- /dev/null
+++ b/docs/my-website/sidebars-release-notes.js
@@ -0,0 +1,14 @@
+// @ts-check
+
+/** @type {import('@docusaurus/plugin-content-docs').SidebarsConfig} */
+const sidebars = {
+ releaseNotesSidebar: [
+ { type: 'doc', id: 'index', label: 'Release Notes' },
+ {
+ type: 'autogenerated',
+ dirName: '.',
+ },
+ ],
+};
+
+module.exports = sidebars;
diff --git a/docs/my-website/sidebars.js b/docs/my-website/sidebars.js
index 8888a7229da..a1faf231036 100644
--- a/docs/my-website/sidebars.js
+++ b/docs/my-website/sidebars.js
@@ -20,6 +20,7 @@ const sidebars = {
{
type: "category",
label: "Observability",
+ link: { type: "doc", id: "integrations/observability_index" },
items: [
{
type: "category",
@@ -29,61 +30,24 @@ const sidebars = {
type: "autogenerated",
dirName: "contribute_integration"
}
- ]
+ ],
},
{
type: "autogenerated",
dirName: "observability"
- }
+ },
],
},
{
type: "category",
- label: "Guardrails",
+ label: "Guardrail Providers",
+ link: {
+ type: "generated-index",
+ title: "Guardrail Providers",
+ description: "Add safety and content filtering to LLM calls",
+ slug: "/guardrail_providers"
+ },
items: [
- "proxy/guardrails/quick_start",
- "proxy/guardrails/team_based_guardrails",
- "proxy/guardrails/guardrail_load_balancing",
- "proxy/guardrails/test_playground",
- "proxy/guardrails/litellm_content_filter",
- "proxy/guardrails/realtime_guardrails",
- {
- type: "category",
- label: "Providers",
- items: [
- ...[
- "proxy/guardrails/qualifire",
- "proxy/guardrails/aim_security",
- "proxy/guardrails/onyx_security",
- "proxy/guardrails/aporia_api",
- "proxy/guardrails/azure_content_guardrail",
- "proxy/guardrails/bedrock",
- "proxy/guardrails/crowdstrike_aidr",
- "proxy/guardrails/enkryptai",
- "proxy/guardrails/ibm_guardrails",
- "proxy/guardrails/grayswan",
- "proxy/guardrails/hiddenlayer",
- "proxy/guardrails/lasso_security",
- "proxy/guardrails/guardrails_ai",
- "proxy/guardrails/lakera_ai",
- "proxy/guardrails/model_armor",
- "proxy/guardrails/noma_security",
- "proxy/guardrails/dynamoai",
- "proxy/guardrails/openai_moderation",
- "proxy/guardrails/pangea",
- "proxy/guardrails/pillar_security",
- "proxy/guardrails/pii_masking_v2",
- "proxy/guardrails/panw_prisma_airs",
- "proxy/guardrails/secret_detection",
- "proxy/guardrails/custom_guardrail",
- "proxy/guardrails/custom_code_guardrail",
- "proxy/guardrails/prompt_injection",
- "proxy/guardrails/tool_permission",
- "proxy/guardrails/zscaler_ai_guard",
- "proxy/guardrails/javelin"
- ].sort(),
- ],
- },
{
type: "category",
label: "Contributing to Guardrails",
@@ -93,16 +57,42 @@ const sidebars = {
"adding_provider/adding_guardrail_support",
]
},
- ],
- },
- {
- type: "category",
- label: "Policies",
- items: [
- "proxy/guardrails/guardrail_policies",
- "proxy/guardrails/policy_flow_builder",
- "proxy/guardrails/policy_templates",
- "proxy/guardrails/policy_tags",
+ {
+ type: "doc",
+ id: "proxy/guardrails/team_based_guardrails",
+ label: "Team Bring-Your-Own Guardrails",
+ },
+ ...[
+ "proxy/guardrails/qualifire",
+ "proxy/guardrails/aim_security",
+ "proxy/guardrails/onyx_security",
+ "proxy/guardrails/aporia_api",
+ "proxy/guardrails/azure_content_guardrail",
+ "proxy/guardrails/bedrock",
+ "proxy/guardrails/crowdstrike_aidr",
+ "proxy/guardrails/enkryptai",
+ "proxy/guardrails/ibm_guardrails",
+ "proxy/guardrails/grayswan",
+ "proxy/guardrails/hiddenlayer",
+ "proxy/guardrails/lasso_security",
+ "proxy/guardrails/guardrails_ai",
+ "proxy/guardrails/lakera_ai",
+ "proxy/guardrails/model_armor",
+ "proxy/guardrails/noma_security",
+ "proxy/guardrails/dynamoai",
+ "proxy/guardrails/openai_moderation",
+ "proxy/guardrails/pangea",
+ "proxy/guardrails/pillar_security",
+ "proxy/guardrails/pii_masking_v2",
+ "proxy/guardrails/panw_prisma_airs",
+ "proxy/guardrails/secret_detection",
+ "proxy/guardrails/custom_guardrail",
+ "proxy/guardrails/custom_code_guardrail",
+ "proxy/guardrails/prompt_injection",
+ "proxy/guardrails/tool_permission",
+ "proxy/guardrails/zscaler_ai_guard",
+ "proxy/guardrails/javelin"
+ ].sort(),
],
},
{
@@ -115,11 +105,6 @@ const sidebars = {
"proxy/pyroscope_profiling"
]
},
- {
- type: "doc",
- id: "integrations/websearch_interception",
- label: "Web Search Integration"
- },
{
type: "category",
label: "[Beta] Prompt Management",
@@ -140,7 +125,7 @@ const sidebars = {
},
{
type: "category",
- label: "AI Tools (OpenWebUI, Claude Code, etc.)",
+ label: "AI Tools",
link: {
type: "generated-index",
title: "AI Tools",
@@ -167,14 +152,13 @@ const sidebars = {
},
"tutorials/opencode_integration",
"tutorials/openclaw_integration",
- "tutorials/cost_tracking_coding",
"tutorials/cursor_integration",
"tutorials/github_copilot_integration",
"tutorials/litellm_gemini_cli",
- "tutorials/google_genai_sdk",
"tutorials/litellm_qwen_code_cli",
"tutorials/openai_codex",
- "tutorials/retool_assist"
+ "tutorials/retool_assist",
+ "tutorials/cost_tracking_coding"
]
},
{
@@ -191,7 +175,11 @@ const sidebars = {
"tutorials/claude_agent_sdk",
"tutorials/copilotkit_sdk",
"tutorials/google_adk",
+ "tutorials/google_genai_sdk",
"tutorials/livekit_xai_realtime",
+ "integrations/letta",
+ { type: "doc", id: "tutorials/instructor", label: "Instructor with LiteLLM" },
+ { type: "doc", id: "langchain/langchain", label: "LangChain with LiteLLM" },
"projects/openai-agents"
]
},
@@ -212,7 +200,20 @@ const sidebars = {
],
// But you can create a sidebar manually
tutorialSidebar: [
- { type: "doc", id: "index", label: "Getting Started" },
+ // ════════════════════════════════════════════════════════════
+ // GET STARTED
+ // ════════════════════════════════════════════════════════════
+ {
+ type: "category",
+ label: "Get Started",
+ collapsible: false,
+ collapsed: false,
+ items: [
+ { type: "doc", id: "index", label: "Quickstart" },
+ { type: "link", label: "Models & Pricing", href: "https://models.litellm.ai" },
+ { type: "link", label: "Changelog", href: "/release_notes" },
+ ],
+ },
{
type: "category",
@@ -280,11 +281,6 @@ const sidebars = {
},
"completion/token_usage",
"exception_mapping",
- {
- type: "category",
- label: "LangChain, LlamaIndex, Instructor",
- items: ["langchain/langchain", "tutorials/instructor"],
- }
],
},
{
@@ -297,16 +293,46 @@ const sidebars = {
slug: "/simple_proxy",
},
items: [
- "proxy/docker_quick_start",
+ { type: "doc", id: "proxy/docker_quick_start", label: "Getting Started Tutorial" },
{
- type: "link",
- label: "A2A Agent Gateway",
- href: "https://docs.litellm.ai/docs/a2a",
- },
- {
- type: "link",
- label: "MCP Gateway",
- href: "https://docs.litellm.ai/docs/mcp",
+ type: "category",
+ label: "Agent & MCP Gateway",
+ items: [
+ {
+ type: "category",
+ label: "A2A Agent Gateway",
+ items: [
+ "a2a",
+ "a2a_invoking_agents",
+ "a2a_agent_headers",
+ "a2a_cost_tracking",
+ "a2a_agent_permissions",
+ "a2a_iteration_budgets",
+ ],
+ },
+ {
+ type: "category",
+ label: "MCP Gateway",
+ items: [
+ "mcp",
+ "mcp_usage",
+ "mcp_openapi",
+ "mcp_oauth",
+ "mcp_aws_sigv4",
+ "mcp_zero_trust",
+ "mcp_public_internet",
+ "mcp_semantic_filter",
+ "mcp_control",
+ "mcp_cost",
+ "mcp_guardrail",
+ {
+ type: "link",
+ label: "MCP Troubleshooting Guide",
+ href: "/docs/mcp_troubleshoot"
+ },
+ ],
+ },
+ ],
},
{
"type": "category",
@@ -365,7 +391,11 @@ const sidebars = {
type: "category",
label: "Teams & Organizations",
items: [
- "proxy/access_control",
+ {
+ type: "link",
+ label: "Role-based Access Controls (RBAC) →",
+ href: "/docs/proxy/access_control"
+ },
"proxy/self_serve",
"proxy/public_teams",
"proxy/ui_project_management",
@@ -400,6 +430,7 @@ const sidebars = {
"proxy/architecture",
"proxy/multi_tenant_architecture",
"proxy/control_plane_and_data_plane",
+ "proxy/high_availability_control_plane",
"proxy/db_deadlocks",
"proxy/db_info",
"proxy/image_handling",
@@ -448,14 +479,40 @@ const sidebars = {
},
"proxy/caching",
{
- type: "link",
+ type: "category",
label: "Guardrails",
- href: "https://docs.litellm.ai/docs/proxy/guardrails/quick_start",
+ items: [
+ "proxy/guardrails/quick_start",
+ "proxy/guardrails/team_based_guardrails",
+ "proxy/guardrails/guardrail_load_balancing",
+ "proxy/guardrails/test_playground",
+ "proxy/guardrails/litellm_content_filter",
+ "proxy/guardrails/realtime_guardrails",
+ {
+ type: "link",
+ label: "Providers →",
+ href: "/docs/guardrail_providers",
+ },
+ {
+ type: "category",
+ label: "Contributing to Guardrails",
+ items: [
+ "adding_provider/generic_guardrail_api",
+ "adding_provider/simple_guardrail_tutorial",
+ "adding_provider/adding_guardrail_support",
+ ]
+ },
+ ],
},
{
- type: "link",
+ type: "category",
label: "Policies",
- href: "https://docs.litellm.ai/docs/proxy/guardrails/guardrail_policies",
+ items: [
+ "proxy/guardrails/guardrail_policies",
+ "proxy/guardrails/policy_flow_builder",
+ "proxy/guardrails/policy_templates",
+ "proxy/guardrails/policy_tags",
+ ],
},
{
type: "category",
@@ -528,6 +585,7 @@ const sidebars = {
label: "Spend Tracking",
items: [
"proxy/cost_tracking",
+ "tutorials/vertex_ai_pay_go",
"proxy/request_tags",
"proxy/custom_pricing",
"proxy/pricing_calculator",
@@ -551,16 +609,9 @@ const sidebars = {
},
items: [
{
- type: "category",
+ type: "link",
label: "/a2a - A2A Agent Gateway",
- items: [
- "a2a",
- "a2a_invoking_agents",
- "a2a_agent_headers",
- "a2a_cost_tracking",
- "a2a_agent_permissions",
- "a2a_iteration_budgets"
- ],
+ href: "/docs/a2a",
},
"assistants",
"audio_transcription",
@@ -637,6 +688,7 @@ const sidebars = {
"mcp_control",
"mcp_cost",
"mcp_guardrail",
+ "mcp_zero_trust",
"mcp_troubleshoot",
]
},
@@ -687,6 +739,7 @@ const sidebars = {
"proxy/realtime_webrtc",
"rerank",
"response_api",
+ "prompt_management",
"response_api_compact",
{
type: "category",
@@ -797,6 +850,7 @@ const sidebars = {
items: [
"providers/gemini",
"providers/gemini/videos",
+ "providers/gemini/music",
"providers/google_ai_studio/files",
"providers/google_ai_studio/image_gen",
"providers/google_ai_studio/realtime",
@@ -974,51 +1028,14 @@ const sidebars = {
"providers/zai",
],
},
- {
- type: "category",
- label: "Guides",
- items: [
- "budget_manager",
- "completion/computer_use",
- "completion/web_search",
- "completion/web_fetch",
- "completion/function_call",
- "completion/audio",
- "completion/document_understanding",
- "completion/drop_params",
- "completion/image_generation_chat",
- "completion/json_mode",
- "completion/knowledgebase",
- "providers/anthropic_tool_search",
- "guides/code_interpreter",
- "completion/message_trimming",
- "completion/message_sanitization",
- "completion/model_alias",
- "completion/mock_requests",
- "completion/predict_outputs",
- "completion/prefix",
- "completion/prompt_caching",
- "completion/prompt_formatting",
- "completion/reliable_completions",
- "completion/stream",
- "completion/provider_specific_params",
- "completion/vision",
- "exception_mapping",
- "completion/batching",
- "guides/finetuned_models",
- "guides/security_settings",
- "proxy/veo_video_generation",
- "reasoning_content",
- "extras/creating_adapters",
- ]
- },
+
{
type: "category",
- label: "Routing, Loadbalancing & Fallbacks",
+ label: "Routing & Load Balancing",
link: {
type: "generated-index",
- title: "Routing, Loadbalancing & Fallbacks",
+ title: "Routing & Load Balancing",
description: "Learn how to load balance, route, and set fallbacks for your LLM requests",
slug: "/routing-load-balancing",
},
@@ -1046,43 +1063,6 @@ const sidebars = {
"load_test_rpm",
]
},
- {
- type: "category",
- label: "Tutorials",
- items: [
- {
- type: "link",
- label: "AI Coding Tools (OpenWebUI, Claude Code, Gemini CLI, OpenAI Codex, etc.)",
- href: "/docs/ai_tools",
- },
- "tutorials/anthropic_file_usage",
- "tutorials/default_team_self_serve",
- "tutorials/msft_sso",
- "tutorials/prompt_caching",
- "tutorials/tag_management",
- 'tutorials/litellm_proxy_aporia',
- "tutorials/presidio_pii_masking",
- "tutorials/elasticsearch_logging",
- "tutorials/gemini_realtime_with_audio",
- "tutorials/claude_code_beta_headers",
- {
- type: "category",
- label: "LiteLLM Python SDK Tutorials",
- items: [
- 'tutorials/azure_openai',
- 'tutorials/instructor',
- "tutorials/gradio_integration",
- "tutorials/huggingface_codellama",
- "tutorials/huggingface_tutorial",
- "tutorials/TogetherAI_liteLLM",
- "tutorials/finetuned_chat_gpt",
- "tutorials/text_completion",
- "tutorials/first_playground",
- "tutorials/model_fallbacks",
- ],
- },
- ]
- },
{
type: "category",
label: "Contributing",
@@ -1140,12 +1120,11 @@ const sidebars = {
"projects/Codium PR Agent",
"projects/Prompt2Model",
"projects/SalesGPT",
+ "projects/Softgen",
"projects/Quivr",
"projects/Langstream",
"projects/Otter",
- "projects/GPT Migrate",
"projects/YiVal",
- "projects/LiteLLM Proxy",
"projects/llm_cord",
"projects/pgai",
"projects/GPTLocalhost",
@@ -1183,23 +1162,310 @@ const sidebars = {
"troubleshoot",
],
},
+ ],
+};
+
+const learnSidebar = {
+ learnSidebar: [
+ // ── Landing page ──────────────────────────────────────────────────
+ { type: "doc", id: "learn/index", label: "Learn" },
{
type: "category",
- label: "Blog",
+ label: "Start Here",
+ collapsible: true,
+ collapsed: false,
+ items: [
+ "learn/sdk_quickstart",
+ "learn/gateway_quickstart",
+ ],
+ },
+
+ // ── Guides ────────────────────────────────────────────────────────
+ {
+ type: "category",
+ label: "Guides",
+ collapsible: true,
+ collapsed: false,
+ link: { type: "doc", id: "guides/index" },
items: [
{
- type: "link",
- label: "Day 0 Support: Claude Sonnet 4.6",
- href: "/blog/claude_sonnet_4_6",
+ type: "category",
+ label: "Core Requests",
+ collapsible: true,
+ collapsed: false,
+ link: {
+ type: "generated-index",
+ title: "Core Requests",
+ description: "Streaming, batching, structured outputs, and reasoning behavior",
+ slug: "/guides/core_request_response_patterns"
+ },
+ items: [
+ "completion/stream",
+ "completion/batching",
+ "completion/json_mode",
+ "reasoning_content",
+ ],
+ },
+ {
+ type: "category",
+ label: "Tool Calling",
+ collapsible: true,
+ collapsed: true,
+ link: {
+ type: "generated-index",
+ title: "Tool Calling",
+ description: "Function calling, web tools, interception patterns, computer use, code interpreter, and tool-call hygiene",
+ slug: "/guides/tools_integrations"
+ },
+ items: [
+ "completion/function_call",
+ "completion/web_search",
+ {
+ type: "doc",
+ id: "integrations/websearch_interception",
+ label: "Web Search Interception",
+ },
+ "completion/web_fetch",
+ "completion/computer_use",
+ "guides/code_interpreter",
+ "completion/message_sanitization",
+ ],
+ },
+ {
+ type: "category",
+ label: "Multimodal I/O",
+ collapsible: true,
+ collapsed: true,
+ link: {
+ type: "generated-index",
+ title: "Multimodal I/O",
+ description: "Vision, audio, PDFs, image generation, and video generation",
+ slug: "/guides/multimodal_io"
+ },
+ items: [
+ "completion/vision",
+ "completion/audio",
+ "completion/document_understanding",
+ "completion/image_generation_chat",
+ "proxy/veo_video_generation",
+ ],
+ },
+ {
+ type: "category",
+ label: "Retrieval & Knowledge",
+ collapsible: true,
+ collapsed: true,
+ link: {
+ type: "generated-index",
+ title: "Retrieval & Knowledge",
+ description: "Vector stores, file search, citations, and knowledge-base routing",
+ slug: "/guides/retrieval_knowledge"
+ },
+ items: [
+ "completion/knowledgebase",
+ ],
+ },
+ {
+ type: "category",
+ label: "Prompts & Context",
+ collapsible: true,
+ collapsed: true,
+ link: {
+ type: "generated-index",
+ title: "Prompts & Context",
+ description: "Prompt caching, trimming, formatting, assistant prefill, and predicted outputs",
+ slug: "/guides/prompts_context"
+ },
+ items: [
+ "completion/prefix",
+ "completion/predict_outputs",
+ "completion/message_trimming",
+ "completion/prompt_caching",
+ "completion/prompt_formatting",
+ ],
+ },
+ {
+ type: "category",
+ label: "Compatibility & Extensibility",
+ collapsible: true,
+ collapsed: true,
+ link: {
+ type: "generated-index",
+ title: "Compatibility & Extensibility",
+ description: "Provider-specific params, model aliases, fine-tuned models, and adapters",
+ slug: "/guides/compatibility_extensibility"
+ },
+ items: [
+ "completion/provider_specific_params",
+ "completion/drop_params",
+ "completion/model_alias",
+ "guides/finetuned_models",
+ "extras/creating_adapters",
+ ],
+ },
+ {
+ type: "category",
+ label: "Reliability, Testing & Spend",
+ collapsible: true,
+ collapsed: true,
+ link: {
+ type: "generated-index",
+ title: "Reliability, Testing & Spend",
+ description: "Retries, fallbacks, mock responses, and budget controls",
+ slug: "/guides/reliability_testing_spend"
+ },
+ items: [
+ "completion/mock_requests",
+ "completion/reliable_completions",
+ "budget_manager",
+ ],
+ },
+ {
+ type: "category",
+ label: "Security & Network",
+ collapsible: true,
+ collapsed: true,
+ link: {
+ type: "generated-index",
+ title: "Security & Network",
+ description: "SSL, custom CA bundles, HTTP proxy settings, and per-service verification",
+ slug: "/guides/security_network"
+ },
+ items: [
+ "guides/security_settings",
+ ],
+ },
+ ],
+ },
+
+ // ── Tutorials ─────────────────────────────────────────────────────
+ {
+ type: "category",
+ label: "Tutorials",
+ collapsible: true,
+ collapsed: false,
+ link: { type: "doc", id: "tutorials/index" },
+ items: [
+ {
+ type: "category",
+ label: "Getting Started",
+ collapsed: false,
+ link: {
+ type: "generated-index",
+ title: "Getting Started",
+ description: "Installation, playground, text completion, and mock completions",
+ slug: "/tutorials/getting_started"
+ },
+ items: [
+ "tutorials/installation",
+ "tutorials/first_playground",
+ "tutorials/text_completion",
+ "tutorials/mock_completion",
+ ],
},
{
type: "link",
- label: "Incident: Broken Model Cost Map",
- href: "/blog/model-cost-map-incident",
+ label: "Agent SDKs & Frameworks",
+ href: "/docs/agent_sdks",
+ },
+ {
+ type: "link",
+ label: "AI Coding Tools",
+ href: "/docs/ai_tools",
+ },
+ {
+ type: "category",
+ label: "Python SDK",
+ collapsed: true,
+ link: {
+ type: "generated-index",
+ title: "Python SDK",
+ description: "Tutorials using only the Python SDK — no proxy server required",
+ slug: "/tutorials/python_sdk"
+ },
+ items: [
+ "tutorials/gradio_integration",
+ "tutorials/provider_specific_params",
+ "tutorials/model_fallbacks",
+ "tutorials/fallbacks",
+ ],
+ },
+ {
+ type: "category",
+ label: "Provider Setup",
+ collapsed: true,
+ link: {
+ type: "generated-index",
+ title: "Provider Setup",
+ description: "Connect LiteLLM to Azure OpenAI, HuggingFace, TogetherAI, local models, and more",
+ slug: "/tutorials/provider_tutorials"
+ },
+ items: [
+ "tutorials/azure_openai",
+ "tutorials/TogetherAI_liteLLM",
+ "tutorials/huggingface_tutorial",
+ "tutorials/huggingface_codellama",
+ "tutorials/finetuned_chat_gpt",
+ "tutorials/oobabooga",
+ ],
+ },
+ {
+ type: "category",
+ label: "Proxy: Admin & Access",
+ collapsed: true,
+ link: {
+ type: "generated-index",
+ title: "Proxy: Admin & Access",
+ description: "User and team management, SSO, SCIM, and routing rules",
+ slug: "/tutorials/proxy_admin_access"
+ },
+ items: [
+ "tutorials/default_team_self_serve",
+ "tutorials/msft_sso",
+ "tutorials/scim_litellm",
+ "tutorials/tag_management",
+ ],
+ },
+ {
+ type: "category",
+ label: "Proxy: Features & Safety",
+ collapsed: true,
+ link: {
+ type: "generated-index",
+ title: "Proxy: Features & Safety",
+ description: "Prompt caching, passthrough APIs, realtime, guardrails, and PII masking",
+ slug: "/tutorials/proxy_features_safety"
+ },
+ items: [
+ "tutorials/prompt_caching",
+ "tutorials/file_search_responses_api",
+ "tutorials/anthropic_file_usage",
+ "tutorials/gemini_realtime_with_audio",
+ "tutorials/litellm_proxy_aporia",
+ "tutorials/presidio_pii_masking",
+ ],
+ },
+ {
+ type: "category",
+ label: "Observability & Evaluation",
+ collapsed: true,
+ link: {
+ type: "generated-index",
+ title: "Observability & Evaluation",
+ description: "Logging, monitoring, benchmarking, and evaluation suites",
+ slug: "/tutorials/observability_evaluation"
+ },
+ items: [
+ "tutorials/elasticsearch_logging",
+ "tutorials/compare_llms",
+ "tutorials/litellm_Test_Multiple_Providers",
+ "tutorials/eval_suites",
+ "tutorials/lm_evaluation_harness",
+ ],
},
],
},
],
};
-module.exports = sidebars;
+module.exports = { ...sidebars, ...learnSidebar };
diff --git a/docs/my-website/src/components/ControlPlaneArchitecture/ControlPlaneArchitecture.tsx b/docs/my-website/src/components/ControlPlaneArchitecture/ControlPlaneArchitecture.tsx
new file mode 100644
index 00000000000..5cc41979b02
--- /dev/null
+++ b/docs/my-website/src/components/ControlPlaneArchitecture/ControlPlaneArchitecture.tsx
@@ -0,0 +1,95 @@
+import React from 'react';
+import styles from './styles.module.css';
+
+/* ────────────────────── Shared small pieces ────────────────────── */
+
+function InfraChip({ color, label }: { color: string; label: string }) {
+ const dotClass =
+ color === 'green'
+ ? styles.infraDotGreen
+ : color === 'blue'
+ ? styles.infraDotBlue
+ : styles.infraDotOrange;
+
+ return (
+
+
+ {label}
+
+ );
+}
+
+/* ────────────────────── Architecture tab ────────────────────── */
+
+function ArchitectureView() {
+ return (
+
+ {/* User */}
+
+
👤
+ Admin
+
+
+
+
+ {/* Control Plane */}
+
+
+ Control Plane
+ UI
+
+
cp.example.com
+
+
+
+
+
+
+
+ {/* Branch connector */}
+
+
+
+
+
+ {/* Workers */}
+
+
+
+ Worker A
+ US East
+
+
worker-a.example.com
+
+
+
+
+
+
+
+
+
+ Worker B
+ EU West
+
+
worker-b.example.com
+
+
+
+
+
+
+
+
+ );
+}
+
+/* ────────────────────── Main component ────────────────────── */
+
+export default function ControlPlaneArchitecture() {
+ return (
+