Loading the catalogue…
Loading the catalogue…
A multilingual BAAI text-pair reranker that scores query–passage relevance for retrieval pipelines.
Overview. BAAI/bge-reranker-v2-m3 is an open-weight, 568M-parameter multilingual text-pair reranker built on XLM-RoBERTa. It accepts a query and passage, then returns a scalar relevance score. Developers can use it to reorder retrieved candidates before presenting results to a user or downstream model.
Key strengths. Its core strength is focused relevance scoring rather than text generation. The XLM-RoBERTa architecture and multilingual design make it suitable for ranking query-and-passage pairs across languages, while its 8,192-token tokenizer limit supports comparatively long text pairs.
When to use it. Use this for retrieval reranking when you already have a candidate set and need to score query–passage relevance. It fits ranking pipelines where a non-generative model is preferable to a general-purpose model. It is not intended for chat or text generation, and the supplied findings do not establish support for tool calling, structured output, or native document, image, or audio processing.
Limitations. This model returns a scalar relevance score rather than generated text; the supplied findings do not establish support for reasoning, tool calls, or structured JSON output. No latency measurements, domain-specific benchmark scores, or training-data cutoff are available in the supplied findings.
Sovereignty note. BAAI is the creator, and the supplied findings do not establish a CLOUD Act exposure classification or endpoint data residency. The model is available under the Apache-2.0 licence, but no Sovereign residency claim is verified.
| Inference Provider | Sovereignty | Runs in | Price | Status | Pin |
|---|---|---|---|---|---|
| L1 | €0.10 per 1M input tokens | Online |
13 use cases classified by the curator. The note says why.
Cross-encoder reranker (~568M params, 8192-token context) built for scoring query-passage relevance in retrieval pipelines, with multilingual coverage from the v2-m3 line. This is its primary designed function.
Used as the second-stage scorer over candidates from a separate embedding retriever, not as a standalone retriever. It improves precision for semantic search but cannot retrieve from a full corpus alone.
Relevance scoring can match incoming queries against candidate intent or route descriptions without generation. Works best as a lightweight matcher over a fixed label set.
Scores and orders passages but does not generate text. It can supply high-relevance context to a generator but cannot produce answers itself.
Produces a relevance score for query-document pairs rather than trained class labels. Adapting it to general classification would require reformulating the task as pairwise scoring.
Not a code-generation model. It can rank code snippets for retrieval but cannot complete code.
Ranks document passages against a question but does not extract or compose answers. Pair it with a generative or extractive reader for end-to-end Q&A.
Text-only model with no vision encoder, so it cannot process images.
No autoregressive decoding; the model outputs relevance scores, not prose.
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": "baai/bge-reranker-v2-m3",
"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