Request fields
Candidates keep the order you sent them in. Every result names its candidate by
index, the position in the array you supplied, so you can join the scores back onto your own records without matching on text.
Response
The values below are an example, not a measurement.
Candidate limits
A single call scores at most 100 candidates. The deployment serving the request also carries its own verified batch limit, and the lower of the two applies. Over either limit the call fails withrerank_document_limit_exceeded, and the message names the limit that was hit. Split a larger candidate set across calls and merge the ranked lists yourself.
Retries
Send anIdempotency-Key and a retried call replays the stored result instead of scoring again, so a lost response never costs a second run. See Idempotent retries for the header rules and the replay headers.
Billing
Reranking bills on the terms of the deployment serving it.Errors
Failures use the same OpenAI-style error envelope as every other/v1 operation. These codes are specific to this endpoint.
A
404 model_not_found means the id in model is not a model this key can reach. Deploy the model in your workspace, then call GET /v1/models to confirm the id before retrying.
Related
Embeddings
Produce the vectors your first-stage search retrieves before this call reorders them.
Models
Discover the model ids your key can reach.
Errors
Handle validation, availability, and rate-limit failures.