viberank
Model economics

Observed spend

gpt-5.6-sol

What developers actually spend on gpt-5.6-sol — 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
$9,347
across their tracked usage
Developers
361
observed using it
Share of spend
13%
#3 of all models tracked

Frontier workload

High spend concentrated in relatively few developers — the pattern of a model reserved for long agentic runs rather than everyday edits.

For scale, spend per developer across tracked models runs from claude-sonnet-4-6 at $217 to claude-opus-5-5 at $18,979 — 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
gpt-5.6-sol$9,34713%
claude-opus-5-5$18,97919%
claude-opus-5$12,30918%
claude-opus-4-8$4,8229%
claude-fable-5$5,2209%
gpt-6-astra$8,8618%
gpt-5.5$4,6448%
claude-opus-4-7$2,3213%
claude-fable-5-1$2,9633%

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.

Folded from 2 raw identifiers: [pi] gpt-5.6-sol, gpt-5.6-sol — the same model reached through different harnesses.

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.