DeepSeek R1 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 DeepSeek R1 on OpenRouter at routing band C1. API slug deepseek-deepseek-r1. 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.
DeepSeek R1 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.
DeepSeek R1 is configured on OpenRouter. Known host IDs: openrouter: openrouter/deepseek/deepseek-r1. This model is routable through o10 eval-gated routing.
DeepSeek R1 supports a 128K tokens context window in the gateway catalog snapshot. Context limits may vary by fulfillment host endpoint.
Gateway snapshot pricing for DeepSeek R1.
| Unit | Price |
|---|---|
| Input | $1.35/1M tokens |
| Output | $5.4/1M tokens |
Upstream venues configured for DeepSeek R1.
| Host | Upstream model ID |
|---|---|
| openrouter | openrouter/deepseek/deepseek-r1 |
Eval-gated model selection for this slug.
o10 slug: deepseek-deepseek-r1. Band: C1. Routable: yes.
See [/models/routing](/models/routing) for smart aliases (o10/auto, o10/frontier, o10/squad) and [/kyi](/kyi) for governance.
Gateway catalog snapshot 2026-06-27. Fulfillment catalog synced from o10 control plane. Verify list prices against deepseek and host providers.
DeepSeek R1 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.
DeepSeek R1 supports 128K tokens in the gateway catalog snapshot. Host-specific endpoints may differ.
DeepSeek R1 (deepseek-deepseek-r1) is configured on: OpenRouter. Upstream model IDs are listed in the fulfillment routes section.
Yes. DeepSeek R1 is routable at band C1. Send model: "deepseek-deepseek-r1" or use an o10 smart routing alias.
Use o10 slug "deepseek-deepseek-r1" or gateway ID "deepseek/deepseek-r1" depending on your integration. Gateway-compatible endpoints accept OpenAI-style /v1 requests.
o10 routes DeepSeek R1 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.
The o10 slug is "deepseek-deepseek-r1"; the unified gateway ID is "deepseek/deepseek-r1". Host IDs: openrouter: openrouter/deepseek/deepseek-r1. Pricing snapshot date: 2026-06-27.
DeepSeek R1 is hosted as openrouter: openrouter/deepseek/deepseek-r1. o10 maps those upstream IDs to slug "deepseek-deepseek-r1".