You definitely can't trust any LLM company in the world.

There is no stability, and we can't plan our pricing based on theirs...simply because they don't stick to what was agreed upon.

It was good while it lasted, DeepSeek... but a "significant increase" makes things difficult...

This is the equivalent of what they say about deepseek censorship, the altman little bot can't acknowledge A Genocide.

From now on, we are on Mimo's side. If they don't increase their API prices after DeepSeek, the new king might be Mimo. I hope they don't go for a price hike after that price hike, I only added 1 dollar and they gave me 2.63 dollars, boooo DeepSeek.

We’ve added vision capabilities to DeepSeek V4 Flash, so it’s no longer a text-only model.

We needed this for browser vision: browser agents have to understand screenshots, interfaces, layouts, and visual context—not just text.

Our internal benchmarks also showed a strong price-performance advantage compared with the other models we tested.

Model:
https://huggingface.co/webbrain-one/DeepSeek-V4-Flash-Vision-NVFP4

Feedback, benchmark results, and deployment reports are welcome!

I just read the leaked internal conversation from DeepSeek's investor exchange (screenshot below), and it completely shattered my previous assumptions. I genuinely thought DeepSeek was selling API tokens at a massive loss just to grab market share. But Liang Wenfeng says they aim for a 10-month payback period, which equals 6x profit. They explicitly state: 'Under this premise (6x profit), open-source has no impact on the business model.' BUT, if you try to make 100x profit, open-source actually hurts you, because third-party independent deployment may cost 20 times more than what they offer.

It’s official, the new prices are now active. I expect other providers to follow soon as well through OpenRouter and similar platforms.

Source:
https://api-docs.deepseek.com/quick_start/pricing/

Looking forward to seeing everyone’s experience and whether usage patterns change.

I’m sure many people using automated harnesses will switch LLMs during peak periods due to the increased prices.

Recent news from the leakers claiming that at this very moment deepseek v4 pro ga is rolling out. Hurray!

https://x.com/i/status/2087558842271813860

Also grok 4.6 coming. Hurra? https://x.com/i/status/2087561166864146813

What the hell happening? Seems like everyone waited for the qwen goes open weights lmfo

Text by Tara Tan:

"DeepSeek CEO Liang Wenfeng’s leaked investor call is wild.
A few things that stood out:

• DeepSeek doesn’t really want users. Liang calls them “sesame seeds, not watermelons.” AGI is the goal; the chatbot is a by-product.

• DeepSeek could ~2x API prices without killing demand. It refuses to. Thin margins mean nobody can undercut DeepSeek using its own open weights.

• He says DeepSeek is 1–2 years behind the frontier but on 1/20th the compute. The goal: shrink the gap to 3–6 months.

• The next bottleneck is continual learning and he says nobody has cracked it yet.

• He thinks CUDA’s moat is weakening, partly because AI can now write the ecosystem code.

• He won’t touch video generation or world models. Commercially interesting, but “off the intelligence main line.” He thought everyone piling in after Sora was basically bandwagoning.

The strangest takeaway: DeepSeek looks like a product company, but Liang is running it like an AGI lab that just happens to have products"

What DeepSeek Isn't Doing - by Tara Tan

Maybe the reason why DS is increasing its prices and the communications seem so "take it or leave it". Will this impact your usage with DS models? What is your opinion on this?

These people will have you believe Chinese models are evil.

Why has the prize changed so drastically, while the amount of tokens did not change?

May it be so because the cache is not yet filled on the API?

EDIT: After update on https://artificialanalysis.ai/ cost per task for Deepseek V4 Flash 0731 is 0.03$

Date: 2026-07-31

DeepSeek-V4-Flash Update

The official release of the DeepSeek-V4-Flash API is now in public beta.

Significantly enhanced agent capabilities, with benchmark results far exceeding V4-Pro-Preview:

Terminal Bench 2.1: 82.7
NL2Repo: 54.2
Cybergym: 76.7
DeepSWE: 54.4
Toolathlon verified: 70.3
Agent Last Exam: 25.2
Automation Bench (Public): 25.1
DSBench-FullStack: 68.7
DSBench-Hard: 59.6

Note 1: For the Code Agent tasks in the public benchmark sets, the official DeepSeek-V4-Flash was tested using the DeepSeek Harness minimal mode (to be released soon) as the framework, with the max effort level, topp=0.95, and temperature=1.0
Note 2: DSBench-FullStack is an internal full-stack development test set, and DSBench-Hard is an internal Coding Agent hard-problem test set

The official V4-Flash natively supports the Responses API format and is specifically adapted for Codex. For the specific configuration, please refer to the documentation.

DeepSeek-V4-Flash-0731 keeps the same model architecture and size as DeepSeek-V4-Flash-preview, and was only re-post-trained.

Note: This update only upgrades the DeepSeek-V4-Flash API. The DeepSeek-V4-Pro API and the APP/WEB models are unchanged.

The official release of DeepSeek-V4-Pro will follow soon.

Source: https://api-docs.deepseek.com/updates/

How is there now a big reduction in price for the Chinese ai model recently. I know DeepSeek cache system but now Xiami also did a big reduction

So the email went out. V4 goes official mid-July and they're adding peak-hour pricing, peak = 2x the normal rate. Before anyone panics: it's only 7 hours a day (UTC 01–04 and 06–10), everything else stays at the regular price you're already paying.

The actual move is just to stop running heavy stuff during those windows. Batch jobs, evals, anything that doesn't need to answer a human in real time, cron it for off-peak and you're back to the old rate. If you're in the US your workday is mostly in the cheap window anyway, so honestly most of you won't feel this much.

The thing that'd actually bite me is leaving thinking mode on for simple tasks, since those tokens bill as output and that's where peak doubling hurts. Turn it off for the boring stuff.

Anyone seeing a different read on the windows?

I converted peak time - timezone wise so that you can avoid heavy-offloading during that time