Loading...

How Credits Work

What a credit is and what spends it. Compiling in Cloud Build is free, but every AI run, a bug fix included, costs credits. How to make fixes cheaper.

Credits are the currency

Almost everything the AI does for you costs credits: a chat message, a generated image, a plugin, a video. Two AI actions are free: Enhance prompt, the sparkle button beside the box on the home screen that rewrites your idea into a fuller description, and the plan a generator page shows you before you have an account.

Most charges happen once: you spend credits on a run. Three things repeat instead, every 30 days, paid from the same balance: a bot hosting plan (one for each bot you host), VyroAI+, and extra storage. When the balance runs out, you top up.

The build is free. Fixing the bug is not

This is the commonest surprise on VyroAI, so it is worth being blunt about.

Compiling really is free. Pressing Build sends your project to Cloud Build, and that costs you nothing, however many times you press it.

Fixing an error is an AI run, and AI runs cost credits. To fix a bug the AI has to read your code, read the error and write corrected code — the same work as writing a feature, so it is priced the same way. That is true whether you press Auto-Fix on the failed build or type "fix the build error" into the chat: both are the same run.

So a build that fails, gets fixed, fails again and gets fixed again is two paid runs and no free ones. Nothing is charged for the compiling in between.

How to make fixes cost less

Three habits do most of the work, and they are the same three our support answers give:

• Paste the exact error. Copy the real console or build output rather than typing "it does not work". VyroAI keeps the fixes that were proven to solve each error before and feeds them back in when it recognises the same error again — but it can only recognise it from the real text. Guessing costs you extra attempts; pasting usually costs you one.
• One problem per message. Three unrelated bugs in one message make one long, expensive run that often half-solves all three. Sent separately they are three short ones.
• Use the Auto-Fix button on the failed build, not a fresh description in chat. The button hands the compiler output over exactly as it came out; re-describing the failure in your own words throws that away and makes the AI work it out again.

If a run was genuinely broken — the AI errored, or produced nothing usable — report it with the feedback dialog rather than paying for a second attempt. See Refunds When Something Fails.

Seeing your balance

Your balance sits in the top bar on most pages — the exception is the Code Studio, whose toolbar belongs to the project. Profile → Usage breaks it down: what you have, what you have spent, and over which period — the last 7 days, the last 30 days, or all time.

You see the price first

Before you generate anything expensive, the screen tells you what it will cost. Image and video generation both show the price in a summary just above the button, and it changes as you change the options — a bigger format or HD quality costs more than a small one.

The Pricing page has the live, always-current numbers for every pack and plan. This article deliberately does not repeat them, so it can never go stale.

Two ways to keep a lid on it

If you would rather not rely on watching the number: the full cost of an image or a video is written beside the Generate button before you press it — there is no confirmation step after that press, so that number is your last look — and you can set a monthly spending limit that warns you as you approach it — see Spending Limit.

The Image Creator's Chat mode asks before it draws — a Generate / Edit / Cancel row appears before any picture is made — but two things are worth knowing. It shows no price on that row, unlike the normal form; and the conversation is billed as you talk, so the wait for Generate covers the image, not the chat turn that proposed it. Watch the balance while using it, or stay in the normal form if you want to see the cost before you confirm.

Where to next

• Next in Getting Started: Earning Free Credits
• When the balance is low: Buying Credits — How to actually top up.
• Sitting on unused credits: Do Credits Expire? — Purchased credits last a year.
• Spent faster than expected: Usage & History — Where your credits went.
• Worried about overspending: Spending Limit — A monthly budget with warnings.

Also linked from this page: Auto-Fix — the button that spends a run, and how to spend fewer

12 of 19 in Getting Started · Last checked 18 September 2026 · Previous: The Public Menu