+ds docs changelog.
+Ask deepseek-v4-pro what model it is and it may tell you it is
+GPT-4o. A model that answers with a competitor's name looks like a swap, and
+the question came up: did the 0813 GA get pulled and replaced with something
+older? Short answer, no. The build behind deepseek-v4-pro is still
+DeepSeek-V4-Pro-0813.
+The record is consistent on every side that can actually be checked. The
+Models & Pricing version cell
+still reads DeepSeek-V4-Pro-0813 (the page's last-modified date is 2026-08-12,
+the GA day, and it has not moved since). The API still serves
+deepseek-v4-pro. Third-party hosts that mirror the build, OpenRouter
+and NanoGPT among them, list 0813. The change log carries no rollback. Nothing
+was withdrawn.
So why does it say GPT-4o? Because a language model does not know its own
+name or its training date. Asked to state its version with nothing to look at,
+deepseek-v4-pro answers differently on different samples:
GPT-4o
+GPT-4o
+DeepSeek-V3-0324
+# and flash, asked the same, answered: Qwen/Qwen2.5-7B-InstructThat is the model repeating identities from its training data, not reporting
+what it was deployed as. It is not a version signal and never was, on any
+model. The signal that is real is the one nobody has to imagine: the docs
+version cell and the model list. ds docs show quick_start/pricing
+prints that same table offline, and ds models lists what the
+endpoint serves. Neither asks the model to introspect, which is exactly why the
+CLI carries the documentation inside the binary: the answer to “what am I
+calling” should not depend on the model's memory of itself.
The preview is over. The Models & Pricing page now lists diff --git a/site/news/deepseek-v4-pro-0813-still-live-2026-08-13.jpg b/site/news/deepseek-v4-pro-0813-still-live-2026-08-13.jpg new file mode 100644 index 0000000..7ad3d40 Binary files /dev/null and b/site/news/deepseek-v4-pro-0813-still-live-2026-08-13.jpg differ diff --git a/site/news/index.html b/site/news/index.html index e601652..155c025 100644 --- a/site/news/index.html +++ b/site/news/index.html @@ -81,6 +81,47 @@
ds docs changelog.
+Ask deepseek-v4-pro what model it is and it may tell you it is
+GPT-4o. A model that answers with a competitor's name looks like a swap, and
+the question came up: did the 0813 GA get pulled and replaced with something
+older? Short answer, no. The build behind deepseek-v4-pro is still
+DeepSeek-V4-Pro-0813.
+The record is consistent on every side that can actually be checked. The
+Models & Pricing version cell
+still reads DeepSeek-V4-Pro-0813 (the page's last-modified date is 2026-08-12,
+the GA day, and it has not moved since). The API still serves
+deepseek-v4-pro. Third-party hosts that mirror the build, OpenRouter
+and NanoGPT among them, list 0813. The change log carries no rollback. Nothing
+was withdrawn.
So why does it say GPT-4o? Because a language model does not know its own
+name or its training date. Asked to state its version with nothing to look at,
+deepseek-v4-pro answers differently on different samples:
GPT-4o
+GPT-4o
+DeepSeek-V3-0324
+# and flash, asked the same, answered: Qwen/Qwen2.5-7B-InstructThat is the model repeating identities from its training data, not reporting
+what it was deployed as. It is not a version signal and never was, on any
+model. The signal that is real is the one nobody has to imagine: the docs
+version cell and the model list. ds docs show quick_start/pricing
+prints that same table offline, and ds models lists what the
+endpoint serves. Neither asks the model to introspect, which is exactly why the
+CLI carries the documentation inside the binary: the answer to “what am I
+calling” should not depend on the model's memory of itself.
The preview is over. The Models & Pricing page now lists