Usage and costs

Purpose

Every call to a language model costs money, usually fractions of a cent, but noticeable in total. dAI Pro logs every call per collection, purpose and model and converts it into costs using the stored list prices. So you see what the chat, the search, the agents and the indexing cost, and what a resolved request is worth on average.

Where

Open Usage in the collection rail.

The "Usage" page with conversation outcome, usage by day and export

Storing prices

The box Configure prices applies to all collections of the instance. For each model you enter the provider's list prices: input and output per million tokens, for text recognition per 1,000 pages, for audio per minute, plus the share a hit in the provider's cache costs. Prices in the provider's currency; dAI Pro converts dollar prices into euros at the current reference rate of the European Central Bank. Without a price, only tokens are shown, no costs.

Conversation outcome and cost per resolved request

The upper block assesses the current month without an AI verdict, from signals alone: a refusal counts as a knowledge gap; thumbs, follow-up question, rephrasing and handover update the answer before them.

Metric	Meaning
Answers	All answers of the chat in the month.
Resolved	Answered, confirmed, follow-up question, action triggered.
Not resolved	Knowledge gap, rejected, rephrased, handover, error.
Resolution rate	Resolved divided by all.
AI cost of the answers	Cost of all answers with a stored price.
Cost per resolved request	The number that counts: what a request costs that the chat actually dealt with.

Usage by day

Per day an expandable block with calls, tokens and costs, containing the table per purpose and model:

Column	Meaning
Purpose	The purpose: chat, search, embedding, agent, Copilot, voice chat, endpoint for agents.
Model	The model used.
Calls	Number of calls.
Tokens in, of which cache hits, of which cache new	Input tokens and how many of them came from the provider's cache. A high share of cache hits makes CAG mode inexpensive.
Tokens out	Output tokens.
Pages, minutes	For text recognition and audio.
Costs	According to the stored price, in euros.

Export

Excel export and CSV export deliver one row per day, purpose and model in the selected period, with costs in euros. For the cost centre, for reconciling with the provider's invoice or for your own analyses.

What drives costs

Long answers and long conversations. Every answer carries the history with it. The main prompt can afford to be brief.
Search while typing (Chapter 9): every intermediate input is a summary.
Re-indexing. Every processed document costs embeddings; the freshness guard processes only what has changed.
Agents with an AI verdict: quality audit, golden set with judge, content guard. Their schedule determines the costs.
The answer cache saves: the same questions do not cost a second time.

Frequently asked questions

The costs show 0.00 euros. No price is stored for the model. Enter it in the "Configure prices" box; the conversion applies retroactively to the usage.

The total differs from the provider's invoice. List prices, exchange rate fluctuations and rounding. The usage in tokens is correct; the costs are an estimate based on list prices.

Does the test chat in the backend count? Yes, like any other call.