Usage, budget & credits
Credits are the usage currency of nara. Every billable action — a nara turn, a phone minute, a file import — consumes credits from the organization balance. Organization admins manage usage under Account > Budget (/admin/credits) with the tabs Overview, Limits, and Bookings. People with the credits permission who are not organization admins see only the Bookings tab.
Balance
Section titled “Balance”The Bookings tab shows three figures:
- Available credits — what can be spent right now.
- Reserved credits — estimates held for runs that are currently in progress.
- Total consumed — cumulative usage.
How credits are consumed
Section titled “How credits are consumed”Before a billable action starts, nara reserves the estimated cost. When the action finishes, the actual cost is committed and any unused remainder of the reservation is released. Because the reservation is checked against the available balance up front, the organization can never be overdrawn. A run that would exceed the balance is rejected with an insufficient-credits error instead of starting.
Usage limits
Section titled “Usage limits”Limits stop new work when usage reaches them. Work that is already running can still be booked afterwards, so a period can end slightly above its limit. All limits are off by default, and the available balance always stays the hard stop.
- Organization: change the monthly and annual limit on the Overview with Change on each row. The month follows your plan’s billing period. Set the start of the fiscal year under Rules; a new start date applies from the next year boundary.
- Reserve for essential Assistants and capabilities (under Rules): a part of the organization limit that only Assistants and capabilities with priority Always runs may use. It requires at least one of them.
- Groups and people (Limits tab): optional limits for existing groups (all direct members share one limit), a limit per person for everyone without their own setting, and own limits with a higher, lower, or no personal limit. Every matching limit applies.
- Assistants and capabilities (Limits tab): priority Always runs, Normal, or Can wait right in the row, plus, via Edit, an optional monthly and annual limit, a maximum per request, and Counts toward group for requests without a person. A capability uses its own priority, also inside an Assistant chat; otherwise the Assistant’s priority applies. The limits of both apply, and the smaller maximum per request wins.
- Maximum per request: a request stops once it has used this amount. Its last step can go slightly over. Set the default for all Assistants and capabilities under Rules.
- Fixed bounds: every request, automation, and knowledge run has fixed step and time bounds. A request stops when the same tool call fails three times with the same error.
Usage is attributed to people and groups from the first request after this feature was released. When you set a limit in the middle of a period that started earlier, nara asks how much may still be used in the current period. The full limit applies from the next period.
When work stops
Section titled “When work stops”- People see at the message input which limit stopped their request and the Message when stopped from the Overview. Their own limits and stops are listed on their profile.
- Queued background work pauses. Admins can Continue it under Waiting for you once the limit allows it again, or Discard it.
- Partly finished work stops and needs review. nara does not restart it automatically.
- Pause non-essential work (top right) holds new work of Assistants and capabilities set to Can wait and all imports until you resume it.
When a group or the organization reaches its limit, an import waits for approval, or work is paused, every admin page shows a notice. The notification bell also lists limits that will be reached soon.
Imports
Section titled “Imports”One-time work runs as an import: file uploads, the initial import of a connector, and the reindex of a data type. An upload or connector import waits until an admin approves it on the Overview under Imports with Approve against the shown estimate. Until then, files and objects are stored but not processed. A reindex runs without approval.
- Uploads to the same data type within 24 hours join the open import.
- An import pauses when it reaches its approved amount. Raise it to continue. Provider batches that were already submitted still settle.
- Decline or Close cancels the queued work. Connector sync after the initial import counts as regular usage.
- Imports count toward used credits and limits but stay out of the recurring forecast.
Forecast and changes
Section titled “Forecast and changes”The forecast uses the recurring usage of the last 14 days, including days without usage. With fewer than 7 days of data, it is marked provisional. Changes (top right) lists every change to limits and settings, every approval, continued or discarded work, and every stop caused by a limit, filterable by Settings, Stops, and Approvals.
Costs per action
Section titled “Costs per action”The table lists the minimum charge per billable action. nara turns and media analysis settle against measured model usage, so a run with more context, more output, or retries costs more than the minimum. Every other action costs exactly the listed value.
| Action | Item code | Minimum credits |
|---|---|---|
| nara turn (pro) | AGENT_TURN_PRO | 8 |
| nara turn (balanced) | AGENT_TURN_BALANCED | 4 |
| nara turn (budget) | AGENT_TURN_BUDGET | 1 |
| Phone minute | PHONE_MINUTE | 50 |
| Knowledge file import | MEMORY_INGEST_FILE | 5 |
| Knowledge write | MEMORY_EMBEDDING_WRITE | 1 |
| Knowledge media analysis | MEMORY_MEDIA_EXTRACTION | 1 |
| Ticket creation | TICKET_CREATE | 0 |
Top-up credits cost €0.025 each. The costs configured for your organization are shown in the Configured credit costs table on the page.
Ledger
Section titled “Ledger”The Bookings tab records every credit movement as a ledger entry with Created At, Type, Item Code, Sequence, Units, Unit Cost, Total Cost, and Details. Entries produced by a conversation or ticket link directly to the related Chat or Ticket, so any charge can be traced back to its source.
| Entry type | Meaning |
|---|---|
| PURCHASE | Credits added through a purchase |
| INITIAL | Starting balance |
| USAGE | Direct consumption |
| RESERVATION | Estimate held before a run starts |
| RESERVATION_COMMIT | Actual cost committed after the run |
| RESERVATION_RELEASE | Unused part of a reservation returned |
| REFUND | Credits returned for a charge |
| CORRECTION | Manual adjustment (admin-only) |
| MONTHLY_GRANT | Monthly allowance credited |
| MONTHLY_EXPIRATION | Unused monthly allowance expired |
Usage analysis
Section titled “Usage analysis”Charts and breakdowns of credit usage by person, Assistant, capability, channel, and period are on Reports (/admin/reports). The Bookings tab links there.
Purchases, corrections, and monthly allowances
Section titled “Purchases, corrections, and monthly allowances”Purchases add PURCHASE entries to the ledger. Manual CORRECTION entries are admin-only and are used to fix billing discrepancies. If your plan includes a monthly allowance, credits are granted each month as MONTHLY_GRANT entries; any unused portion expires with a matching MONTHLY_EXPIRATION entry at the end of the period.