Kimi K2.7 Code vs Qwen3.8 Max
什么时候选哪个
kimi-k2.7-code 在价目表的每一行都更便宜，输入 $0.95 对 $2（低约 2.1 倍）、输出 $4 对 $6，而且它独有地在文本和图像之外还接受视频，尽管它的思考模式无法关闭。qwen3.8-max 每 token 更贵，但换来约 3.8 倍的上下文（983616 token）、131072 token 的最大输出（是 Kimi 的 32768 的 4 倍），以及明确的长上下文和视觉标志。常规大小输入上的大批量编码与推理，或视频输入工作选 kimi-k2.7-code；整个代码库或超长生成必须装进一次调用时选 qwen3.8-max。
Benchmark 成绩
供应商公布： Alibaba (Qwen) Anthropic ByteDance DeepSeek Google MiniMax Moonshot OpenAI Tencent Z.ai
价格
| Kimi K2.7 Code | Qwen3.8 Max | Δ | |
|---|---|---|---|
| 输入 / 1M token | $0.95 | $2 | 0.47× |
| 输出 / 1M token | $4 | $6 | 0.67× |
| 缓存读取 / 1M token | $0.19 | $0.25 | 0.76× |
| 缓存写入 | - | 1.25x | - |
价格取自构建时的实时目录，最新价格见各模型页面。
两个模型所处的位置：全部 76 个按同一单位计费的聊天模型的每 1M token 输入价分布（对数刻度）
能力
| Kimi K2.7 Code | Qwen3.8 Max | |
|---|---|---|
| 工具调用 | 是 | 是 |
| 思考控制 | 始终开启 | 是，但供应商未公布调节参数 |
| 结构化输出 | - | 是 |
| 提示词缓存 | 隐式（自动） | 隐式 + 显式 |
| 缓存有效期 | 未公布 | explicit: 5m, reset on hit |
| 最小缓存前缀 | 未公布 | 1024 个 token |
规格
| Kimi K2.7 Code | Qwen3.8 Max | |
|---|---|---|
| 输入模态 | 文本 图像 视频 | 文本 图像 |
| 输出模态 | 文本 | 文本 |
| 发布日期 | 2026-06 | 2026-08-03 |
| 上下文窗口 | 256K | 984K |
| 最大输出 | 33K | 131K |
| 思考参数 |
| - |
| 可选值 | type
keep
| - |
| 默认值 | thinking on with Preserved Thinking on | - |
规格照录自各供应商的文档；供应商没有公布的项目，对应的行直接省略，不做推断。 完整来源： Kimi K2.7 Code · Qwen3.8 Max
同一条提示词，两个模型，经网关实测
Kimi K2.7 Code 通过 · 3 sentences
Enabling reasoning mode causes the model to generate an internal chain-of-thought before producing each answer, and that hidden reasoning text is billed like any other output. Those extra reasoning tokens typically add up to much more than the final response itself, so every API call now costs significantly more than before. Because our overall usage volume did not change, the doubled bill reflects that each query consumes roughly twice as many billable tokens.
输出 259 tok (+174 思考) 延迟 5.4 s
Qwen3.8 Max 通过 · 3 sentences
Enabling reasoning makes the model produce additional hidden steps before responding, and those tokens are billable. It also tends to lengthen each interaction because the model works through more possibilities before settling on an answer. Therefore, the bill doubled mainly due to higher compute and token usage per request, not necessarily because the number of requests doubled.
输出 378 tok (+305 思考) 延迟 8.6 s
指令遵循（恰好三句，数得出来）、受众适配（对 CFO 说话的口吻），以及下方 token 计数暴露出的隐藏思考计费差额。
Kimi K2.7 Code 通过 · 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 best = max(best, cur) else: cur = 1 return best ``` The bug is that the function counts *transitions* between equal neighbors instead of counting the items themselves, so a single-element list never enters the loop and returns `0` instead of `1`. Likewise, resetting `cur` to `0` on a mismatch forgets the current item that starts a new run, which causes runs that end at the last index to be undercounted. Initializing both `best` and `cur` to `1` and resetting `cur` to `1` fixes both issues.
输出 410 tok (+222 思考) 延迟 9.4 s
Qwen3.8 Max 通过 · 8/8 cases
```python def longest_run(xs): if not xs: return 0 best = 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 the original code starts `best` and `cur` at `0`, so it counts adjacent equal *transitions* rather than the number of items in the run. A run of length `n` has only `n - 1` equal-neighbor transitions, so single-element inputs return `0`, and runs that reach the end are undercounted by one. Initializing the current run to `1` for the first element, resetting it to `1` on a break, and updating `best` from that count fixes the off-by-one.
输出 1616 tok (+1411 思考) 延迟 34.7 s
修复是否真的正确（能运行）、解释的信息密度，以及在一个范围明确的任务上的 token 效率。
Kimi K2.7 Code 通过 · 5/5 fields, guidance "withheld pending the Q4 close"
```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": "withheld pending the Q4 close" } ```
输出 721 tok (+663 思考) 延迟 13.2 s
Qwen3.8 Max 通过 · 5/5 fields, guidance null
{ "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": null }
输出 1199 tok (+1141 思考) 延迟 24.4 s
是否严守 schema（不臆造字段）、能否顶住幻觉压力（原文明说暂不给出 guidance），以及结构化输出路径的差异。
Kimi K2.7 Code 通过 · 120 words, 0 banned, 1 question
We're introducing Prompt Cache for our API Gateway, a new capability that stores prompt responses across multiple AI providers. By caching replies, you reduce redundant calls, lower latency, and cut costs without changing how you build. Teams using several model providers can now reuse identical prompt results instantly, keeping traffic consistent and budgets predictable. Responses are keyed by provider, model, and exact prompt, so you always get the right result. Configure TTL, hit thresholds, and eviction rules from a single dashboard. It fits into your existing routing and requires no code changes. Setup takes minutes and works with your current endpoints. Want to see how much latency and spend you can trim? Check the docs to enable Prompt Cache today.
输出 2375 tok (+2235 思考) 延迟 38.6 s
Qwen3.8 Max 通过 · 120 words, 0 banned, 1 question
Today, our API gateway adds prompt caching across major model providers. It stores prompts and responses in one fast cache layer. Teams can lower token spend, reduce latency, and repeat reliable answers. The feature supports OpenAI, Anthropic, Google, and Mistral through one configuration. You can set retention rules, scope access, and invalidate entries quickly. How does your team maintain consistent results during provider outages? Approved cached responses keep applications stable while fallback routes recover. The dashboard shows hit rates, savings, latency, and provider usage. Engineers receive audit trails for every cached prompt, enabling safer testing. Product managers can compare cost trends before and after cache adoption. Start with a small route, then safely expand caching to production traffic right now.
输出 2744 tok (+2591 思考) 延迟 46.3 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="kimi-k2.7-code",
# model="qwen3.8-max", # 取消注释此行，注释上一行
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: "kimi-k2.7-code",
// model: "qwen3.8-max", // 取消注释此行，注释上一行
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": "kimi-k2.7-code",
# "model": "qwen3.8-max", # 取消注释此行，注释上一行
"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: "kimi-k2.7-code",
// Model: "qwen3.8-max", // 取消注释此行，注释上一行
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("kimi-k2.7-code")
// .model("qwen3.8-max") // 取消注释此行，注释上一行
.addUserMessage("Summarize this diff")
.reasoningEffort(ReasoningEffort.MEDIUM)
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));常见问题
Kimi K2.7 Code 和 Qwen3.8 Max 哪个更便宜？
按「输入 / 1M token」算，Kimi K2.7 Code 更便宜（$0.95 对 $2，相差 2.1×）。其他计费项的结论可能相反，完整价格见上方表格，实际成本取决于你的用量构成。
不用分别集成两次，就能对 Kimi K2.7 Code 和 Qwen3.8 Max 做 A/B 测试吗？
可以。两个模型走同一个 OpenAI 兼容端点，用同一个 API key，切换时只要改一行里的模型名，所以可以给两个模型各分一部分流量，直接对比账单。
Kimi K2.7 Code 和 Qwen3.8 Max 支持提示词缓存吗？
支持。两个模型的缓存读取价都低于各自的输入价，所以前缀能反复命中缓存的负载，实际成本会比按官网价估算的低。具体的缓存读取价见上方价格表。