My Subscriptions
Role: Member user Last updated: 2026-08-06
Pay-as-you-go quota and subscription quota are two independent billing sources. When an API Key is bound to a pay-as-you-go group, it uses the organization balance and personal pay-as-you-go quota. When bound to a subscription group, it uses the corresponding subscription quota.
Two Billing Sources
| Billing Source | Deduction Location | Common Limits |
|---|---|---|
| Balance | Organization balance, also counted toward member quota | Organization balance, user quota, Key limit |
| Subscription Quota | Daily, weekly, or monthly subscription quota | Subscription validity, subscription quota, member scope |
Exhausting pay-as-you-go quota does not affect subscription-bound Keys that are still valid. Exhausting subscription quota does not affect pay-as-you-go Keys with sufficient quota.
Checking Subscription Status
You can confirm from the following locations:
- Top status area: View subscription count and availability.
- Dashboard: Compare pay-as-you-go quota with subscription quota.
- My Subscriptions: View plan, validity period, subscription quota, and remaining amount.
- API Key: Check the "Billing Source" for each Key to see whether it uses "Balance" or "Subscription Quota".
If you have no subscriptions, the "My Subscriptions" page shows an empty state. Subscriptions are purchased or assigned by the admin user. Members cannot modify the member scope on their own.
Determining Whether a Key Is Usable
A subscription-bound Key must meet all of the following:
- The Key is enabled and not expired.
- The bound subscription is still within its validity period.
- The current user is still a member of that subscription.
- The subscription quota is not exhausted.
- The target model and upstream account are available.
The API Key page shows billing source and status. When pay-as-you-go quota is insufficient, check this page first to avoid disabling subscription-bound Keys that are still usable.
Cross-Group Calls
By default, subscription-bound Keys use the bound subscription group. Only after the admin user enables the subscription cross-group capability can you access other permitted groups via default model configuration or group identifiers. The resulting costs still count toward the original subscription quota.
If a cross-group request is rejected, check the organization switch, target group permissions, and subscription rules. Do not repeatedly retry with unconfirmed call names.
FAQ
Pay-as-you-go quota is 0, but some Keys still work. Why? These Keys use "Subscription Quota" as their billing source. Check the "Billing Source" column on the API Key page.
How do I confirm that I have been assigned a subscription? Open "My Subscriptions". The page lists assigned subscriptions, validity periods, and subscription quota.
Is subscription quota exclusive to me? Not necessarily. A subscription can be shared by multiple members. The sharing scope and quota rules are configured by the admin user in subscription management. The member page does not display the member list; confirm with the admin user.
What do I do when a subscription expires or quota runs out? Contact the admin user to renew, adjust member assignments, or rebind the Key to another available group.
Why can't my subscription-bound Key access other groups? The subscription cross-group capability may not be enabled, or the target group is not within the allowed scope. Contact the admin user to confirm.
For related operations, see API Key Management and Admin Guide - Subscription Management.