A TPM reservation locks in dedicated inference capacity for a specific model, ensuring that your services are not affected by public rate limits during peak business hours. This topic describes how to create, integrate, and manage TPM reservations.
Overview
With a TPM (Tokens Per Minute) reservation, you can lock in dedicated inference throughput for a specific model. Requests within your reserved capacity are not subject to the rate limits of the public resource pool.
Capacity guarantee: The reserved TPM capacity is dedicated to your workload and is not shared with other users.
Dedicated model code: After you create a TPM reservation, the system automatically generates a dedicated model code. You must replace the
modelparameter in your API requests with this code.Graceful degradation: Requests that exceed your reserved capacity are automatically downgraded to the pay-as-you-go tier for processing, ensuring service continuity without any code changes.
Compare and select a plan
Model Studio offers various capacity and billing plans for inference calls, including pay-as-you-go, resource plans, savings plans, TPM reservations, and PTU dedicated deployments. Each plan has different characteristics regarding billing units, capacity guarantee levels, overage handling, and integration changes. This section helps you choose the right plan for your business needs.
Plan | Billing unit | Capacity guarantee | Use cases | Overage handling | Code changes |
pay-as-you-go | Per token | None (shared public resource pool) | Highly variable or short-term traffic | Served automatically, subject to public rate limits | No changes required |
resource plan / savings plan | Prepaid quota | Committed-use discount (not dedicated capacity) | Cost optimization | Overage switches to pay-as-you-go | No changes required |
TPM reservation | Prepaid per kTPM | Dedicated capacity with a firm guarantee | Predictable traffic and no tolerance for rate limiting | Overage gracefully degrades to the pay-as-you-go public resource pool without interruption. | Requires replacing the model parameter |
PTU (model deployment) | Prepaid per kTPM | dedicated deployment instance | High throughput and performance | Overage switches to pay-as-you-go | Requires replacing the model parameter |
Supported models
China (Beijing)
Model name | Prepaid - daily | |
Input | Output | |
qwen3.6-plus-2026-04-02 | CNY 2.02 | CNY 12.10 |
qwen3.6-flash-2026-04-16 | CNY 1.21 | CNY 7.26 |
qwen3.5-plus-2026-04-20 | CNY 0.81 | CNY 4.84 |
qwen3.7-max-2026-05-20 | CNY 12.10 | CNY 36.29 |
qwen3.7-plus-2026-05-26 | CNY 2.02 | CNY 8.06 |
glm-5.1 | CNY 6.05 | CNY 24.19 |
kimi-k2.6 | CNY 6.55 | CNY 27.22 |
deepseek-v4-flash | CNY 1.01 | CNY 2.02 |
deepseek-v4-pro | CNY 12.10 | CNY 24.19 |
glm-5.2 | CNY 8.06 | CNY 28.22 |
Singapore
Model name | Prepaid - daily | |
Input | Output | |
qwen3.6-plus-2026-04-02 | CNY 3.78 | CNY 22.66 |
qwen3.6-flash-2026-04-16 | CNY 1.89 | CNY 11.33 |
qwen3.5-plus-2026-04-20 | CNY 3.02 | CNY 18.13 |
qwen3.7-max-2026-05-20 | CNY 18.89 | CNY 56.66 |
qwen3.7-plus-2026-05-26 | CNY 3.02 | CNY 12.09 |
glm-5.1 | CNY 10.58 | CNY 33.24 |
deepseek-v4-flash | CNY 1.51 | CNY 3.02 |
deepseek-v4-pro | CNY 18.13 | CNY 36.26 |
Billing and usage
Billing begins once the deployment is successful. Calls within the reserved capacity do not incur additional charges.
This is a prepaid service with a one-time payment. The reservation is active continuously from the time of purchase. For detailed pricing, refer to the Model Studio console.
Refunds for scaling down or unsubscribing: The used portion is billed at a 1.5x rate, and the refund is calculated using the following formula:
Refund = Prepaid amount for the reduced portion - (Prepaid amount for the reduced portion × Used duration / Subscription duration × 1.5)Requests that exceed your guaranteed capacity are automatically downgraded to the standard pay-as-you-go tier, ensuring service continuity. You can view the number of degradations on the details page under Overage Degradation Statistics.
After expiration:
Create a TPM reservation
Prerequisites: You must have an active workspace in Model Studio. Sign in to the Model Studio console and click Create TPM Reservation.

Creating a TPM reservation requires a one-time prepaid payment. Use the capacity calculator to estimate your required TPM and confirm the cost before you submit the request.
Configure the following parameters:
Parameter
Description
Required
Value description
Reservation name
A custom name for easy identification.
Yes
Up to 50 characters.
Select model
Select the model for which you want to reserve capacity. A dedicated model code is automatically generated after you submit the request.
Yes
The console displays the available models.
Billing cycle
The billing period.
Yes
Daily
Input TPM
The reserved input throughput, measured in kTPM (1 kTPM = 1,000 tokens per minute).
Yes
The minimum value and increment step vary by model and are displayed in the console.
Output TPM
The reserved output throughput, measured in kTPM.
Yes
The minimum value and increment step vary by model and are displayed in the console.
Subscription duration
The validity period of the reservation.
Yes
Multiple options are available.
Auto-renewal
If enabled, the system automatically renews the subscription by deducting payment at 08:00 on the day before expiration. Enabled by default.
No
On / Off
Renewal duration
The duration for each automatic renewal.
No
The available values are the same as for Subscription duration.
After confirming the parameters, click Buy Now. In the payment confirmation dialog box, verify the cost and click Confirm Payment.
On the Overview tab of the TPM reservation details page, find the dedicated model code and click Copy.
Replace the
modelparameter in the API request with the copied dedicated model code:Prerequisites: A TPM reservation instance has been created and its status is Running.
# When request volume ramps up quickly in a short time, the system needs a brief warm-up period to allocate the required computing power. # During this warm-up, some requests may experience latency fluctuations. Performance stabilizes after the warm-up is complete. # We recommend implementing a request queue or a retry mechanism. import dashscope response = dashscope.Generation.call( api_key="your-api-key", model="your-dedicated-model-code", # Replace with your dedicated model code messages=[{"role": "user", "content": "Hello"}], ) print(response.output.text)# When request volume ramps up quickly in a short time, the system needs a brief warm-up period to allocate the required computing power. # During this warm-up, some requests may experience latency fluctuations. Performance stabilizes after the warm-up is complete. # We recommend implementing a request queue or a retry mechanism. curl -X POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions \ -H "Authorization: Bearer $DASHSCOPE_API_KEY" \ -H "Content-Type: application/json" \ -d '{"model":"your-dedicated-model-code","messages":[{"role":"user","content":"Hello"}]}'
Capacity calculator
The creation page includes a capacity calculator on the right that helps you estimate the TPM quota you need based on your workload. After you enter the following parameters, the calculator automatically outputs the recommended input and output TPM.
Parameter | Description | Impact on results |
requests per minute (RPM) | The number of requests sent per minute during peak business hours. | As RPM increases, the recommended input and output TPM increase proportionally. |
Average input length (tokens) | The average number of input tokens per request. | Longer input may fall into a higher tier with a larger coefficient, increasing the recommended input TPM. Tier boundaries differ by model. Refer to the console for actual values. |
Average output length (tokens) | The average number of output tokens per request. | Longer output may have a larger coefficient, increasing the recommended output TPM. |
Estimated cache hit rate (%) | The percentage of repeated prefixes in requests that result in a cache hit. The actual cache hit rate depends on the repetition in your request content and is determined at runtime. | A higher hit rate reduces input capacity consumption, lowering the recommended input TPM. This only affects input TPM, not output TPM. |

View and manage

Reservation details
Click a model card to go to its details page, which includes the following three tabs:
Overview

Basic Information: Reservation name, dedicated model code (can be copied), base model, and input/output capacity.
Statistics (last 7 days): Number of active reservations, total TPM and peak usage, and average utilization.
TPM Usage Trend: Switch between input and output to view the reserved capacity limit and actual usage.
Overage Degradation Statistics: Shows the number of times requests were downgraded after exceeding the reserved capacity.
Monitoring
This tab displays detailed monitoring metrics: utilization, quota usage (input/output), in-quota and out-of-quota call counts, and cache hit volume. For more details, see Model Monitoring.

API access
Displays the dedicated model code and call examples.

Management actions
On the Overview tab of the details page, find the target instance in the reservation list and perform the following actions from the Actions column:
Scaling

Click Scale and adjust the input TPM and output TPM in the dialog box.
Renewal
Click Renew, select a renewal duration, and complete the payment. If auto-renewal is enabled, the system automatically deducts the renewal fee at 08:00 on the day before expiration.
Unsubscribe
Click Unsubscribe. The system redirects you to the Billing Center to complete the process.
Unsubscribing cannot be undone. After you unsubscribe, the dedicated model code becomes invalid, and existing requests fall back to the public resource pool.