Side-by-side comparison
Command A vs Jamba Large 1.7
| Command A | Jamba Large 1.7 | |
|---|---|---|
| Provider | Cohere | AI21 |
| Context window Maximum tokens (input + output) the model can process in a single request. Glossary → | 256,000 | 256,000 |
| Capabilities Optional capabilities the model advertises: vision (images), tools (function calling), json_mode (structured output). | json_mode | tools, json_mode |
| Input $ / 1M tokens Cost for tokens you send (prompt + context). Cheaper side highlighted. Glossary → | 2.5000 | 2.0000 |
| Output $ / 1M tokens Cost for tokens the model generates. Output is normally 3–5× pricier than input. Glossary → | 10.0000 | 8.0000 |
Frequently asked questions
Which is cheaper, Command A or Jamba Large 1.7?
Jamba Large 1.7 is cheaper than Command A on a 50/50 input/output blend by about $1.25 per 1M tokens. Exact savings depend on your input-vs-output ratio — use the cost calculator on this page for a workload-specific estimate.
What is the difference between Command A and Jamba Large 1.7?
Command A comes from Cohere; Jamba Large 1.7 comes from AI21. They differ in pricing, context window, and supported capabilities — see the side-by-side table on this page for the exact figures, refreshed nightly.