DeepSeek vs Kimi vs Qwen API Pricing for Agent Workloads
Route DeepSeek, Kimi, and Qwen by official per-million-token prices, peak windows, cache rules, and region constraints—with failure modes and a fixed-prompt load test.
The spine remains DeepSeek vs Kimi vs Qwen API pricing, context window, and agent workload routing.
This DeepSeek vs Kimi vs Qwen API pricing guide helps cost-sensitive developers choose a default model route for agent and Chinese-language workloads—not another leaderboard post.
When you ship agents or Chinese apps, social rankings are a distraction. Three questions matter: whether official per-million-token prices survive your volume; whether context and cache rules match the job; and whether region plus billing can actually land. This comparison uses official pricing pages observed on 2026-09-20 to route DeepSeek, Kimi, and Qwen (Tongyi Qianwen).
Cost-first general chat and tool calls: start with DeepSeek
DeepSeek’s official pricing page lists deepseek-flash and deepseek-v4-pro per 1M tokens, with peak/off-peak and cache-hit rates. For example, flash off-peak cache-miss input is about $0.15 and output about $0.60; peak rates are roughly double. Pro is higher off-peak and carries a lower concurrency limit. Peak hours are documented as 01:00–04:00 and 06:00–10:00 UTC, Monday through Friday, excluding Chinese public holidays; all other hours are off-peak. That fits pushing volume inside a budget if you can account for UTC peak windows.
Do not read input price alone. Tool calls, retries, and longer answers push the bill toward output. If most jobs are short and your system prompt caches well, flash plus cache hits is usually the cheapest controllable tier among the three.
Ultra-long context and flagship reasoning: look at Kimi
Kimi’s docs list kimi-k3 at $3.00 input and $15.00 output per 1M tokens, with cached input at $0.30 and roughly a 1,048,576-token context, plus cache-write charges and 5-minute / 1-hour TTL tiers. Unit price is higher than DeepSeek’s flash tier, but long-document and long-horizon coding work often lands here. K2-series models are cheaper with about 262K context and can serve as a downgrade sidecar—keep flagship and flash rows on separate budget lines.
Write “how much source text must fit in one request” as a hard constraint. If most calls stay far below 100K tokens, paying for a million-token window is usually waste.
Alibaba Cloud ecosystem and regional quotas: look at Qwen
Qwen is billed through Alibaba Cloud Model Studio / DashScope. International docs list tiers such as qwen3.7-max around $2.5 input / $7.5 output per 1M tokens, and newer qwen3.8-max international around $2 / $6, with notes that some free quotas are region-limited. China (Beijing) list prices for equivalent classes are often lower, but endpoints, invoicing, and compliance differ. If you already run on Alibaba Cloud and need invoices plus same-cloud networking, integration cost can beat “cheapest absolute model.”