Command A vs Command A Vision

Benchmark Performance

Available Benchmarks

No Protocol-Matched Benchmark Yet.Results appear here only when both models share the same benchmark version, metric, evaluation protocol, and evidence class.
FieldAt a Glance
Cohere · activeCommand AVerified Aug 29, 2026
Cohere · activeCommand A VisionVerified Aug 29, 2026

Technical Differences

Side-by-Side Facts

Indexable
FieldCommand ACommand A Vision
DeveloperCohereCohere
FamilyCommand ACommand A
ModelCommand ACommand A Vision
VersionCommand ACommand A Vision
Lifecycleactiveactive
ReleasedUnknownUnknown
Knowledge cutoff2024-06-012024-06-01
Input modalitiesTextText, Image
Output modalitiesTextText
Context window256,000128,000
Total parameters111,000,000,000Unknown
Active parametersUnknownUnknown
LicenseUnknownUnknown
Open weightsNoNo
API availableYesYes
Self-hostableNoNo
Provider accessCohere (Standard)Cohere (Standard)
Capabilitiesagents, chat, citations, multilingual, rag, structured_outputs, toolschat, citations, multilingual, ocr, reasoning, structured_outputs, vision

14 comparable fields · 5 material differences · Pair passes the primary-source comparison gate

Command A Capabilities

agentschatcitationsmultilingualragstructured outputstools
Input price$2.50
Output price$10.00
Serving providers1
Canonical IDcoherelabs/command-a-03-2025

Command A Vision Capabilities

chatcitationsmultilingualocrreasoningstructured outputsvision
Input price
Output price
Serving providers1
Canonical IDcoherelabs/command-a-vision-07-2025

Internal Comparison Graph

Related Comparisons

All text comparisons →
APairBContext
vscross-developer peersimage, text
vscross-developer peersimage, text
vscross-developer peersimage, text
vscross-developer peersimage, text
vscross-developer peersimage, text
vsfamily variantsimage, text
vscross-developer peersimage, text
vscross-developer peersimage, text
vsfamily variantstext
vscross-developer peerstext
vscross-developer peerstext
vscross-developer peerstext

Primary Evidence

Sources and Freshness

Questions

Command A vs Command A Vision FAQs

Is Command A or Command A Vision better for coding?+

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

Which is cheaper, Command A or Command A Vision?+

Only Command A has a directly sourced input price: $2.50 per million tokens. Only Command A has a directly sourced output price: $10.00 per million tokens.

Which has a larger context window, Command A or Command A Vision?+

Command A has the larger sourced context window. Command A supports 256,000 and Command A Vision supports 128,000.

Which performs better in benchmarks, Command A or Command A Vision?+

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

Can Command A or Command A Vision be self-hosted?+

Both models have the same recorded self-hosting status: unsupported. Command A is not marked open weight; Command A Vision is not marked open weight.

Can Command A and Command A Vision understand images?+

Command A is not documented with image input; Command A Vision is documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, Command A or Command A Vision?+

Neither has a larger sourced maximum output. Command A is 8,000 and Command A Vision is 8,000.

Do Command A and Command A Vision support reasoning and tool use?+

Command A: tool calling. Command A Vision: reasoning and image input. Feature support does not establish relative quality.

Which is available from more inference providers, Command A or Command A Vision?+

Command A has 1 sourced provider route; Command A Vision has 1, a tie.

Which offers better value, Command A or Command A Vision?+

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.

Send Feedback