Rerank Text (BGE)

How it fits

Typical backends

Caveats

• I/O contractEach RerankResult keeps the document's position in the original RerankInput document list as its index, preserved across the sort and any truncation, so downstream consumers can map results back to inputs.
• FallbackAn empty query or an empty document list returns an empty [RerankResult] with no error rather than failing the message.
• Parameter interactiontop_k zero keeps every reranked document; a positive value truncates to that many after the descending sort, so it only ever drops the lowest-scoring tail.
• Hard constraintThe checkpoint named by hf_model_id must be a cross-encoder reranker; a bi-encoder or other architecture loads but produces meaningless scores. A gated or private repo additionally needs an access token via hf_token.
• AccuracyScores rank relevance within a single invocation and are not calibrated for comparison across separate queries.
• State lifetimeThe model, device and all configuration are captured once at startup; the model is loaded once and reused across messages, and changing any setting requires a redeploy.