DeepSeek V4.1 Flash: API Cost and When to Self-Host

The table uses DeepSeek’s uncached input and output rates, in US dollars per million tokens. The example combines 1 million uncached input tokens with 100,000 output tokens. Treat those as total usage for a workload, not a required request size.

DeepSeek bills peak and off-peak periods differently, and cache-hit input has a separate lower rate. Peak hours are Monday–Friday, 01:00–04:00 and 06:00–10:00 UTC, excluding Chinese public holidays; other hours use off-peak rates. For an agent, count the follow-up calls and tool results as well as the initial request when estimating the whole task.

Cache-hit input costs $0.003 per million tokens off-peak or $0.006 at peak, checked October 26. For a workload with 1M cache-hit input tokens and 100K output tokens, the calculated token charge is $0.063 off-peak or $0.126 at peak. Cache misses use the standard input rates in the comparison above; measure the returned cached and uncached usage separately.

If you want an agent that works on files, start with a client such as DeepSeek Harness or WorkBuddy. These tools supply the workspace, conversation interface and actions around the model. Installing a client on your computer still uses a hosted model when you configure it with a DeepSeek API key.

For your own application, create a DeepSeek platform account, configure an API key on your server and select deepseek-flash. Since October 17, this API name serves V4.1-Flash-1017; the official web and app have moved to that version too. The API calling method and token prices are unchanged. The separate deepseek-v4-pro endpoint serves V4-Pro-0813. Keep the key on the server when building a public website.

Begin with one complete task before building a larger workflow: send the input, inspect the response, record token usage and decide what your application should do next. For coding, use a small, reproducible issue and ask the agent to inspect the relevant files, propose a change and run the tests. The application supplies file access and command execution; the model chooses and interprets tool calls. Decide which file changes and commands need your approval.

For an image or document question, provide a screenshot or document image with a specific question, such as which setting is selected or how two diagrams differ, and ask for the visible evidence behind the answer. For long-document work, start with a bounded comparison and request citations to the supplied text. The large context window provides capacity, but a clear selection of relevant material still helps.

A model API returns responses and tool-call requests. A finished agent application also needs to keep the conversation, expose files and tools, execute approved actions and show what happened. Using an existing client saves you from building that surrounding workflow before you can try the model.

For the October 17 model update, DeepSeek recommends DeepSeek Harness 0.2.1-rc.1 or later and reports targeted optimization for Harness, CodeBuddy and WorkBuddy. Its game and 3D-project demonstrations are examples produced in Harness. Try a small project with explicit acceptance checks before handing over a larger task.

Choose a client around the work you need to do. For a repository task, check how it chooses the working directory, previews edits and shows command output. For a document workflow, check how it passes attachments and preserves the source material. Test one representative task before moving a large project into it.

DeepSeek’s September 10 announcement highlighted V4.1 Flash’s benchmark and efficiency gains and planned to move Pro API traffic to Flash. Its amended update says Pro will remain available in response to user demand. The current API documentation lists them as separate choices.

Creative-writing preferences deserve a separate comparison. In an r/DeepSeek story-writing discussion, Smart_Boysenberry_64 described repetitive phrasing after several turns with Flash. Commenter Silent_Truck_4622 preferred how Pro responded to corrective instructions in the web app. These are specific users’ app experiences; they help identify what to test for fiction and character dialogue.

For your own comparison, give both models the same scene, character notes and revision request. Read several turns rather than just the opening answer. Compare whether each keeps the character’s voice, responds to corrections and avoids repeated wording. For coding, use a separate task and assess the resulting change and tests.

The original V4.1 Flash checkpoint has downloadable MIT-licensed weights and is a large distributed-inference project. Its 552B-parameter backbone and 196B Engram component need far more storage than the 8B/16B active-parameter figures suggest. For a typical personal or small-business setup, start with a hosted service.

For infrastructure teams, SGLang has a model-specific cookbook and vLLM has added V4.1 support. The reference inference guide covers checkpoint conversion and distributed execution. The release announcement links the new DeepSeek-V4.1-Flash-1017 checkpoint for download; match it with a runtime that supports that checkpoint before reusing an older deployment recipe. Community projects now publish checkpoint-specific 1017 runs on a single RTX 5090, a large-RAM CPU/GPU server and four DGX Spark systems. Their custom runtimes, weight formats and test workloads differ, so compare the complete deployment rather than treating their token rates as a hardware ranking.

DeepSeek’s Apache-2.0 DeepInfer core runs V4.1-Flash offline on NVIDIA SM100 GPUs and Huawei Ascend 950 NPUs. A complete service needs additional cache, disaggregation and load-balancing components. Use the dedicated guide below to plan installation, interconnect and the full cluster budget before comparing self-hosting with the API.