You don't pay the meter rate. You pay the fare.
token cost vs. task cost
The meter rate isn't the fare
Everyone compares price per token. You pay per task. On Artificial Analysis's own numbers, the gap between the two is where the budget goes.
This week someone dropped Artificial Analysis's intelligence-vs-cost chart into a trading group I'm in, with two green arrows pointing at the top right.
Everyone looks at the top right. I looked at the x-axis. It isn't price per token. It's cost per task, and those are different numbers.
Rate times distance
Think of a taxi. Price per token is the meter rate. Tokens per task is the route the driver takes. You pay the fare.
The dial you own
Same model, same price per token, four effort settings:
The price of a point
So what do I do with this?
Budget in tasks, not tokens. Ask vendors for cost per task on your workload, then set the effort dial as low as the task will stand.
We learned this the hard way in our own census. The model that ate about a third of our bill didn't have the highest price per token. It just took the long way round.
One thing I can't settle: these are one lab's numbers, on its workload, read on one day, and it hasn't published the v4.3 weights. Your tasks will take a different route.
You don't pay the meter rate. You pay the fare.
When did you last see an AI budget line priced per task instead of per token?
Every figure here describes something measured and committed. See the measurements · read the method