Throughput Reservation

Throughput Reservation (formerly TPM Reservation) locks dedicated inference capacity for a specified 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 Throughput Reservation.

Overview

With a TPM (Tokens Per Minute) reservation, you can lock dedicated inference throughput for a specified model. Calls within the 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 Throughput 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).
• Add Capacity Package: Purchase additional capacity instances on top of an existing reservation. The new instance shares the same dedicated model code, and the total reserved capacity increases accordingly. See Management operations.
• 8-hour time-slot reservation: In Standard mode, you can opt for pre-paid (by 8-hour time slot), fixed at 8 hours and effective immediately, suitable for scenarios where load is concentrated in specific time slots. For more information, see Throughput Reservation billing.

Compare and select a plan

Model Studio offers multiple capacity and billing plans for inference calls, including pay-as-you-go, resource plans and savings plans, Throughput Reservation, and PTU dedicated deployments. Each plan has different characteristics regarding billing unit, capacity guarantee level, overflow handling, and integration changes. This section helps you choose the appropriate plan based on your business needs.

Plan	Billing unit	Capacity guarantee	Use cases	Overflow handling	Code changes
Pay-as-you-go	Per token	None (shared public pool)	Highly variable/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	Excess traffic switches to pay-as-you-go	No changes required
Throughput Reservation	Prepaid per kTPM	Dedicated capacity with a firm guarantee	Predictable traffic, no tolerance for rate limiting	Optional: auto-overflow to pay-as-you-go (default) / reserved-capacity-only returns 429	Replace the model parameter
PTU (Model deployment)	Prepaid per kTPM	Dedicated deployment instance	High throughput and high performance	Optional: auto-overflow to pay-as-you-go (default) / PTU-capacity-only returns 429	Replace the model parameter

Supported models

For prices, see Throughput Reservation billing.

China (Beijing)

• Qwen3.8-Max
• Qwen3.7-Flash-2026-07-15
• Qwen3.7-Max-2026-05-20
• Qwen3.7-Plus-2026-05-26
• Qwen3.6-Flash-2026-04-16
• GLM-5.3
• GLM-5.2
• GLM-5.1
• DeepSeek-v4.1-Flash
• DeepSeek-v4-Flash
• DeepSeek-v4-Flash-0731
• DeepSeek-v4-Pro
• DeepSeek-v4-Pro-0813
• Kimi-K2.6
• kimi-k3.1-pro: Supports only daily prepaid reservations in standard mode.

Singapore

• Qwen3.8-Max
• Qwen3.7-Flash-2026-07-15
• Qwen3.7-Max-2026-05-20
• Qwen3.7-Plus-2026-05-26
• Qwen3.6-Flash-2026-04-16
• GLM-5.3
• GLM-5.2
• GLM-5.1
• DeepSeek-v4.1-Flash
• DeepSeek-v4-Flash
• DeepSeek-v4-Flash-0731
• DeepSeek-v4-Pro
• DeepSeek-v4-Pro-0813

Billing and usage notes

• Billing starts once deployment succeeds: capacity fees are billed based on the purchased amount, charged regardless of whether you make any calls, and not reduced based on actual usage (fees are incurred in full even if no calls are made). Calls within the reserved capacity incur no additional charges; the prepaid fee is paid as a one-off upfront payment, and the reservation remains in effect continuously from the successful purchase onward. For detailed charges, refer to the Bailian console.
• For the billing rules and sales constraints of the 8-hour time-slot reservation (pre-paid by 8-hour time slot), see Throughput Reservation billing.
• When the overflow policy is "Auto overflow": requests exceeding the quota 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 can still be called and renewed; from 2 to 14 hours after expiry, the instance is stopped, cannot be called, but can still be renewed; after 14 hours, the instance is released and cannot be recovered. (Based on the daily reservation policy; the 8-hour time-slot reservation does not apply to this grace period. For details, see 8-hour time-slot reservation billing.)

Create a Throughput Reservation

Prerequisites: Bailian model service is activated and a workspace has been created. Sign in to the Bailian console and click Create Throughput Reservation.

On the Create Throughput Reservation page, fill in parameters including reservation name, model, billing cycle, input TPM, output TPM, purchase duration, auto-renewal on expiry, and overflow policy. The right side of the page provides a TPM capacity calculator to help with estimation.

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 Throughput Reservation are available; refer to the console display.
   Performance mode	Inference performance tier that determines the output rate of the capacity.	Yes	Standard mode (same TPS as the standard API) / High-speed mode (PTU model deployment, 1.5–2× TPS improvement over the standard API)
   Billing cycle	Billing cycle.	Yes	Daily; 8-hour time slot (Standard mode only; fixed 8 hours, effective immediately. For details, see Throughput Reservation billing)
   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 one day before expiry (for execution rules, see Throughput Reservation billing). Enabled by default. The 8-hour time slot does not support renewal; this parameter does not apply.	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 Throughput 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 Throughput Reservation instance has been created and its status is Running.

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

# 短时间内请求量快速拉升时，系统需要短暂预热以匹配所需算力
# 预热期间部分请求可能出现延迟波动，预热完成后恢复稳定。
# 请做好请求排队或重试机制。

import dashscope

client = dashscope.Client(api_key="your-api-key")

response = client.chat.completions.create(
    model="your-dedicated-model-code",   # 替换为专属模型 code
    messages=[{"role": "user", "content": "你好"}],
)
print(response.choices[0].message.content)

# 短时间内请求量快速拉升时，系统需要短暂预热以匹配所需算力
# 预热期间部分请求可能出现延迟波动，预热完成后恢复稳定。
# 请做好请求排队或重试机制。
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":"你好"}]}'

After selecting the 8-hour time slot billing cycle, the creation page expands an 8-hour time-slot capacity configuration area: the effective window is displayed as read-only (the start point is rounded down from the purchase moment to the current full hour and cannot be customized; it is fixed at 8 hours and can cross natural days; durations shorter than 1 hour are counted as 1 hour), and the supply status is shown in real time. Orders can be placed only between 22:00 and 00:00 the next day (no orders can be placed between 00:00 and 22:00). When the time slot expires, the capacity automatically becomes invalid and the 2h/14h grace period does not apply. For details, see 8-hour time-slot reservation billing.

TPM capacity calculator

The TPM capacity calculator on the right side of the creation page helps you estimate the TPM quota to purchase based on your business load. After you fill in the following parameters, the calculator automatically outputs the recommended input TPM and output TPM.

Parameter	Description	Impact on result
Requests per minute (RPM)	Number of requests sent per minute during peak business hours.	The larger the RPM, the larger the recommended input and output TPM in proportion.
Average input length (tokens)	Average number of input tokens per request.	The longer the input, the higher the tier and the larger the coefficient, so the higher the recommended input TPM. Tier boundaries differ by model; refer to the actual console display.
Average output length (tokens)	Average number of output tokens per request.	The longer the output, the larger the coefficient may be, so the higher the recommended output TPM.
Cache hit rate	The proportion of requests whose repeated prefixes are cache hits. The actual hit rate depends on the repetition of request content; refer to the runtime result.	The higher the hit rate, the slower the input capacity is consumed, so the lower the recommended input TPM. Affects only input TPM, not output TPM.

View and manage

Go to the Bailian console and open the reservation list page. The list displays all reservation instances as model cards and supports filtering by model, time, and status.

On the Throughput Reservation page, each model card shows the active reservation count, reserved input/output TPM, and peak utilization ratio. The reservation list table includes columns for reservation ID, input/output TPM, status, billing method (daily, 8-hour time slot, hourly, etc.) and expiry date, and supports filtering by model, time, and status.

Reservation details

Click a target model card to open the detail page, which contains the following 3 tabs:

Overview

The Overview tab shows the following:

• 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).

Monitoring

Provides detailed runtime monitoring data: utilization, quota usage (input/output), number of calls inside and outside the quota, and cache hit volume; for 8-hour time-slot reservations, the package utilization within the 8-hour window is also displayed. For more details, see: Model monitoring.

API access

Displays the dedicated model code and invocation examples.

Management operations

On the target card on the reservation list page or in the detail page, you can perform the following management operations on a reservation instance. 8-hour time-slot reservation instances do not support scaling, renewal, or unsubscription (the capacity automatically becomes invalid after the time slot expires).

Add Capacity Package

The Throughput Reservation page manages both TPM reservations and PTU (Provisioned Throughput Units); Add Capacity Packages apply to both. In the "Active capacity instances" area of a target card on the reservation list page, click Add Capacity Package to purchase an additional capacity instance on top of an existing reservation. After the addition, the reservation's total capacity equals the sum of the base reservation and all add-capacity packages; the dedicated model code remains unchanged, so no API changes are required.

The top of the dialog shows the following information of the base reservation:

• Dedicated model code, base model, performance mode (Standard/High-speed), and overflow policy: inherited from the base reservation and cannot be changed.
• Existing packages: the number of capacity instances already added.

Fill in the following purchase parameters:

Parameter	Description	Required	Value description
Billing cycle	The billing cycle of the add-capacity package is constrained by the base reservation's billing method: if the base reservation is pre-paid, only pre-paid add-capacity packages can be selected; if the base reservation is post-paid, both pre-paid and post-paid add-capacity packages are available. High-speed mode supports post-paid or pre-paid; Standard mode only supports pre-paid (daily or 8-hour time slot).	Yes	Post-paid/Hourly / Pre-paid/Daily / Pre-paid/8-hour time slot (Standard mode only; capacity increases within the window and becomes invalid outside the window. For rules, see Throughput Reservation billing)
Input capacity	Added input throughput, in kTPM.	Yes	Starts at 10 kTPM, step 10 kTPM.
Output capacity	Added output throughput, in kTPM.	Yes	Starts at 1 kTPM, step 1 kTPM.
Purchase duration	Valid duration of the add-capacity package. Required only for Pre-paid/Daily; Post-paid/Hourly bills by actual duration and needs no entry.	Yes	1~30, 60, 90, 120, 365 days.
Auto-renewal on expiry	Applies only to Pre-paid/Daily. Automatically deducts payment and renews one day before expiry (for execution rules, see Throughput Reservation billing).	No	On / Off

NoteA Model Code can have at most one non-deleted post-paid (hourly) capacity instance. If a post-paid instance already exists, the billing cycle for Add Capacity Package can only be Pre-paid/Daily.

The bottom shows the input reservation, output reservation fees, and total. After confirming, click Confirm purchase. After the purchase succeeds, the new capacity instance appears in the "Active capacity instances" list, and the total reserved capacity increases accordingly.

Scaling

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

NoteInput 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.2x coefficient for refund (for details, see Throughput Reservation billing).

Renewal

Click Renew, select a renewal duration, and complete the payment. If Auto-renewal on expiry is enabled, the system automatically deducts payment and renews one day before expiry (for execution rules, see Throughput Reservation billing).

Unsubscribe

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

ImportantUnsubscription is irreversible. After unsubscription, the dedicated model code becomes invalid and existing requests fall back to public resource processing. When unsubscribing, the used portion is settled at a 1.2x coefficient for refund. For details, see Throughput Reservation billing.

Reservation instance status

Within 2 hours after the service expires, the status is Running; from 2 to 14 hours after expiry, it becomes Stopped; after 14 hours, it becomes Released and is eventually deleted.

Status	Description
Running	Running normally; can be called using the dedicated model code.
Pending	Created; waiting to take effect.
Modifying	Scaling in progress; service is not interrupted during this period.
Stopped	Stopped due to reasons such as overdue payment; can be restored after renewal.
Released	Reservation ended without renewal or via unsubscription; resources have been released and are irreversible.

FAQ

Q: What happens when the reserved capacity is exceeded?

It depends on the overflow policy selected at creation: under "Auto overflow", requests exceeding the reserved capacity automatically degrade to pay-as-you-go billing without service interruption. You can view the degradation count and time on the Overview tab of the detail page at Overflow degradation statistics; if degradations occur frequently, we recommend scaling up. Under "Reserved capacity only", requests exceeding the quota return a 429 error and incur no additional charges; if 429s occur frequently, we recommend scaling up.

Q: How do I obtain the dedicated model code?

After a Throughput Reservation is created, the system automatically generates a dedicated model code. You can copy the code on the Overview tab of the Throughput Reservation detail page. You must replace the model parameter in your API request with this code to use the reserved capacity.

Q: What happens when a reservation expires?

After a reservation expires, the dedicated model code becomes invalid, and subsequent requests automatically fall back to public resource processing (pay-as-you-go). We recommend enabling Auto-renewal on expiry in advance to avoid service impact.

Q: How do I determine whether to scale up?

On the Overview tab of the detail page, view the TPM usage trend chart and overflow degradation statistics. If utilization stays close to 100% or degradations occur frequently, we recommend scaling up the input/output TPM.