// head_to_head
DeepSeek V4 Pro 0423 vs KAT-Coder-Pro V2.5
Published LiveBench scores across all seven categories, live list pricing, context windows, and the measured cost of a point of capability — for both models, side by side.
DeepSeek V4 Pro 0423 and KAT-Coder-Pro V2.5 are priced within ~10% of each other.
KAT-Coder-Pro V2.5 does not have a published LiveBench run, so this comparison covers price, context and declared capabilities only. A missing score means "not evaluated", not "worse" — the right way to separate these two is an eval on your own workload.
deepseek
DeepSeek V4 Pro 0423
- Blended / 1M
- $1.19
- Context
- 1.0M
- Released
- Apr 24, 2026
- Overall score
- 71.6
kwaipilot
KAT-Coder-Pro V2.5
- Blended / 1M
- $1.29
- Context
- 262K
- Released
- Jul 10, 2026
- Overall score
- Not evaluated
Specs and pricing
| Metric | DeepSeek V4 Pro 0423 | KAT-Coder-Pro V2.5 |
|---|---|---|
| LiveBench overall Mean of the seven LiveBench category scores, 0–100. Higher is better. | 71.6 | — |
| Cost per point Measured benchmark spend divided by overall score — dollars per point of capability. | $0.0261 | — |
| Blended price / 1M 3:1 input:output mix, the usual shape of production traffic. | $1.19 | $1.29 |
| Input price / 1M | $0.955 | $0.740win |
| Output price / 1M | $1.91win | $2.96 |
| Cached input / 1M Price of an input token served from the prompt cache, where the provider publishes one. | $0.080win | $0.150 |
| Context window | 1.0Mwin | 262K |
| Max output tokens | 384Kwin | 236K |
Benchmarks by category
An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — DeepSeek V4 Pro 0423 on top, KAT-Coder-Pro V2.5 below, both out of 100.
What each one costs to run
Per-token prices are hard to feel. These are monthly list costs for both models across five workload shapes, using each provider's published cached-input rate where there is one.
| Workload | DeepSeek V4 Pro 0423 | KAT-Coder-Pro V2.5 |
|---|---|---|
| Support chatbot 1.2K in / 400 out × 200K requests | $319.06/mo | $371.92/mo |
| RAG assistant 8K in / 600 out × 100K requests | $528.58/mo | $533.60/mo |
| Coding agent 40K in / 4K out × 20K requests | $426.68/mo | $498.40/mo |
| Document extraction 20K in / 1.5K out × 50K requests | $1,055/mo | $932.50/mo |
| Bulk classification 500 in / 20 out × 5M requests | $2,141/mo | $1,851/mo |
Which should you pick?
You need to fit large documents in one call
DeepSeek V4 Pro 0423
Wider context window — 1.0M against 262K.
DeepSeek V4 Pro 0423 vs KAT-Coder-Pro V2.5 FAQ
Which is better, DeepSeek V4 Pro 0423 or KAT-Coder-Pro V2.5?
DeepSeek V4 Pro 0423 and KAT-Coder-Pro V2.5 are priced within ~10% of each other. KAT-Coder-Pro V2.5 does not have a published LiveBench run, so this comparison covers price, context and declared capabilities only. A missing score means "not evaluated", not "worse" — the right way to separate these two is an eval on your own workload.
Is DeepSeek V4 Pro 0423 cheaper than KAT-Coder-Pro V2.5?
They cost about the same. Both land near $1.19 per million tokens on a 3:1 input:output blend, so price is unlikely to be the deciding factor between them.
Does DeepSeek V4 Pro 0423 or KAT-Coder-Pro V2.5 have a bigger context window?
DeepSeek V4 Pro 0423 has the larger context window: 1.0M for DeepSeek V4 Pro 0423 against 262K for KAT-Coder-Pro V2.5. Note that a window you can fill is not a window you should fill — retrieval quality usually degrades well before the limit, and you pay for every token you put in it.
Do DeepSeek V4 Pro 0423 and KAT-Coder-Pro V2.5 support prompt caching?
Both publish a cached-input rate: $0.080 per million for DeepSeek V4 Pro 0423 and $0.150 for KAT-Coder-Pro V2.5, against full input rates of $0.955 and $0.740. On a workload with a long stable prefix — a system prompt, a tool schema, a retrieved corpus — that changes the economics more than the headline price does.
Related comparisons
How these numbers are produced
- Price — provider list price from OpenRouter, refreshed every 15 minutes. “Blended” is a 3:1 input:output mix.
- Scores — LiveBench release 2026-06-25, using their own category map. Each model shows its strongest published run. A blank means “not evaluated”, never “bad”.
- Cost per point — the measured dollars LiveBench spent on the run, divided by the score it earned.
- “Win” — awarded only past a threshold: one full point on a benchmark score, 10% on a price, 25% on a context window. Anything tighter reports as a tie, because effort settings alone move a LiveBench score by more than that.
Published benchmarks rank models on someone else's tasks. Before committing, see LLM & agent evaluation for building an eval on your own.