AI Credits

AI credits give your organisation one balance for Runnit’s AI features. Text, image, video, search, and Ru activity all draw from the same balance when your organisation uses platform credits. AI activity inside your client workspaces draws from this balance too, so one top-up covers your whole organisation.

Organisation owners and administrators can open Admin → AI Credits. The page is shown only when it applies to your organisation’s billing mode.

Understand the balance

The page shows:

your current credit balance and its purchase value in US dollars;
credits used over the last 7 and 30 days;
an estimate of how many days the balance may last, based on recent use;
available credit packs and a custom top-up amount; and
a transaction history for purchases, grants, refunds, adjustments, and daily AI use.

The first eligible platform-credit organisation created by an account starts with 1,000 welcome credits. New credit wallets have a low-balance warning set to 250 credits. An owner or administrator can change or clear that warning.

Only successful AI work uses credits. A request that fails, including one that fails because the balance ran out, is recorded in the audit log but is never charged.

Indexing your documents does not use credits. When you upload a file, Runnit reads it and builds the search index that makes it findable by meaning rather than by filename. That work is free in every plan, so search keeps working even when the balance is empty. AI Usage still shows what it was worth, listed separately from the credits you were charged.

A balance of zero does not always mean AI has stopped. Monthly license allowances are used before the balance, so an organisation can run a whole cycle on licenses alone and never draw on the prepaid balance. While the balance is empty and licenses still have credits, the page says AI features keep working on monthly license allowances and shows how many are left this cycle, and the balance also shows that remaining amount. The page says AI features are paused only once the allowances are used up as well.

If your workspace is a client workspace managed by an agency, the page explains that billing is handled by the agency organisation instead of showing balance controls. Ask an agency administrator about top-ups.

One credit normally represents US$0.01 of purchase value. For example, 5,000 credits normally cost US$50. Your Runnit provider may change the credit value, so the pack price shown on the page is the amount that applies now.

Different AI tasks use different amounts. A short Ru response may use a small fraction of a credit, while image or video generation usually uses more. Check AI Usage to see where your credits are going.

Licenses and monthly allowances

Each member of a credit organisation has a license with a monthly AI credit allowance. Allowances are used before your prepaid balance, so day-to-day AI work draws on each member’s allowance first and only spills over to the shared balance once their allowance for the cycle is used up.

Licences themselves are assigned on the Team page, where each member’s row shows their licence, the credits used and remaining this cycle, and the date allowances next reset. Allowances reset to the full license amount each cycle, and unused allowance does not carry over. New members start on the default license automatically. See Managing Users for assigning licences and for Pool allowances across the team, which shares one combined monthly allowance instead of capping each member individually.

A member who has used their whole allowance can keep working while the organisation balance is positive. When both the allowance and the balance are gone, new AI requests are paused for that member until the next cycle or a top-up.

Buy or request credits

Under Buy credits, choose a pack or enter a custom amount, then select Buy. All purchases are billed in US dollars. A custom amount can be any whole-cent value from US$10 to US$2,000 and buys credits at the same per-credit value as the packs; the card shows how many credits the amount buys before you confirm.

If your organisation has a saved card (from a subscription or an earlier purchase), the pack is charged to it straight away and the page confirms the charge. Credits arrive as soon as Stripe confirms the payment.
If there is no saved card yet, Runnit opens a secure Stripe checkout instead. After payment, return to AI Credits.

Some payment methods take longer to confirm; Runnit keeps the purchase pending until Stripe reports that it succeeded. You can manage the saved card under Payment method and invoices on the billing page.

If checkout is not enabled, the packs are still listed but the Buy buttons are unavailable. Contact your Runnit administrator to arrange a top-up.

Auto top-up

Under Auto top-up, you can keep the balance from running out without manual purchases. Tick Enabled, set a credit amount in Trigger below, choose the Pack to buy, and save. When the balance drops below the trigger, Runnit charges the chosen pack to your saved card automatically.

Auto top-up has fixed safety limits: at most one automatic charge per day and three packs per calendar month. If an automatic charge fails, auto top-up turns itself off and the billing contacts are notified, so a card problem never causes repeated charge attempts. Turn it back on after fixing the card.

Auto top-up needs a saved card. If there is none, make one purchase through checkout first.

Set a low-balance warning

Enter a credit amount under Low-balance warning and select Save. Runnit notifies active owners and administrators when the balance falls to or below that amount. Runnit’s configured operations contact also receives an email with the organisation’s active owner and administrator email addresses and the Runnit site URL, so they can identify the tenant that needs attention.

The warning is sent once while the balance remains low. After a top-up takes the balance above the warning amount, the warning is ready to send again if the balance falls back to or below it. If the operations email can’t be sent, Runnit retries it during the next scheduled check.

Clear the field and save to turn the warning off.

When credits run out

Runnit checks each member’s remaining allowance and the organisation balance before starting AI work. A member with allowance left can keep working even when the balance is empty. When both are gone, new AI requests are paused and Runnit says so wherever the work was started:

Ru replies in the chat with an out-of-credits notice. For owners and administrators, the notice includes a Top up AI credits button that opens this page.
A background job that cannot run fails straight away and sends an Out of AI credits notification to the person who started it. For owners and administrators, selecting the notification opens this page; other members are asked to contact an administrator.

Work already running can finish, so several requests started together may take the final balance below zero.

Buying or receiving more credits restores access as soon as the balance is positive, and every member’s allowance returns at the start of their organisation’s next cycle.

Uploading and searching documents is not affected. Files uploaded while the balance was empty are still indexed and still findable. Runnit may skip the short AI written summary on those files until credits return.

Other billing modes

Some organisations do not use the prepaid balance.

Unmetered access

The AI Credits page explains that credits are not enabled. AI features continue without wallet checks, and AI Usage shows the full technical usage report.

Your own API keys

Enterprise organisations may connect their own OpenAI, Anthropic, Google, and fal.ai accounts. In this mode, Runnit does not use platform provider keys and does not show credit balances.

Owners and administrators can open Admin → AI API Keys to:

enter or replace a provider key;
test the saved connection; or
remove the key.

Saved keys are encrypted and are never displayed again. Only a masked hint is shown. If an AI feature needs a provider whose key is missing, Runnit pauses that request and links an administrator to AI API Keys. It never falls back to a platform key in this mode.

Provider network addresses are controlled by Runnit. Organisation keys cannot set a custom base URL.

Set up every provider used by your enabled features. Text and search features may need OpenAI, Anthropic, or Google. Image and video generation need fal.ai.

For the reporting available in each mode, see AI Usage & Model Settings.