2.4 mo
Traffic doubled roughly every quarter
From 22.3T in Oct 2025 to 379T in Aug 2026 is 17x in 10 months, a doubling every 2.4 months. Any footprint that doubles that fast is out of date by the time it is reported.
A single gateway now routes 379 trillion tokens a month, 83.7 kt of CO₂e, up 17x in a year, and none of it appears in a Scope 3 disclosure. Your own usage curve has the same shape.
1,276T
tokens routed, Oct 2025 to Aug 2026
281.7 kt
CO₂e over the eleven months, methodology v1.2
17x
growth in monthly tokens over the year
66%
of Aug 2026 traffic went to six providers
Between Oct 2025 and Aug 2026, OpenRouter’s public rankings recorded 1.3 quadrillion tokens routed through one gateway, with monthly volume growing 17x. Run through CrbonFree methodology v1.2, that traffic amounts to about 281.7 kt of CO₂e for the year, concentrated in six providers, and reported by no one at this granularity.
Fetched 13 Sep 2026, 17:19 UTC from the product's public endpoint, which mirrors openrouter.ai/rankings as of 2026-09-13. Page last checked 5 September 2026. Every figure on this page is computed from the dataset below.
The monthly series, the computed CO₂e with bounds and the provider share are published as JSON so a spreadsheet, a script or an agent can check them.
Download the datasetCite as: Crbon Labs, “OpenRouter public traffic, metered with CrbonFree methodology v1.2”, data from OpenRouter as of 2026-09-13 (fetched 13 sep 2026, 17:19 utc).
2.4 mo
From 22.3T in Oct 2025 to 379T in Aug 2026 is 17x in 10 months, a doubling every 2.4 months. Any footprint that doubles that fast is out of date by the time it is reported.
33%
The average month added 33 percent on the one before. Two months, Mar 2026 and Apr 2026, each grew by more than half.
66%
DeepSeek, OpenAI, Tencent, Xiaomi, Google, Z-AI together took 66 percent of Aug 2026. Concentration like that means a handful of provider choices decide most of the footprint.
61,247
281.7 kt of CO₂e is what about 61,247 passenger cars emit in a year, or roughly 281,735 economy round trips between New York and London.
Sources: US EPA, 4.6 t per typical passenger vehicle per year; ICAO carbon calculator, about 1 t per round trip
±28%
The Aug 2026 figure of 83.7 kt sits in a band from 60.1 kt to 107.4 kt. The band is stated on purpose: a number without one cannot be audited.
22.3T in Oct 2025 to 379T in Aug 2026. The curve is public, but nobody publishes the footprint underneath it. Hover a month for its figures.
1.3 quadrillion tokens over eleven months
Tokens are as published by OpenRouter, and the CO₂e comes from methodology v1.2 at the medium tier, assuming a 75/25 input to output split. Every row can be reproduced from the factors below.
| Month | Tokens | Share of peak | vs prior | CO₂e est. |
|---|---|---|---|---|
| Oct 2025 | 22.3T | – | 4.9 kt | |
| Nov 2025 | 26.6T | +19% | 5.9 kt | |
| Dec 2025 | 26T | -2% | 5.7 kt | |
| Jan 2026 | 31.7T | +22% | 7.0 kt | |
| Feb 2026 | 49.8T | +57% | 11.0 kt | |
| Mar 2026 | 83.8T | +68% | 18.5 kt | |
| Apr 2026 | 97.1T | +16% | 21.4 kt | |
| May 2026 | 123T | +27% | 27.1 kt | |
| Jun 2026 | 188T | +53% | 41.6 kt | |
| Jul 2026 | 248T | +32% | 54.8 kt | |
| Aug 2026 | 379T | +53% | 83.7 kt | |
| Eleven months | 1,276T | 17x | 281.7 kt |
Share of Aug 2026 traffic by model provider, from OpenRouter’s public rankings, with the CO₂e each share implies at the month’s total of 83.7 kt.
This is methodology v1.2, the same three layers the product applies to a customer’s own usage, and it adopts Watershed’s open framework for measuring emissions from AI usage. It is written out here so an auditor can redo the arithmetic.
Per trillion tokens, medium tier
221 t CO₂e
About 459 MWh at the facility meter after host power, utilisation and PUE.
Each token is charged joules for the work it causes: 0.3 J per input token read, 0.5 J per output token generated, 0.03 J when served from cache. Aggregate counts carry no cache data, so nothing is credited to caching here. The 75/25 split is the methodology's worked-example assumption for gateway traffic.
Accelerators do not run alone. Host power adds 18%, clusters average 30% utilisation, and the data centre's overhead is a PUE of 1.2. Grid intensity is 0.42 kg CO₂e per kWh, a global average for the medium tier.
Hardware manufacturing adds 0.02 kg and model training 0.008 kg per million tokens, amortised over the fleet's serving life. This is the figure reported everywhere on this page.
IPCC Tier 1 root sum of squares of 20% activity and 20% factor uncertainty: ±28.3%. For Aug 2026 that is a band of 60.1 kt to 107.4 kt around 83.7 kt.
The public dataset is aggregate, so there is no per-model tiering. Network transfer, end-user devices and the gateway’s own routing infrastructure are left out, and the product reports water separately. Every one of these exclusions pushes the number lower, so the figure on this page is a floor.
A public dataset gets you a shape and a scale. An auditor asks for more. Each row pairs the question with what this page has and what CrbonFree adds when the usage is yours.
Which models and providers produced it?
Provider share for one month, from the public rankings.
Per model and per provider, per call, in the dashboardWhich factors, and which version?
Methodology v1.2, medium tier, stated below.
The full methodology with every factorHow sure are you?
A band of plus or minus 28.3 percent on every figure.
The same band on every figure your own usage producesWho on your team used it?
Not in a public dataset.
The CLI meters coding agents per person and per modelCan an agent or a script check the number?
The dataset behind this page, as JSON.
Seven read-only MCP tools and a typed SDKQuestions
Short answers. The methodology page has the factors and the arithmetic.
Read the methodologyNo. OpenRouter publishes aggregate token counts in its public rankings, and this page applies the CrbonFree methodology to those counts. The carbon figures are ours, not OpenRouter’s, and the assumptions behind them are listed on this page.
They belong to the organisations sending the requests, as purchased services under Scope 3, and to the providers running the models, as the energy their data centres draw. The point of the study is that neither side reports them at this granularity today.
Each figure carries a band of plus or minus 28.3%, the root sum of squares of a 20% activity uncertainty and a 20% factor uncertainty. The public dataset is aggregate, so no per-model factors are applied, which pushes the estimate down rather than up.
The public counts do not separate input from output, and output tokens cost more energy to generate than input tokens cost to read. The methodology’s worked example for gateway traffic assumes three quarters input and one quarter output, and this page uses the same assumption.
Yes. Connect a provider with a read-only key, install the CLI for coding agents or switch on the browser extension, and the dashboard reports your usage per model and per provider with the same methodology and the same uncertainty band.
However your team already runs AI, that is how you connect. Paste a read-only provider key, drop in an SDK, add the MCP server, install the CLI or switch on the browser extension, and the first measured tokens reach your dashboard within seconds.
Free plan · first tokens in seconds