Skip to main content
Reranker models take a query and a list of candidate documents and return a relevance score for each document. They’re typically used as a second-pass filter after an initial vector search to improve retrieval quality in RAG pipelines. Browse all reranker models.

Endpoint

Example

Response

Scores are in the same order as the input documents, and a higher score means a more relevant document. Sort by score descending to get the most relevant documents first. What a score means depends on the model: Compare scores only within one model. A cutoff tuned on one reranker (for example, keep documents scoring above 0.5) does not carry over to another. queries and documents must be the same length, except that a single query is broadcast across many documents (the common case shown above). The Qwen3 rerankers take an optional instruction field that steers the reranking task; it defaults to "Given a web search query, retrieve relevant passages that answer the query". Other models ignore it.

Usage in a RAG pipeline

A typical pattern:
  1. Retrieve — run a vector similarity search to fetch the top-N candidate chunks (e.g. top 50)
  2. Rerank — pass the query + candidates to a reranker to get relevance scores
  3. Select — keep only the top-K highest-scoring chunks (e.g. top 5) for the LLM context
This two-stage approach improves precision significantly compared to embedding similarity alone.

Available models

Browse all reranker models.