Command A Plus 05 2026 BF16 vs Lyria 3.5

This comparison does not currently contain a protocol-matched coding benchmark for both Command A Plus 05 2026 BF16 and Lyria 3.5, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.

Neither model has a directly sourced input price in this comparison. Neither model has a directly sourced output price in this comparison.

Lyria 3.5 has the larger sourced context window. Command A Plus 05 2026 BF16 supports 200K and Lyria 3.5 supports 1,049K.

There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.

Command A Plus 05 2026 BF16 is the only model in this pair currently marked as self-hostable. Command A Plus 05 2026 BF16 is open weight; Lyria 3.5 is not marked open weight.

Command A Plus 05 2026 BF16 is documented with image input; Lyria 3.5 is documented with image input. This reflects supported input modalities, not vision quality.

Neither has a larger sourced maximum output. Command A Plus 05 2026 BF16 is 66K and Lyria 3.5 is 66K.

Command A Plus 05 2026 BF16: tool calling and image input. Lyria 3.5: image input. Feature support does not establish relative quality.

Command A Plus 05 2026 BF16 has 0 sourced provider routes; Lyria 3.5 has 2, so Lyria 3.5 has broader tracked availability.

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.