Side-by-side technical and economic comparison between Google's Gemini 3.1 Pro Preview and DeepSeek's DeepSeek-V3 (Legacy API Alias).
• DeepSeek-V3 (Legacy API Alias): Classified as a Legacy Reference model (Legacy Reference (API Aliased)).
| Metric | Gemini 3.1 Pro Preview | DeepSeek-V3 (Legacy API Alias) | Advantage |
|---|---|---|---|
| Provider Organization | DeepSeek | — | |
| Standard Input / 1M | $2.00 | $0.14 | DeepSeek-V3 (Legacy API Alias) (93% lower) |
| Cached Input / 1M | $0.20 | $0.014 | DeepSeek-V3 (Legacy API Alias) lower |
| Output / 1M | $12.00 | $0.28 | DeepSeek-V3 (Legacy API Alias) lower |
| Context Window | 1.05M | 128k | Gemini 3.1 Pro Preview (1.05M) |
| Max Generation Tokens | 16.4k | 8.2k | Gemini 3.1 Pro Preview |
| Tokenizer Family | Google Gemini SentencePiece (256k vocabulary) | DeepSeek Byte-level BPE (~128k vocabulary) | — |
Opt for Gemini 3.1 Pro Preview when your engineering requirements prioritize Google's ecosystem, specific tokenizer efficiencies (Calibrated Gemini Tokenizer (±4%)), or when your expected prompt-to-completion ratios favor its $2/M input rate.
Opt for DeepSeek-V3 (Legacy API Alias) when looking for DeepSeek's tooling integration, specific context window depth (128k tokens), or when output generation volume favors its $0.28/M rate.