TPM reservation

​

Overview

• 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 model parameter in your API requests with this code.
• Overflow strategy: When creating a reservation, you can choose how to handle excess traffic — automatically overflow to pay-as-you-go (default, no service interruption) or use reserved capacity only (excess requests return 429, no additional charges incurred).

​

Compare and select a plan

​

Supported models

Prices are subject to the console; the tables are for reference only.

​

Billing and usage notes

• Billing starts once deployment succeeds. Calls within the reserved capacity incur no additional charges.
• Prepaid fees are paid in a one-off upfront payment and remain in effect from the moment of purchase. Refer to the Bailian console for the actual charges.
• The "daily" billing cycle is calculated by natural day: from the moment the instance takes effect until 00:00:00 the next day, rather than a continuous 24 hours from the purchase time. For example, a 1-day reservation purchased at 16:00 expires at 00:00 (effective for about 8 hours). We recommend purchasing at the start of a day, or enabling Auto-renewal on expiry to avoid service interruption.
• Downgrade and unsubscribe refund: the used portion is settled at a 1.2x coefficient. Formula: Refund = prepaid fee of the reduced portion - (prepaid fee of the reduced portion × used duration / purchased duration × 1.2)
• When the overflow policy is "Auto overflow": requests exceeding the guaranteed quota automatically degrade to standard pay-as-you-go billing without service interruption. You can view the degradation count on the detail page at Overflow degradation statistics. When set to "Reserved capacity only": requests exceeding the quota return 429 and incur no additional charges.
• Within 2 hours after the service expires: the instance is still running, can be called, and can be renewed; 2 to 14 hours after expiry: the instance is stopped, cannot be called, but can still be renewed; 14 hours after expiry: the instance is deleted and cannot be recovered.

​

Create a TPM reservation

1. Fill in the following parameters:

   Parameter	Description	Required	Value description
   Reservation name	Custom name for identification.	Yes	≤ 50 characters
   Select model	Select the model for which to reserve capacity. A dedicated model code is generated automatically upon submission.	Yes	Only models that support TPM reservation are available; refer to the console display.
   Billing cycle	Billing cycle.	Yes	Daily
   Input TPM	Reserved input throughput, in kTPM (1 kTPM = 1,000 tokens/minute).	Yes	The starting value and step vary by model; refer to the console display.
   Output TPM	Reserved output throughput, in kTPM.	Yes	The starting value and step vary by model; refer to the console display.
   Purchase duration	Valid duration of the reservation.	Yes	Enter the number of days in the input box. Supported values: 1-30, 60, 90, 120, 365 days.
   Auto-renewal on expiry	Automatically deducts payment and renews at 08:00 one day before expiry. Enabled by default.	No	On / Off
   Single renewal duration	Duration of each automatic renewal.	No	Enter the number of days in the input box. The value range is the same as the purchase duration.
   Overflow policy	How requests exceeding the reserved capacity are handled when it is exhausted.	Yes	Auto overflow to per-token pay-as-you-go (default; overflow switches to pay-as-you-go, no service interruption) / Reserved capacity only (overflow returns 429, no additional charges)

2. After confirming the parameters, click Buy now. In the fee confirmation dialog, verify the charges and click Confirm payment.
3. On the Overview tab of the TPM reservation detail page, find the Dedicated model code and click copy.
4. Replace the model parameter in your API request with the copied dedicated model code:

   Prerequisite: a TPM reservation instance has been created and its status is Running.

   The thinking_budget parameter of GLM-5.2 (which limits thinking length) does not take effect when called.

# When the request volume surges within a short period, the system needs a brief warm-up to match the required compute.
# During warm-up, some requests may experience latency fluctuations. Stability recovers after warm-up completes.
# Ensure you have request queuing or retry mechanisms in place.

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 the request volume surges within a short period, the system needs a brief warm-up to match the required compute.
# During warm-up, some requests may experience latency fluctuations. Stability recovers after warm-up completes.
# Ensure you have request queuing or retry mechanisms in place.
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"}]}'

​

TPM capacity calculator

​

View and manage

​

Reservation details

• Overview
• Monitoring
• API access

• Basic information: reservation name, dedicated model code (copyable), base model, input/output capacity.
• Statistics cards (last 7 days): active reservation count, total and peak TPM usage, average utilization.
• Utilization trend: switch between input/output directions; shows the reserved capacity line and actual usage.
• Overflow degradation statistics: shows the number of requests degraded after exceeding the reserved capacity (degradation occurs only under the "Auto overflow" policy).

Provides detailed runtime monitoring data: utilization, quota usage (input/output), number of calls inside and outside the quota, and cache hit volume. For more details, see: Model monitoring.

Displays the dedicated model code and invocation examples.

​

Management operations

• Scaling
• Renewal
• Unsubscribe

Click Scaling and adjust the input TPM and output TPM in the dialog.

Input TPM and output TPM can be set to 0: after zeroing, no capacity charges accrue and the dedicated model code is retained, avoiding code invalidation caused by expiry or unsubscription. However, zeroing is a downgrade, and the used portion is settled at a 1.5x penalty coefficient (see Billing and usage notes above).

Click Renew, select a renewal duration, and complete the payment. If Auto-renewal on expiry is enabled, the system automatically deducts payment and renews at 08:00 one day before expiry.

Click Unsubscribe and the system redirects to the Billing Center to complete the unsubscribe process.

Unsubscription is irreversible. After unsubscription, the dedicated model code becomes invalid and existing requests fall back to public resource processing.

​

FAQ