—
·
an illustrated field guide, drawn badly on purpose
You type eight words and press send. Somewhere between your thumb and the answer, a building in another country gets slightly warmer and evaporates a mouthful of water. Here is the whole journey, one stop at a time.
…for one ordinary message. Now multiply by a billion a day.
Type anything. We will follow it the whole way and keep the receipts.
Click any stop to poke at it. Or hit play and watch your message travel.
pick a stop up there, or press play
·
Everything you have sent on this page, added up. Keep sending, watch the glass fill.
0 mL evaporated on your behalf
0 messages sent
— on site · — at the power plant
Same message, different choices. Watch the same question cost twenty times as much — or a fortieth.
300 output tokens (~225 words)
1,200 tokens of history re-read every single turn
one message, with these settings
A mouthful is nothing. That is exactly why the argument is never about one message.
1 billion messages a day
—
Six things that come up every time a data centre shows up in a town. Tap a card to open it.
Not "turn off your camera on calls". Things with real leverage.
None of this is an argument for not using the thing. It is an argument for knowing what you are spending, the same way you know roughly what a flight costs or what a steak costs.
A mouthful of water. Then you close the tab.
And, more importantly, how wrong they might be.
Nobody outside the big labs knows the real per-message figures, and the honest published range spans more than a factor of ten. These are back-of-an-envelope estimates anchored to the few measurements that exist.
The shape of the thing is solid — decode dominates, water follows the grid, location matters more than almost anything. The exact digits are not.
IT energy = (context + input) × 0.12 mWh + output × 0.95 mWh × model factor
facility = IT energy × PUE
water = facility kWh × (on-site WUE × cooling factor + off-site EWIF)
carbon = facility kWh × grid intensity