A second pass for relevance
Five rerank records cover up to 100 candidate documents, returning original input indexes and model-specific scores.
A topic from the capability archive
This note explains the design being adapted. It does not announce a shipped Noemad API, a verified model deployment, or a currently available promotion.
The subject
Five rerank records cover up to 100 candidate documents, returning original input indexes and model-specific scores.
What this means for Noemad
A smaller top_n changes the response size, not the submitted candidates billed. Validate multilingual retrieval with representative queries before enabling a paid profile.
Before this can go live
- Implement the contract behind the relevant frontend controls.
- Validate ownership, limits, failure recovery, and the exact provider configuration.
- Publish authoritative availability and customer terms before accepting any payment.
- Keep request, payment, usage, and result records linked to one logical operation.
What you can explore now
The interface includes the corresponding documentation and navigation. Local samples stay clearly marked, and no service availability or account balance is inferred from a static catalog.
Explore the related reference