Measuring the tokenizer that actually governs the bill is the right correction to the 6.1-times headline. I would extend the measurement to the whole multilingual request path: query language, retrieved-document language, and answer language can each contribute a different token distribution.

The average 1,531 retrieved tokens is useful, but an Amharic question answered from English source passages is a different workload from an entirely Amharic exchange. A small matrix of those paths, with input and output tokens reported separately, would show where the 1.9-times ratio actually applies. It would also make cost projections more useful as Afaan Oromoo traffic grows.