Buying Guides

Practical buying guide

How AI app builders bill: tokens, credits, messages and the costs outside the plan

Prompt-to-app builders sell a monthly allowance rather than a number of apps. Knowing which unit is counted, when it resets and what sits outside the plan is the difference between a predictable bill and a stalled project.

By AI RightFitPublished AI-assisted editorial analysis

Three ways the same work gets counted

These builders meter usage in different units, so allowances cannot be compared line by line.

  • Tokens (Bolt). Bolt counts the text it reads and writes, including your project files. Its help centre explains that most usage comes from reading and syncing the project, so each message costs more as the app grows.
  • Dollar-value credits spent by tokens (v0). v0 gives a monthly credit balance in dollars and charges it at per-model token rates listed on its pricing page. Larger models cost far more per token, so model choice matters.
  • Dollar-value credits spent by effort (Replit). Replit charges Agent work per checkpoint, scaled to how much work a request took, and its docs say planning can be charged even when no code changes.

Free tiers may add a daily message cap; v0 Free allows seven a day.

Why one revision can use many units

A single request such as changing a form layout is rarely one small operation. The tool may reread files, rewrite them, check the result and retry on errors. On token-metered tools that whole loop is billed, and because context grows with the project, the same request costs more in week four than in week one. On effort-metered tools a vague request can become a long job. Make small edits yourself where a code editor is offered (Bolt says Code view edits use no tokens), and ask for one specific change per message.

Daily limits, monthly resets and rollover

  • Bolt Free gives 1M tokens a month with a separate 300K daily ceiling; unused daily tokens are lost and free tokens never roll over.
  • Bolt paid plans refill on the renewal date. Unused tokens roll over and stay valid for two months from the start of the cycle that issued them, and the oldest are spent first. Cancelling removes access to rolled-over tokens when the cycle ends.
  • v0 Plus adds $30 of monthly credit per user plus $2 of daily credit on login. The pricing page does not say whether either balance rolls over or when bought credits expire.
  • Replit Core includes $20 of monthly credit that resets each cycle without rolling over. Pro credits roll over for two months, and top-up credits expire six months after purchase.

For how free allowances differ from trials, see free plans, trials and sign-up credits.

Hosting, databases and other costs outside the allowance

The build allowance is not the whole bill once an app is live.

  • Bolt includes hosting with paid plans, shared across every site on the account: 30 GB of bandwidth and 1M requests a month on Pro, against 10 GB and about 333K requests on Free, where a site goes offline for the rest of the month at the limit. Pro can switch on pay-as-you-go overage with a spending cap. A Supabase database needs a paid plan, and Bolt's help pages do not cover Supabase's own charges.
  • Replit draws published apps, storage, database storage and network transfer from the same credit pool as Agent work, so a busy live app competes with your building budget.
  • v0 deploys to Vercel, but its pricing page does not state hosting prices, so check the Vercel account the project lands in.

For export and domains, see the website builder exit plan.

Worked example: one small app over one month

Suppose you build a booking page on Bolt Pro at $25 a month (the 10M-token tier named in Bolt's billing help). The weekly token figures below are illustrative assumptions for the arithmetic, not measurements; replace them with the numbers from your own usage screen.

Illustrative Bolt Pro month (10M tokens)
WeekWorkTokens usedRemaining
1First build3.5M10M − 3.5M = 6.5M
2Layout and form fixes2.5M6.5M − 2.5M = 4.0M
3Add sign-in2.0M4.0M − 2.0M = 2.0M
4Copy and bug fixes1.5M2.0M − 1.5M = 0.5M

Total use is 9.5M, so 0.5M rolls into month two, where you would start with 10M + 0.5M = 10.5M at another $25. The same week-one build would not fit on Bolt Free: seven days at the 300K daily ceiling allows 2.1M, but the 1M monthly cap stops you first.

On v0 Plus at $30, logging in on 20 days would add 20 × $2 = $40 of daily credit to the $30 monthly credit, up to $70 of usage value if each day's credit is spent; whether unspent daily credit carries over is not stated. On Replit Core, the $20 credit must cover both Agent work and the live app; if that month's usage came to $26, about $6 would need top-up or pay-as-you-go credit on top of the subscription fee.

Checks to run before you pay

  1. Build the first screen on a free tier and note the units used per message from the usage page, then repeat the same request a week later to see how project growth changes it.
  2. Find where hosting and database use is reported.
  3. Set any spending cap or budget alert the tool offers before enabling overage.
  4. Check what happens to rolled-over or bought credits on cancelling.

The coding assistant purchase test covers a broader evaluation method.

Sources and scope

Pricing examples use the dated records below. This article is a snapshot, not a live checkout quote. Open the tool record and official source for current terms.

AI-assisted editorial analysis using dated public-source snapshots. No hands-on product testing or human review is claimed. Calculations are illustrative, before tax and extras, with assumptions stated in the text.

Editorial policy · Verification method · Report a source or calculation error