What is Rerank V3 5?
Rerank V3 5 is a reranking model from openrouter (slug: rerank-v3-5). Pick Rerank V3 5 when your evals pass at band C0 and the fulfillment hosts below are allowed venues. Context window: 4K tokens.
Catalog snapshot 2026-06-27.
Rerank V3 5 is listed in the o10 fulfillment catalog as of 2026-06-27. Openrouter publishes this model with a 4K tokens context window. o10 lists Rerank V3 5 on Cohere at routing band C0. API slug rerank-v3-5. Verify list prices against the venue you call.
Last updated: 2026-06-27. Full catalog. Reference prices are dated snapshots. Compare total cost and measured task quality before choosing a route.
Rerank V3 5. Specs, hosts, and routing
Snapshot
No list price in snapshot
Spec
openrouter · 4K context · band C0
On this page
AnswersSelf-contained
When should you pick Rerank V3 5?
Pick Rerank V3 5 when your evals pass at band C0 and the fulfillment hosts below are allowed venues. Rerank V3 5 is the openrouter SKU in this catalog. Compare same-provider siblings before jumping labs.
How does Rerank V3 5 differ from sibling models?
Rerank V3 5 is the openrouter SKU in this catalog. Compare same-provider siblings before jumping labs.
How much does Rerank V3 5 cost per million tokens?
Rerank V3 5 does not have published per-token pricing in the current gateway snapshot. See fulfillment hosts below for routing options.
Pricing unavailable in current snapshot.
Where can you run Rerank V3 5?
Rerank V3 5 is configured on Cohere. Known host IDs: cohere: cohere/rerank-v3.5. This model is cataloged but not marked routable for chat routing.
What is Rerank V3 5's context window?
Rerank V3 5 supports a 4K tokens context window in the gateway catalog snapshot. Context limits may vary by fulfillment host endpoint.
What o10 routing band is Rerank V3 5?
Rerank V3 5 is classified at o10 routing band C0. Bands group models by cost tier and eval profile: C0 (economy), C1 (standard), C2 (capable), C3/C4 (frontier). Chat routing is disabled for this slug.
Who makes Rerank V3 5?
Rerank V3 5 is attributed to source provider openrouter in the o10 catalog. Fulfillment hosts (Cohere) supply API access; list pricing may differ by venue.
01Deep dive
Specifications
Rerank V3 5 in the o10 unified catalog.
| Field | Value |
|---|---|
| o10 slug | `rerank-v3-5` |
| Type | rerank |
| Band | C0 |
| Routable | No |
| Source provider | openrouter |
| Primary host | Cohere |
| Gateway ID | `cohere/rerank-v3.5` |
| Context window | 4,096 tokens |
| Released | 2024-12-02 |
02Deep dive
Fulfillment hosts
Upstream venues configured for Rerank V3 5.
| Host | Upstream model ID |
|---|---|
| cohere | cohere/rerank-v3.5 |
03Deep dive
Gateway provider endpoints
Endpoint-level pricing and latency from the gateway catalog.
| Provider | Input ($/1M) | Latency p50 | Uptime 1d |
|---|---|---|---|
| bedrock | $0 | - | 10000.0% |
04Deep dive
Routing with o10
Eval-gated model selection for this slug.
o10 slug: rerank-v3-5. Band: C0. Routable: no.
See [/models/routing](/models/routing) for smart aliases (o10/auto, o10/frontier, o10/squad) and [/kyi](/kyi) for governance.
SourceMethodology
Fulfillment catalog 2026-06-27. Gateway pricing joined where slug match exists.
FAQFrequently asked questions
Common questions
How much does Rerank V3 5 cost?
Rerank V3 5 has no published per-token price in the current gateway snapshot. Use the fulfillment hosts table to identify available venues.
What is Rerank V3 5's context window?
Rerank V3 5 supports 4K tokens in the gateway catalog snapshot. Host-specific endpoints may differ.
Which hosts serve Rerank V3 5?
Rerank V3 5 (rerank-v3-5) is configured on: Cohere. Upstream model IDs are listed in the fulfillment routes section.
Is Rerank V3 5 routable through o10?
No. Rerank V3 5 is cataloged but not enabled for chat routing in the current fulfillment config.
How do I call Rerank V3 5 via o10?
Use o10 slug "rerank-v3-5" or gateway ID "cohere/rerank-v3.5" depending on your integration. Gateway-compatible endpoints accept OpenAI-style /v1 requests.
How does o10 route this model?
o10 routes Rerank V3 5 only when per-use-case evals clear at your quality floor. Band C0 indicates cost tier. See /kyi for governance and /models/routing for smart aliases.