Dola Seed 2.0 Lite vs Tencent Hy4

Dola Seed 2.0 Lite 已從我們的目錄下架。下方是它最後公布的費率;它已經無法呼叫,這組比較裡的另一個模型則仍可呼叫。

vs

什麼情況選哪一個

提示詞不超過 128000 個輸入 token 時,每百萬輸出 token 為 $2 和 $2.501(Dola-Seed-2.0-lite 對 hy4)。 短文字請求可評估 Dola-Seed-2.0-lite,並核對輸入超過 128000 token 時的輸出價。 與 Dola-Seed-2.0-lite 相比,中英文長文件夾有截圖時,可評估 hy4。

Benchmark 成績

Tencent Hy4:供應商沒有公布 benchmark 成績。

高於平均沒有模型更高Dola Seed 2.0 Lite4 / 103 / 10
Dola Seed 2.0 Lite Tencent Hy4 其他有成績的模型 其他模型平均 ★ 沒有模型分數更高
SWE Multilingual GPT-5.4 High
66.6%
N/A
WenetSpeech test-net (CER)
沒有模型分數更高 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

供應商公布: 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

定價

Dola Seed 2.0 Lite Tencent Hy4 Δ
輸入 / 1M tokens $0.25 $0.834 0.3×
輸出 / 1M tokens $2 $2.501 0.8×
快取讀取 / 1M tokens $0.05 $0.042 1.2×

費率取自網站建置時的即時目錄;各模型頁面都列有最新的價目。 主表顯示基礎級距。提示詞長度可能改變整筆請求的費率,各模型頁有完整價目。

Dola Seed 2.0 Lite · 依輸入長度分級的價格

整次請求依輸入長度所在級距計費。價格單位為美元/百萬 token。

輸入 token 數輸入輸出
0 - 128,000 $0.25 $2
128,001 - ∞ $0.5 $4

兩者的相對位置:每 1M tokens 的輸入價格,涵蓋同一計費單位下全部 86 個聊天模型(對數尺度)

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

功能

Dola Seed 2.0 Lite Tencent Hy4
工具使用 是 是
思考控制 可設定 是,但供應商未公布調整參數
結構化輸出 是 -
提示詞快取 隱式 + 顯式 隱式(自動)
快取存活時間 未公布 未公布
最小快取前綴 1,024 個 token 未公布

規格

Dola Seed 2.0 Lite Tencent Hy4
輸入模態 文字 圖像 音訊 影片 文字 圖像
輸出模態 文字 文字
發布日期 2026-02-14 2026-11-04
上下文視窗 256,000 1,048,576
最大輸出 131,072 65,536
思考參數
  • thinking.type
  • reasoning_effort
-
可接受的值
thinking.type
  • enabled
  • disabled (no auto)
reasoning_effort
  • minimal
  • low
  • medium
  • high
-
預設值 enabled,且 reasoning_effort 為 medium -

規格摘錄自各供應商的文件;供應商沒有公布的項目就直接略過,不自行推測。 完整來源: Dola Seed 2.0 Lite · Tencent Hy4

同一段提示詞,兩個模型,經閘道實測

提示詞 Explain to a CFO, in exactly three sentences, why our LLM bill doubled after we enabled reasoning. 檢查 恰好 3 句

Dola Seed 2.0 Lite 通過 · 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. […]

輸出 1306 tok (+1096 思考) 延遲 18.2 s

Tencent Hy4 通過 · 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.

輸出 1519 tok (+1409 思考) 延遲 21.0 s

是否照指令做(剛好三句,數得出來)、語氣是否貼合對象(寫給 CFO 看),以及下方 token 計量顯示出的隱藏思考計費落差。

提示詞 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. 檢查 修正後通過測試

Dola Seed 2.0 Lite 通過 · 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. […]

輸出 2620 tok (+2217 思考) 延遲 33.2 s

Tencent Hy4 通過 · 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. […]

輸出 4509 tok (+4263 思考) 延遲 56.0 s

修正是否真的正確(跑得起來)、說明的資訊密度,以及在範圍明確的任務上的 token 效率。

提示詞 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. 檢查 有效的 JSON,完全符合 schema

Dola Seed 2.0 Lite 通過 · 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" }

輸出 1502 tok (+1439 思考) 延遲 20.2 s

Tencent Hy4 通過 · 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"}

輸出 9869 tok (+9827 思考) 延遲 125.2 s

是否遵守 schema(不自創欄位)、面對幻覺誘因的表現(題目明確不給 guidance),以及結構化輸出路徑的差異。

提示詞 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. 檢查 120 詞,0 個禁用詞

Dola Seed 2.0 Lite 未通過 · 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. […]

輸出 1870 tok (+1695 思考) 延遲 23.1 s

Tencent Hy4 通過 · 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.

輸出 5744 tok (+5601 思考) 延遲 57.6 s

是否遵守限制(字數上限、禁用詞清單、只能有一句問句)、文字風格的特徵,以及長度控制。

改一行程式碼就能在兩者之間切換

下面每個頁籤都列了這兩個模型 ID,要改的只有醒目標示的那兩行。端點、金鑰和請求格式都不變。

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",  # 取消這一行的註解,並把上一行註解掉
    messages=[{"role": "user", "content": "Summarize this diff"}],
)
print(resp.choices[0].message.content)

取得 API 金鑰 →

常見問題

Dola Seed 2.0 Lite 和 Tencent Hy4 哪個比較便宜?

主表顯示基礎級距。提示詞長度可能改變整筆請求的費率,各模型頁有完整價目。

可以只串接一次,就對 Dola Seed 2.0 Lite 和 Tencent Hy4 做 A/B 測試嗎?

可以。兩個模型都走同一個 OpenAI 相容端點,用的也是同一把 API 金鑰,切換時只要改一行裡的模型名稱字串。你可以把一部分流量分別導到兩邊,再直接比較帳單。

Dola Seed 2.0 Lite 與 Tencent Hy4 支援提示詞快取嗎?

支援。兩者的快取讀取費率都低於輸入費率,所以前綴已經進快取的工作負載,實際成本會比官網價算出來的低。確切的快取讀取價格請見上方定價表。

相關比較