Fetching from the wire…
Public story · 2026-07-14 · high
Chinese open-weight models went from 4.5% to 30-46% of US enterprise API traffic in a year, per CNBC.
Why now: Goldman reportedly issued the recommendation to Wall Street clients on July 13, turning a traffic-share trend into an explicit vendor call from a compliance-bound bank.
Goldman Sachs reportedly told Wall Street clients on July 13 to adopt DeepSeek V4, Kimi K2.6, GLM-5, and Qwen3.5, citing 80-90% of frontier capability at 70x lower cost, per CNBC.
A year ago, Chinese open-weight models were about 4.5% of US enterprise API traffic. The current figure is 30 to 46%. A bank that answers to compliance officers reportedly told regulated clients to route real work to models built in China. That's a cost gap wide enough to override the reflex to buy American frontier.
I've been skeptical of the 'Chinese models caught up' story. The benchmarks felt cherry-picked and the deployment stories were thin. A formal recommendation from Goldman to a compliance-bound institution is different evidence than a leaderboard screenshot. Goldman isn't in the hype business.
Seventy times cheaper at 80-90% capability is the number that reorganizes a budget. Most production traffic isn't frontier-hard. You don't need GPT-5.6 to classify a support ticket or pull fields off an invoice. Paying frontier prices for that work was habit and vendor gravity, not necessity.
Stop treating 'which model' as a fixed decision. Build an eval suite against your real workload, drop DeepSeek V4 and Qwen3.5 into it, and measure. If they clear your quality bar on 70% of traffic, route that share. Keep frontier for the hard 30%. That's recurring savings, not a one-time win.
None of this settles the harder question. Running an open-weight model on your own hardware is one thing. Calling a hosted Chinese API with customer data is another, and export-control and data-residency rules haven't caught up to either. Read the license and know where the weights actually run before you wire one in.
Each link below shares sources, entities, or timing with this story.
Goldman Sachs uses Claude / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Goldman Sachs uses Claude); both cover DeepSeek V4, GLM, GPT, Kimi K2; overlapping topics (cost, deepseek, model).
DeepSeek released DeepSeek V4 / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (DeepSeek released DeepSeek V4); both cover Chinese, CNBC, GLM, GPT; overlapping topics (chinese, deepseek, frontier, model, traffic).
Moonshot AI deprecates Kimi K2 / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Moonshot AI deprecates Kimi K2); both cover Chinese, DeepSeek V4, GLM, GPT; overlapping topics (cost, frontier, model).
Goldman Sachs uses Claude / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Goldman Sachs uses Claude); both cover GLM, GPT, Kimi K2; reported by the same outlet (unrot.co).
DeepSeek released DeepSeek V4 / Shared entities / Earlier coverage / Tension
Linked by a graph relationship (DeepSeek released DeepSeek V4); both cover Chinese, GLM, GPT; earlier Chinese coverage from 2026-04-20.
DeepSeek released DeepSeek V4 / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (DeepSeek released DeepSeek V4); both cover Chinese, CNBC; overlapping topics (chinese, frontier, model).
DeepSeek released DeepSeek V4 / Shared entities / Earlier coverage
Linked by a graph relationship (DeepSeek released DeepSeek V4); both cover Chinese, GPT, When; earlier Chinese coverage from 2026-07-01.
Anthropic partners with Goldman Sachs / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Anthropic partners with Goldman Sachs); both cover GPT, Kimi K2, Qwen3; overlapping topics (capability, frontier, model).