Repository navigation
When will reranker support (/v1/rerank) be available? #5301
Replies: 1 comment
|
Here is the current state and path forward for 1. Roadmap status & core supportReranker support is tracked as a desired capability (originally requested in #936). Currently on 2. PR direction: why a clean, scoped PR is needed
3. Provider scopeThe standard Cohere/Jina/Voyage rerank wire schema ( |
Uh oh!
There was an error while loading. Please reload this page.
Reranking is the one piece missing from using 9router as a single endpoint for a RAG-style pipeline (embeddings → rerank → chat). Before planning around it, I wanted to ask about direction and timing. This is not a new feature request — #936 has tracked it since May 2026 — but the two PRs that implement it are both stalled, so it is hard to tell where this is going.
What I can see in
mastertoday: there is no rerank handler or executor. The only occurrence of "rerank" is inopen-sse/providers/visionPatterns.js, which excludesrerank-*model ids from vision routing, so those models currently have no endpoint to call at all.The open work:
rerankCore.jsandPOST /v1/rerankfor Cohere/Jina/Voyage-style providers. It has had no activity since the day it was opened and now conflicts withmaster./v1/rerank, but scoped tonan/rerankonly.My questions:
masterbe welcome from the community?Not looking for a hard commitment. An indication of whether this is on the roadmap and which PR path you want is enough for me to decide whether to build around the missing endpoint or wait for it.
All reactions