How credits are charged

A credit is Vibely's unit of AI spend, and exactly one thing consumes credits: an agent turn — a message you send in chat, plan, or build mode. Nothing else on the platform is metered.

The formula

Billing is measured, not estimated. When a turn ends, Vibely takes the real provider cost of the tokens that turn actually used and converts it:

credits = max(CREDIT_MIN_PER_TURN, costUsd × CREDIT_PER_USD)

On vibely.sh, CREDIT_PER_USD is 30 and CREDIT_MIN_PER_TURN is 0.5. A turn that cost $0.04 of model spend bills 1.2 credits; a turn that cost $0.001 bills the 0.5 floor.

Two consequences worth knowing before they surprise you:

• There is a floor and no ceiling. Every billed turn costs at least 0.5 credits, and a turn that genuinely spends $2 of model time bills 60.
• Chat and plan turns bill exactly like build turns. The charge tracks the work, not the button you pressed. A long conversation on a large model costs more than a short one on a small model.

Model choice is the biggest lever you have.

What is free

Action	Metered
Chat, plan and build turns	Yes
An auto-fix turn — the agent repairing an error it caused	No, always 0
A build turn that called no tools	No, always 0
Visual edits in the preview (no model turn runs)	No
Publishing, re-publishing, custom domains	No
Mobile builds, OTA updates and store submissions	No
Preview sandbox time, restarts, hot reload	No
Storage, file uploads, project count	No

The two zero cases are guarantees in the pricing function, not discounts applied afterwards. If the agent breaks something and fixes it, you are not billed for the repair.

The visual-edit line is the cheap lever most people miss: selecting an element in the preview and changing its typography, colour, spacing or layout writes the change into the real source at the exact file and line, re-runs the build check, and runs no model turn at all. Nudging padding by prompt costs credits; nudging it in the inspector does not.

How a charge is recorded

Each charge is one atomic database call that moves the money and writes the ledger row in the same transaction — there is no window where your balance has moved but the receipt is missing, and two turns finishing at the same moment queue rather than race.

The charge drains your wallet in a fixed order:

1. Unexpired rollover first. Rollover is last cycle's leftover and expires first, so it is spent first.
2. Then this cycle's balance.
3. Never below zero. A charge larger than the wallet clamps both buckets to 0 and records the shortfall as an overrun on the ledger row. Your balance cannot go negative.

Where to watch it

Three screens in workspace settings:

• Usage — credits used against granted with the reset date, broken down by project and by teammate for the current cycle, plus the top-up flow.
• Auto top-up — adds a fixed number of credits when the balance falls below a threshold you set, charged to a saved card, with a monthly cap. Owner-only.
• Usage limits & alerts — per-scope caps and low-balance alerts. A limit can target the whole workspace, a project type, a named member or the balance itself, and can either warn or block turns outright.

Billing is USD only. Current plan prices, included credits and top-up rates live on the pricing page.

Three habits that cut spend

• Use plan mode before a big change. One plan turn beats three wrong builds.
• Make small visual changes in the preview inspector rather than in chat — they cost nothing.
• Scope each turn to one thing. A turn that tries four features costs more and produces a diff you cannot review.