Every generation on x-rush.ai is priced in credits, against one fixed price list that every plan shares. Two rules decide what you pay: the price comes from the output type, and a confirmed task consumes its credits only after the result is actually delivered. Those two rules govern every generation.
The Price List
| Output | Price per generation |
|---|---|
| Text | 0.5 credits |
| Image | 1 credit |
| Audio (voice, sound effects) | 2 credits |
| Music | 5 credits |
| Video | 10 credits |
Audio and music sit on separate lines on purpose. A voice line or a sound effect costs 2 credits; a song or a scored track costs 5. What you pay follows the task's final main output, so background music bills at the music rate and a spoken line at the audio rate. Confirm ten generations in one batch and the dialog shows the full total, ten times the unit price, before anything runs.
Reserved, Then Consumed
Accepting a task reserves its full credit total up front. The reservation becomes a real charge only once the complete result has passed the safety check, been saved, and is available in your Project. If the task never starts, fails, gets blocked, or is cancelled before delivery, the reservation is released and the balance comes back.
Retries inside the same task are covered by the original price. Clicking regenerate yourself starts a new paid unit. And delivery is final in one direction: a generation that produced what you asked for is charged, whether you end up liking it or not.
The Agent Assist Pool
Assistants bill separately from generations, through one pool per account. Chat replies, prompt optimization, "give me inspiration", summarizing material, completing a configuration, form-filling help: every successful assist anywhere in the app advances the same counter, and every 10 successful assists consume 0.5 credits. Switching Projects, features, sessions, or devices never resets the count.
Some things never advance it: a failed reply, a request that never started because the balance was short, system notifications, execution status, content moderation, internal model calls. Adopting, editing, or ignoring a suggestion costs nothing extra.
The counter is visible, and it flags the assist that will complete a batch. At 9 out of 10, the next assist reserves 0.5 credits before it runs, consumes them on success, and releases them on failure. Agent help inside a paid generation, such as prompt completion, is already part of the generation price and never touches this pool.
How Many Run at Once
Plans cap running generations: Free runs 1, Lite runs 2, Pro runs 3. The cap counts what is executing. An accepted task with its credits reserved can queue behind a full set of slots and starts as soon as one frees, and those slots are shared across Projects, features, browser tabs, and devices, so three open tabs draw on the same allowance. Downgrading never stops a running generation; it only lowers how many may run next. A batch is a management grouping, and each unit inside it still takes its own slot.
Where Credits Come From
Free accounts receive 5 credits a day. Lite grants 300 credits a month for $15, and Pro's monthly grant scales with its tiers, from 800 up. Credit packs are open to every plan, Free included: a one-time pack tops up the balance at a list price of $0.10 per credit. Free pays list price, Lite pays 20% below list, Pro pays half.
Storage works separately from credits. Your media library holds 500 MB per account, shared by every Project and workflow. Reaching the limit blocks new uploads until you delete files; nothing is removed automatically.
Spending Them Well
- Draft copy in text first, at 0.5 a generation, before committing it to images or video.
- Reuse what already exists. Selecting a previous result or a library file as input is free; the charge comes only when a generation runs.
- Templates are curated per feature on HTML Studio, Meme Image, and Meme Video only. Everywhere else you start from a blank input or a past result.
- Watch the assist counter before a long stretch of form-filling. The batch boundary is the one place where assistance starts costing anything.
Every number here is enforced by the billing backend, and the confirmation step always shows the fixed total before a task runs. If any page disagrees with that dialog, the dialog wins.