Dola Seed 2.0 Lite vs Tencent Hy4

Dola Seed 2.0 Lite has been retired from our catalogue. Its figures below are the last published rates; calls to it are no longer served, while the other model in this comparison is.

vs

Which one, when

For prompts up to 128000 input tokens, output costs $2 vs $2.501 per million tokens (Dola-Seed-2.0-lite vs hy4). Evaluate Dola-Seed-2.0-lite for short text requests and check the output rate above 128000 input tokens. Against Dola-Seed-2.0-lite, consider hy4 for long Chinese or English documents with embedded screenshots.

Benchmarks

Tencent Hy4: the vendor has not published benchmark scores.

Above averageNo peer higherDola Seed 2.0 Lite4 / 103 / 10
Dola Seed 2.0 Lite Tencent Hy4 other models measured peer average ★ no peer scored higher
SWE Multilingual GPT-5.4 High
66.6%
N/A
WenetSpeech test-net (CER)
no peer scored higher 4.47%
N/A
OSWorld-Verified
64.4%
N/A
GPQA Diamond
88.4%
N/A
BrowseComp
64%
N/A
MMVU
76.7%
N/A

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

Pricing

Dola Seed 2.0 Lite Tencent Hy4 Δ
Input / 1M tokens $0.25 $0.834 0.3×
Output / 1M tokens $2 $2.501 0.8×
Cache read / 1M tokens $0.05 $0.042 1.2×

Rates from the live catalogue at build time; each model page carries the current rate card. The main table shows base rates. Prompt length can change the rate for the entire request. See each model’s full rate card.

Dola Seed 2.0 Lite · Rates by prompt length

The whole request uses the rate for its input-length tier. Prices are USD per million tokens.

Input tokensInputOutput
0 - 128,000 $0.25 $2
128,001 - ∞ $0.5 $4

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

Dola Seed 2.0 Lite · $0.25 Tencent Hy4 · $0.834
$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

Capabilities

Dola Seed 2.0 Lite Tencent Hy4
Tool calling yes yes
Thinking control configurable yes (vendor dial not published)
Structured output yes -
Prompt caching implicit + explicit implicit (automatic)
Cache lifetime not published not published
Minimum cached prefix 1,024 tokens not published

Specs

Dola Seed 2.0 Lite Tencent Hy4
Input modalities text image audio video text image
Output modalities text text
Released 2026-02-14 2026-11-04
Context window 256,000 1,048,576
Max output 131,072 65,536
Thinking parameter
  • thinking.type
  • reasoning_effort
-
Accepted values
thinking.type
  • enabled
  • disabled (no auto)
reasoning_effort
  • minimal
  • low
  • medium
  • high
-
Default enabled, with reasoning_effort medium -

Specs are transcribed from each vendor’s documentation; a row a vendor does not publish is left out rather than inferred. Full sources: Dola Seed 2.0 Lite · 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

Dola Seed 2.0 Lite passed · 3 sentences

Enabling reasoning on our production LLM requires the model to run resource-intensive multi-step chain-of-thought inference for every customer-facing query, rather than the single-pass inference that powered our original non-reasoning deployment, and GPU compute—which makes up 90% of our total LLM bill—scales directly with the number of compute cycles each query consumes. Our cloud provider’s LLM billing model charges per million processed tokens, and reasoning workflows generate an average of 2.1x more hidden processing tokens (the intermediate problem-solving steps the model never surfaces to end users) that are still billable, pushing our total monthly token consumption just over double what it was prior to enabling the feature. […]

out 1306 tok (+1096 thinking) latency 18.2 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

Dola Seed 2.0 Lite passed · 8/8 cases

### Corrected Function ```python def longest_run(xs): if not xs: # Handle empty input edge case return 0 best = cur = 1 # Base run length of 1 for any non-empty single element for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 best = max(best, cur) else: cur = 1 # Reset run length for the new, different element return best ``` ### Bug Explanation (single paragraph) The original function’s core flaw was that it counted the number of consecutive equal adjacent element pairs, rather than the number of elements in the run itself, leading to all results being off by one, which caused both reported issues: a run of k equal elements only has k-1 consecutive matching pairs, so the original function’s maximum `best` value was always one less than the true element count of the longest run. […]

out 2620 tok (+2217 thinking) latency 33.2 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

Dola Seed 2.0 Lite passed · 5/5 fields, guidance "Formal guidance withheld pending Q4 clos"

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

out 1502 tok (+1439 thinking) latency 20.2 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

Dola Seed 2.0 Lite missed · 141 words, 0 banned, 1 question

Today we launch Cross-Provider Prompt Cache, a new feature for our Core API Gateway built to cut redundant AI costs and latency for teams routing requests across multiple LLM providers. Many development teams rotate between OpenAI, Anthropic, and Google Gemini to balance performance, cost, and capability, but identical prompts get reprocessed from scratch with every provider switch, wasting tokens and slowing response times. This feature stores validated prompt responses at the gateway layer, so repeat requests pull from cache regardless of which provider they route to, with configurable TTLs and built-in compliance with all major provider data policies. […]

out 1870 tok (+1695 thinking) latency 23.1 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="Dola-Seed-2.0-lite",
    # model="hy4",  # uncomment this line, comment the one above
    messages=[{"role": "user", "content": "Summarize this diff"}],
)
print(resp.choices[0].message.content)

Get your API key →

FAQ

Which is cheaper, Dola Seed 2.0 Lite or Tencent Hy4?

The main table shows base rates. Prompt length can change the rate for the entire request. See each model’s full rate card.

Can I A/B test Dola Seed 2.0 Lite 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 Dola Seed 2.0 Lite 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