Command A Translate vs Lyria 3.5
At a Glance
| Compare | Command A TranslateCohere | Lyria 3.5Google DeepMind |
|---|---|---|
| Pricing and Limits | ||
| Context windowMaximum documented tokens | 8K | 1,049K |
| Model facts checked | Sep 3, 2026View model evidence → | Sep 22, 2026View model evidence → |
Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →
Available Benchmarks
Side-by-Side Facts
| Field | Command A Translate | Lyria 3.5 |
|---|---|---|
| Developer | Cohere | Google DeepMind |
| Family | Command A | Lyria |
| Model | Command A Translate | Lyria 3.5 |
| Version | Command A Translate | Lyria 3.5 |
| Lifecycle | active | active |
| Released | 2025-08-28 | 2026-07-29 |
| Knowledge cutoff | 2024-06-01 | Unknown |
| Input modalities | Text | Text, Image |
| Output modalities | Text | Text, Audio |
| Context window | 8K | 1,049K |
| Total parameters | 111B | Unknown |
| Active parameters | Unknown | Unknown |
| License | Unknown | Unknown |
| Open weights | No | No |
| API available | Yes | Yes |
| Self-hostable | No | No |
| Provider access | Cohere (Standard) | Google AI (Standard), Google Gemini (Standard) |
| Capabilities | chat, generation, structured_outputs, translation | generation, image-to-music, lyrics, music-generation, synthid, vocals |
Command A Translate Capabilities
Lyria 3.5 Capabilities
Primary Evidence
Sources and Freshness
Questions
Command A Translate vs Lyria 3.5 FAQs
Is Command A Translate or Lyria 3.5 better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Command A Translate and Lyria 3.5, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Command A Translate or Lyria 3.5?+
Neither model has a directly sourced input price in this comparison. Neither model has a directly sourced output price in this comparison.
Which has a larger context window, Command A Translate or Lyria 3.5?+
Lyria 3.5 has the larger sourced context window. Command A Translate supports 8K and Lyria 3.5 supports 1,049K.
Which performs better in benchmarks, Command A Translate or Lyria 3.5?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Command A Translate or Lyria 3.5 be self-hosted?+
Both models have the same recorded self-hosting status: unsupported. Command A Translate is not marked open weight; Lyria 3.5 is not marked open weight.
Can Command A Translate and Lyria 3.5 understand images?+
Command A Translate is not documented with image input; Lyria 3.5 is documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Command A Translate or Lyria 3.5?+
Lyria 3.5 has the larger sourced maximum output: Command A Translate supports 8K and Lyria 3.5 supports 66K output tokens.
Do Command A Translate and Lyria 3.5 support reasoning and tool use?+
Command A Translate: none of these features are definitively sourced. Lyria 3.5: image input. Feature support does not establish relative quality.
Which is available from more inference providers, Command A Translate or Lyria 3.5?+
Command A Translate has 1 sourced provider route; Lyria 3.5 has 2, so Lyria 3.5 has broader tracked availability.
Which offers better value, Command A Translate or Lyria 3.5?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.