Pinecone API
cohere-rerank-3.5 model retirement
RedirectedSubscribe to Pinecone APIShare
On August 31, 2026, requests using model cohere-rerank-3.5 were retired and redirected to a newer model. Since that date, Pinecone API automatically serves calls to model cohere-rerank-3.5 using cohere-rerank-4-fast instead.
What to use instead of cohere-rerank-3.5
To control the transition yourself, migrate your rerank requests to cohere-rerank-4-fast.
In Pinecone API's words
August 31, 2026: requests to cohere-rerank-3.5 are automatically served by cohere-rerank-4-fast.
Facts
- API
- Pinecone API
api.pinecone.io - Model
cohere-rerank-3.5- Kind
- Model retirement
- Takes effect
- August 31, 2026
- Calls after that day
- Answered by a newer version
- Source
- Changelog
- Last updated
- Verified
- , against Pinecone API's own pages
Questions
When does this change take effect?
Since August 31, 2026, Pinecone API answers calls to the model cohere-rerank-3.5 from a newer version.
What happens to calls after August 31, 2026?
Pinecone API answers them from a newer version. The response can differ from what your code expects.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.