[GH-ISSUE #22698] feat: Expose Reranking via API Endpoint like /v1/rerank #58459

New Issue

GiteaMirror · 2026-05-05T23:12:31-05:00

GiteaMirror commented

2026-05-05 23:12:31 -05:00

Originally created by @JKratto on GitHub (Mar 15, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22698

Check Existing Issues

I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

Currently, Open WebUI allows the configuration and use of reranking models within the internal RAG. However, unlike embeddings and chat completions, there is no public API endpoint to access the configured reranker externally. While the model appears in the model list, it cannot be called through Open WebUI API.

Desired Solution you'd like

I would like to see a dedicated API endpoint (e.g., /v1/rerank or /api/rerank) that follows the de facto industry standard used by Cohere, vLLM etc. This would allow external tools and scripts to utilize the reranking models already configured in Open WebUI.

A similar gap was previously addressed for the embedding API (see #8719), and adding reranking support would improve the feature set for using Open WebUI as a unified model provider.

Alternatives Considered

Currently, the only way to use reranking is to proxy the API endpoint directly to the backend, bypassing Open WebUI.

Additional Context

No response

Originally created by @JKratto on GitHub (Mar 15, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22698 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description Currently, Open WebUI allows the configuration and use of reranking models within the internal RAG. However, unlike embeddings and chat completions, there is no public API endpoint to access the configured reranker externally. While the model appears in the model list, it cannot be called through Open WebUI API. ### Desired Solution you'd like I would like to see a dedicated API endpoint (e.g., /v1/rerank or /api/rerank) that follows the de facto industry standard used by Cohere, vLLM etc. This would allow external tools and scripts to utilize the reranking models already configured in Open WebUI. A similar gap was previously addressed for the embedding API (see #8719), and adding reranking support would improve the feature set for using Open WebUI as a unified model provider. ### Alternatives Considered Currently, the only way to use reranking is to proxy the API endpoint directly to the backend, bypassing Open WebUI. ### Additional Context _No response_

GiteaMirror closed this issue

2026-05-05 23:12:33 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#58459