How Credits Work
After this page you will understand what a credit is, when your allowance comes back, what a turn actually costs, and how to get more done with fewer credits.
What a credit is
A credit is Revix's unit of AI work. Sending one message and getting the finished build back is one turn, and a turn costs credits in proportion to the work it took — how much of your place it read, how long it thought, and how much it wrote.
Small asks often cost a fraction of a credit. A whole system costs several. Charges are rounded to the nearest 0.1 credits, so your balance can read 3.4. Any billed turn costs at least 0.1, and you need at least 0.1 on your balance to start one.
Your allowance refills every day
Every plan refills daily, including the paid ones — 5 a day on Free, 25 on Developer, 75 on Studio.
Three details that surprise people:
- It is not midnight. The clock runs from your last refill. Refill at 11pm and your next one is around 11pm tomorrow.
- It happens when you come back. The refill is applied the next time you use Revix, not on a schedule in the background.
- It does not stack. Away for a week, you come back to one day's allowance, not seven.
Plan credits do not roll over. Each refill sets your allowance back to the flat number for your plan, so yesterday's unused credits are gone. Credits you bought and credits you earned behave differently — they survive every refill and never expire.
Which balance gets spent first
Revix spends in this order:
- Credits you bought in a pack
- Credits you earned — Discord bonus, content rewards, credits shared from a Studio pool
- Your daily allowance
So a pack you bought is used up before today's free refill. If you are saving a pack for a big build later, spend it soon after buying it rather than sitting on it.
Revix and Revix MAX
Both charge the same rate for the same amount of work. The difference is that MAX thinks longer before acting, so the same request usually costs more on MAX than on Revix.
Use Revix for everything ordinary. Use MAX when the shape of the problem is the hard part — a whole gameplay system, a bug you cannot pin down, a multi-screen flow. See Picking the Right Model.
Fixed prices
Some things cost a set amount rather than being metered.
| Action | Cost |
|---|---|
| Generate an image — thumbnail, game icon, gamepass icon, UI icon | 2 credits |
| Edit an image | 2 credits |
| The automatic review-and-repair pass on a new image | Free |
| 3D: the concept picture | 1 credit |
| 3D: build the mesh | 2 credits |
| 3D: add a texture pass to an existing mesh | 1 credit |
| 3D: rig a humanoid mesh | 3 credits |
| 3D: rig it and add a motion preset | 5 credits |
Revix Forge, the higher-detail mesh model, is temporarily unavailable, so it is not priced here.
Images and 3D jobs are charged before they run and refunded in full if they fail. Animations made inside Studio have no separate price; they cost whatever the turn costs.
What you are not charged for
- A turn that never reached Studio. If the plugin was not connected, nothing is billed.
- Answering a clarifying question. The card that appears above the composer pauses the same turn. Answering it resumes that turn — it does not start a new one.
- A failed image or 3D job. You get the credits back, and the message says so.
What makes a turn expensive
- Asking for several things at once. "Build a shop, a leaderboard and a settings menu" is one very long turn.
- Making it hunt. "Fix the bug" with no location means searching your whole place first.
- Turning thinking up. The deeper levels think longer, and thinking costs.
- Rework. A vague request that gets built wrong and then rebuilt costs twice.
Spending fewer credits
- One thing per message. "Build the shop screen" then "now wire the buttons" costs less than both together, and is easier to check.
- Point at the file. Use an
@mention or a full path so Revix opens the right script instead of searching for it. - Say what you actually want. Colours, sizes, names, where it goes. Detail up front is cheaper than a second attempt.
- Stay on Revix unless the problem is genuinely architectural, and leave thinking at the default.
- Answer the question card instead of stopping and re-asking — it is free and it prevents a wrong build.
- Press Stop the moment it goes the wrong way. Everything built so far is kept, and you stop paying for the rest.
A cheap, precise request looks like this:
@ServerScriptService.ShopHandler the buy button takes coins twice — fix that onlyWhen you run out
At zero, sending is blocked and you are offered the ways to get more: upgrade, top up, or link Discord for free daily refills.
If you run out mid-build, everything built so far stays in Studio. Top up, then send:
continue