What is Cohere Embed V4 0 2?
Cohere Embed V4 0 2 is a embedding model from cohere (slug: cohere-embed-v4-0-2). Pick Cohere Embed V4 0 2 for Cohere Command RAG and enterprise chat on Cohere or Bedrock hosts.
Catalog snapshot 2026-06-27.
Cohere Embed V4 0 2 is listed in the o10 fulfillment catalog as of 2026-06-27. Cohere publishes this model without a published context window in this snapshot. o10 lists Cohere Embed V4 0 2 on AWS Bedrock at routing band C0. API slug cohere-embed-v4-0-2. 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.
Cohere Embed V4 0 2. Specs, hosts, and routing
Snapshot
No list price in snapshot
Spec
cohere · context varies by host · band C0
On this page
AnswersSelf-contained
When should you pick Cohere Embed V4 0 2?
Pick Cohere Embed V4 0 2 for Cohere Command RAG and enterprise chat on Cohere or Bedrock hosts. Cohere Embed V4 0 2 is Command R+. Smaller Command SKUs exist for cheaper retrieval jobs.
How does Cohere Embed V4 0 2 differ from sibling models?
Cohere Embed V4 0 2 is Command R+. Smaller Command SKUs exist for cheaper retrieval jobs.
How much does Cohere Embed V4 0 2 cost per million tokens?
Cohere Embed V4 0 2 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 Cohere Embed V4 0 2?
Cohere Embed V4 0 2 is configured on AWS Bedrock. Known host IDs: bedrock: bedrock/cohere.embed-v4:0. This model is cataloged but not marked routable for chat routing.
What is Cohere Embed V4 0 2's context window?
Cohere Embed V4 0 2 context limits depend on the fulfillment host. Check the specifications table for endpoint-specific limits.
What o10 routing band is Cohere Embed V4 0 2?
Cohere Embed V4 0 2 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 Cohere Embed V4 0 2?
Cohere Embed V4 0 2 is attributed to source provider cohere in the o10 catalog. Fulfillment hosts (AWS Bedrock) supply API access; list pricing may differ by venue.
01Deep dive
Specifications
Cohere Embed V4 0 2 in the o10 unified catalog.
| Field | Value |
|---|---|
| o10 slug | `cohere-embed-v4-0-2` |
| Type | embedding |
| Band | C0 |
| Routable | No |
| Source provider | cohere |
| Primary host | AWS Bedrock |
02Deep dive
Fulfillment hosts
Upstream venues configured for Cohere Embed V4 0 2.
| Host | Upstream model ID |
|---|---|
| bedrock | bedrock/cohere.embed-v4:0 |
03Deep dive
Routing with o10
Eval-gated model selection for this slug.
o10 slug: cohere-embed-v4-0-2. 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 Cohere Embed V4 0 2 cost?
Cohere Embed V4 0 2 has no published per-token price in the current gateway snapshot. Use the fulfillment hosts table to identify available venues.
What is Cohere Embed V4 0 2's context window?
Context limits for Cohere Embed V4 0 2 vary by fulfillment host. See the specifications table on this page.
Which hosts serve Cohere Embed V4 0 2?
Cohere Embed V4 0 2 (cohere-embed-v4-0-2) is configured on: AWS Bedrock. Upstream model IDs are listed in the fulfillment routes section.
Is Cohere Embed V4 0 2 routable through o10?
No. Cohere Embed V4 0 2 is cataloged but not enabled for chat routing in the current fulfillment config.
How do I call Cohere Embed V4 0 2 via o10?
Use o10 slug "cohere-embed-v4-0-2" in the model field. See /models/routing for smart aliases (o10/auto, o10/frontier, o10/squad).
How does o10 route this model?
o10 routes Cohere Embed V4 0 2 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.