Why Fusion spends more tokens on purpose
Fusion uses more AI sessions than a single-agent build. Our own runs show what that extra verification caught, where it helped, and when one builder is the better buy.
topic · pricing
Tokens, not vibes: how we count what a run costs
Tokens are the primary unit for every engine in a run, metered per role: candidate lanes, judge seats, integrator, QA. Dollar figures from subscription CLIs are estimates. The usage record ships on the Receipt.
Depth is the meter
Fusion prices by verification depth: how many candidates compete, how many judges vote, how deep review goes. The meter is rigor, not tokens.
Failed runs are free
A run that misses its frozen Definition of Good is not billable. The failure still lands on a receipt; you just do not pay. Why we wired billing this way.