DeepSeek V4.1 Flash vs Tencent Hy4

vs

Which one, when

Base output costs $1.2 vs $2.501 per million tokens (deepseek-v4.1-flash vs hy4). Evaluate deepseek-v4.1-flash for text and image workloads where open weights matter. Against deepseek-v4.1-flash, consider hy4 for long Chinese or English documents with embedded screenshots.

Benchmarks

Tencent Hy4: the vendor has not published benchmark scores.

Above averageNo peer higherDeepSeek V4.1 Flash14 / 194 / 19
DeepSeek V4.1 Flash Tencent Hy4 other models measured peer average ★ no peer scored higher
DeepSWE 1.1
no peer scored higher 74.2%
N/A
Cybergym
no peer scored higher 88.1%
N/A
GPQA Diamond
90.9%
N/A
Agents' Last Exam
31.8%
N/A
Chartography with tools
78.9%
N/A

Vendor-published: Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Anthropic Anthropic Anthropic Anthropic ByteDance DeepSeek DeepSeek Google Google Google MiniMax Moonshot OpenAI OpenAI OpenAI OpenAI OpenAI Tencent Z.ai Z.ai Z.ai Z.ai

Pricing

DeepSeek V4.1 Flash Tencent Hy4 Δ
Input / 1M tokens $0.3 $0.834 0.36×
Output / 1M tokens $1.2 $2.501 0.48×
Cache read / 1M tokens $0.006 $0.042 0.14×
Cache write no separate charge - -

Rates from the live catalogue at build time; each model page carries the current rate card.

Where they sit · input price per 1M tokens across all 86 chat models on this billing unit (log scale)

DeepSeek V4.1 Flash · $0.3 Tencent Hy4 · $0.834
$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

Capabilities

DeepSeek V4.1 Flash Tencent Hy4
Tool calling yes yes
Thinking control yes (vendor dial not published) yes (vendor dial not published)
Prompt caching implicit (automatic) implicit (automatic)
Cache lifetime no fixed TTL (evicted when unused) not published
Minimum cached prefix not published not published

Specs

DeepSeek V4.1 Flash Tencent Hy4
Input modalities text image text image
Output modalities text text
Released 2026-09-10 2026-11-04
Context window 1,000,000 1,048,576
Max output 393,216 65,536

Specs are transcribed from each vendor’s documentation; a row a vendor does not publish is left out rather than inferred. Full sources: DeepSeek V4.1 Flash · Tencent Hy4

One prompt, both models, measured through the gateway

PROMPT Explain to a CFO, in exactly three sentences, why our LLM bill doubled after we enabled reasoning. CHECK exactly 3 sentences

DeepSeek V4.1 Flash passed · 3 sentences

Enabling reasoning changed the unit economics: the model now spends extra billable tokens internally to “think” before producing the answer, and those reasoning tokens are charged like output tokens even though users never see them. That added token generation—plus longer contexts and occasional retries on harder prompts—roughly doubled our cost per request. We can control this by capping reasoning depth, routing only complex queries to reasoning models, and caching common prompts to bring the bill back down.

out 423 tok (+327 thinking) latency 14.6 s

Tencent Hy4 passed · 3 sentences

Enabling reasoning changed the unit economics of each request: the model now produces extra “reasoning tokens” and consumes more compute before it returns an answer, and those tokens are billed even if users never see them. Because our pricing is largely token-based, that extra work roughly doubled average cost per call, so flat request volume could still produce a doubled invoice. We are paying for better accuracy and less downstream rework on complex tasks, so the spend is justified only in high-value workflows and should be managed by cost per successful outcome.

out 1519 tok (+1409 thinking) latency 21.0 s

Instruction following (exactly three sentences, so countable), audience shaping (CFO register), and the hidden-thinking billing gap the token meters below expose.

PROMPT This function is supposed to return the longest run of consecutive equal items, but callers report it is off by one on single-element inputs and misses runs that end at the last index. Fix it and explain the bug in one paragraph. CHECK fix passes tests

DeepSeek V4.1 Flash passed · 8/8 cases

```python def longest_run(xs): if not xs: return 0 best = 1 cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 else: cur = 1 best = max(best, cur) return best ``` The bug is that `cur` is counting equal adjacent pairs, not elements in the current run: every time `xs[i] == xs[i - 1]`, the run length increases by one element, but the first element of the run was never counted, so all runs are undercounted by one. Also, `best` starts at `0`, so single-element inputs return `0` instead of `1`, and a one-element run ending at the last index is missed entirely.

out 918 tok (+733 thinking) latency 11.4 s

Tencent Hy4 passed · 8/8 cases

```python def longest_run(xs): n = len(xs) if n == 0: return 0 best = cur = 1 for i in range(1, n): if xs[i] == xs[i - 1]: cur += 1 else: cur = 1 best = max(best, cur) return best ``` The loop range already includes the last index; the real bug is that `cur` and `best` start at `0` and only increase on equal adjacent comparisons, so the function counts equality links (`L - 1` for a run of `L` equal items), not the items in the run: a single item has no link, and the first item of a final run is never counted, with no end-of-list flush to compensate. […]

out 4509 tok (+4263 thinking) latency 56.0 s

Whether the fix is actually correct (runnable), explanation density, and token efficiency on a bounded task.

PROMPT Extract a JSON object with fields {company, quarter, revenue_usd_m, growth_pct, guidance} from this text. Use null for anything not stated; add no other fields. CHECK valid JSON, schema exact

DeepSeek V4.1 Flash passed · 5/5 fields, guidance "withheld pending the Q4 close"

{"company":"Meridian Robotics","quarter":"September quarter","revenue_usd_m":412,"growth_pct":11.0,"guidance":"withheld pending the Q4 close"}

out 1707 tok (+1667 thinking) latency 15.1 s

Tencent Hy4 passed · 5/5 fields, guidance "withheld pending the Q4 close"

{"company":"Meridian Robotics","quarter":"September quarter","revenue_usd_m":412,"growth_pct":"eleven and change","guidance":"withheld pending the Q4 close"}

out 9869 tok (+9827 thinking) latency 125.2 s

Schema obedience (no invented fields), hallucination pressure (guidance is explicitly withheld), and structured-output path differences.

PROMPT Write a 120-word product announcement for an API gateway feature that caches prompts across providers. Forbidden words: "seamless", "unlock", "game-changer", "revolutionize", "empower". Exactly one sentence must be a question. CHECK 120 words, 0 banned words

DeepSeek V4.1 Flash passed · 116 words, 0 banned, 1 question

Today we're launching Cross-Provider Prompt Cache for our API gateway. It stores identical prompt requests and their responses across supported model providers, then serves cached results when a match is found. Teams can cut duplicate inference costs, reduce latency, and keep behavior consistent during provider failover. The cache works with configurable TTLs, per-route rules, and cache-key controls, so you decide what is reusable and what must stay fresh. Does your application send the same prompts to multiple providers? Now your gateway can answer many of those calls without another upstream request. Existing observability dashboards show hit rates, saved tokens, and estimated spend reduction. Enable it in the gateway console, set your policy, and start caching today.

out 917 tok (+770 thinking) latency 9.0 s

Tencent Hy4 passed · 120 words, 0 banned, 1 question

Today we are introducing Cross Provider Prompt Cache for our API gateway, a feature that caches prompts and securely reuses them across all connected model providers. Teams can cut duplicate calls, reduce latency, and keep spend predictable when identical instructions appear in chat, search, agents, or batch jobs. What if one cached prompt could support traffic routed to any provider in your stack? Gateway policies control cache keys, time to live, tenant isolation, redaction, and fallback behavior, while usage metrics show hit rates and savings by application. Setup requires one configuration change, and existing client code stays intact. Cross Provider Prompt Cache is available in private beta today for enterprise plans, with general availability next month across all supported regions.

out 5744 tok (+5601 thinking) latency 57.6 s

Constraint obedience (word budget, banned-word list, the single question), style fingerprint, and length control.

Switch between them with one line

Both ids are in every tab below; the highlighted pair of lines is the only edit. Same endpoint, same key, same request shape.

from openai import OpenAI

client = OpenAI(
    base_url="https://synthorai.io/v1",
    api_key="sk-syn-...",
)

resp = client.chat.completions.create(
    model="deepseek-v4.1-flash",
    # model="hy4",  # uncomment this line, comment the one above
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

Get your API key →

FAQ

Which is cheaper, DeepSeek V4.1 Flash or Tencent Hy4?

DeepSeek V4.1 Flash is cheaper on the "Input / 1M tokens" row ($0.3 vs $0.834, 2.8× apart). Other rows may point the other way; the table above carries the full rate card, and real cost depends on your mix.

Can I A/B test DeepSeek V4.1 Flash against Tencent Hy4 without two integrations?

Yes. Both are served through the same OpenAI-compatible endpoint with one API key. Switching is a one-line change to the model id, so you can route a fraction of traffic to each and compare bills directly.

Do DeepSeek V4.1 Flash and Tencent Hy4 support prompt caching?

Yes. Both bill cache reads below their input rate, so warm-prefix workloads cost less than the list rates suggest. The exact cache-read rows are in the pricing table above.

Related comparisons

From our measured studies