DeepSeek-OCR is a vision-language model launched by DeepSeek AI, focusing on optical character recognition (OCR) and “contextual optical compression.” The model is designed to explore the limits of compressing contextual information from images, efficiently processing documents and converting them into structured text formats such as Markdown. The model requires an image as input.
DeepSeek-OCR vs kimi-k3
Output tokens cost $0.02 per million on DeepSeek-OCR and $15.00 per million on kimi-k3. Input tokens cost $0.02 per million on DeepSeek-OCR and $3.00 per million on kimi-k3. Cached input tokens are billed at $0.02 per million on DeepSeek-OCR and $0.30 per million on kimi-k3. Context lengths are 8,000 tokens on DeepSeek-OCR and 1,048,576 tokens on kimi-k3. Time to first token (TTFT) measured on AIHubMix is 1.7s on DeepSeek-OCR and 12.9s on kimi-k3. Measured output throughput is 105.2 tok/s on DeepSeek-OCR and 18.8 tok/s on kimi-k3.
Kimi K3 is Kimi’s flagship model for long-horizon coding and end-to-end knowledge work, with a 1M-token context window and industry-leading intelligence.
Pricing & Specifications
Prices are per million tokens. Time to First Token and throughput are rolling averages measured on AIHubMix.
Promotional prices show the discounted rate; see each model page for promotion windows.
Activity Past 30 Days
Daily traffic served through AIHubMix — how demand for each model is trending.
Tokens / day
Requests / day
Performance Past 3 Days
Measured on real AIHubMix traffic, hourly buckets. Gaps mean no traffic in that hour.
Throughput (tok/s)
TTFT (s)
Uptime (%)
Cost calculator
Estimate your monthly bill for the same workload on each model.
Monthly = daily × 30. Discounted rates applied where a promotion is active.
FAQ
Which is cheaper: DeepSeek-OCR, kimi-k3?
DeepSeek-OCR: $0.02/M output tokens; kimi-k3: $15.00/M. Use the cost calculator above to estimate your own workload.
Which responds faster?
DeepSeek-OCR: 1.7s time to first token measured on AIHubMix; see the live performance charts above for how each model behaves across the day.
How large is each context window?
DeepSeek-OCR accepts 8,000 and kimi-k3 accepts 1,048,576 input tokens.
Which one generates tokens faster?
DeepSeek-OCR at 105.2 tok/s and kimi-k3 at 18.8 tok/s, measured as output throughput on AIHubMix — a separate metric from time to first token.
What inputs and capabilities does each model support?
DeepSeek-OCR accepts text and image input; kimi-k3 accepts text, image and video input and supports thinking, function calling and structured outputs.
Can I call DeepSeek-OCR and kimi-k3 with the same API key?
Yes. AIHubMix serves every model on this page behind one OpenAI-compatible endpoint, so switching between them is a one-line change to the model field — no second account, key or SDK.
Popular comparisons
Related model match-ups readers also look at.
