DeepSeek R1: reasoning history, not the current API alias

R1 remains a useful version-specific topic. DeepSeek's current provider docs now point to V4 Pro and Flash, while Flowith availability must be checked in the live workspace.

Current status

Keep R1 history separate from current V4 access

The R1 route answers model-history and earlier reasoning-workflow questions. DeepSeek's V4 release says its legacy deepseek-reasoner alias was retired and identifies V4 Pro and Flash as the current provider models.

What the R1 route is useful for

DeepSeek R1 reasoning model history

Reasoning-model history

Understand why R1 became a reference point for reasoning-heavy math, code, and problem-solving prompts.

DeepSeek R1 prompt migration review

Prompt migration

Use old R1 examples as historical context, then retest prompts against the current provider model before production use.

DeepSeek R1 availability boundary

Access boundary

A historical route, an open-weight model, a provider API alias, and Flowith workspace access are different facts.

How to use this R1 guide

1

Use R1 for Historical Intent

Review R1 when your question is specifically about the earlier reasoning model, its workflows, or migration history.

2

Check the Current Provider Model

DeepSeek's V4 documentation now names Pro and Flash model IDs and says the deepseek-reasoner alias was retired.

3

Verify Your Workspace

Confirm the model enabled in your Flowith account before relying on a route label or an old API name.

DeepSeek R1 history vs. current provider state

Use the earlier-version route for R1 intent and current official docs for live provider facts.

R1 historical route

Current V4 provider state

Primary intent

R1 reasoning-model history

Current DeepSeek provider access

API identity

deepseek-reasoner (retired alias)

deepseek-v4-pro or deepseek-v4-flash

Version facts

Check the official R1 model materials

Check the current V4 release and API docs

Flowith availability

Check the live workspace

Check the live workspace

DeepSeek R1 status FAQ

DeepSeek R1 is an earlier DeepSeek reasoning-model release. This page preserves R1-specific historical, reasoning, and migration intent rather than presenting R1 as DeepSeek's current provider model.
No. DeepSeek's V4 Preview release says the deepseek-reasoner and deepseek-chat aliases were retired after July 24, 2026. Current provider documentation names deepseek-v4-pro and deepseek-v4-flash.
Do not infer Flowith availability from this historical route. Open the current workspace and check the account's model selector before planning an R1 workflow.
Use the R1 page for R1-specific history, reasoning-era comparisons, earlier prompts, or migration questions. Use the V4 page for current provider model IDs, context, and launch status.
Use DeepSeek's official R1 model materials for the historical release and DeepSeek's current V4 release and pricing documentation for present provider state.

Need the current DeepSeek model?

Continue to the V4 status page, then verify Flowith access in the current workspace.

Review DeepSeek V4 status