Operating Flux

Billing and credits

Billing is per project. A credits wallet pays for usage on Flux's built-in keys, and bills and invoices record what was charged.

The credits wallet

Each project has a wallet with a balance. Usage that runs on Flux's own API keys — the DEFAULT credential on a model node — draws it down.

Open Credits Wallet from the console.
Read the current balance.
Enter an amount to add, in your billing account's currency.
Confirm. Tax may apply depending on your billing account details.

The credits wallet dialog showing the current balance and an amount field for topping up

Screenshot to be added

One wallet per project.

Usage on your own credentials does not touch the wallet — the provider bills you directly. The wallet only covers Flux's built-in keys. See the credential store.

Bills and invoices

The Billing page lists your bills, each covering a period with a due date and an amount. Every bill carries a status:

Status	Means
Paid	Settled — the invoice is there for your records
Pending	Not paid yet. A Pay button is shown
Processing	Payment is in flight; nothing to do
Failed	Payment did not go through. Retry from the same row

Every bill has an Invoice link for your accounting.

Currency

Amounts follow your billing account's currency, so a project set to INR shows ₹ and one set to USD shows $. It is set on the billing account rather than per project.

Plans

Flux has four tiers — Free, Basic, Premium and Enterprise. Your plan affects which nodes appear in the palette and which marketplace templates you can use; each template card carries a plan badge.

Keeping cost predictable

Watch the interval triggers. They run whether anyone is using the agent or not, and a short interval left on after testing is the classic surprise.
Read usage weekly at first. The analytics dashboard shows today and this month, which is enough to catch a trend early.
Use your own keys for heavy workloads. Once volume is predictable, your own provider agreement is usually cheaper than credits.
Keep test modules out of production mode so a half-finished workflow is not quietly firing.

If the wallet empties, workflows running on the built-in keys stop being able to call the model. A customer-facing agent will fail quietly at the AI node, so top up before the balance reaches zero rather than after.

Deleting a project

Project Settings → Danger Zone → Delete this project permanently removes the project and all associated data. It cannot be undone, and it takes the modules, workflows, credentials and logs with it.