Credits & billing
Credits are the usage currency of nara. Every billable action — an agent turn, a phone minute, a file ingestion — consumes credits from the organization balance. Admins manage credits under Account > Credits (/admin/credits).
Balance
Section titled “Balance”The page header 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.
Costs per action
Section titled “Costs per action”The table lists the minimum charge per billable action. Agent 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 |
|---|---|---|
| Agent turn (Pro model) | AGENT_TURN_PRO | 8 |
| Agent turn (Balanced model) | AGENT_TURN_BALANCED | 4 |
| Agent turn (Budget model) | AGENT_TURN_BUDGET | 1 |
| Function call | AGENT_FUNCTION_CALL | 1 |
| Phone minute | PHONE_MINUTE | 50 |
| File ingestion | MEMORY_INGEST_FILE | 5 |
| Embedding write | MEMORY_EMBEDDING_WRITE | 1 |
| 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”Every credit movement is recorded 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 charts
Section titled “Usage charts”The Daily Credit Usage chart and the usage Distribution chart break consumption down over a selectable range of 7d, 30d, or 3m — useful for spotting cost spikes and seeing which action types dominate spend.
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.