viberank
Model economics

Observed spend

claude-haiku-4-5

What developers actually spend on claude-haiku-4-5 — measured from real sessions, not list prices. For specs and pricing tables, look elsewhere; this page only answers what the model costs the people using it.

Per developer
$51
across their tracked usage
Developers
763
observed using it
Share of spend
0.3%
#14 of all models tracked

Everyday workhorse

Broad adoption and low spend per developer — reached for constantly, and cheap enough that it barely registers on the bill.

For scale, spend per developer across tracked models runs from claude-haiku-4-5 at $51 to gpt-5.6-sol at $12,697 — a spread list pricing alone never reveals, because it depends entirely on what people reach for the model to do.

Against other models

ModelPer developerShare
claude-haiku-4-5$510.3%
gpt-5.6-sol$12,69722%
claude-opus-4-8$5,10517%
claude-fable-5$5,46817%
claude-opus-5$8,23215%
gpt-5.5$5,37214%
claude-opus-4-6$1,7975%
claude-opus-4-7$1,7574%
claude-sonnet-5$6492%

How this is measured

Developers run npx viberank-cli, which reads token counts and API-equivalent costs that ccusage computes from their own local session logs. Spend here is what the usage would cost at model list prices — most people on the board pay a flat subscription instead, so this measures consumption rather than a bill.

Full methodology, caveats and a free JSON endpoint are on the data page. For the distribution across developers rather than models, see what Claude Code actually costs.