Loading the catalogue…
Loading the catalogue…
Qwen’s open-weight model for scoring query-document relevance and reranking text results.
Overview. Qwen3-Reranker-4B is an open-weight text-ranking model from Qwen, built to score the relevance of query-document pairs. Developers can use it to rerank candidate documents for search or retrieval workflows.
Key strengths. The model is supervised-trained for reranking and supports instructions tailored to the ranking task. No benchmark results are available here to quantify its ranking quality.
When to use it. Use this model to score and reorder candidate documents against a query in a text retrieval pipeline. Its published sequence length is 32K tokens, which can accommodate longer query-document inputs.
Limitations. No benchmark, latency, or throughput data is available here, so ranking quality and serving speed cannot be characterized. Qwen publishes a 32K sequence length, while the model configuration lists 40,960 maximum position embeddings; no training cutoff or completion-token limit is specified.
Sovereignty note. Qwen is the model creator, and the weights are released under Apache-2.0. Creator-country, CLOUD Act exposure, training-on-input policy, and endpoint data residency are not established by the available findings, so Sovereign status cannot be confirmed.
| Inference Provider | Sovereignty | Runs in | Price | Status | Pin |
|---|---|---|---|---|---|
| L3 | — | Online | |||
| L1 | €0.05 per 1M input tokens | Online |
10 use cases classified by the curator. The note says why.
Dedicated reranker model at a 4B parameter scale (per model name), purpose-built to score query-document relevance as a second-stage ranker. Its core function matches this use case directly, though the card publishes no benchmark scores to rank it against alternatives.
Can rank retrieved passages by relevance to a question before they reach a downstream reader, improving the evidence set for document Q&A. It does not generate answers, so it cannot serve as the answering model on its own.
Relevance reranking over retrieved policy passages can improve the precision of the context supplied to a generator. The model contributes retrieval quality only and produces no answer text.
A cross-encoder style reranker refines candidates returned by a first-stage retriever rather than performing retrieval itself. It is suitable as the rescoring layer in a semantic search pipeline, not as a standalone search component.
As a reranker it outputs relevance scores rather than generated text, and the card lists no generative capability. It lacks the core function this use case requires.
Pairwise relevance scoring can be loosely repurposed for binary routing decisions, but the model is not designed or documented for general classification. Dedicated classifiers or instruction-tuned generative models would be stronger choices.
No text-generation capability is flagged and the model is a scoring component, so it cannot produce long-form output. This use case is outside its design.
Scoring-only architecture with no text-generation capability, so it cannot produce rewritten queries. A generative model is required for this use case.
Reranker architecture produces relevance scores, not natural-language summaries, and no generative capability is listed. Summarisation requires a generative model.
No tool-calling or agentic capability is flagged, and the model's output is relevance scores rather than actions or structured calls. It is unsuited to orchestration roles.
Sourced numbers, not our own evaluations. Percentiles are against the rerank models on Stav.
No benchmark source yet
curl https://api.stav.ai/v1/rerank \
-H "Authorization: Bearer $STAV_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "qwen/qwen3-reranker-4b",
"query": "Which provider hosts in Norway?",
"documents": ["Green Mountain is in Stavanger.", "Paris is in France."],
"top_n": 1}'→ X-Stav-Request-Id · X-Stav-Model · X-Stav-Provider → X-Stav-Sovereignty-Level — the rung the request was served at