Qwen 3.8 Max vs Kimi K3 at a Glance
CategoryQwen 3.8 MaxKimi K3Current statusqwen3.8-max-preview; may change during Preview or be replaced by a production versionReleased model with documented API accessReported total parameters2.4T2.8TArchitecture detailsActive parameters and full MoE configuration not yet disclosedKDA, Attention Residuals, and Stable LatentMoE; 16 of 896 experts activatedContext windowNot clearly disclosed on the current model product page1,048,576 tokensDocumented inputsText and imagesText, images, and videoReasoningAlways on; low, high, or xhigh; default xhighAlways on; low, high, or max; default maxCurrent access modelAlibaba Token Plan and supported coding or agent toolsConventional hosted API, Kimi products, and coding toolsOrdinary per-token priceNot published$3/M fresh input and $15/M output at Moonshot’s current list rateGPT Proto priceNot yet available$2.70/M input and $13.50/M outputOpen-weight status on July 23Announced as coming “soon”; no published date or licenseFull weights announced for July 27; files and license still need verificationBest current fitLow-cost Preview testing in supported coding workflowsProduction applications, multimodal agents, and costed coding workloadsMain riskPreview behavior, access terms, and commercial pricing may changeAlways-on reasoning can increase latency, output tokens, and long-session cost
Alibaba’s own Token Plan documentation says the Qwen Preview may be continually updated and later removed or replaced. Moonshot’s Kimi K3 announcement and API guide disclose substantially more about the model and its current interface.
Why This Is Not an Equal Comparison Yet
Qwen 3.8 Max Is Still a Moving Preview
Alibaba describes Qwen 3.8 Max as a 2.4T model, but the hosted model available today is specifically qwen3.8-max-preview. That suffix matters. Alibaba states that its capabilities may be upgraded throughout the Preview and that the endpoint may later be removed or replaced by a production version.
This makes every current benchmark a dated snapshot. A useful Qwen result should record the test date, endpoint, reasoning level, agent shell, tool permissions, and raw output. Without those details, two people may believe they tested the same model while actually receiving different Preview behavior.
The access terms also limit what developers can conclude from the low launch price. Alibaba’s Personal Token Plan currently offers Qwen 3.8 Max through a Credits-based subscription, but its official terms restrict the key to supported interactive coding and agent tools. Automation scripts, custom application backends, and non-interactive batch calls are prohibited on that plan.
So Qwen is callable. It is not yet a normal pay-as-you-go backend for a customer-facing app.
Kimi K3 Is Available, but Its Open Release Is Not Finished
Kimi K3 is already available through a conventional API. Moonshot documents its 2.8T scale, 1M-token context, native visual understanding, reasoning controls, tool calling, JSON output, and automatic caching. The model activates 16 of 896 experts per token and combines Kimi Delta Attention with Attention Residuals and Stable LatentMoE.
That is a much firmer base for integration. It is not the same as a completed open-source release.
Moonshot says the full model weights will arrive by July 27, 2026. Until the files, model card, and license are actually published, the accurate description is “an announced open-weight release,” not “a model you can already download and self-host.”
This distinction is easy to miss because API availability, open weights, open-source licensing, and practical self-hosting are four separate questions. Kimi currently answers the first. The remaining three still need to be checked after the promised release date.
Coding Comparison: What the 269-File Test Actually Shows
The best current head-to-head evidence is a matched StackPerf architecture test. Both models received the same read-only snapshot of two unfamiliar software projects containing 269 files. They used OpenCode 1.17.13, identical task instructions, the same permissions, a 60-minute limit, and a 65,536-token completion ceiling. Editing, web access, plugins, and subagents were disabled.
The final reports were anonymized before scoring, then checked separately for unsupported claims.
Test resultQwen 3.8 MaxKimi K3Final score80/10083/100Tool calls4453Failed or denied tool calls02, followed by successful recoveryRepository citation occurrences354274Unsupported claim groups after verification77Clearest strengthSystem boundaries and replay metadataRevision, regeneration, and lifecycle state
Where Kimi K3 Did Better
Kimi’s report modeled the editing lifecycle more completely. It tracked revisions, superseded takes, retry attempts, fallback history, artifact hashes, invalidation, editorial selection, and trimming. That made its proposed contract better suited to a system in which one scene may be generated, rejected, revised, and generated again without losing its history.
Kimi also finished sooner and used fewer tokens on the tested route. That result is encouraging for long coding tasks, but it includes the serving system around the model. Kimi ran through a Kimi subscription endpoint, while Qwen ran through Alibaba’s international Token Plan endpoint. Provider capacity, caching, and launch-period traffic all affected the observed result.
My reading is that Kimi won this task because it understood changing state more completely, not because it wrote prettier code or proved itself better at every software task.
Where Qwen 3.8 Max Did Better
Qwen drew a cleaner boundary between the two systems and created a stronger replay record. Its proposed metadata included the model, seed, prompt, references, provider request ID, media location, duration, and cost. Those fields matter when a team needs to reproduce an output or investigate why the same workflow changed after a provider update.
Its tool behavior was also disciplined: 44 tool calls, all successful. Qwen produced the longer report with fewer requests and received a higher tool-use score in the blind review.
The cost of that cleaner architecture was weaker lifecycle modeling. Its contract did not fully cover scene order, revisions, supersession, retry history, or take invalidation. Clean boundaries are valuable. They are not enough when the product’s state keeps changing.
What This Test Cannot Prove
One architecture-analysis run cannot tell us which model produces better frontend code, fixes more real bugs, passes more tests, or needs fewer human corrections over a month of development. It also cannot isolate model intelligence from endpoint performance.
The most important warning is hidden in the factual review: both models cited real repository locations, yet both produced seven groups of claims that went beyond what the code proved. A report can contain hundreds of valid citations and still reach an unsafe conclusion.
That is the real takeaway. Use either model as an engineering assistant. Do not treat either one as its own reviewer.
How Developers Should Test Qwen 3.8 Max Against Kimi K3
Benchmark tables are useful for discovery, but a purchase decision should use your repository, your tools, and your definition of “done.” I would run three matched tasks before moving a production workflow to either model.
TestGive Both ModelsMeasureRepository architecture reviewThe same frozen commit, architecture question, read-only tools, and time limitCorrect file citations, missed dependencies, unsupported claims, and review timeMulti-file implementationThe same issue, tests, writable files, and tool permissionsTests passed, files changed, retries, regressions, and human correctionsVisual frontend repairThe same screenshot, source files, browser tools, and target behaviorVisual match, valid code, repair loops, and final test result
Keep the agent shell and permissions identical. Set a fixed time limit. Record the full model ID and date, especially for Qwen’s moving Preview. Then capture task completion, wall-clock time, input and output tokens, cache hits, failed tool calls, retries, human interventions, and final tests passed.
Do not score an answer because it “looks thorough.” Check whether the patch works and whether the model’s claims survive review.
For high-value architecture decisions, there is another useful pattern: run both models independently, hide their identities during review, and compare their disagreements. The 269-file test produced its strongest design only after combining Qwen’s system boundaries with Kimi’s lifecycle model. Sometimes the right answer to Qwen versus Kimi is both, followed by verification.
Qwen 3.8 Max vs Kimi K3 Pricing and Cost
Kimi K3 Has Predictable Token Pricing
Kimi K3 has an ordinary token-based price. The current GPT Proto Kimi K3 API page lists $2.70 per 1M input tokens and $13.50 per 1M output tokens, 10% below Moonshot’s current $3/$15 list rate.
That makes a basic cost estimate possible before a test begins:
estimated cost = (input tokens ÷ 1,000,000 × $2.70) + (output tokens ÷ 1,000,000 × $13.50)
A run with 200,000 input tokens and 20,000 output tokens would cost about $0.81 at the current GPT Proto rate: $0.54 for input and $0.27 for output. Retries, additional turns, tool results, and retained reasoning history would increase the total.
Predictable does not mean automatically cheap. Kimi always reasons, and reasoning content counts toward token use. Long agent histories can therefore become expensive even when the visible final answer is short.
Qwen 3.8 Max Is Cheaper to Experiment With, but Harder to Budget
Qwen 3.8 Max Preview currently uses subscriptions and Credits rather than a disclosed per-million-token price. Alibaba’s Personal Token Plan lists promotional monthly prices of CNY 39, CNY 139, and CNY 499 for its three tiers. During the Preview, Qwen calls may consume as little as 10% of the standard Credits rate, with an additional time-limited night discount documented for calls between 22:00 and 08:00 UTC+8.
That is attractive for interactive testing. It is not a clean cost comparison.
Credits can vary with token use, caching, reasoning, and tools, so a CNY subscription cannot honestly be converted into a stable $X per 1M tokens figure from the information currently published. The Personal Plan restriction also means that its promotional economics do not represent the cost of running Qwen behind your own application.
Qwen wins on low-cost Preview access. Kimi wins on production cost visibility.
Open Weights and Self-Hosting
The phrase “Chinese open-source AI” needs careful handling in this comparison. As of July 23, neither exact model can be downloaded as a completed public release.
Alibaba’s Qwen 3.8 Max announcement says open weights are coming, but it does not provide a release date, license, or enough deployment detail to confirm whether the exact hosted Max checkpoint will be published. Moonshot provides a firmer date for Kimi K3—July 27—but the actual files and license still need to appear.
Even after weights are published, “open-weight” will only mean that the parameters are available. “Open source” additionally raises questions about the license, training code, data disclosure, and permitted use. “Can run locally” is a hardware question.
Here the scale matters. A 2.4T or 2.8T model is not a normal laptop download. It is reasonable to infer that full-scale self-hosting will be a data-center project even with aggressive quantization and expert parallelism. Teams considering self-hosting should wait for the model cards, supported inference frameworks, memory calculations, and license terms instead of budgeting from total parameter count alone.
Multimodal Inputs, Reasoning, and Agent Behavior
CapabilityQwen 3.8 Max PreviewKimi K3Image understandingDocumentedDocumentedVideo understandingNot clearly documented as a current model inputDocumentedThinking modeAlways onAlways onReasoning levelslow, high, xhighlow, high, maxDefault reasoning levelxhighmaxContext windowNot clearly disclosed on the current product page1,048,576 tokensStructured outputPreview capabilities require continued verificationJSON mode and strict JSON Schema documentedLong tool historiesBehavior may change with the PreviewFull assistant messages, including reasoning content, should be preserved
Qwen’s documented vision support makes it relevant for screenshot-based debugging. Kimi goes further by accepting video, which is useful when the input is a screen recording, animation reference, or product demo that would be difficult to describe frame by frame.
Kimi’s richer documented interface also adds integration work. Its Preserved Thinking behavior means a multi-turn application should return the complete assistant message, including reasoning content and tool calls, rather than keeping only the visible answer. That history occupies context and is billed. The 1M-token window is large, but it is not free storage.
Both models default to their highest reasoning setting. For evaluation, keep those settings consistent. For production, test lower effort on simpler tasks. A model that solves 99% of requests at lower effort may be cheaper and faster than one left at maximum reasoning for every autocomplete, classification, or short transformation.
Which Model Should You Choose?
Your situationBetter current choiceWhyBuilding a customer-facing application nowKimi K3Conventional API and forecastable token priceRunning a long repository task with image or video inputKimi K31M context and documented image/video supportTesting inside Qwen Code, Qoder, or another supported Alibaba toolQwen 3.8 Max PreviewLow promotional Credits consumptionNeed stable repeatable benchmarksKimi K3, for nowQwen’s Preview may change between runsNeed the cleanest architecture and replay metadataTest QwenIt showed a real advantage in the matched architecture reviewNeed strong revision and regeneration handlingTest KimiIt was more complete in the available matched testNeed downloadable weights todayNeitherVerify again after July 27Need to compare several model families behind one accountKimi K3 on GPT ProtoOne key and balance can access the broader model catalog
For an application going live this week, I would choose Kimi K3. It has enough published information to estimate cost, define integration behavior, and repeat a test against a stable model name.
For an internal coding experiment, I would not ignore Qwen. Its Preview handled a long repository analysis with zero failed tool calls and showed better architectural boundaries than Kimi in the matched test. That is a serious capability signal. It is not yet a production contract.
How to Try Kimi K3 Through GPT Proto
Qwen 3.8 Max is not yet available on GPT Proto, so the current integration example uses Kimi K3 only. You can call it through GPT Proto’s OpenAI-compatible Chat Completions endpoint with the kimi-k3 model string:
curl https://gptproto.com/v1/chat/completions \
-H "Content-Type: application/json" \
-H "Authorization: $GPTPROTO_API_KEY" \
-d '{
"model": "kimi-k3",
"messages": [
{
"role": "user",
"content": "Review this migration plan. Identify unsupported assumptions, missing rollback steps, and the tests required before production."
}
]
}'
The endpoint and authorization structure follow the GPT Proto API quickstart. For multi-turn Kimi workflows, preserve the complete assistant message returned by the API, including reasoning and tool-call fields, rather than storing only the final visible text.
You can try the Kimi K3 API, browse 200+ AI models, or use the GPT Proto unified AI API to compare Kimi with other text, image, video, and audio models. When Qwen 3.8 Max is added, the useful test will be the same task, prompt, tool permissions, and scoring method on both model endpoints.
Final Verdict
Qwen 3.8 Max and Kimi K3 appear close enough in coding capability that one small benchmark should not decide the next year of your architecture. Qwen’s cleaner system boundaries and flawless tool execution deserve attention. Kimi’s stronger lifecycle reasoning and three-point lead deserve attention too.
The product decision is clearer. Kimi K3 has a standard API, public token pricing, a documented 1M context window, richer multimodal input, and a specific open-weight date. Qwen 3.8 Max remains a changeable Preview with Credits-based access and incomplete production details.
Kimi K3 is the better model to deploy today. Qwen 3.8 Max may still become the stronger model, but developers should wait for the production endpoint, ordinary pricing, model card, and actual weight release before making that bet.
