Usage Billing controls how the platform records and charges model usage. The admin console supports self mode, period billing, and usage billing, plus payment settings, subscription plans, redemption codes, model pricing, tool pricing, and call logs.
Entry Point#
Open Billing in the admin console. The page is organized around billing configuration, payment settings, subscription plans, redemption codes, model pricing, tool pricing, and usage logs.
Billing mode affects what users see on the Subscription page and whether Account Management shows subscription fields or balance fields.
For cache billing, tiered pricing, service multipliers, and tool billing details, see Billing & Pricing.
Billing Modes#
| Mode | Best For | User-Side Result |
|---|---|---|
| Self mode | Internal deployments, shared team cost, no user charging | Usage is recorded only; purchase and top-up actions are hidden. |
| Period billing | Plan-based monthly, yearly, or fixed entitlements | Users see current subscription, period credit, and plan usage. |
| Usage billing | Balance deduction by actual consumption | Users see balance, top-up, and redemption actions. |
Before switching modes, confirm that existing subscription or balance data matches the new mode. Self mode still records usage logs but does not deduct user balance or plan credit.
Prepaid Amount#
Usage billing can require a prepaid amount before calls. Final deduction still follows the real bill.
A prepaid amount reduces mid-task failure from insufficient balance. If it is too high, users face a higher usage barrier; if too low, long tasks or expensive models may still fail.
Payment Settings#
Payment settings support Stripe and EPay. Administrators can configure USD to CNY rate, enabled channels, Stripe keys and webhook secret, EPay gateway, merchant information, and payment types.
Multiple channels can be enabled at the same time, and users choose during payment. After saving payment settings, test with a small amount and confirm user subscription or balance updates correctly.
Subscription Plans#
In period billing mode, administrators maintain subscription plans. A plan includes name, description, price, interval, period credit, and discount.
Intervals can be monthly, yearly, or lifetime. Period credit controls the amount users can consume during the period. The user page may show notes such as free models not counting against credit.
When editing plans, consider existing entitlements. Lowering credit, changing price, or disabling a plan may affect renew and upgrade paths.
Redemption Codes#
Redemption codes can grant balance, subscription plans, or other billing benefits. Administrators can create single or bulk codes and configure billing mode, amount, plan, duration, total uses, per-user limit, expiration, and description.
Codes support search, filtering, enable/disable, copy, export, and delete. Deleted codes stop showing and cannot be redeemed, while redemption history remains. Billing entitlements usually cannot be redeemed in self mode.
Model Pricing#
Model pricing defines cost rules for platform models. Modes include token, per-call, per-second, and tiered pricing. Models can also be marked free.
Token pricing can separately configure input, output, cache read, and cache write. Per-call fits fixed-cost model operations. Per-second fits duration-sensitive generation. Tiered pricing fits ranges based on original input size.
Pricing can be imported and exported for environment migration or bulk maintenance. Before import, confirm platform model names match the current model catalog.
Tool Pricing#
Tool pricing applies to official native tools. When enabled, administrator-enabled native tools are billed using configured prices; self mode still records usage only.
Tool price is configured per call. A value of 0 means no separate tool charge. Model tokens generated by tool results still follow model pricing. Tools without returned call counts do not create separate tool bill items.
Usage Logs#
Billing and Logs both expose usage logs. Logs show model, tokens, cache, cost, latency, billing mode, and route source, useful for bill checks, abnormal consumption, and pricing validation.
Pricing changes usually affect future calls only. Historical calls keep their billing snapshot, so do not use current prices to explain old bills without checking call details.
Practical Tips#
Choose billing mode first, then configure payment, plans, or balance rules. Before launch, price core models and run test calls. Before changing billing mode, payment channels, plans, or prices, notify the team and confirm user-side display.