90 days of the enterprise, pro and team plans free, no card needed. See the plans
Model comparison
DeepSeek's DeepSeek V4.1 Flash 1017 against Moonshot AI's Kimi K3: vendor list prices, limits, abilities and the Artificial Analysis indexes side by side - and what OpenSmartRoute does when both are available.
DeepSeek V4.1 Flash 1017 lists at $0.262 per million tokens blended against $5.17 for Kimi K3 - 20x less.
Kimi K3 scores 44 on the intelligence index against 40 - 4 points apart.
DeepSeek V4.1 Flash 1017 was released about 3 months later.
Vendor list prices per million tokens and published limits; indexes are Artificial Analysis composites (0-100).
| Specification | DeepSeek V4.1 Flash 1017 | Kimi K3 |
|---|---|---|
| Input price / 1M tokens | $0.15 | $0.23 |
| Output price / 1M tokens | $0.60 | $20.0 |
| Blended (3 in : 1 out) | $0.26 | $5.17 |
| Cached input / 1M | $0.003 | $0.22 |
| Context window | 1.0M | 1.0M |
| Max output | 393K | 944K |
| Input | text, image | text, image, video |
| Output | text | text |
| Tool calls | ||
| Structured output | ||
| Reasoning | ||
| Open weights | ||
| Intelligence index | 40 | 44 |
| Coding index | - | 76 |
| Agentic index | - | 50 |
| Released | Oct 17, 2026 | Jul 16, 2026 |
| Available on this deployment |
List price times tokens for three typical workloads; your mix of input and output decides which model's pricing suits you.
| Workload | DeepSeek V4.1 Flash 1017 | Kimi K3 | Difference |
|---|---|---|---|
| Support chat20M tokens in, 5M out a month - a help desk answering a few thousand conversations. | $6.00 | $105 | $98.62 less on DeepSeek V4.1 Flash 1017 |
| Document summaries100M in, 5M out - long inputs, short answers. | $18.00 | $123 | $105 less on DeepSeek V4.1 Flash 1017 |
| Coding assistant60M in, 20M out - a team's editor assistant, output-heavy. | $21.00 | $414 | $393 less on DeepSeek V4.1 Flash 1017 |
DeepSeek V4.1 Flash 1017 takes the short and general requests - at $0.262 blended it is the default - and Kimi K3 the ones whose complexity or quality floor rules the cheaper model out. The split is per request, not per app, and every decision carries the scores for both.
# targets.yaml - both models as routing targets (metadata.model links each to the catalogue entry)
targets:
- { id: deepseek-v4.1-flash-1017, kind: llm, metadata: { model: deepseek/deepseek-v4.1-flash-1017 } }
- { id: kimi-k3, kind: llm, metadata: { model: moonshotai/kimi-k3 } }
# rules.yaml - the cheaper model by default, the stronger one when the request is hard
rules:
- name: simple-requests-stay-cheap
when: { max_complexity: 0.45 }
prefer: [deepseek-v4.1-flash-1017]
weight: 0.8
- name: hard-requests-escalate
when: { min_complexity: 0.45 }
prefer: [kimi-k3]
weight: 0.8Every DeepSeek and Moonshot AI model, with prices, is on the vendor pages; the rankings show what the router actually picks.