Account and billing
Understand site credits, top-ups, subscriptions, developer levels, and usage records. Current model prices, checkout amounts, and plan benefits are determined by the live pages and confirmed order.
Distinguish four concepts
| Item | Meaning | Where to check |
|---|---|---|
| Wallet credits | Site balance from top-ups or credit redemption | Top-ups and balance |
| API token quota | A limit on one key, not a separate wallet | Token management |
| Subscription benefits | Resources restricted by validity, group, model, and quota | Subscriptions |
| Developer level | Reviewed D0-D3 progression tied to a special user group and multipliers | Personal Center |
Raising a token limit does not add wallet funds. Buying a plan does not transfer all advertised plan resources into the wallet.
The site credit symbol
Nbility’s top-up explanation uses $ as a site credit symbol, not a US-dollar cash balance. Ordinary CNY top-ups follow the displayed ¥1 = $1 site credit rule. Payment-method, amount-tier, or campaign variations are governed by the amount due and credits shown before payment.
Do not combine upstream USD list prices, site credit symbols, and CNY payments using a fixed exchange-rate formula. On Pricing, review the model, group, billing unit, and applicable conditions together.
Review request charges
- Find the exact model ID in Models or Pricing.
- Check the request’s billing group and the user’s effective group multiplier.
- Distinguish input, output, and cache charges from image, duration, request-count, or other units. One simplified formula cannot describe every model.
- After the request, inspect Usage logs and reconcile the selected period in Billing.
Some requests involve a reservation followed by final settlement; asynchronous tasks also need to finish. A temporary balance change is not necessarily the final charge. Use request and billing details rather than a client’s token estimate as the account record.
Where discounts apply
- Top-up offers affect payment or credited amounts; see Top-up rules.
- Developer levels / tier discounts affect later requests through group multipliers; see Developer levels.
- Subscriptions depend on model scope, groups, periods, and billing preference; see Subscriptions and billing order.
Do not simply add these discounts together or apply the same group multiplier again to a price that already includes it.
Control usage
Create a separate token per client with appropriate quotas and model restrictions. Test short requests before long contexts, automated tasks, or retries. After a timeout, check logs before resubmitting a request that may already have succeeded.
Use payment records for orders and usage logs for model calls. When submitting a ticket, include the order or request ID, time, model, and redacted error, never the API key.