Nemotron-3.5-Rerank-8B-BF16 API

What is Nemotron-3.5-Rerank-8B-BF16?

Use the public identifier di-nvidianemotron-35-rerank-8b-bf16-2752e71a5e for Nemotron-3.5-Rerank-8B-BF16 in ServerNet. The gateway uses this identifier to select the configured route; the developer is nvidia.

Where to use Nemotron-3.5-Rerank-8B-BF16

• Rerank the candidates from your search index with Nemotron-3.5-Rerank-8B-BF16.
• Place the most relevant passages first in a retrieval augmented generation workflow.
• Compare ranking quality and added latency on representative queries before using Nemotron-3.5-Rerank-8B-BF16 for every search.

Build your integration

Send query and documents to /v1/rerank, then order candidates by their relevance scores. Retrieve a shortlist first so the reranker sees only documents worth comparing.

Inputs and service limits

Use text queries and up to 128 text documents. The query is paired with each candidate, so adding long documents increases input consumption. Media and unsupported native parameters are not forwarded.

A request cost example

For 1,000 input tokens and 0 output tokens, without a cache discount. This is a catalogue estimate, not a fixed request fee. Reported consumption and the price frozen for your request determine the usage amount.

Estimated usage, Toman

15

Connect to Nemotron-3.5-Rerank-8B-BF16 API

Enable ai:rerank on your key and ai:models:read to check availability. Set SERVERNET_API_KEY in your server environment. Change the idempotency key for each new request; keep it unchanged only for an identical retry.

curl https://servernet.cloud/v1/rerank \
  -H "Authorization: Bearer $SERVERNET_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: CHANGE_FOR_EACH_NEW_REQUEST' \
  -d '{
    "model": "di-nvidianemotron-35-rerank-8b-bf16-2752e71a5e",
    "query": "What is the capital of Iran?",
    "documents": [
        "Tehran is the capital of Iran.",
        "Paris is the capital of France."
    ]
}'

Use the same Idempotency-Key when retrying an identical request. Successful responses are replayed without a second charge for 24 hours. Do not automatically retry when x-should-retry:false is present. The key is shown once. Store it in a server environment variable. Keep it out of browser code, GitHub and logs.

Compare models for the same task