
Whole-document and whole-repository passes
A 1M-token context window is only half of a long job; the other half is being allowed to write the answer out. deepseek-v4.1-flash pairs that window with a 384,000-token output ceiling, so a translated manual, a rewritten test suite or a clause-by-clause contract review can come back in one response instead of being chunked, stitched and reconciled. Because deepseek-v4.1-flash prices the same at any context length, a long prompt does not cross a threshold and change the rate mid-workload. Set max_tokens deliberately on these jobs — deepseek-v4.1-flash uses the endpoint default otherwise, not the ceiling.
Read the API docs




