Skip to content

docs: add native GPUStack embedding and rerank provider - #911

Open
qdivan wants to merge 1 commit into
BerriAI:mainfrom
qdivan:docs_gpustack_provider
Open

docs: add native GPUStack embedding and rerank provider#911
qdivan wants to merge 1 commit into
BerriAI:mainfrom
qdivan:docs_gpustack_provider

Conversation

@qdivan

@qdivan qdivan commented Aug 17, 2026

Copy link
Copy Markdown

Summary

Documents the native GPUStack embedding and rerank provider added by BerriAI/litellm#37138.

  • documents the gpustack/ provider route
  • documents GPUSTACK_API_BASE and GPUSTACK_API_KEY
  • adds Python SDK examples for embeddings and rerank
  • adds LiteLLM Proxy configuration and curl examples
  • explains accepted API base forms

Duplicate check

Related docs PR #629 covers configuring GPUStack chat models through the generic Custom OpenAI provider and currently describes gpustack/v1, which is not a native LiteLLM provider route. This PR has a different acceptance boundary: it documents the native gpustack/<model> embedding and rerank routes implemented by BerriAI/litellm#37138 and does not claim native chat support.

Validation

The page includes the exact environment variables required by LiteLLM's tests/documentation_tests/test_env_keys.py gate.

@vercel

vercel Bot commented Aug 17, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
litellm Ready Ready Preview Aug 17, 2026 7:28am

Request Review

@qdivan

qdivan commented Aug 17, 2026

Copy link
Copy Markdown
Author

This docs PR is now the remaining documentation dependency for BerriAI/litellm#37138

The code PR's current head has passed its lint, strict Ruff, type-discipline, full basedpyright, tests, and benchmarks. Its two remaining failures run LiteLLM's environment-key documentation test against the default docs branch, so they cannot turn green until this docs page lands

I also ran the official tests/documentation_tests/test_env_keys.py locally with this exact docs branch paired with the code head; it passes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant