What is R1 V1 0?
R1 V1 0 is a language model in the o10 fulfillment catalog (slug: deepseek-r1-v1-0). Published input pricing starts at $1.35/1M tokens. Context window: 128K tokens.
Catalog snapshot 2026-06-27.
R1 V1 0 costs $1.35/1M input tokens and $5.40/1M output tokens as of 2026-06-27. Deepseek publishes this model with a 128K tokens context window. o10 lists R1 V1 0 on AWS Bedrock at routing band C1.
Last updated: 2026-06-27. Full catalog
R1 V1 0 — specs, hosts, and routing
AnswersSelf-contained
How much does R1 V1 0 cost per million tokens?
R1 V1 0 costs $1.35/1M input tokens and $5.40/1M output tokens in the gateway catalog snapshot (2026-06-27). Endpoint pricing may differ by fulfillment host.
Sourced from gateway catalog snapshot.
Where can you run R1 V1 0?
R1 V1 0 is configured on AWS Bedrock. Each host maps to an upstream model ID listed in the fulfillment routes table. This model is routable through o10 eval-gated routing.
What is R1 V1 0's context window?
R1 V1 0 supports a 128K tokens context window in the gateway catalog snapshot. Context limits may vary by fulfillment host endpoint.
What o10 routing band is R1 V1 0?
R1 V1 0 is classified at o10 routing band C1. Bands group models by cost tier and eval profile: C0 (economy), C1 (standard), C2 (capable), C3/C4 (frontier). Production routing is enabled for this slug.
Who makes R1 V1 0?
R1 V1 0 is attributed to source provider deepseek in the o10 catalog. Fulfillment hosts (AWS Bedrock) supply API access; list pricing may differ by venue.
01Deep dive
Specifications
R1 V1 0 in the o10 unified catalog.
| Field | Value |
|---|---|
| o10 slug | `deepseek-r1-v1-0` |
| Type | text |
| Band | C1 |
| Routable | Yes |
| Source provider | deepseek |
| Primary host | AWS Bedrock |
| Gateway ID | `deepseek/deepseek-r1` |
| Context window | 128,000 tokens |
| Released | 2025-01-20 |
02Deep dive
Token pricing
Gateway snapshot pricing for R1 V1 0.
| Unit | Price |
|---|---|
| Input | $1.35/1M tokens |
| Output | $5.4/1M tokens |
03Deep dive
Fulfillment hosts
Upstream venues configured for R1 V1 0.
| Host | Upstream model ID |
|---|---|
| bedrock | bedrock/deepseek.r1-v1:0 |
04Deep dive
Gateway provider endpoints
Endpoint-level pricing and latency from the gateway catalog.
| Provider | Input ($/1M) | Latency p50 | Uptime 1d |
|---|---|---|---|
| bedrock | $1.35 | 311.5ms | 10000.0% |
| deepinfra | $0.5 | 652ms | 10000.0% |
05Deep dive
Routing with o10
Eval-gated model selection for this slug.
o10 slug: deepseek-r1-v1-0. Band: C1. Routable: yes.
See [/models/routing](/models/routing) for smart aliases (o10/auto, o10/economy) 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 R1 V1 0 cost?
R1 V1 0 costs $1.35/1M input tokens and $5.40/1M output tokens in the gateway snapshot (2026-06-27). Verify against your provider's published pricing.
What is R1 V1 0's context window?
R1 V1 0 supports 128K tokens in the gateway catalog snapshot. Host-specific endpoints may differ.
Which hosts serve R1 V1 0?
R1 V1 0 (deepseek-r1-v1-0) is configured on: AWS Bedrock. Upstream model IDs are listed in the fulfillment routes section.
Is R1 V1 0 routable through o10?
Yes. R1 V1 0 is routable at band C1. Send model: "deepseek-r1-v1-0" or use an o10 smart routing alias.
How do I call R1 V1 0 via o10?
Use o10 slug "deepseek-r1-v1-0" or gateway ID "deepseek/deepseek-r1" depending on your integration. Gateway-compatible endpoints accept OpenAI-style /v1 requests.
How does o10 route this model?
o10 routes R1 V1 0 only when per-use-case evals clear at your quality floor. Band C1 indicates cost tier. See /kyi for governance and /models/routing for smart aliases.