We moved our agent stack to the DeepSeek V3.1 Terminus API and the tool calls came back cleaner right away.
Loading model information...
DeepSeek V3.1 Terminus API — The Refined V3.1, Tuned for Agents
The DeepSeek V3.1 Terminus API serves DeepSeek V3.1 Terminus, the polished update to V3.1 — same hybrid thinking, cleaner output, and stronger agent skills.
DeepSeek V3.1 Terminus is the refined release of V3.1: it keeps the hybrid design — think step by step or answer directly, your choice per request — and sharpens the rough edges. The DeepSeek V3.1 Terminus API gives you steadier language consistency, with far fewer stray characters or mid-answer language switches, plus stronger Code Agent and Search Agent behavior, so tool-using workflows run cleaner. It keeps the 128K context window for long files and multi-step traces.
You reach the DeepSeek V3.1 Terminus API through RouterBase on the OpenAI chat-completions protocol; set the model to deepseek-v3-1-terminus and your client is unchanged. The DeepSeek V3.1 Terminus API bills $0.27 per 1M input tokens, $1.10 per 1M output, and $0.07 for cached input — 5% under list, on one key that reaches the whole catalog.
What the DeepSeek V3.1 Terminus API gives you
Same hybrid model, cleaner output, better agents.
Refined update to V3.1
The DeepSeek V3.1 Terminus API is the polished V3.1 — same core, fewer rough edges, tuned output.
Hybrid thinking kept
Think step by step or answer directly per request; the DeepSeek V3.1 Terminus API carries both modes in one model.
Built for agents
Stronger Code Agent and Search Agent behavior make the DeepSeek V3.1 Terminus API a cleaner backbone for tool-using workflows.
Cleaner output
The DeepSeek V3.1 Terminus API holds language consistency, cutting stray characters and mid-answer language switches.
128K context
A 128K window lets the DeepSeek V3.1 Terminus API hold long files, transcripts, and tool traces in one call.
Same low price
At $0.27 in, $1.10 out, and $0.07 cached input, the DeepSeek V3.1 Terminus API stays affordable at volume — 5% below list.

First call to the DeepSeek V3.1 Terminus API in three steps
Wire it once, then flip modes as you like.
Create a key
One RouterBase key reaches the DeepSeek V3.1 Terminus API and every other model in the catalog.
Point and pick a mode
Send any OpenAI client to routerbase.com/v1 with model=deepseek/deepseek-v3.1-terminus, and toggle thinking on or off per request.
Watch usage
The DeepSeek V3.1 Terminus API returns token usage per response, so cost and latency stay visible on every call.
Pay only for what you use
RouterBase passes through partner-tier pricing. Compared against the model's official published API rate.
Teams building on the DeepSeek V3.1 Terminus API
The refined hybrid model, running agents cleaner.
The language mixing we saw on the old V3.1 is gone — the DeepSeek V3.1 Terminus API just returns clean text.
Same hybrid modes, better agent behavior — the DeepSeek V3.1 Terminus API was a drop-in upgrade for us.
At $0.27 in with cached reads at $0.07, the DeepSeek V3.1 Terminus API kept our agent costs down as we scaled.
Our search agent stopped tripping over stray tokens once we switched to the DeepSeek V3.1 Terminus API.
We run thinking on for hard steps and off for the rest, all on the DeepSeek V3.1 Terminus API.
The 128K window let the DeepSeek V3.1 Terminus API keep a whole tool trace in context.
Upgrading from V3.1 to the DeepSeek V3.1 Terminus API was one string, and our code agent got noticeably steadier.
The DeepSeek V3.1 Terminus API gave us cleaner output without changing a line of our pipeline.
DeepSeek V3.1 Terminus API — common questions
What to know before you route traffic to it.
RouterBase's hosted access to DeepSeek V3.1 Terminus, the refined update to V3.1 — same hybrid model, cleaner output, stronger agents — over an OpenAI-compatible endpoint.