Usage and Billing

Use the balance overview for a quick check, usage records to investigate calls, and the ledger to understand balance changes. Read the unit and service type before comparing amounts.

Check the overview — Review balance and recent spending.
Find the usage — Filter the relevant service and time range.
Reconcile the balance — Compare the final charge with ledger changes.

Review intelligent-service usage

Open Usage and Billing to inspect the balance, available service prices, usage records and balance movements. AI replies, translation and vector operations may consume the shared intelligent-service balance according to the tenant’s configured services.

The support response path matters: a stored answer and a large-model request are not the same type of usage. Model and price availability can change; use the current console rather than fixed amounts in this guide.

Understand settlement

The service may reserve an estimated amount before a metered request. Reliable upstream usage is used for normal settlement under the existing rules. When a valid result is returned but reliable usage is unavailable, the reserved amount can be retained as the fallback charge without applying the buffer again. Failed requests or invalid results release the reserved amount under the failure rules.

A reservation is not an additional second charge. Compare the final charge, original reservation and any balance adjustment before interpreting a record. Fallback estimated units must not be interpreted as upstream-measured tokens.

MCP and costs

MCP does not introduce a separate billing rule, but tools that invoke platform AI, translation or vector services can incur their normal costs. An external AI provider may charge independently for its own service. Billing tools can read balances, usage, transactions and prices; they cannot recharge balances or edit bills.

Use the right billing view

View	What it answers
Usage	When a service was called, its input/output units where applicable, final charge and status.
Balance ledger	The type and amount of each balance change, with the balance before and after.
Service prices	The currently available service and its pricing unit. Use the displayed rate rather than a price copied from an old document.

Example: investigate an unexpected balance change

Note the approximate time and select the relevant range. Use the service filter to separate AI, translation, language detection and embeddings.
Read the call status and final charged amount. A message on screen is not itself a billing record.
Review ledger changes for the same period, including consumption, refunds and other displayed adjustments.
If the figures still need explanation, keep the time range, service and relevant record details for the platform operator. Do not repeatedly rerun a billable operation just to see whether the number changes.

Different services use different units. AI text generation can have input and output token prices; embedding service pricing is based on input usage. Read translation or language-detection units as displayed instead of treating every number as tokens.

Common questions

Is an initial hold a second charge?

No. It is part of the settlement process described above. Review the final charge and balance adjustments together instead of adding the hold again.

Does connecting MCP make all AI usage free?

No. Existing platform services can still consume the shared balance, and the external AI application may have its own charges.