Gemini 4 Carbon vs Kimi K3.1 Pro

vs

什麼情況選哪一個

基礎檔每百萬輸出 token 的價格為 $10 和 $10(gemini-4-carbon 對 kimi-k3.1-pro)。 需直接輸入音訊或影片時選 gemini-4-carbon,並將已公布的調價納入預算。 與 gemini-4-carbon 相比,長程程式設計任務需要讀取截圖並回傳結構化結果時,可評估 kimi-k3.1-pro。

Benchmark 成績

Kimi K3.1 Pro:供應商沒有公布 benchmark 成績。

高於平均沒有模型更高Gemini 4 Carbon12 / 1210 / 12
Gemini 4 Carbon Kimi K3.1 Pro 其他有成績的模型 其他模型平均 ★ 沒有模型分數更高
FrontierSWE 2 Proximal leaderboard, Carbon report
61.2%
N/A
OSWorld 2.1 82 offline tasks, partial score. Gemini: best of 3. Peers: published evaluations
81.5%
N/A
AutomationBench (Zapier) Zapier private set
沒有模型分數更高 53.9%
N/A
GraphWalks BFS (F1) 256k to 1M tokens, 200 tasks, Google evaluation
沒有模型分數更高 96.2%
N/A
Blueprint-Bench 2 Similarity score, Andon Labs leaderboard
沒有模型分數更高 58.6%
N/A
Vending-Bench 2 (USD) Andon Labs leaderboard, Carbon report · 5422-16484
沒有模型分數更高 16484
N/A
Chartography No tools, Carbon report
沒有模型分數更高 72.5%
N/A

供應商公布: Google

定價

Gemini 4 Carbon Kimi K3.1 Pro Δ
輸入 / 1M tokens $2 $2 =
輸出 / 1M tokens $10 $10 =
快取讀取 / 1M tokens $0.1 $0.2 0.5×

費率取自網站建置時的即時目錄;各模型頁面都列有最新的價目。

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

功能

Gemini 4 Carbon Kimi K3.1 Pro
工具使用 是 是
思考控制 一律開啟 是,但供應商未公布調整參數
結構化輸出 是 是
提示詞快取 隱式(自動) 隱式(自動)
快取存活時間 未公布 未公布
最小快取前綴 4,096 個 token 未公布

規格

Gemini 4 Carbon Kimi K3.1 Pro
輸入模態 文字 圖像 音訊 影片 文字 圖像
輸出模態 文字 文字
發布日期 2026-11-10 2026-10-23
知識截止日期 2026-03 -
上下文視窗 1,048,576 1,048,576
最大輸出 65,536 1,048,576
思考參數 thinking_level -
可接受的值
thinking_level
  • low
  • medium
  • high

"minimal" and thinking_budget return 400

-
預設值 medium -

規格摘錄自各供應商的文件;供應商沒有公布的項目就直接略過,不自行推測。 完整來源: Gemini 4 Carbon · Kimi K3.1 Pro

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

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

Gemini 4 Carbon 通過 · 3 sentences

Enabling reasoning instructs the AI to generate a lengthy, behind-the-scenes "thought process" to verify its logic before delivering a final answer. Because our vendor bills us based on total output volume, we are charged for all of that invisible scratchpad work in addition to the visible response, effectively doubling the compute consumed per query. Moving forward, we can control this cost by restricting reasoning strictly to complex, high-stakes workflows where higher accuracy justifies the premium, while routing routine tasks back to standard, lower-cost models.

輸出 908 tok (+799 思考) 延遲 18.0 s

Kimi K3.1 Pro 通過 · 3 sentences

Enabling reasoning makes the model generate extra internal “thinking” tokens before responding, and these are typically billed at output-token rates even though users never see them. If request volume and pricing stayed flat but reasoning substantially increased tokens per request, the total bill could double. Compare pre- and post-change usage reports for reasoning tokens, then control costs with lower reasoning effort, token budgets, cheaper models, and selective use on tasks where the quality gain justifies the spend.

輸出 471 tok (+366 思考) 延遲 14.3 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. 檢查 修正後通過測試

Gemini 4 Carbon 通過 · 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 original function counts the number of matching adjacent *transitions* rather than the number of *elements* in a run because `best` and `cur` are initialized and reset to `0` instead of `1`. Because a single item on its own already forms a run of length `1`, starting at `0` causes every non-empty result to be short by one: single-element lists (where the loop never executes) and lists with no duplicates return `0` instead of `1`, and any run of $k$ equal items—including one ending at the last index—only increments `cur` $k - 1$ times, making it appear as though the final element of the run was missed. […]

輸出 1411 tok (+1131 思考) 延遲 32.7 s

Kimi K3.1 Pro 通過 · 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: best = max(best, cur) cur = 1 return max(best, cur) ``` The original `cur` counts matching adjacent pairs rather than items: it starts at 0, so a singleton returns 0, and a run of `k` equal items is recorded as only `k - 1`. Its bookkeeping also never correctly finalizes the current run’s length at end of input. The fix starts every run at 1, records its length when a mismatch ends it, and takes a final `max` after the loop so a run ending at the last index is included; empty input returns 0.

輸出 2984 tok (+2785 思考) 延遲 70.1 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

Gemini 4 Carbon 通過 · 5/5 fields, guidance null

```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": null, "growth_pct": null, "guidance": null } ```

輸出 3338 tok (+3281 思考) 延遲 61.6 s

Kimi K3.1 Pro 通過 · 5/5 fields, guidance null

{"company":"Meridian Robotics","quarter":"September quarter","revenue_usd_m":412,"growth_pct":11,"guidance":null}

輸出 454 tok (+410 思考) 延遲 12.0 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 個禁用詞

Gemini 4 Carbon 通過 · 120 words, 0 banned, 1 question

Are your engineering teams paying multiple AI vendors to generate identical responses? Today, we are introducing Universal Prompt Caching for our flagship API Gateway. When applications route traffic across providers like OpenAI, Anthropic, and Mistral, duplicate queries drain budgets and degrade user experiences. Our new unified caching layer intercepts incoming prompts directly at the network edge. If an identical request was previously fulfilled by any connected model, the gateway delivers the stored response in milliseconds, completely bypassing external API calls. This practical upgrade cuts monthly token expenses substantially while accelerating overall application speed. Best of all, deployment requires zero complex code changes. Simply activate this capability inside your gateway configuration dashboard today to start reducing latency and infrastructure costs immediately.

輸出 2620 tok (+2480 思考) 延遲 31.1 s

Kimi K3.1 Pro 通過 · 120 words, 0 banned, 1 question

Meet Prompt Cache, our new API gateway feature for caching prompts and responses across model providers. It cuts token spend, lowers latency, and keeps applications responsive during traffic surges. Define cache keys, expiration rules, and tenant boundaries in one policy, then apply them to OpenAI, Anthropic, Gemini, or custom models without changing application code. Encryption, redaction, and immediate purges help protect sensitive data, while metrics reveal hit rates, savings, and performance by endpoint and provider. Need a faster way to handle repeated requests? Serve eligible results from cache and preserve your existing routing, fallback, and retry behavior. Available today in beta, Prompt Cache gives platform teams controls for cost, speed, and reliability, with no extra infrastructure to deploy or maintain.

輸出 2740 tok (+2576 思考) 延遲 55.8 s

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

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

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

from openai import OpenAI

client = OpenAI(
    base_url="https://synthorai.io/v1",
    api_key="sk-syn-...",
)

resp = client.chat.completions.create(
    model="gemini-4-carbon",
    # model="kimi-k3.1-pro",  # 取消這一行的註解,並把上一行註解掉
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

取得 API 金鑰 →

常見問題

Gemini 4 Carbon 和 Kimi K3.1 Pro 哪個比較便宜?

兩者的「輸入 / 1M tokens」同為 $2。其他費率與實際用量仍可能影響總費用。

可以只串接一次,就對 Gemini 4 Carbon 和 Kimi K3.1 Pro 做 A/B 測試嗎?

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

Gemini 4 Carbon 與 Kimi K3.1 Pro 支援提示詞快取嗎?

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

相關比較