Tencent Hy4 vs Kimi K3.1 Pro Highspeed
什麼情況選哪一個
兩者都接收圖文輸入。優先控制 token 成本時從 hy4 開始,若更快的互動回應值得更高費率,再試 kimi-k3.1-pro-highspeed。
定價
| Tencent Hy4 | Kimi K3.1 Pro Highspeed | Δ | |
|---|---|---|---|
| 輸入 / 1M tokens | $0.834 | $4 | 0.21× |
| 輸出 / 1M tokens | $2.501 | $20 | 0.13× |
| 快取讀取 / 1M tokens | $0.042 | $0.2 | 0.21× |
費率取自網站建置時的即時目錄;各模型頁面都列有最新的價目。
兩者的相對位置:每 1M tokens 的輸入價格,涵蓋同一計費單位下全部 86 個聊天模型(對數尺度)
功能
| Tencent Hy4 | Kimi K3.1 Pro Highspeed | |
|---|---|---|
| 工具使用 | 是 | 是 |
| 思考控制 | 是,但供應商未公布調整參數 | 是,但供應商未公布調整參數 |
| 提示詞快取 | 隱式(自動) | 隱式(自動) |
| 快取存活時間 | 未公布 | 未公布 |
| 最小快取前綴 | 未公布 | 未公布 |
規格
| Tencent Hy4 | Kimi K3.1 Pro Highspeed | |
|---|---|---|
| 輸入模態 | 文字 圖像 | 文字 圖像 |
| 輸出模態 | 文字 | 文字 |
| 發布日期 | 2026-11-04 | 2026-10-23 |
| 上下文視窗 | 1,048,576 | 1,048,576 |
| 最大輸出 | 65,536 | 131,072 |
規格摘錄自各供應商的文件;供應商沒有公布的項目就直接略過,不自行推測。 完整來源: Tencent Hy4 · Kimi K3.1 Pro Highspeed
同一段提示詞,兩個模型,經閘道實測
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
Kimi K3.1 Pro Highspeed 通過 · 3 sentences
Enabling reasoning makes the model generate extra “thinking” tokens before each answer, so every request consumes more compute and output tokens even when the visible response stays short. Those reasoning tokens are typically billed, and the new configuration may also use a more expensive model or processing tier, raising both usage and unit cost. To control spend, we should verify reasoning-token volume and model pricing on the invoice, then cap reasoning effort and reserve it for high-value tasks.
輸出 410 tok (+410 思考) 延遲 8.6 s
是否照指令做(剛好三句,數得出來)、語氣是否貼合對象(寫給 CFO 看),以及下方 token 計量顯示出的隱藏思考計費落差。
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
Kimi K3.1 Pro Highspeed 通過 · 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 counter bookkeeping, not the loop bounds: `cur` starts at zero, so the original counts equal adjacent pairs rather than items and never records a run for a single-element input. Runs are therefore reported one short, with singleton runs appearing as zero, including runs reaching the last index. The fix treats each item as a run of length one, resets `cur` to one on a mismatch, and updates `best` after every step, so a trailing run is recorded without needing a following mismatch; empty input returns `0`.
輸出 2102 tok (+2079 思考) 延遲 31.7 s
修正是否真的正確(跑得起來)、說明的資訊密度,以及在範圍明確的任務上的 token 效率。
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
Kimi K3.1 Pro Highspeed 通過 · 5/5 fields, guidance "Formal guidance withheld pending the Q4 "
{ "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": "Formal guidance withheld pending the Q4 close" }
輸出 2170 tok (+2170 思考) 延遲 29.3 s
是否遵守 schema(不自創欄位)、面對幻覺誘因的表現(題目明確不給 guidance),以及結構化輸出路徑的差異。
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
Kimi K3.1 Pro Highspeed 通過 · 120 words, 0 banned, 1 question
Introducing Cross-Provider Prompt Cache, a new API gateway feature that stores prompt responses and serves them across model providers. By reusing responses, teams can reduce latency, cut duplicate inference costs, and keep applications responsive during traffic spikes. You choose cache lifetime, scope, and eligibility rules, while provider credentials and routing policies remain under your control. Built-in metrics show hit rates, savings, and response times, helping you tune performance with confidence. Sensitive workloads can bypass caching, and entries expire according to your retention settings. Ready to spend less on repeated prompts? Enable the feature from your gateway configuration, define a cache policy, and start measuring results today. Cross-Provider Prompt Cache is available now, with documentation and examples in the developer console.
輸出 2161 tok (+2151 思考) 延遲 23.5 s
是否遵守限制(字數上限、禁用詞清單、只能有一句問句)、文字風格的特徵,以及長度控制。
改一行程式碼就能在兩者之間切換
下面每個頁籤都列了這兩個模型 ID,要改的只有醒目標示的那兩行。端點、金鑰和請求格式都不變。
from openai import OpenAI
client = OpenAI(
base_url="https://synthorai.io/v1",
api_key="sk-syn-...",
)
resp = client.chat.completions.create(
model="hy4",
# model="kimi-k3.1-pro-highspeed", # 取消這一行的註解,並把上一行註解掉
messages=[{"role": "user", "content": "Summarize this diff"}],
reasoning_effort="medium",
)
print(resp.choices[0].message.content)import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://synthorai.io/v1",
apiKey: "sk-syn-...",
});
const resp = await client.chat.completions.create({
model: "hy4",
// model: "kimi-k3.1-pro-highspeed", // 取消這一行的註解,並把上一行註解掉
messages: [{ role: "user", content: "Summarize this diff" }],
reasoning_effort: "medium",
});
console.log(resp.choices[0].message.content);curl https://synthorai.io/v1/chat/completions \
-H "Authorization: Bearer sk-syn-..." \
-H "Content-Type: application/json" \
-d '{
"model": "hy4",
# "model": "kimi-k3.1-pro-highspeed", # 取消這一行的註解,並把上一行註解掉
"messages": [{"role": "user", "content": "Hello"}],
"reasoning_effort": "medium"
}'package main
import (
"context"
"fmt"
"github.com/openai/openai-go/v3"
"github.com/openai/openai-go/v3/option"
)
func main() {
client := openai.NewClient(
option.WithBaseURL("https://synthorai.io/v1"),
option.WithAPIKey("sk-syn-..."),
)
resp, _ := client.Chat.Completions.New(context.TODO(), openai.ChatCompletionNewParams{
Model: "hy4",
// Model: "kimi-k3.1-pro-highspeed", // 取消這一行的註解,並把上一行註解掉
Messages: []openai.ChatCompletionMessageParamUnion{
openai.UserMessage("Summarize this diff"),
},
ReasoningEffort: openai.ReasoningEffortMedium,
})
fmt.Println(resp.Choices[0].Message.Content)
}import com.openai.client.OpenAIClient;
import com.openai.client.okhttp.OpenAIOkHttpClient;
import com.openai.models.chat.completions.*;
import com.openai.models.ReasoningEffort;
OpenAIClient client = OpenAIOkHttpClient.builder()
.baseUrl("https://synthorai.io/v1")
.apiKey("sk-syn-...")
.build();
ChatCompletion resp = client.chat().completions().create(
ChatCompletionCreateParams.builder()
.model("hy4")
// .model("kimi-k3.1-pro-highspeed") // 取消這一行的註解,並把上一行註解掉
.addUserMessage("Summarize this diff")
.reasoningEffort(ReasoningEffort.MEDIUM)
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));常見問題
Tencent Hy4 和 Kimi K3.1 Pro Highspeed 哪個比較便宜?
以「輸入 / 1M tokens」來看,Tencent Hy4 比較便宜($0.834 對 $4,相差 4.8×)。其他項目的結果可能相反,完整價目請看上表;實際成本要看你的用量組合。
可以只串接一次,就對 Tencent Hy4 和 Kimi K3.1 Pro Highspeed 做 A/B 測試嗎?
可以。兩個模型都走同一個 OpenAI 相容端點,用的也是同一把 API 金鑰,切換時只要改一行裡的模型名稱字串。你可以把一部分流量分別導到兩邊,再直接比較帳單。
Tencent Hy4 與 Kimi K3.1 Pro Highspeed 支援提示詞快取嗎?
支援。兩者的快取讀取費率都低於輸入費率,所以前綴已經進快取的工作負載,實際成本會比官網價算出來的低。確切的快取讀取價格請見上方定價表。