3.0× less energy than Command A.
Command A Environmental Impact
Enterprise RAG and agent model — 256K context, 23 languages
The figures below are for one quick question. A longer chat with follow-ups uses about 2.1 Wh, and an hour or two of agent work about 60.0 Wh.
One query, in context
Energy, carbon and water for a single use. Quick single question (one exchange)
About 2.0× a Google search and 72% of a minute of laptop use.
About 1.8× a Google search and 10% of 10 m by car.
About 22× a drop of water and 22% of a teaspoon of water.
- Where it runsCloud (US / EU / Asia)
- Grid carbon intensity450 g CO₂/kWh · 25% renewable
- Compared with a Google search2x more than a search (0.3 Wh)
- Water~909 queries to fill 1 litre
Where Command A sits
#128 of 199 by energy per query. Heavier than 62% of all models. Lit dots are the same kind of model; click any dot to open it.
Want something lighter?
1.5× less energy than Command A.
1.5× less energy than Command A.
What a month of use adds up to
Pick how much you use it. Based on one quick use at a time, five days a week.
- Energy
- 65.0 Wh
- Carbon
- 22.7 g
- Water
- 119 mL
A month of 5 chats a day, 5 days a week. The energy is about 5.4× a phone charge and 59% of a kettle boil.
Work out your own →- Energy
- 259.8 Wh
- Carbon
- 90.9 g
- Water
- 476 mL
A month of 20 chats a day, 5 days a week. The energy is about 2.4× a kettle boil and 4% of a UK home's day.
Work out your own →- Energy
- 1.30 kWh
- Carbon
- 454.6 g
- Water
- 2.38 L
A month of 100 chats a day, 5 days a week. The energy is about 12× a kettle boil and 18% of a UK home's day.
Work out your own →How does Command A compare?
Next to similar models. Bars use a log scale, so each step is a big jump.
Detailed breakdown
Energy
We estimate Command A at ~0.6 Wh for a quick single question. The open-weight models CLEER has benchmarked directly follow a clear pattern: roughly 0.02 Wh plus 0.005 Wh per billion parameters active on each token (our fit across 11 models from 3B to 49B active). Command A activates ~111B (it is a dense model, so every parameter is active), which gives ~0.6 Wh when served from a batched data-centre deployment. That is above the range the fit was built on, so treat it as indicative. Run locally, the figure depends entirely on your hardware. This is our extrapolation, not a CLEER figure or a measurement. It replaces our earlier ~1.3 Wh estimate, which was built on 2025 benchmark figures for older hardware.
Power source & carbon
Cohere offers deployment across multiple cloud providers and regions, including private cloud deployments. This gives enterprises control over which grid powers their inference.
Water use
At ~1.1 mL per quick question, derived from the energy estimate at the ~1.8 L/kWh water factor we apply to this model's infrastructure. Water scales directly with energy, so longer chats, reasoning and agentic sessions use proportionally more.
About Command A
Command A is a 111B-parameter text and chat model from Cohere, released March 13, 2025. Enterprise RAG and agent model — 256K context, 23 languages. At 0.60 Wh per query, it uses 2x the energy of a Google search. It runs on a Dense Transformer (RAG-optimised) architecture.
These figures are estimates derived from hardware specifications and API benchmarks — Cohere has not published official energy data for Command A. Actual consumption may vary significantly depending on batching, quantisation, and infrastructure optimisations that we cannot observe from outside.
Command A in context
What does your Command A usage cost the planet?
Use the calculator to estimate your personal footprint based on how often you use Command A.
Frequently asked questions
How much energy does Command A use per query?
Each Command A query consumes approximately 0.60 Wh of energy. This is 2x more than a traditional Google search (~0.3 Wh).
What is Command A's carbon footprint?
Based on the carbon intensity of Cloud (US / EU / Asia), each query produces approximately 0.21 g of CO2. The grid in this region has a carbon intensity of 450 g CO2/kWh with 25% renewable energy.
How much water does Command A use?
Each query consumes approximately 1 mL of water, primarily used for cooling the data centers that process the request.
How does Command A compare to a Google search?
A Command A query uses 2x more than a Google search in terms of energy. A Google search uses approximately 0.3 Wh, while Command A uses 0.60 Wh.
Technical details
- Architecture
- Dense Transformer (RAG-optimised)
- Parameters
- 111B
- Context window
- 256,000 tokens
- Release date
- 2025-03-13
- Open source
- No
- Training data cutoff
- 2025-02