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 pipelines.
Modalities
Price
$0.001/search
Context
4K
Released
Apr 5, 2026
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 pipelines.
Rerank v3.5 costs $0.001/search.
Rerank v3.5 accepts up to 4,096 tokens per query and document. Longer text has to be split into multiple documents.
Rerank v3.5 accepts text as input and returns relevance-ranked documents.
Rerank 4 Pro and Rerank 4 Fast are other reranking models from Cohere.
Rerank v3.5 was released on April 5, 2026.
This model is hosted by one provider. OpenRouter forwards every request to it directly — no routing decisions to make.
The average price customers actually pay for this model, next to the prices providers post. Caching and discounts mean the price actually paid is often well below the listed one.
Throughput is how fast the model writes (tokens per second — higher is better). Latency is total round-trip time (lower is better). TTFT is time-to-first-token — how long before you see anything appear (lower is better).
Uptime is the percentage of the past 3 days that at least one provider was responding to requests. Availability is the percentage of time that inference was successfully served. OpenRouter continuously monitors and uses the next-best provider when one returns an error.
Public apps that send the most traffic to this model. Good signal for what real production workloads look like — and a hint at which use cases this model is best suited for.
Token volume and request traffic to this model over time.
Drop-in code to call this model. OpenRouter's API is OpenAI-compatible — most SDKs work by just swapping the base URL. The only thing that changes between models is the model slug below.
| $0.001 | -- | -- |
100.00%
99.99%
When an error occurs in an upstream provider, we can recover by routing to another healthy provider, if your request filters allow it. You can access per-provider uptime data programmatically through the Endpoints API. Learn more about our load balancing and customization options.