Asking very specific questions to Sonnet 3.7 costs a couple of tenths of a cent every time, and even if you're doing that all day it will never amount to more than maybe a dollar at the end of the day.
On average, one line of, say, JavaScript represents around 7 tokens, which means there are around 140k lines of JS per million tokens.
On Openrouter, Sonnet 3.7 costs are currently:
- $3 / one million input tokens => $100 = 33.3 million input tokens = 420k lines of JS code
- $15 / one million output tokens => $100 = 3.6 million output tokens = 4.6 million lines of JS code
For one developer? In one day? It seems that one can only reach such amounts if the whole codebase is sent again as context with each and every interaction (maybe even with every keystroke for type completion?) -- and that seems incredibly wasteful?
I can't edit the above comment, but there's obviously an error in the math! ;-) Doesn't change the point I was trying to make, but putting this here for the record.
33.3 million input tokens / 7 tokens per loc = 4.8 million locs
3.6 million output tokens / 7 tokens per loc = 515k locs
That's how it works, everything is recomputed again every additional prompt. But it can cache the state of things and restore for a lower fee, and reingesting what was formerly output is cheaper than making new output (serial bottleneck) so sometimes there is a discount there.
On average, one line of, say, JavaScript represents around 7 tokens, which means there are around 140k lines of JS per million tokens.
On Openrouter, Sonnet 3.7 costs are currently:
- $3 / one million input tokens => $100 = 33.3 million input tokens = 420k lines of JS code
- $15 / one million output tokens => $100 = 3.6 million output tokens = 4.6 million lines of JS code
For one developer? In one day? It seems that one can only reach such amounts if the whole codebase is sent again as context with each and every interaction (maybe even with every keystroke for type completion?) -- and that seems incredibly wasteful?