The model name and the API ID are not always the same thing. DeepSeek uses one API ID per family, then switches thinking and reasoning effort through request settings. We keep those configurations as separate benchmark rows because their scores differ, but we do not pretend they are separate billable SKUs.
Older R1, V3.2, V3.1, Coder, and Math rows remain useful for reproducibility and self-hosting. They are not current first-party API choices. DeepSeek set July 24, 2026 as the retirement deadline for the deepseek-chat and deepseek-reasoner aliases, so new integrations should use the two IDs above.