Best for trials, light usage, and bursts. Top up balance and pay for actual model usage.
Higher concurrency and quota with invoicing, support, and custom model access.
$500 credits/day, $15000 credits/month.
Price: ¥60. $12 credits/day, $360 credits/month
Price: ¥135. $30 credits/day, $900 credits/month.
Price: ¥294. $70 credits/day, $2100 credits/month.
$100 credits/day, $3000 credits/month. Price: ¥360.
$250 credits/day, $7500 credits/month. Price: ¥750.
SU500
SU750
SU1000
Common questions about packages, pay-as-you-go, and purchasing.
SU8 supports both packages and pay-as-you-go. Packages usually cost less in practice, refresh quota every day at 00:00 Beijing time (UTC+8), and have an expiry date. Pay-as-you-go has no expiry date and charges only for what you use.
Model detail pages show cache read and cache write prices when the model has cache pricing configured. After a request is completed, the Console usage detail breaks cost down into fresh input, cache read, cache write, output, and request components.
SU8 only carries over the previous day's remaining quota. If the previous carryover is not used, it will not be carried over again. Example: with a $30 daily quota, if today's available remainder is above $30, carryover is reduced by $30; if it is $30 or less, all of it carries over.
Daily package quota refreshes at 00:00 Beijing time (UTC+8), and the previous day's remainder is processed by the carryover rule.
Yes. Multiple active packages stack daily quota, total available quota, and concurrency. Usage first consumes all package carryover quota.
No. Package time does not merge. Multiple packages stack quota and concurrency, and usage first consumes all carryover quota.
Yes. Concurrency from multiple active packages is combined for the account.
Yes. A 10% handling fee applies to refunds.
When someone registers through your invite link and completes a valid purchase, the system creates a cashback record based on the active campaign rules.
Yes. A request with an applicable package entitlement keeps package pricing for the full request. If all applicable package quota is exhausted, the next request can use balance according to the key configuration; a model outside the package scope uses balance when the key allows it.
