Skip to content

Cohere: Rerank v3.5 provider comparison

cohere/rerank-v3.5

Rerank v3.5 is designed to reorder search results for improved relevance. It supports multi-aspect and semi-structured data reranking over 100+ languages. Ideal for refining results from semantic or keyword search...

Endpoints:
1
Context:
4.1K
Input:
text
Output:
rerank

Visual comparison

Endpoint pricing chart

Compare published endpoint pricing visually.

Effective price by endpoint

USD per unit for prompt. Lower is better.

Only directly comparable published units are charted.

Server-rendered comparison

Provider endpoints

Prices are shown only in the units published by OpenRouter; cross-unit rankings are intentionally omitted. Missing speed data never removes an endpoint.

Endpoint comparison for Cohere: Rerank v3.5
Provider / routeCurrent pricingSpeed measurementsEndpoint details
Provider / route
Coherecohere
Current pricing
  • Free per unit (prompt)
  • Free per unit (completion)
Speed measurements
500-token response
Not applicable
Response starts
Insufficient recent data
Output speed
Insufficient recent data
Endpoint details
Uptime (30 min)
100.00%
Context
4.1K
Model format
unknown
Max output
N/a
10 parameters

frequency_penalty, max_tokens, presence_penalty, response_format, seed, stop, structured_outputs, temperature, top_k, top_p

Endpoint data fetched .

Rerank v3.5 deployment guide

How to choose a Rerank v3.5 inference provider

Rerank v3.5 is indexed here as a reranking model by Cohere, with 1 provider endpoint from Cohere. The comparison preserves each exact OpenRouter routing tag so pricing and performance observations can be connected to the route an application would actually request.

Match the endpoint to the workload

The model publishes a 4.1K-token context window. It accepts text input and returns rerank output. 10 distinct supported parameters appear across the listed routes. Confirm limits on the specific endpoint rather than assuming every host exposes the same configuration.

Compare reranking billing units directly

At least one unit is published consistently across the listed endpoints, allowing a direct price chart for prompt. Other charges remain in the table using OpenRouter’s exact billing labels.

Verify route format and availability

Published endpoint formats include unknown. Availability, rate limits, and regional support can change independently of catalog pricing, so confirm the selected routing tag before production deployment.