Credits and usage
Hatz Credits are the usage units used for AI activity in the Hatz platform. Each tenant has a monthly credit allowance that is shared across the users and AI features available to that tenant. Monthly credit allowances reset each calendar month.
Credit usage is not a fixed charge per message. It can change based on the model selected, the amount of input and output, the files or context included, and the tools or workflow steps used during a request.
Related articles: Model Multipliers, Custom Roles - Credit Limits, Understanding Rate Limiting, and Upgrade Tenant Package.
What uses credits?
Credit-consuming activity can include:
Secure AI chat and assistants
Workflow, app, and agent runs
Document analysis, file uploads, and generated outputs
API requests and tool actions that call AI models or connected services
For workflows, apps, and agents, completed AI or tool work can consume credits even if a later step fails or the full run does not complete. If this happens, review the run details to identify which steps completed before the failure.
Why does usage vary?
The same type of task can use different amounts of credits depending on how much work the model needs to do. Common factors include:
The AI model selected for the request. Different models can use different credit multipliers, so a larger or more specialized model may use more credits than a smaller model for the same prompt.
The length of the prompt, conversation history, uploaded files, or other input context
The length and complexity of the answer or generated output
Whether the request uses tools, integrations, web actions, file actions, or API calls
How many steps, retries, or model calls are required inside a workflow, app, or agent
Because AI requests are dynamic, credit usage should be treated as directional usage data rather than a fixed per-message price quote.
Do credits reset?
Credits are available at the tenant level and reset each calendar month. Unused monthly credits generally do not roll over unless your agreement says otherwise.
For package-specific allocations or billing details, review the Billing area in your Admin Dashboard or contact your Hatz account team.
Can I estimate credit usage in advance?
You can usually estimate usage directionally, but exact usage depends on the model and request. A short chat with a smaller model will usually use fewer credits than a long workflow that reads files, uses tools, and generates a detailed output with a larger model.
For most users, Auto Mode is the best starting point because it helps route requests to an appropriate model for the task. For a new rollout or high-volume workflow, monitor the first few days of usage and adjust the model, prompt, files, user caps, disabled models, or workflow design if usage is higher than expected.
Where can admins monitor usage?
Admins can review usage from the Admin Dashboard, Tenant Management, billing-period usage, and users and roles views available to their role. These views are intended to help monitor adoption, spot unusual spikes, and plan capacity.
Usage reporting may not be a token-by-token invoice and may not update instantly. If usage looks higher than expected, start by reviewing the available usage views for the tenant, users, models, workflows, apps, agents, API activity, files, and date range involved. Look for high-volume users, repeated workflow runs, larger models, long prompts, uploaded files, tool use, retries, or automation that may be running more often than expected.
What happens if a tenant reaches its allowance?
If a tenant approaches or reaches its monthly credit allowance, admins may see in-product usage indicators and receive email notifications. If the allowance is reached, some credit-consuming actions may be limited until the allowance resets, the package is upgraded, or an extra credit pack is added. See Upgrade Tenant Package for package upgrade steps. The exact experience can vary by feature, model, role, and tenant configuration.
Users should generally still be able to sign in and use chat. Depending on tenant settings and model availability, they may be routed to a less expensive model or asked to choose an available model. Other credit-consuming functionality may be limited, including higher-cost models, Workshop actions, API requests, file or tool actions, workflows, and follow-up automation.
Does ADEL Phone Agent use Hatz Credits?
ADEL Phone Agent usage is measured separately in minutes. It is not treated as billable Hatz Credit usage for chat, workflow, app, agent, file, or API activity. For setup details, see AI Phone Agent Settings.
How can I manage credit usage?
Use Auto Mode when available so Hatz can route the request to an appropriate model for the task.
Choose the model that matches the task. Use larger models when the task needs them, and smaller models for simpler work.
Disable higher-multiplier models for users or groups that do not need them.
Use Auto Mode policies to keep users on the Auto Mode options that fit their role, such as lower-cost modes for higher-volume teams.
Keep prompts and uploaded context focused on the information needed for the task.
Review workflows, apps, and agents that run multiple model or tool steps.
Use role-based credit limits where you need monthly usage caps for a group of users.
Monitor usage regularly after onboarding a new team, workflow, or integration.
When should I contact support?
Most high-usage questions can be narrowed down by reviewing usage reports first. Contact support when the reports do not match a specific request or workflow run, a user or tenant appears to be limited despite available credits, or you cannot reconcile a specific spike after checking users, models, workflows, files, tools, API activity, and date ranges. Include the tenant name, user, date and time, feature used, model selected, and any workflow, file, API, or usage-report details that may help us investigate.