Kimi K3 Resets the AI Price Curve: From Kimi Linear to HBM and Big Tech Strategy

Fri, 17 Jul 2026 12:31:36 +0900

Kimi K3 launched on July 16, 2026 at $3 per million uncached input tokens and $15 per million output tokens. That is not the familiar ultra-low-price positioning of a Chinese challenger. It matches Claude Sonnet 5’s standard price and sits 40% below GPT-5.6 Sol on input and 50% below it on output. Moonshot AI is positioning K3 as a primary enterprise model, not a budget fallback.

The architecture is designed to support that claim. K3 has 2.8 trillion total parameters but effectively activates 16 of 896 experts per token. Kimi Delta Attention controls the cost of long context, Attention Residuals selectively retrieve earlier representations across depth, and quantization-aware training uses MXFP4 weights with MXFP8 activations. Moonshot recommends a supernode with at least 64 accelerators.

That combination creates a two-sided semiconductor outcome. Memory and compute per token can fall while the number of institutions able to deploy a frontier-class model, and the amount of work they run, can rise. K3 is both an efficiency technology and an infrastructure workload.

Related reading: AI token value and memory value capture / AI token futures and cost per token / US-China divergence in agentic inference infrastructure / Cross-checking the 2030 HBM shortage model

Executive Summary

K3 combines 2.8T parameters, native vision and a 1M-token context window. Its products and API are live, but as of July 17 the full weights, technical report and license have not been released. The open-weight thesis must be verified after the July 27 deadline.
Moonshot’s official GDPval-AA v2 score is 1,668, not 1,687. AA-Briefcase is 1,548. BrowseComp 91.2 uses context compaction; the no-compaction 1M-context result is 90.4. The results are strong, but mixed harnesses and company-run evaluations require independent replication.
Kimi Linear’s claims of up to 75% lower KV cache and up to 6.3x theoretical decoding throughput at 1M context come from a 48B-total, 3B-active research model. They should not be presented as measured K3 API performance.
K3 is not a low-cost model. It matches Sonnet 5’s standard price, is 50% more expensive than Sonnet’s temporary launch promotion, and is cheaper than GPT-5.6 Sol. Because only max reasoning is currently available and independent tests show high output-token use, cost per completed task may be less attractive than the rate card implies.
The semiconductor impact pits lower compute and KV cache per request against more self-hosted deployments and higher total workload. Server DRAM and enterprise SSDs are the cleanest second-order beneficiaries because long-lived agent context spills below HBM into disaggregated cache tiers.
The model and cloud layers experience opposite economics. OpenAI, Anthropic and Gemini API pricing face pressure, while Azure, AWS and Google Cloud can monetize K3 and other models through compute, storage and networking. Meta must defend US open-weight leadership.
The July 27 proof points are the license, full weights, external evaluation, throughput on NVIDIA and AMD, support on Chinese accelerators, actual output tokens per task, vLLM compatibility and cloud catalog adoption.

1. Correcting the Numbers Before Drawing Conclusions

Several numbers changed as the launch circulated through social media. The official values matter because some differences alter the investment interpretation.

Item	Official value	Investor interpretation
Total parameters	2.8T	Total model size, not per-token active compute
Expert routing	16 of 896	Extremely sparse MoE; routing and communication become first-order constraints
Context	1M tokens	Useful for repositories and research, but task cost depends on output length and cache hits
GDPval-AA v2	1,668	The official table does not show 1,687
AA-Briefcase	1,548	Above GPT-5.6 Sol at 1,495, below Claude Fable 5 at 1,583
BrowseComp	91.2	Uses compaction starting at 300K tokens
BrowseComp without compaction	90.4	The cleaner result for the native 1M-context claim
Product availability	Web, Work, Code and API live	Commercial testing can begin now
Weights	Promised by July 27	License and complete artifacts remain unverified as of July 17
Reasoning effort	Max only	Low-cost modes are not yet available

Moonshot explicitly states that K3 still trails Claude Fable 5 and GPT-5.6 Sol in overall user experience. At the same time, it reports frontier-level performance across coding, knowledge work and multimodal benchmarks. The credible interpretation is not that China has conclusively taken the lead. It is that a Chinese model has entered the performance band immediately below the strongest proprietary systems while promising a 1M context and downloadable weights.

The benchmark table is not a single controlled tournament. K3 runs at maximum reasoning effort. Depending on the task, models use Kimi Code, Claude Code or Codex, and some competitor scores are the best results across harnesses or are imported from external leaderboards. Independent reproduction remains necessary.

Still, Terminal-Bench 2.1 at 88.3, FrontierSWE at 81.2, SWE Marathon at 42.0, AutomationBench at 30.8, GPQA-Diamond at 93.5 and MMMU-Pro at 81.6 indicate that K3 is designed for long-horizon tool use and coding, not merely chat. The more important signal is the package: near-frontier capability, 1M context and promised open weights.

2. How a 2.8T Model Becomes Deployable

2.1 Total parameters are not active parameters

Computing all 2.8T parameters for every token would be prohibitively expensive. Stable LatentMoE effectively activates 16 of 896 experts, or about 1.8% of the expert pool. The technical report is needed to establish exact active parameter counts, but total parameters clearly do not equal per-token compute.

Sparse MoE shifts rather than eliminates bottlenecks.

What improves	What becomes harder
Active compute per token	Router quality and expert balance
Compute needed for a quality target	Communication across accelerators
Some inference costs	Avoiding idle accelerators and hot experts
Scaling model capacity	Keeping the full weight set accessible

This is why Moonshot recommends a supernode with 64 or more accelerators. Even when only a small subset of experts is active, the selected expert is not known in advance and the full model must remain accessible. At four bits, 2.8T weights imply a theoretical minimum of about 1.4 TB before scales, metadata, buffers, cache and replication. Sparse activation reduces arithmetic but does not remove model-residency memory or fabric requirements.

2.2 Kimi Linear addresses long-context cost

The Kimi Linear paper predates K3 and evaluates a 48B-total, 3B-active research model, not K3 itself. It combines Kimi Delta Attention with full Multi-head Latent Attention in a 3:1 ratio.

Full attention is strong at exact copying and fine-grained retrieval, but KV cache grows with context. Linear attention compresses history into a fixed-size state, reducing sequence-length dependence, but can lose exact detail. Kimi Linear uses three KDA layers followed by one full-attention layer to balance efficiency and expressiveness.

Component	Role	Trade-off
KDA	Compress long history into fixed-size state	Can weaken exact copying and fine retrieval
Full MLA	Restores precise token-to-token recall	KV cache still grows with context
3:1 hybrid	Balances efficiency and quality	Requires more complex kernels and serving software

The paper reports up to 75% lower KV cache and up to 6.3x theoretical decoding throughput at 1M context. A measured comparison in the complexity analysis reports 2.3x acceleration. These results establish direction, not guaranteed K3 API performance.

For investors, lower KV cache means more concurrent requests per accelerator. It also makes longer repositories, more documents and persistent agents economical. Memory per token can fall while total tokens rise.

2.3 Attention Residuals improve depth efficiency

Standard residual connections keep adding earlier layer outputs. In very deep networks, useful representations can be diluted. Attention Residuals allow a layer to select the earlier representations it needs. Block AttnRes groups layers and retains block-level representations, reducing memory overhead.

Moonshot’s research says roughly eight blocks recover most of the gains, and Block AttnRes can match a baseline trained with about 1.25x compute. This improves training capital efficiency, but it does not automatically reduce data-center demand. Better efficiency can be reinvested into larger models and longer tasks.

2.4 Quantization is a hardware-portability strategy

K3 applies quantization-aware training from supervised fine-tuning onward, using MXFP4 weights and MXFP8 activations. This should control accuracy loss better than aggressive post-training quantization and make deployment across multiple hardware platforms easier.

Moonshot’s kernel arena included NVIDIA H200 and a general-purpose GPU from an alternative vendor. The official post does not name a Chinese chip or claim H200-equivalent economics. What is verified is the strategic intent to optimize outside NVIDIA as well as on NVIDIA.

That matters for both China and global buyers. China needs frontier-level models that can survive constrained access to top NVIDIA systems. Other buyers want bargaining power across NVIDIA, AMD and custom accelerators.

3. What the Price Card Reveals

3.1 K3 is priced as a primary model

Model	Cached input per 1M	Standard input	Output	Current positioning
Kimi K3	$0.30	$3	$15	Frontier primary-model pricing
Claude Sonnet 5 launch promo	Varies	$2	$10	Temporary through August 31
Claude Sonnet 5 standard	Varies	$3	$15	Same headline price as K3
GPT-5.6 Sol	$0.50	$5	$30	67% higher input and 100% higher output than K3

K3 is more expensive than Sonnet 5’s current promotion. It is inaccurate to describe it as universally half-price. The clearer strategy is to match Sonnet’s standard tier while undercutting the most expensive frontier API.

The price is both a confidence signal and a monetization decision. Moonshot is no longer accepting a deep discount simply to acquire usage. It is claiming a position in the enterprise default-model tier.

3.2 Cost per completed task matters more than cost per token

Rate cards assume equal token use. Agents differ in planning length, tool calls, retries and verbosity. K3 currently exposes only max reasoning. Artificial Analysis reports that K3 used about 130 million output tokens in its Intelligence Index evaluation, more than twice the peer median of roughly 63 million. A cheaper output token can still lead to a costly completed task.

Task cost = input tokens × input rate + output tokens × output rate + tool and retry cost

Enterprise buyers will monitor task success, output tokens, time to first token, throughput, tool reliability, cache hit rate and session stability. Moonshot says Mooncake delivers more than 90% cache hits on coding workloads, making cached input one-tenth the uncached price. If that rate holds on enterprise traffic, K3’s effective economics improve materially.

3.3 Mooncake moves memory demand down the hierarchy

Mooncake separates prefill and decode clusters and disaggregates KV cache across CPU, DRAM and SSD rather than keeping everything in GPU HBM. Its paper reports up to 525% higher throughput in simulation and 75% more requests on production workloads.

This explains why AI memory demand extends beyond HBM.

Accelerator HBM → server DRAM → enterprise SSD → remote cache tier

KDA can reduce KV cache per request, yet persistent 1M-context agents increase total cache volume and retention time. Hot data remains in HBM and DRAM; colder context moves to SSD. Efficiency can soften an HBM-only thesis while strengthening the broader memory hierarchy.

4. Chinese Open Weights Move Up the Enterprise Stack

OpenRouter reports that Chinese models surpassed US models in token share on its platform in early June 2026, based on more than 450 trillion tokens from January through June 14. DeepSeek’s share rose from roughly 9% to 18% and it became the leading provider by mid-May.

The adoption path has three stages:

Low-cost open models take classification, translation and testing workloads.
Better coding and agent performance take repetitive enterprise workflows.
Near-frontier quality and million-token context compete for primary routing.

K3’s price is designed for the third stage. It is not following the most aggressive low-price strategy. It is charging a frontier-tier API price while promising weights that clouds, governments and enterprises can deploy themselves.

Proprietary APIs and open weights accumulate different strategic assets.

Proprietary frontier API	Near-frontier open weights
Controls the best UX and capability	Multiplies deployment routes and hardware options
Centralizes usage data	Lets enterprises retain data and operations
Changes pricing and policy centrally	Released files are difficult to withdraw
Model provider captures gross margin	Cloud, chip and application vendors share value

The strongest proprietary model can remain number one while losing paid token share. Enterprises can route repetitive work to K3-class models and reserve the most difficult legal, design and research tasks for the top closed model. Paid token mix and blended price matter more than leaderboard rank.

5. Semiconductor Demand: Efficiency and Diffusion Arrive Together

5.1 NVIDIA: near-term efficiency risk, medium-term deployment elasticity

Sparse MoE, KDA, quantization and autonomous kernel optimization reduce GPU time per task. Hardware portability also weakens the assumption that every frontier workload must stay on CUDA. Those are negative valuation signals for NVIDIA.

The positive side is equally material. Moonshot recommends at least 64 accelerators for self-hosted K3. Released weights could drive clouds, governments, laboratories and large enterprises to build their own clusters. Demand concentrated behind one API becomes hardware demand across many data centers.

Total accelerator demand = lower GPU time per task × higher total workload × more self-hosting institutions

The first term is negative; the last two are positive. K3 alone is not enough to cut NVIDIA earnings estimates, but neither is it enough to assume that every efficiency gain creates more GPU demand. Workload elasticity is the deciding variable.

5.2 AMD: optionality from hardware choice

AMD benefits if MXFP4, MXFP8 and vLLM portability allow enterprises to separate model choice from accelerator choice. A near-frontier open model gives buyers a realistic workload on which to test NVIDIA alternatives.

The proof must come after the weights. ROCm kernels, expert-parallel communication, 1M-context throughput and 64-accelerator stability need to be measured. AMD’s upside grows only if K3 demonstrates superior cost per successful task on MI systems.

5.3 HBM: lower per-request cache, larger model residency

Demand layer	K3 efficiency impact	Direction
Weight residency	A 2.8T model must remain quickly accessible	More accelerators and high-bandwidth memory
Per-request KV cache	KDA lowers cache size and growth	Less HBM capacity per request
Concurrent users and agents	Lower cost and open deployment can expand workloads	More total HBM and DRAM

The headlines can be negative for SK hynix, Micron and Samsung because 75% lower KV cache and 6.3x throughput sound like lower memory intensity. Those numbers belong to a Kimi Linear research model, not measured K3 production. HBM also stores weights, activations, communication buffers and batches, not only KV cache.

The medium-term balance is neutral to positive if self-hosted clusters and agent workloads grow faster than efficiency. It turns negative if workload elasticity is weak and compression improves faster than usage.

5.4 Server DRAM and enterprise SSDs are the clearest second-order beneficiaries

Long context and cache reuse cannot remain entirely in HBM. Once serving separates prefill and decode and spills cache across CPU, DRAM and SSD, server DRAM and enterprise SSD become operating assets for AI inference.

Samsung can sell HBM, server DRAM, high-capacity SSDs, foundry and packaging.
SK hynix combines HBM and server DRAM with Solidigm enterprise SSDs.
Micron supplies HBM, data-center DRAM and SSDs.

K3 does not show that AI needs less memory. It shows that AI memory is becoming hierarchical. The hottest data stays in HBM, retained context sits in server DRAM, and colder cache moves to enterprise SSD. Vendors with a full memory stack have greater resilience than a single-product HBM thesis.

5.5 Networking and custom silicon are the hidden MoE bottlenecks

Spreading 896 experts across accelerators creates variable communication depending on token routing. This is why Moonshot emphasizes balanced expert-parallel training, static shapes and removal of host synchronization from the critical path. Efficient operation across 64 or more accelerators requires high-bandwidth scale-up and scale-out fabric.

That is structurally positive for Broadcom, Marvell, NVIDIA networking, optical interconnect and switch silicon. It also encourages inference ASICs optimized for open models. K3’s 48-hour small-chip design exercise is not a commercial product, but it illustrates faster model-hardware co-design.

6. US Big Tech Strategy and Stock Transmission

6.1 Microsoft: pressure on OpenAI economics, more Azure usage

Microsoft owns exposure to OpenAI IP and economics as well as Azure infrastructure. The April 2026 partnership update keeps Microsoft as a primary cloud partner and extends a non-exclusive IP license through 2032.

K3 pressures the model layer because repetitive work can move away from OpenAI APIs. It can support the cloud layer if Azure hosts K3 as managed or self-hosted infrastructure.

Microsoft layer	K3 impact
OpenAI revenue share	Negative through price and mix
Copilot	Positive if routing costs fall
Azure AI	Positive if multi-model usage rises
Custom silicon and data centers	Positive if open-weight optimization expands

The near-term stock impact is neutral. The medium-term question is whether Azure converts model price deflation into usage and Copilot margin.

6.2 Amazon: Anthropic and AWS have different economics

Amazon is a major Anthropic investor and the provider of AWS, Bedrock, Trainium and Inferentia. K3 can reduce Claude pricing power and the value of Amazon’s Anthropic stake. If enterprises run K3 on AWS, however, EC2, Bedrock, storage, networking and Trainium usage can rise.

Amazon’s optimal strategy is to keep the workload on AWS regardless of which model wins. If K3 arrives with a permissive license and efficient Trainium support, AWS can monetize a competitor’s diffusion. The stock impact is neutral to modestly positive, although inference price competition could lower cloud margins even as revenue grows.

6.3 Alphabet: Gemini pricing pressure, TPU and Vertex defense

Google controls a model, a chip, a deployment platform and final demand through Search, Ads and Workspace. Vertex Model Garden supports first-party, third-party and open models.

K3 pressures Gemini API pricing but can create TPU and Google Cloud demand. Lower model cost also reduces the expense of AI Overviews, ad generation and Workspace agents. The stock impact is neutral to positive because Google is not solely a model vendor. The risk is that Gemini loses both performance and price leadership, raising cloud customer-acquisition cost.

6.4 Meta: from open-weight beneficiary to defender

Meta benefited from open-weight diffusion by commoditizing competitors’ APIs and lowering its own recommendation, advertising and content costs. If Chinese labs release near-frontier capability and longer context first, Meta risks losing its position as the benchmark US open-weight ecosystem.

K3 forces two responses: the next Llama must compete on long context, agent tools and deployment cost, and Meta must provide a trusted US alternative for enterprises and governments unwilling to deploy Chinese weights. The near-term earnings impact is limited because advertising drives cash flow. The strategic risk is lower returns on AI infrastructure and developer ecosystem investment if Llama falls behind.

6.5 Existing market positioning matters more than one launch

From June 22 through July 16, before most of the K3 evidence could affect trading, the US AI complex had already diverged sharply.

Company	Return	Drawdown from period high	Positioning signal
Meta	+17.9%	-3.1%	Strong ad cash flow and AI utilization expectations
Microsoft	+9.2%	-1.2%	Cloud and software resilience
Amazon	+7.3%	-3.2%	AWS and consumer recovery expectations
Alphabet	+1.4%	-5.5%	Mixed search and cloud positioning
NVIDIA	-0.6%	-3.1%	Relatively resilient
Broadcom	-4.5%	-9.7%	Custom AI optimism meets valuation pressure
AMD	-9.2%	-14.3%	Alternative accelerator optionality with high volatility
Micron	-29.6%	-32.0%	Correction after elevated memory expectations
Oracle	-29.1%	-32.7%	Tension between AI infrastructure growth and financing
Marvell	-38.8%	-40.1%	Severe derating in networking and custom silicon

These are not K3-caused returns. They show the positions into which K3 arrived. A relatively resilient NVIDIA may be more sensitive to efficiency headlines, while already-corrected Micron and Marvell could react more strongly if the released weights create verifiable infrastructure demand.

7. Company Impact Map

Company or layer	Near-term signal	Medium-term path	What to do now
NVIDIA	Valuation pressure from efficiency and portability	Self-hosted 64+ accelerator clusters offset efficiency	Watch workload elasticity, do not change estimates on the launch alone
AMD	Alternative deployment optionality	Share upside if ROCm economics are proven	Wait for post-July 27 throughput
Broadcom and Marvell	Networking complex already derating	MoE expert parallelism raises fabric demand	Verify orders and actual K3 cluster topology
SK hynix	Sensitive to KV-cache efficiency headlines	HBM, server DRAM and Solidigm SSD hierarchy exposure	Value the full memory stack, not HBM alone
Samsung Electronics	HBM efficiency risk plus catch-up position	HBM, server DRAM, SSD and foundry optionality	Broadest portfolio, execution still required
Micron	High expectations already corrected	Integrated US AI memory and storage exposure	Watch deployment volume versus pricing
Microsoft	OpenAI price and mix pressure	Azure and Copilot cost leverage	Cloud usage matters more than model margin
Amazon	Pressure on Anthropic asset value	AWS, Bedrock and Trainium benefit from model choice	The cleanest internal offset
Alphabet	Gemini price pressure	TPU, Vertex and Search cost benefits	Application-layer defense remains strong
Meta	Pressure on US open-weight leadership	Llama acceleration or broader open ecosystem	Strategic impact exceeds near-term earnings impact

There is not enough evidence for a new buy or sell call from this launch alone. Weights, license and external hardware throughput remain unavailable. The order of proof matters more than the direction of the narrative.

8. Three Scenarios

Base case: strong model, limited re-rating

Subjective probability: 55%. Full weights and a reasonably permissive license arrive by July 27. External results reproduce 85% to 95% of official performance. K3 runs on NVIDIA and AMD, but 64+ accelerators, max reasoning and high output-token use keep deployment expensive.

Proprietary APIs face more price pressure on repetitive work.
Clouds gain K3 hosting and self-deployment demand.
Per-token efficiency offsets higher workload.
HBM is neutral to modestly positive.
Server DRAM, enterprise SSD and networking are positive.

Bull case: open weights enter primary enterprise routing

Subjective probability: 25%. The license is close to MIT, vLLM and SGLang support is stable, and NVIDIA, AMD and Chinese accelerators show strong throughput. External evaluation confirms performance immediately below the top proprietary models. Lower reasoning modes reduce task cost. Major clouds and enterprise gateways add K3 to default routing.

Proprietary model blended price and token share fall.
Hyperscaler multi-model usage rises.
Self-serving clusters increase accelerator demand.
HBM, networking, server DRAM and enterprise SSD benefit from deployment volume.
Meta and US open-model programs accelerate investment.

Bear case: weights reveal a cost and quality gap

Subjective probability: 20%. Weights are delayed or restricted, external scores fall below the official table, preserved-thinking-history requirements and excessive proactiveness create enterprise failures, and task cost exceeds Sonnet 5 because of max reasoning and verbosity. The 64-accelerator requirement limits self-hosting.

Moonshot may have to retreat from frontier pricing.
Proprietary APIs retain a UX and reliability premium.
Incremental semiconductor demand remains limited.
Existing earnings and capex regain control of stock prices.

9. The July 27 Verification Checklist

Proof point	Strong signal	Weak signal
Weights and license	Full release on time with commercial modification rights	Delay, restrictions or missing components
External evaluation	Official scores broadly reproduced under one harness	Large drop versus company table
Cost per task	Lower reasoning modes and fewer output tokens	Max-only reasoning and persistent verbosity
NVIDIA throughput	Stable expert parallelism on 64-accelerator nodes	Fabric bottlenecks and low utilization
AMD throughput	Cost advantage under ROCm and vLLM	Immature kernels or accuracy loss
Chinese accelerators	Named hardware and measured throughput	Only “alternative GPU” language
Caching	Near-90% hits on enterprise traffic	Sharp decline outside coding
Cloud adoption	AWS, Azure, Google Cloud or Oracle listings	Limited to a few Chinese platforms
Competitive pricing	Standard price cuts or wider cache discounts	Temporary promotions only
Memory orders	Upward revisions to HBM, server DRAM and SSD volumes	Efficiency rises while volumes stagnate

10. The Strongest Counterargument

The strongest bear case is straightforward: semiconductor demand falls if efficiency improves faster than usage. Model compression, linear attention, quantization, cache reuse and inference ASICs could process the same number of useful tasks with far fewer GPUs and less HBM. Open-weight competition can reduce API prices without producing enough incremental paid work to justify AI capex.

Evidence for that outcome would include slower inference revenue despite falling prices, higher accelerator utilization but fewer new clusters, HBM bit growth below model-efficiency gains, weak conversion of cloud AI backlog into revenue, and enterprises using open models only to cut costs rather than create new workflows.

The bull case requires price declines to unlock new work: repository-scale coding, research automation, video editing, chip design and workflows that were previously uneconomic. Workload elasticity relative to model efficiency is the common proof point for both accelerator and HBM investing.

11. Conclusion

Kimi K3 does not prove that China has surpassed the strongest US proprietary models. Moonshot acknowledges the remaining UX gap. As of July 17, the full weights and technical report are not available, and a mixed-harness benchmark table cannot declare a winner.

It does change market structure. A 2.8T, 1M-context, near-frontier model is live at Sonnet’s standard price, with weights promised within ten days. Chinese open weights are moving from cheap second-tier substitutes toward primary enterprise workloads.

For semiconductors, the event is more demand reallocation than demand destruction. KDA and quantization reduce HBM and GPU time per request. Sparse MoE and 64-accelerator supernodes increase model-residency memory and fabric. Mooncake pushes cache into server DRAM and enterprise SSDs. The HBM-only story becomes less simple, while the full memory and data-center hierarchy remains exposed to wider deployment.

US Big Tech faces the same split. Model APIs absorb price pressure; clouds and applications absorb lower model cost. Microsoft, Amazon and Alphabet can host K3 even if their preferred models lose share. Meta must defend its strategic role as the trusted US open-weight standard.

On July 27, the important evidence is not the existence of a weight file. It is a permissive license, reproducible evaluation, multi-hardware throughput and competitive cost per completed task. If those conditions hold, K3 becomes an event that changes both the AI price curve and the semiconductor demand path. If they do not, it remains an impressive product launch rather than an industry reset.

Sources and Limitations

Primary materials: Kimi K3 launch, Kimi K3 API documentation, Kimi Linear paper, Kimi Linear GitHub, Attention Residuals paper, Mooncake paper, Claude Sonnet 5 pricing, GPT-5.6 Sol pricing, OpenRouter model adoption analysis, Microsoft-OpenAI partnership, Google Vertex Model Garden, and Amazon-Anthropic partnership.

The semiconductor and stock transmission analysis is an inference from public architecture, serving and market data. Exact active parameters, weight size, license terms, AMD and Chinese-accelerator throughput, and enterprise cost per completed task remain blocked as of July 17. This article is for research and information purposes only and is not investment advice.

Attention Residuals on Korea Invest Insights