Side-by-side technical and economic comparison between Google's Gemini 2.5 Flash-Lite and Cohere's Command A.
| Metric | Gemini 2.5 Flash-Lite | Command A | Advantage |
|---|---|---|---|
| Provider Organization | Cohere | — | |
| Standard Input / 1M | $0.10 | $2.00 | Gemini 2.5 Flash-Lite (95% lower) |
| Cached Input / 1M | $0.01 | $0.20 | Gemini 2.5 Flash-Lite lower |
| Output / 1M | $0.40 | $8.00 | Gemini 2.5 Flash-Lite lower |
| Context Window | 1.05M | 256k | Gemini 2.5 Flash-Lite (1.05M) |
| Max Generation Tokens | 8.2k | 64k | Command A |
| Tokenizer Family | Google Gemini SentencePiece (256k vocabulary) | Cohere Byte-Pair Encoding (256k vocabulary) | — |
Opt for Gemini 2.5 Flash-Lite 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 $0.1/M input rate.
Opt for Command A when looking for Cohere's tooling integration, specific context window depth (256k tokens), or when output generation volume favors its $8/M rate.