DeepSeek V4 Pro 0813 quietly released

Aug 12, 2026 · 4:37 PM UTC ·3 min read · 0 reactions · 0 comments · 4 views

TL;DR · WeSearch summary

Key facts

▪API GuidesUsing the Responses APIOn this pageUsing the Responses API To meet the demand for Codex, our API now supports the Responses API format, with the base_url being https://api.deepseek.com.
▪With a simple configuration, you can use DeepSeek models in Codex.
▪Integrating DeepSeek Models into Codex Please refer to Integrate with Codex.

How this story was covered

2 outlets in our directory ran this story. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 1

▪ DeepSeek V4 Pro 0813 — Openrouter

About this source

Hacker News (Front Page) files mainly under programming. We currently carry 1,484 of its stories. Top-voted stories on Hacker News.

All Hacker News (Front Page) coverage →

Original article

Deepseek

Read full at Deepseek →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	Deepseek
Canonical URL	https://api-docs.deepseek.com/guides/responses_api/
Publication time	Wed, 12 Aug 2026 16:37:13 +0000
Retrieval time	2026-08-12T17:06:33.403Z
Last seen	2026-08-12T17:06:33.403Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	t1967wRakpoj · 2 stories
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

API GuidesUsing the Responses APIOn this pageUsing the Responses API To meet the demand for Codex, our API now supports the Responses API format, with the base_url being https://api.deepseek.com. With a simple configuration, you can use DeepSeek models in Codex. Integrating DeepSeek Models into Codex Please refer to Integrate with Codex. Calling DeepSeek Models via the Responses API # Please install OpenAI SDK first: `pip3 install openai`from openai import OpenAIclient = OpenAI(api_key="<your DeepSeek API Key>", base_url="https://api.deepseek.com")response = client.responses.create( model="deepseek-v4-flash", instructions="You are a helpful assistant.", input="Hi, how are you?",)print(response.output_text) Streaming Set stream: true to receive the response as a sequence of semantic…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Deepseek.

Anonymous · no account needed

Discussion

0 comments