Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Cohere / Rerank

Rerank 4 Pro

Document reranking variant focused on retrieval relevance.

availableClosed weightsReranking
Official documentation (opens in a new tab)Reviewed 14 Oct 2026
11 of 23 specification fields collected
Context window32.8K32,768 tokens
Maximum outputNot collectedAwaiting source review
Input billingNot collectedCohere API
Output billingNot collectedNo inferred price

Specifications

Provider-documented facts. “Not collected” means we have not verified that field yet, not that the feature is unsupported.

Context / input limit
32,768 tokensSource for Context / input limit (opens in a new tab)

Per query/document pair. Long documents may be chunked; this is not a chat-generation context window.

Maximum output
Not collected
Output modalities
Relevance scoresSource for Output modalities (opens in a new tab)
Reasoning
Not collected
Tool calling
Not collected
Structured output
Not collected
Streaming
Not collected
Batch processing
Not collected
Fine-tuning
Not collected
Knowledge cutoff
Not collected
Release date
Not collected
Parameters
Not collected
Architecture
Not collected
Languages
100+ languagesSource for Languages (opens in a new tab)

Provider-reported language coverage; performance varies by language and task.

Context caching
Not collected

See endpoint caching records. No verified support claim for this model.

Query token limit
16,384Source for Query token limit (opens in a new tab)

Longer queries are truncated to this token count; query and document share the model context window.

Ranking results
Ordered document indexes and relevance scores from 0 to 1. Scores are query dependent; compare rank rather than interpreting scores as calibrated probabilities.Source for Ranking results (opens in a new tab)
Ranking controls
top_n selects the number of returned results; omitted means all results, v2 max_tokens_per_doc defaults to 4096 and truncates longer documents, v1 max_chunks_per_doc controls chunking; v1 also offers rank_fields and return_documentsSource for Ranking controls (opens in a new tab)

Version-specific controls: v1 details are documented in the separately linked v1 API. The default v2 truncation setting is not the model context length.

Input file formats
Text strings, Structured data serialized as YAML stringsSource for Input file formats (opens in a new tab)

v2 removed document-object arrays. Preserve YAML field order because long strings can be truncated.

Output formats
JSON: ordered results with document index and relevance_scoreSource for Output formats (opens in a new tab)

This fixed API response does not imply general-purpose JSON-schema constrained generation.

Request limits
For performance, v2 recommends at most 1,000 documents per request. The best-practices guide describes a 10,000 document/chunk limit for v1-style chunking.Source for Request limits (opens in a new tab)

The recommendation is not an enforced 1,000-document ceiling. Best-practices and v1 reference differ on the equality boundary and default chunk count; check the selected transport.

Customization options
Dashboard/API fine-tuning for Rerank and access to previously fine-tuned models were retired in the September 15, 2025 platform change.Source for Customization options (opens in a new tab)

This service lifecycle notice does not establish whether custom enterprise contracts can provide a different deployment arrangement.

Access & pricing

Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.

API model ID
rerank-v4.0-pro
Access
API key required. Trial and production keys have different limits and permitted usage.
Regions
Not collected

Endpoint pricing has not been collected. Check the provider for applicable rates.

Data & enterprise terms

Retention, training use, regional processing and enterprise terms have not been summarized for this endpoint.

API model ID
Not collected
Access
Dedicated instance deployment. Select the performance tier and billing commitment in Model Vault.
Regions
Not collected

Prices retain their published currencies and billing units below.

Published billing units · original currency · observed 12 Oct 2026
CategoryUsageRateUnit
Dedicated inference · MediumHourly1$5.00instance-hour
Dedicated inference · MediumMonthly1$3,250.00instance-month
Dedicated inference · LargeHourly2$10.00instance-hour
Dedicated inference · LargeMonthly2$6,500.00instance-month

Rate conditions

  1. Model Vault Medium performance tier. Hourly and monthly prices are alternative billing commitments, not additive token charges. Taxes, region and contract conditions require confirmation.
  2. Model Vault Large performance tier. Hourly and monthly prices are alternative billing commitments, not additive token charges. Taxes, region and contract conditions require confirmation.
Pricing source (opens in a new tab)

Data & enterprise terms

Retention, training use, regional processing and enterprise terms have not been summarized for this endpoint.

Caching

Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.

01 / INITIAL INPUTProcess & retain

The system processes eligible input and retains reusable state.

02 / LATER REQUESTCheck available state

Reuse depends on matching input, session state and the cache policy.

03 / CACHE HITReuse & generate

Reusing state can reduce repeated work. Any charges follow the billing rules below.

Cohere API

rerank-v4.0-pro
Not verified

Provider-side caching has not been verified for this endpoint. Missing documentation is not evidence that caching is unsupported.

How it works
Not collected
Minimum reusable input
Not collected
Lifetime & refresh
Not collected
How to enable it
Not collected
Usage fields
Not collected
Billing rules
Not collected
Limits & data boundaries
Not collected

No verified cache rate for this endpoint. An empty rate is not a zero charge.

Cohere Model Vault

Not verified

Provider-side caching has not been verified for this endpoint. Missing documentation is not evidence that caching is unsupported.

How it works
Not collected
Minimum reusable input
Not collected
Lifetime & refresh
Not collected
How to enable it
Not collected
Usage fields
Not collected
Billing rules
Not collected
Limits & data boundaries
Not collected

No verified cache rate for this endpoint. An empty rate is not a zero charge.

What the measurements say

No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.

Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.

The record behind the model

Why it is included

The provider explicitly labels this exact model Proprietary, separately from families with public weight downloads.

Classification evidence (opens in a new tab)

Sources reviewed