跳转到主内容
AIpricly

Kimi K3 vs GPT-5

Side-by-side pricing, capabilities, real-world cost across common scenarios, and our editorial pick.

添加模型最多可对比 4 个模型
全部价格按美元 / 百万 token 计
OVERALL WINNER

Kimi K3

Moonshot · released 2026-03-15

Quality (AA Index)80
Input price$0.30
Output price$1.20
Context200K
Throughput150 tok/s
P50 latency0.8s

GPT-5

OpenAI · released 2026-01-15

Quality (AA Index)91
Input price$1.25
Output price$10.00
Context400K
Throughput120 tok/s
P50 latency0.7s

链接通过我们的 OpenRouter 推荐链接在新标签页打开。 查看推广披露

规格对比

绿色列 = 该指标获胜方
MetricKimi K3GPT-5Verdict
Input price
/百万 tokens
$0.30$1.25Kimi K3 −76%
Output price
/百万 tokens
$1.20$10.00Kimi K3 −88%
Context window
max input length
200K400KGPT-5 +2.0×
AA Quality
AA Intelligence Index (0–100)
8091GPT-5 +11pt
Arena Elo
LMArena human-pref Elo (800–2000)
Tied
Throughput
tokens per second
150120Kimi K3 +25%
P50 latency
first token
0.8s0.7sGPT-5 −13%
Vision
multimodal
Function calling
tool use
Tied
Reasoning mode
chain-of-thought

常见场景月度费用

默认用量假设
ScenarioKimi K3GPT-5
customer support
1000K req · 600/180 tok
$396$2.5K
chat with docs
300K req · 4000/300 tok
$468$2.4K
code generation
500K req · 2000/500 tok
$600$3.8K
voice assistant
600K req · 800/200 tok
$288$1.8K
Our pick

For most workloads, choose Kimi K3.

  • 76% cheaper input price, which compounds at scale
  • 25% faster throughput — matters for streaming UX and voice agents
Choose GPT-5 instead if: Best across-the-board quality but the most expensive token rate in the table; pick GPT-5 when reasoning depth or function-calling reliability outranks per-million-token spend.

阅读完整深度分析

为何选择?通过智能路由同时使用两者

第二阶段 · 带故障转移链的网关

Set Kimi K3 as primary, GPT-5 as fallback. One key, one bill, automatic failover when Kimi K3 errors.

第二阶段预览 · 网关尚未上线该接口目前不存在。网关计划在第二阶段上线——下面只是规划中的接口形态预览,不是可用的 API。上线时会通过 newsletter 通知订阅者。
查看计划中的 API 调用形态
$ curl https://api.aipricly.com/v1/chat/completions \
  -H "Authorization: Bearer $AIPC_KEY" \
  -d '{
    "routing": {
      "primary": "moonshot/kimi-k3",
      "fallback": ["openai/gpt-5"]
    },
    "messages": [{"role": "user", "content": "..."}]
  }'

Related comparisons