This document is intended for Enterprise Token Plan users. It describes the core console operation procedures and limitations to help you efficiently configure, manage, and use the Plan.
Plan Management
On the Enterprise Token Plan page, you can view and configure your plan list, including managing API Keys and viewing plan usage. An account can hold multiple independent Enterprise Token Plan plans simultaneously. Each plan has its own quota pool, API Key management, and usage statistics. These plans do not interfere with each other, making them suitable for enterprises to manage independently by department, project, or business line.
API Key Management
Each plan supports creating multiple API Keys to meet the needs of multiple personnel and diverse business scenarios within a team. Its core capabilities include:
The number of API Keys is allocated based on the plan quota scale.
It supports both single and batch creation. For batch creation, you can reuse existing Key configurations.
Each Key can be independently configured with accessible models, dedicated quota, total quota limit, and TPM restrictions. The dedicated quota ensures the Key's basic quota, while the total quota limit controls the Key's maximum available quota.
Create a Key
1. In the My Plans list, select a plan and click Manage API Keys to go to the API Key Management page. 2. Click Create API Key to go to the Create API Key page.
3. Fill in the API Key configuration and click Confirm to complete the creation of a single API Key or API Keys in batches.
|
Reuse Existing Key. | No | Select an existing Key under the current plan from the dropdown list. Once selected, its configuration (model selection, dedicated quota, total quota limit, TPM restrictions) is automatically populated into the form below, facilitating the quick creation of a new Key with the same configuration. The Key name is not populated and must be re-entered. If you select "Do Not Reuse", the configuration starts from scratch. | Do not reuse. |
Key Name | Yes | Assign a custom name to the Key for easy identification of its purpose and ownership (such as Employee001 and Support Bot). Naming rules: Can only contain Chinese characters, letters, digits, underscores, and hyphens. Must start with a Chinese character or letter and end with a Chinese character, letter, or digit. Length must be between 2 and 50 characters. | Employee001 |
Number of Keys to Create | Yes | The number of Keys to be created in this operation, ranging from 1 to -10. The system automatically appends a sequence number to the Key name (for example, "Employee001-1", "Employee001-2"). When keys are created in batches, all Keys share the same configuration parameters. | 1 |
Model Selection | Yes | Select the models that this Key can call. Multiple selections are supported. Available models include Auto Intelligent Routing, GLM-5, Kimi-K2.5, and MiniMax-M2.5. If a model is not selected, an unauthorized error will be returned when the Key calls it. | Auto |
Exclusive Quota | Yes | The dedicated quota reserved for this Key (Professional Plan unit: points; Light Plan unit: tokens) can only be used by this Key and cannot be occupied by other Keys. Setting it to 0 means no dedicated quota is reserved, and this Key will only use the shared pool. The entered value must not exceed the currently allocatable dedicated quota (the page will prompt "Maximum configurable: X points/tokens"). | 0 |
Total Quota Limit | Yes | The maximum total quota (sum of dedicated + shared portions) that this Key can use within the current billing cycle. Two modes are provided: Same Plan Limit (Default): The limit equals the plan's total quota. This means the Key can theoretically use the entire quota pool, though actual usage is subject to competition within the shared pool. Custom Limit: Manually enter a specific value to limit the Key's maximum available quota. This is suitable for scenarios that require strict control over the cost of a single Key. | Same as the package limit |
TPM Limit | Yes | The maximum number of tokens that this Key can process per minute (Tokens Per Minute), used to control the call rate and prevent a single Key from excessively occupying bandwidth. Two modes are provided: Same Plan Limit (Default): The TPM limit aligns with the plan level. Custom Limit: Manually enter a value, which must not exceed the plan-level TPM limit. | Same as the package limit |
Copy an API Key
1. In the My Plans list, select a plan and click Manage API Keys to go to the API Key Management page. 2. Select the target API Key, then click Copy to obtain the API Key.
Edit an API Key
Edit Rules
Edit Quota: The configuration for each API Key can be modified a maximum of 10 times per day.
Editing does not affect the secret value: The edit operation only modifies the Key's configuration parameters. The API Key secret value remains unchanged, so integrated services do not need to replace the Key.
Changes take effect immediately: All configuration changes become effective instantly upon saving, requiring no service restart or Key redistribution.
Editing is disabled when the plan is invalid: When a plan is in the "Invalid" state, the Key configuration cannot be edited. You must first renew the plan to restore it before you can perform operations.
Operation Steps
1. In the My Plans list, select a plan and click Manage API Keys to go to the API Key Management page. 2. Click Edit to go to the Edit page.
3. You can modify the available models and quota limits for the API Key.
Configurable Field Description:
|
Enabling Status | Controls whether this Key can be used for API calls. After the Key is disabled, all requests using that Key are immediately invalidated and return the "API key is disabled by user" error. After it is re-enabled, it can be called again immediately. |
Model Selection | Adjust the range of models that this Key can call. The model takes effect immediately after it is added. After a model is removed, the system returns the "Model xxx is not authorized for this API key" error when the Key is used to call that removed model. |
Dedicated Quota | Adjust the dedicated reserved quota for this Key. Increase: Allocate more quota from the shared pool and lock it to this Key. Decrease: Release part of the exclusive quota back to the shared pool for use by other Keys. Note: The input value must not exceed the currently allocable exclusive quota. The exclusive quota cannot be reduced to a value lower than the exclusive portion already used by this Key. For example, if the Key's current exclusive quota is 300 credits and 200 exclusive credits have been used, the quota can only be lowered to a minimum of 200 credits. |
Total Quota Limit | Adjust the maximum available quota for this Key. You can switch between "Same as Package Limit" and "Custom Limit". Custom Rules: The total quota limit must be higher than the Key's currently used quota and exclusive quota. |
TPM Limit | Adjust the per-minute Token processing limit for this Key. You can switch between "Same as Package Limit" and "Custom Limit". When the custom limit is configured, the value cannot exceed the package-level TPM limit. |
4. Click OK to complete the modification.
Reset an API Key
1. In the My Plans list, select a plan and click Manage API Keys to go to the API Key Management page. 2. Click Reset to have the system regenerate the API Key.
Attention:
This operation immediately generates a new API Key. The old API Key is expected to become invalid within 5 minutes and cannot be recovered. Proceed with caution.
After the old API Key becomes invalid, all tools/applications/services using that Key will immediately be unable to call the API. Ensure that you update the corresponding configurations.
Delete an API Key
1. In the My Plans list, select a plan and click Manage API Keys to go to the API Key Management page. 2. Click Delete to delete the API Key.
Attention:
After deletion, the old API Key will become invalid and cannot be recovered. All tools/applications/services using that Key will immediately be unable to call the API. Proceed with caution.
Usage Query
Package Usage Query
In the My Plans list, select a plan, click Usage Details to go to the plan details page, and view the plan usage, which includes usage by credits/Tokens, models/API Keys, and requests. API Key Usage Query
1. In the My Plans list, select a plan and click Manage API Keys to go to the API Key page. 2. Click Usage Details to view the plan usage, which includes usage by credits/Tokens and models.
Plan Renewal
1. Renewal Rules
Warning:
Please complete the renewal before your plan expires. Renewal will not be possible after the plan expires, the plan will become invalid, and the API Key will also become invalid.
Plan renewal refers to renewing the plan for the next subscription month. After renewal is completed, the new quota will take effect in the next subscription month:
If the quota for the current subscription month has not been used up: The remaining quota can continue to be used until the end of the current subscription month, and the quota will be automatically reset to the new amount in the next subscription month.
If the quota for the current subscription month are exhausted: renewal will not reset the quota for the current subscription month. The new quota will take effect only in the next subscription month.
2. Renewal Example
Example: The user's total credit quota for the current subscription month (2026-03-23 to 2026-04-23) is 100 million. The user renews the plan for the next subscription month (2026-04-23 to 2026-05-23). The available quota under different scenarios is described as follows:
|
Quota not fully used in the current subscription month | If 0.5 billion has been used in the current subscription month (2026-03-23 to 2026-04-23). | The remaining available quota for the current subscription month (2026-03-23 to 2026-04-23) is 50 million. The available quota for the next subscription month (2026-04-23 to 2026-05-23) is 100 million. |
Quota fully used in the current subscription month | If 1 billion has been used in the current subscription month (2026-03-23 to 2026-04-23). | The remaining available quota for the current subscription month (2026-03-23 to 2026-04-23) is 0. The available quota for the next subscription month (2026-04-23 to 2026-05-23) is 100 million. |
3. Renewal Methods
Enterprise Token Plan supports two methods: manual renewal and automatic renewal. The detailed descriptions are as follows:
Manual Renewal: You can manually renew your plan at any time between its purchase date and expiration date to extend its validity period.
Confirm the renewal period (1 month) and click Renew to complete the operation.
Automatic Renewal: After automatic renewal is enabled for a plan, the plan will be automatically renewed one day before its expiration date, provided that the account has sufficient balance.
On the Enterprise Token Plan page, select your plan, go to the plan details page, and click Enable automatic renewal. Plan Upgrade
Note:
Enterprise The Token Plan plan only supports plan upgrades and does not support plan downgrade operations.
Upgrade Rules
The cost for upgrading a plan = the new plan price − the original plan price (to cover the price difference).
The remaining plan quota after an upgrade = the total quota of the new plan - the usage of the original plan quota.
After a plan upgrade is successful:
The plan API Key remains unchanged.
The expiration date of the plan remains the same as that of the original plan. For example, the original plan (500,000 credits) expires on 2026-05-23, and the upgraded plan (1,000,000 credits) also expires on 2026-05-23.
Steps
On the Enterprise Token Plan page, select your plan, go to the plan details page, click Upgrade, select the target specification, and upgrade your plan.