How credits work, and what happens when a render fails

Read the price on the Generate button

In the image, video and audio composers, and on a model's page, the price is on the button itself, for example Generate video followed by the credits your settings will hold. It is the server's price for exactly what you have set up, and it updates as you change a setting. One click generates at that price, with no confirmation dialog, and you are never charged more than the button showed.

If the price moves before your click, nothing is sent: a note says what changed, and the next click pays the new price. If your balance cannot cover it, you get Add credits instead. A preset shows an estimate for one run at its default settings before you press Create.

The price follows what you ask for:

• Images: each one at the model's price.
• Video: priced per clip of a set length, normally five seconds, and scaled to the duration you pick, rounded up.
• Speech: priced by the number of characters, with a minimum for a short line.
• Quality tier: where a model offers one, each tier has its own price.

Know what a job holds

When NOLGIA accepts your request, it takes a hold for that price. When the result is delivered, the hold becomes the charge, with no second charge on top. Checking on a job, or waiting for it again, adds nothing.

The usage list on your billing page shows each hold as a charge, and a released hold as a refund for the same amount. Every generation the NOLGIA Agent starts takes its own hold, separate from the chat turn that asked for it.

When a render fails or is refused

If a generation fails for a technical reason, such as a provider error, a timeout or a problem on our side, the credits held for it come back in full, automatically.

When a provider's content filter blocks a render, the card in the queue under the composer reads Blocked by the content filter, gives the provider's reason, says "Your credits were refunded." or "The credits for this attempt were charged.", and offers Edit prompt, which puts your prompt back in the composer.

A refused render is refunded unless the provider billed us for the attempt, and GPT Image refusals are always refunded. Refused renders are refunded explains the few cases that are charged.

Cancel a render you no longer want

A generation that is still queued or running has a Cancel button. Cancelled before it reaches the model provider, it is refunded in full. After that it depends on the model: some providers stop for free, most video restore models bill only the part they rendered, and some cannot stop at all, so the render is charged if it finishes. A cancelled render never reaches your library. What happens when you cancel a render has the details.

Quote a job from your own code

POST /jobs/cost returns the exact credits a generation will hold and a confirmation token, valid for ten minutes, to send back with the request. A quote creates no job and holds nothing. On the CLI, --cost-only on nolgia gen video and nolgia gen 3d estimates the price from the published rates and creates no job.

• A duplicate submission within five minutes gets 409 and the job that already exists, with no new hold.
• A timeout while you wait does not cancel or refund the job. It can still finish.
• On a failed job, failure.credits_refunded is true when it cost nothing and false when it was charged.

The pricing and credits guide has the full contract.

Know which credits you are spending

Paid plans add credits every month. They reset each billing cycle and do not roll over. Credits you top up never expire. In the app, a generation is paid from your monthly credits when they cover its price, and from your top-up credits when they do not. One generation is never split between the two.

A request made with a Personal Access Token, from the API or an MCP client set up with a token, spends top-up credits only.

What a few models cost today

Live published rates for an image, two clips and a voice line. Every other rate is on its model's page under Models.