┌─────────────────┬──────────────┬───────────────┬────────────────────┬──────────────────────┐
│ Model │ Input ($/MTok)│ Output ($/MTok)│ Batch Input (−50%) │ Batch Output (−50%)│
├─────────────────┼──────────────┼───────────────┼────────────────────┼──────────────────────┤
│ Haiku 4.5 │ $1.00 │ $5.00 │ $0.50 │ $2.50 │
│ Sonnet 4.6 │ $3.00 │ $15.00 │ $1.50 │ $7.50 │
│ Opus 4.7 │ $5.00 │ $25.00 │ $2.50 │ $12.50 │
│ Opus 4.8 │ $5.00 │ $25.00 │ $2.50 │ $12.50 │
│ Fable 5 │ $10.00 │ $50.00 │ $5.00 │ $25.00 │
└─────────────────┴──────────────┴───────────────┴────────────────────┴──────────────────────┘
Prompt caching: −90% on input tokens (all models)
Ppl who think this is a good idea should be compelled to maintain some M4 or other configuration "files". These configuration files ALWAYS devolve into a full language if they are actually used. So now you have the language you wrote your app in and then you have another, shittier language for your configs ... that you have to maintain.
Please stop doing this.
What should we do? In this case just express the chart in a natural language. Where there are uncertainties, the LLM should ask questions to clarify and record the results.