Current decision boundary
Usage-based Embed and Rerank APIs
Verified 2026-07-27: Cohere publishes model-specific Embed and Rerank pricing; estimates must include index creation, query embedding, reranking volume, batch behavior, and re-embedding.3
Managed retrieval model APIs
Managed embedding and reranking APIs for text, multilingual, image, and structured retrieval workloads under Cohere's current model lifecycle.
Choose Cohere when corpus-specific evaluation shows that its embedding and optional reranking route produces useful relevance within supported inputs, languages, dimensions, throughput, data, and cost boundaries.123
Whether Cohere's current Embed and Rerank models improve retrieval enough on the actual corpus to justify their model, rate-limit, price, and migration boundaries.
This page owns Cohere Embed and Rerank selection, not the full Command generation platform, vector storage, chunking architecture, or generic RAG implementation.123
For: Search and RAG teams evaluating embeddings and optional reranking on representative documents and queries
Embedding is billed by processed tokens and reranking by its current processed-search or token metric. Trial and production keys have separate usage and rate-limit boundaries.3
Current decision boundary
Verified 2026-07-27: Cohere publishes model-specific Embed and Rerank pricing; estimates must include index creation, query embedding, reranking volume, batch behavior, and re-embedding.3
Cohere · Accessed Official
Cohere · Accessed Official
Cohere · Accessed Official
Cohere · Accessed Official
OpenAI · Accessed Official
OpenAI · Accessed Official
OpenAI · Accessed Official
Voyage AI · Accessed Official
Voyage AI · Accessed Official
Voyage AI · Accessed Official
Google · Accessed Official
Google · Accessed Official
Google · Accessed Official