This page collects the exact numbers behind DIJJI.ai billing — the thresholds that gate new work, the points at which DIJJI.ai warns you, and the daily cap. For how billing works as a whole, see the Credits and billing concept page.
All amounts are held in credits (one credit is one US cent) and shown to you as dollar amounts.
Minimum balances
Two thresholds gate new work. Below either one, DIJJI.ai blocks the action until you top up.
| To do this | Balance required |
|---|---|
| Create a project | $100.00 |
| Start a task | $10.00 |
These are floors on the balance, not charges — the money isn’t taken when you cross them. They exist so a run never starts without enough credit to make meaningful progress.
Low-balance warnings
As the balance falls, DIJJI.ai warns you at three points. The default warning threshold is $50.00; the balance card turns amber at or below it and shows an estimated runway — how many days the balance will last at your recent rate of spend.
| Threshold | What you see |
|---|---|
| $50.00 | Balance card turns amber; runway estimate appears. |
| $25.00 | Repeat warning as the balance crosses this point. |
| $10.00 | Final warning — below this you can no longer start a task. |
At zero the card reads Out of credits. A run already working when the balance empties does not fail — it pauses in Waiting for Payment and holds its place. See Run states.
The daily spending limit
The daily spending limit caps how much the organization can spend in one calendar day. An admin sets it on Settings → Organization.
| Property | Value |
|---|---|
| Default for a new organization | $500.00 |
| Maximum | $1,000,000 |
| Value for no limit | 0 |
| Warning point | 80% of the limit |
| Reset | Midnight UTC, daily |
New runs are blocked once the day’s spend reaches the limit; a run already working is not interrupted. The day’s tally returns to zero at midnight UTC. For the full walk-through, see Set a daily spending limit.
How times are displayed
Timestamps across DIJJI.ai — run start and end times, transaction dates, invite expiry dates — are shown in your browser’s local timezone. There is nothing to configure; the time you see is your local time.
One exception: the Usage page groups spend into daily buckets by UTC date, and the daily spending limit also resets on the UTC calendar. If your local day and the UTC day differ, a late-evening run can land in the next day’s bucket.