Command A Translate vs Grok Build 0.1

At a Glance

Compare
Intelligence, Cost, and Efficiency
CostLower is better · Published-token output estimateUnrankedNot in the 44-model eligible cohort#1 of 44$0.0020 per LiveBench case
Pricing and Limits
Input priceFrom · USD / 1M tokensNot reported$1.00Xai · Sep 3, 2026
Output priceFrom · USD / 1M tokensNot reported$2.00Xai · Sep 3, 2026
Context windowMaximum documented tokens8K256K
Model facts checkedSep 3, 2026View model evidence →Sep 3, 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

All benchmark results →
No Protocol-Matched Benchmark Yet.Results appear here only when both models share the same benchmark version, metric, evaluation protocol, and evidence class.

Side-by-Side Facts

FieldCommand A TranslateGrok Build 0.1
DeveloperCoherexAI
FamilyCommand AGrok Build
ModelCommand A TranslateGrok Build 0.1
VersionCommand A TranslateGrok Build 0.1
Lifecycleactivepreview
Released2025-08-282026-05-29
Knowledge cutoff2024-06-01Unknown
Input modalitiesTextText, Image
Output modalitiesTextText
Context window8K256K
Total parameters111BUnknown
Active parametersUnknownUnknown
LicenseUnknownUnknown
Open weightsNoNo
API availableYesYes
Self-hostableNoNo
Provider accessCohere (Standard)Xai (Standard)
Capabilitieschat, generation, structured_outputs, translationchat, generation, reasoning, structured_outputs, tools

Command A Translate Capabilities

chatgenerationstructured outputstranslation
Serving providers1
Canonical IDcoherelabs/command-a-translate-08-2025

Grok Build 0.1 Capabilities

chatgenerationreasoningstructured outputstools
Serving providers1
Canonical IDxai/grok-build-0.1

Primary Evidence

Sources and Freshness

Questions

Command A Translate vs Grok Build 0.1 FAQs

Is Command A Translate or Grok Build 0.1 better for coding?+

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

Which is cheaper, Command A Translate or Grok Build 0.1?+

Only Grok Build 0.1 has a directly sourced input price: $1.00 per million tokens. Only Grok Build 0.1 has a directly sourced output price: $2.00 per million tokens.

Which has a larger context window, Command A Translate or Grok Build 0.1?+

Grok Build 0.1 has the larger sourced context window. Command A Translate supports 8K and Grok Build 0.1 supports 256K.

Which performs better in benchmarks, Command A Translate or Grok Build 0.1?+

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 Grok Build 0.1 be self-hosted?+

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

Can Command A Translate and Grok Build 0.1 understand images?+

Command A Translate is not documented with image input; Grok Build 0.1 is documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, Command A Translate or Grok Build 0.1?+

Neither has a larger sourced maximum output. Command A Translate is 8K and Grok Build 0.1 is —.

Do Command A Translate and Grok Build 0.1 support reasoning and tool use?+

Command A Translate: none of these features are definitively sourced. Grok Build 0.1: reasoning, tool calling, and image input. Feature support does not establish relative quality.

Which is available from more inference providers, Command A Translate or Grok Build 0.1?+

Command A Translate has 1 sourced provider route; Grok Build 0.1 has 1, a tie.

Which offers better value, Command A Translate or Grok Build 0.1?+

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