Account and usage rules
What this page covers
Section titled “What this page covers”How customer accounts are billed, which keys are valid, and how high-volume usage enters negotiated pricing.
Keys and requests
Section titled “Keys and requests”- Use only API keys issued by ArianAPI.
- First-party login tokens, JWT-shaped session strings, and
Bearervalues copied from a browser are rejected. That is a protection measure, not a fault. - Model names must be copied from the model catalog for that day. Names from old chats, posters, or third-party directories may already be offline.
Billing basis
Section titled “Billing basis”- The balance unit in the console is U. The public top-up face-value basis is
1U = ¥1; if support later offers a different campaign price, the written confirmation at that time controls. - Text requests are charged by actual input / output tokens consumed. Cache, long context, preview models, or media models may be billed separately; follow the pricing page for that day.
- The pricing page and model catalog are the only public price sources. This page does not treat any snapshot as a long-term unit price.
Regular usage and high-volume usage
Section titled “Regular usage and high-volume usage”- Regular usage: public prices on the model catalog and pricing page apply.
- High-volume usage: when expected or actual usage reaches or exceeds 1 billion tokens (10 亿 tokens), you may contact support to discuss models and period and negotiate a specific price.
- Until a written agreement takes effect, public prices still apply. A verbal “use the discount first” from support is not a settlement basis.
Account retention
Section titled “Account retention”After the account is opened, log in and start using it promptly. Brand-new accounts with no consumption for a long time may be cleaned up; accounts that have already consumed usage or completed a top-up are not treated under the “unused new account” rule. Exact enforcement follows support’s instructions; this page does not describe internal operations.