Deepseek V3 1 Terminus costs $0.270/1M input tokens and $1.00/1M output tokens as of 2026-06-27. Deepseek publishes this model with a 131K tokens context window. o10 lists Deepseek V3 1 Terminus on OpenRouter at routing band C1.
Last updated: 2026-06-27. Full catalog
Deepseek V3 1 Terminus costs $0.270/1M input tokens and $1.00/1M output tokens in the gateway catalog snapshot (2026-06-27). Endpoint pricing may differ by fulfillment host.
Sourced from gateway catalog snapshot.
Deepseek V3 1 Terminus is configured on OpenRouter. Each host maps to an upstream model ID listed in the fulfillment routes table. This model is routable through o10 eval-gated routing.
Deepseek V3 1 Terminus supports a 131K tokens context window in the gateway catalog snapshot. Context limits may vary by fulfillment host endpoint.
Gateway snapshot pricing for Deepseek V3 1 Terminus.
| Unit | Price |
|---|---|
| Input | $0.27/1M tokens |
| Output | $1/1M tokens |
Upstream venues configured for Deepseek V3 1 Terminus.
| Host | Upstream model ID |
|---|---|
| openrouter | openrouter/deepseek/deepseek-v3.1-terminus |
Eval-gated model selection for this slug.
o10 slug: deepseek-deepseek-v3-1-terminus. 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 V3 1 Terminus costs $0.270/1M input tokens and $1.00/1M output tokens in the gateway snapshot (2026-06-27). Verify against your provider's published pricing.
Deepseek V3 1 Terminus supports 131K tokens in the gateway catalog snapshot. Host-specific endpoints may differ.
Deepseek V3 1 Terminus (deepseek-deepseek-v3-1-terminus) is configured on: OpenRouter. Upstream model IDs are listed in the fulfillment routes section.
Yes. Deepseek V3 1 Terminus is routable at band C1. Send model: "deepseek-deepseek-v3-1-terminus" or use an o10 smart routing alias.
Use o10 slug "deepseek-deepseek-v3-1-terminus" or gateway ID "deepseek/deepseek-v3.1-terminus" depending on your integration. Gateway-compatible endpoints accept OpenAI-style /v1 requests.
o10 routes Deepseek V3 1 Terminus 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.