Refund Policy

You do not need to ask. Credits are held when a task starts and only settled when it produces output. If a task fails — a provider outage, a timeout, a rejected input — the hold is released and the credits are back on your balance.

Every movement is visible in your credit history, so you can confirm it yourself: a released hold appears as a refund line against the task it belonged to.

A partial batch settles partially. If you asked for four images and two came back, you are charged for two.

A generation that ran and produced output has been delivered, even if you do not like the result. Generative models are probabilistic; the same prompt on the same model returns something different each time, and "it is not what I pictured" is not a fault.

This is why every tool shows the price before you press Generate, why cheap draft models exist in every family, and why the model picker states what each model is bad at as well as what it is good at.

• An unused pack — no credits from it spent — can be refunded within the cooling-off window.
• A duplicate or clearly erroneous charge is refunded in full.
• A partially used pack is assessed case by case, against the credits actually spent.
• Refunds go back to the original payment method. Crypto payments are refunded in the same asset at the rate on the day of the refund, and network fees are not recoverable.

Talk to us first. A chargeback raised without contacting us suspends the account while the dispute runs, which usually costs you more time than the ticket would have.

Contact support with the task ID or the invoice number. Task IDs are copyable from every task card, and quoting one turns a conversation into a lookup.