Tencent Hy4 vs Kimi K3.1 Pro Highspeed
什么时候选哪个
两者都接收图文输入。优先控制 token 成本时从 hy4 开始,若更快的交互响应值得更高费率,再试 kimi-k3.1-pro-highspeed。
价格
| Tencent Hy4 | Kimi K3.1 Pro Highspeed | Δ | |
|---|---|---|---|
| 输入 / 1M token | $0.834 | $4 | 0.21× |
| 输出 / 1M token | $2.501 | $20 | 0.13× |
| 缓存读取 / 1M token | $0.042 | $0.2 | 0.21× |
价格取自构建时的实时目录,最新价格见各模型页面。
两个模型所处的位置:全部 86 个按同一单位计费的聊天模型的每 1M token 输入价分布(对数刻度)
能力
| 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,高亮的那两行是唯一要改的地方。端点不变,API key 不变,请求结构也不变。
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 token」算,Tencent Hy4 更便宜($0.834 对 $4,相差 4.8×)。其他计费项的结论可能相反,完整价格见上方表格,实际成本取决于你的用量构成。
不用分别集成两次,就能对 Tencent Hy4 和 Kimi K3.1 Pro Highspeed 做 A/B 测试吗?
可以。两个模型走同一个 OpenAI 兼容端点,用同一个 API key,切换时只要改一行里的模型名,所以可以给两个模型各分一部分流量,直接对比账单。
Tencent Hy4 和 Kimi K3.1 Pro Highspeed 支持提示词缓存吗?
支持。两个模型的缓存读取价都低于各自的输入价,所以前缀能反复命中缓存的负载,实际成本会比按官网价估算的低。具体的缓存读取价见上方价格表。