Observed spend
What developers actually spend on gpt-5.3-codex — 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.
Spend per developer sits mid-pack: used for real work without being the default for the heaviest sessions.
For scale, spend per developer across tracked models runs from claude-haiku-4-5 at $51 to gpt-5.6-sol at $12,698 — a spread list pricing alone never reveals, because it depends entirely on what people reach for the model to do.
| Model | Per developer | Share |
|---|---|---|
| gpt-5.3-codex | $292 | 0.4% |
| gpt-5.6-sol | $12,698 | 22% |
| claude-opus-4-8 | $5,111 | 17% |
| claude-fable-5 | $5,468 | 17% |
| claude-opus-5 | $8,233 | 15% |
| gpt-5.5 | $5,372 | 13% |
| claude-opus-4-6 | $1,797 | 5% |
| claude-opus-4-7 | $1,757 | 4% |
| claude-sonnet-5 | $649 | 2% |
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.