Side-by-side comparison
Command A vs Goliath 120B
| Command A | Goliath 120B | |
|---|---|---|
| Provider | Cohere | Alpindale |
| Context window Maximum tokens (input + output) the model can process in a single request. Glossary → | 256,000 | 6,144 |
| Capabilities Optional capabilities the model advertises: vision (images), tools (function calling), json_mode (structured output). | json_mode | json_mode |
| Input $ / 1M tokens Cost for tokens you send (prompt + context). Cheaper side highlighted. Glossary → | 2.5000 | 3.7500 |
| Output $ / 1M tokens Cost for tokens the model generates. Output is normally 3–5× pricier than input. Glossary → | 10.0000 | 7.5000 |
Frequently asked questions
Which is cheaper, Command A or Goliath 120B?
Goliath 120B is cheaper than Command A on a 50/50 input/output blend by about $0.625 per 1M tokens. Exact savings depend on your input-vs-output ratio — use the cost calculator on this page for a workload-specific estimate.
Which has a larger context window, Command A or Goliath 120B?
Command A has the larger context window at 256k tokens versus 6k tokens for Goliath 120B. That means Command A can ingest about 41.7x as much text per request.
What is the difference between Command A and Goliath 120B?
Command A comes from Cohere; Goliath 120B comes from Alpindale. They differ in pricing, context window, and supported capabilities — see the side-by-side table on this page for the exact figures, refreshed nightly.