Command A vs Reka Edge
Compare Command A from Cohere and Reka Edge from rekaai on key metrics including benchmarks, price, context length, and other model features. Access both models and hundreds of others through the OpenRouter API.
Overview
Analysis
Command A vs Reka Edge at a glance
| Attribute | Command A | Reka Edge |
|---|---|---|
| Input price | $2.50/M tokens | $0.10/M tokens |
| Output price | $10/M tokens | $0.10/M tokens |
| Context window | 256,000 tokens | 16,384 tokens |
| Intelligence Index | Not available | Not available |
| Coding Index | Not available | Not available |
| Agentic Index | Not available | Not available |
| Latency (p50) | 0.43 s | 0.56 s |
| Throughput (p50) | 66.0 tok/s | 92.0 tok/s |
| Provided by | Cohere | rekaai |
| Model page | Command A model details, providers and pricing | Reka Edge model details, providers and pricing |
Benchmark data updated
Frequently asked questions
Is Command A cheaper than Reka Edge?
Reka Edge is cheaper than Command A on OpenRouter: Reka Edge costs $0.10/M tokens input and $0.10/M tokens output, while Command A costs $2.50/M tokens input and $10/M tokens output.
Which has the longer context window, Command A or Reka Edge?
Command A has the longer context window at 256,000 tokens, compared with 16,384 tokens for Reka Edge.
Which is faster, Command A or Reka Edge?
Reka Edge is faster on OpenRouter, generating a median 92.0 tokens per second compared with 66.0 tokens per second for Command A.