The same AI request emits 8.5 times more CO2 in Texas than in Sweden
berget.ai ·
Berget AI released an open-source method for calculating the carbon emissions of individual AI inference requests, developed with the Stockholm Environment Institute, WattTime and Klimatkollen. The Swedish AI infrastructure provider has added per-request emissions tracking to its customer console and published its calculator and methodology under an MIT licence. The method follows the Green Software Foundation’s SCI for AI specification and accounts for infrastructure energy use, cooling and hardware manufacturing, while excluding model training.
Using identical hardware, Berget AI estimates that a typical Kimi K3 request emits 0.38 grams of CO₂e in Sweden, 1.6 grams in Ireland, 2.5 grams in Germany and 3.2 grams in Texas. The Texas estimate is 8.5 times Sweden’s, chiefly because of differences in grid emissions intensity. The example request uses about 4 Wh of energy, consists of 5,000 input and 387 output tokens, and is measured on a shared B300 deployment. Hardware manufacturing represents 89% of the Swedish result, while electricity represents 90% of the Texas result; the Texas request also uses about 6 mL of cooling water.
The calculator applies location-based average grid emissions and can estimate any model and region. Berget AI said it will add marginal-emissions estimates next month and expand coverage to chip-manufacturing water and energy impacts. The company corrected earlier Ireland, Germany and Texas estimates on 21 October 2026 after reviewing its grid-intensity sources.
What people are saying
Commenters largely accepted the core arithmetic: an AI request inherits the carbon intensity of the grid powering it, so the Texas–Sweden gap says more about fossil generation than some mysterious property of the model.
What readers liked
- Location-aware inference could shift flexible AI workloads toward abundant low-carbon power, cutting emissions without requiring users to abandon…
- Open emissions accounting for ML workloads gives developers a concrete way to compare deployment choices instead of treating AI’s footprint as…
Concerns raised
- Tiny request-level estimates can conceal runaway aggregate demand when autonomous agents issue thousands of calls and repeatedly invoke external…
- Reasoning settings can increase token consumption by up to orders of magnitude, making a model’s environmental cost highly sensitive to product…
Read full discussion analysis
Source: Hacker News · Based on 15 sampled comments · Analyzed
Discussion overview
Commenters largely accepted the core arithmetic: an AI request inherits the carbon intensity of the grid powering it, so the Texas–Sweden gap says more about fossil generation than some mysterious property of the model. Readers pointed to Sweden’s hydro, nuclear, and wind-heavy supply against Texas’s substantial gas and coal use, while noting that grid emissions also drive much of the water footprint pinned on data centers. Several saw an obvious practical response: schedule latency-tolerant inference where clean power is abundant, or condition data-center growth on clean-energy investment and carbon pricing.
The thread did not settle into simple AI condemnation. One camp argued that per-request comparisons can trivialize a fast-growing workload: autonomous agents, high reasoning settings, and tool use can multiply requests, tokens, and downstream compute dramatically. Others pushed back that the same location-dependent emissions logic applies to every electrical load, and that burgers, fossil plants, and total energy supply offer necessary scale context. A few commenters challenged the broader fixation on individual austerity, while critics replied that avoiding wasteful AI output and protecting ecosystems remain entirely defensible. There was also skepticism about emissions calculators that rely on provider hardware and backend assumptions users cannot independently inspect. The practical consensus was cleaner electricity and better accounting, but not agreement on whether AI demand itself deserves special restraint.
Points of disagreement
The sharpest dispute was whether AI’s footprint should be treated as a distinctive problem or as another consequence of dirty electricity. Critics argued that agentic workflows and expensive reasoning modes can turn tiny per-call figures into enormous demand, including harmful or pointless generated output. The opposing case was that GPUs do not emit carbon on their own: decarbonize the grid, price emissions, and place flexible inference near clean power rather than singling out AI for moral panic.
What readers liked
- Location-aware inference could shift flexible AI workloads toward abundant low-carbon power, cutting emissions without requiring users to abandon valuable tools.
- Open emissions accounting for ML workloads gives developers a concrete way to compare deployment choices instead of treating AI’s footprint as unknowable.
- Carbon taxes or clean-energy requirements could make data-center capital fund grid improvements while preserving access to AI capability.
- The discussion recognizes that latency-tolerant coding and batch workloads can trade a little responsiveness for much cleaner compute.
Concerns raised
- Tiny request-level estimates can conceal runaway aggregate demand when autonomous agents issue thousands of calls and repeatedly invoke external tools.
- Reasoning settings can increase token consumption by up to orders of magnitude, making a model’s environmental cost highly sensitive to product defaults.
- AI emissions calculators remain uncertain when providers hide the actual accelerators, serving stack, utilization, and throttling behind their APIs.
- Cheap fossil-powered inference risks adding data-center load precisely where residents already face higher electricity prices and dirtier generation.
Keep reading
Sources and details
berget.ai · Published
The same AI request emits 8.5 times more CO2 in Texas than in Sweden
Read report →
Community analysis available for 1 of 1 linked discussions.
Additional discussion searches are still incomplete.
Coverage details and dates
Latest available community analysis:
Summaries: 1 current · 0 awaiting update · 0 not verified
Latest summary update:
Hacker News · berget.ai