Throughput Reservation Billing

​

Billing Rules

Throughput reservation purchases dedicated inference throughput via subscription. Calls within the reserved capacity incur no additional charges; the excess is handled per the overflow strategy. The dedicated model Code (invocation identifier, used to replace the model parameter of the API) generated after you create a throughput reservation is used for billing and invocation statistics.

Performance Mode	Standard mode: same TPS as the standard API. High-speed mode: 1.5~2× TPS improvement over the standard API (i.e., PTU model deployment).
Billing Method	Subscription (by day): supported for both standard and high-speed modes, billed by natural day. Input is priced per 10K-TPM and output per 1K-TPM. Subscription (by 8-hour time slot): only for standard mode, fixed 8 hours, effective immediately. For more information, see 8-Hour Time Slot Reservation Billing. Pay-as-you-go (by hour): only for high-speed mode, billed by actual duration, no duration purchase required.
Billing Formula	Subscription: Reservation Fee = Duration (days) × (Input Unit Price × Input kTPM ÷ 10 + Output Unit Price × Output kTPM)Pay-as-you-go (hour granularity, minute precision): Pay-as-you-go Fee = (Usage Minutes ÷ 60) × (Pay-as-you-go Input Unit Price × Input 10K-TPM + Pay-as-you-go Output Unit Price × Output 1K-TPM)
Billed Upon Activation	Billing starts as soon as the reservation is successfully created; calls within the reserved capacity incur no additional charges; capacity fees are billed based on the purchased amount, not reduced by actual usage.
New Purchase Capacity Expiration Time	UTC+8: if purchased before 22:00 on the current day, the expiration time is 23:59:59 on the current day. If purchased after 22:00, the expiration time is 23:59:59 on the next day.
Input Capacity	Starting from 200 kTPM, step size 10 kTPM.
Output Capacity	Starting from 20 kTPM, step size 1 kTPM.
Duration	Supports 1~30, 60, 90, 120, 365 days.
Renew	Fee = Days × New Purchase Price.
Auto-Renew on Expiration	Auto-deducts and renews 1 day before expiration, with up to 4 attempts between 8:20–20:00 on that day. Enabled by default, can be disabled.

​

Unit Description

• kTPM = 1,000 Tokens/minute, the purchase quantity unit.
• 10K-TPM = 10,000 Tokens/minute = 10 kTPM. Input unit price is quoted per 10K-TPM; in the formula kTPM ÷ 10 converts to 10K-TPM then multiplied by the unit price; output unit price is quoted per 1K-TPM (1K-TPM = 1 kTPM), multiplied directly.

​

Supported Models and Pricing

The subscription prices for standard mode (same TPS as pay-as-you-go invocations) and high-speed mode (1.5~2× TPS) are as follows:

​

Capacity Conversion Rules

Long input is converted by a tiered coefficient, and the cache-hit portion is converted by a cache conversion coefficient; the converted amount is deducted from the purchased quota. Parameters for each model are as follows.

Model	Max Input Token	Cache Conversion Coefficient	Long Input Tiered Coefficient
qwen3.8-max	1M	0.125	No tier (1.0)
qwen3.7-flash-2026-07-15	1M	0.2	Same for input and output (0,32K] 1x (32K,256K] 3x (256,1m] 6x
qwen3.7-max-2026-05-20	256K	0.1	No tier (1.0)
qwen3.7-plus-2026-05-26	256K	0.2	No tier (1.0)
qwen3.6-flash-2026-04-16	256K	1	No tier (1.0)
glm-5.3	1M	0.25	No tier (1.0)
glm-5.2	1M	0.25	No tier (1.0)
glm-5.1	200K	0.2	(0,32K] Input 1x / Output 1x (32K,200K] Input 1.33x / Output 1.17x
deepseek-v4.1-flash	1M	0.06	No tier (1.0)
deepseek-v4-flash	256K	0.1	No tier (1.0)
deepseek-v4-flash-0731	1M	0.1	No tier (1.0)
deepseek-v4-pro	256K	0.08	No tier (1.0)
deepseek-v4-pro-0813	1M	0.1	No tier (1.0)
kimi-k2.6	256K	0.2	No tier (1.0)

Capacity conversion examples are as follows.

​

8-Hour Time Slot Reservation Billing

8-hour time slot reservation (8h Block) provides a continuous 8-hour TPM capacity certainty guarantee for scenarios where the load is concentrated in specific time slots.

​

Purchase and Billing Rules

• Billing method: Subscription (by 8-hour time slot), only for standard mode; enjoy a 10% discount, subject to the price displayed in the Model Studio console.
• Orderable time slots: daily 20:00–next day 04:00 (the order moment must fall within this time slot).
• Effective: effective immediately after purchase, fixed duration of 8 hours, can cross natural days; the effective start point is rounded down to the current whole hour based on the purchase moment and cannot be customized; less than 1 hour is counted as 1 hour.
• Two purchase forms:
  • New independent reservation: generates a dedicated model Code.
  • Added as an add-on capacity package to an existing reservation: reuses the base reservation's dedicated model Code, increasing capacity within that 8-hour window. For more information, see Add-on Capacity Package Billing.

​

Limits

• Scale-out/scale-in and renew/unsubscribe are not supported.
• Capacity automatically becomes invalid after the time slot expires.
• Orders cannot be placed between 04:00–20:00 on the current day.

​

Expiration and Lifecycle

The service stops immediately upon expiration, and resources are released 2 hours after the stop.

Phase (after expiration)	Instance Status	Can Invoke/Renew
0~2 hours	Stopped	Cannot invoke, can still renew
After 2 hours	Released	Cannot be recovered

It is recommended to enable Auto-Renew on Expiration in advance to avoid service interruption.

​

Scale Out

​

Subscription Instances

• Subscription purchase granularity is by day, billing precision is by hour.
• Newly added capacity from scale-out is billed by the remaining validity period, converted to days: remaining hours ÷ 24, rounded up.
• Less than 1 day (24 hours) remaining is still counted as 1 day (e.g., 5 hours remaining counts as 1 day).

Scale-Out Fee = Rounded Up(Remaining Hours ÷ 24) × (Input Capacity Difference (kTPM) ÷ 10 × Input Unit Price + Output Capacity Difference (kTPM) × Output Unit Price)

​

Pay-as-you-go Instances

• Pay-as-you-go purchase granularity is by hour, billing precision is by minute.
• Scale-out is billed by actual usage duration; less than 1 hour (60 minutes) is billed by actual minutes.
• Fee = Usage Minutes ÷ 60 × Unit Price × Capacity (e.g., 30 minutes billed as 0.5 hour).

Scale-Out Fee = (Usage Minutes ÷ 60) × (Pay-as-you-go Input Unit Price × Input Capacity Difference (kTPM) ÷ 10 + Pay-as-you-go Output Unit Price × Output Capacity Difference (kTPM))

​

Scale In

​

Subscription Instances

• Subscription purchase granularity is by day, billing precision is by minute (settled amount rounded up by hour).
• Settled amount = Rounded Up(used hours) × Penalty coefficient.
• New spec fee is precise to the minute; used ≤30 days at 1.2×, >30 days at 1.0×.

Refund = max(Original Spec Remaining Fee - New Spec Purchase Fee, 0)

• Original Spec Remaining Fee = Paid Amount - Settled Amount
• Settled Amount = (Daily Unit Price ÷ 24) × Rounded Up(Used Hours) × Penalty Coefficient × Original Capacity (kTPM) ÷ 10
• New Spec Purchase Fee = Daily Unit Price × (Remaining Hours ÷ 24) × New Capacity (kTPM) ÷ 10

​

Pay-as-you-go Instances

• Pay-as-you-go purchase granularity is by hour, billing precision is by minute.
• Used amount is settled by usage minutes ÷ 60, no refund is generated.
• After scale-in, the new capacity is billed at the new capacity from the effective time; deletion or zeroing stops billing.

Used Amount = Pay-as-you-go Input Unit Price × Input Capacity (kTPM) ÷ 10 × Used Minutes ÷ 60 + Pay-as-you-go Output Unit Price × Output Capacity (kTPM) × Used Minutes ÷ 60

​

Unsubscribe

​

Subscription Instances

• Subscription purchase granularity is by day, billing precision is by minute (settled amount rounded up by hour).
• Unsubscribe is a special case of scale-in (new spec = 0); the settled amount is settled by Rounded Up(used hours) × Penalty coefficient.
• ≤30 days at 1.2×, >30 days at 1.0×; unsubscribe is irreversible, and the dedicated model Code becomes invalid immediately.

Refund = max(Original Spec Remaining Fee, 0) (special case of scale-in where New Spec Purchase Fee = 0) The unsubscribe process is handled in the Expenses Center.

​

Pay-as-you-go Instances

• Pay-as-you-go purchase granularity is by hour, billing precision is by minute.
• Used amount is settled by usage minutes ÷ 60, no refund is generated.
• Deleting the instance stops billing.

Used Amount = Pay-as-you-go Input Unit Price × Input Capacity (kTPM) ÷ 10 × Used Minutes ÷ 60 + Pay-as-you-go Output Unit Price × Output Capacity (kTPM) × Used Minutes ÷ 60

​

Add-on Capacity Package Billing

An additionally purchased capacity instance (add-on capacity package) reuses the same dedicated model Code; the total capacity increases accordingly, with no API changes required.

Billing Item	Description
Billing Cycle	The selectable billing cycle of the add-on package is constrained by the base reservation's billing method: when the base is subscription, only a subscription add-on package can be selected; when the base is pay-as-you-go, either a subscription or pay-as-you-go add-on package can be selected. Subscription (by day): supported for both standard and high-speed modes, billed by natural day; billing rules are the same as a new purchase. Subscription (by 8-hour time slot): only for standard mode, rules same as 8-Hour Time Slot Reservation Billing. After adding, the capacity increases for the same dedicated model Code within that 8-hour window; outside the window, the 8h package capacity becomes invalid. Pay-as-you-go (by hour): only for high-speed mode, billed by actual duration, no duration purchase required.
Input Capacity	Starting from 200 kTPM, step size 10 kTPM.
Output Capacity	Starting from 20 kTPM, step size 1 kTPM.
Duration	Only required for Subscription/by day: 1~30, 60, 90, 120, 365 days.
Auto-Renew on Expiration	Only applies to Subscription/by day; auto-deducts and renews 1 day before expiration, with up to 4 attempts between 8:20–20:00 on that day.

​

Overflow Strategy and Billing

The overflow strategy determines how the excess is handled and billed after the capacity is exhausted:

Overflow Strategy	Excess Behavior	Billing Method
Auto Overflow (Default)	Excess requests are automatically downgraded to the model standard pay-as-you-go billing (Token billing), without service interruption.	The excess is billed at the pay-as-you-go model invocation standard rate, no longer enjoying the reserved pricing. You can view the number of degradations in Overage Degradation Statistics on the details page.
Use Reserved Capacity Only	Excess requests return a 429 error; the business needs to retry or degrade on its own.	The excess incurs no additional fees.

In the auto-overflow scenario, when a single input exceeds the model maximum input Token, that invocation is also converted to pay-as-you-go billing.

​

Bills and Usage Query

• Expense bills: Subscription orders can be viewed in the Expenses Center, supporting order details and consumption records.
• Usage monitoring: On the details page of the Model Studio console, the Overview tab shows usage trends, utilization, and overage degradation statistics; the Monitor tab shows the number of invocations inside and outside the quota and the cache hit volume. For more information, see Monitoring.
• Utilization description: Utilization = Converted Consumption ÷ Purchased Quota. The long-input tiered coefficient has been included in the converted consumption.

​

FAQ

Q: Why is the refund 0?

When the original spec remaining fee ≤ the new spec purchase fee, the refund is 0. Settled amount = (Daily Unit Price/24) × Rounded Up(Used Hours) × Penalty Coefficient × Original Capacity (kTPM) ÷ 10; used duration ≤30 days is settled at the 1.2× penalty coefficient; >30 days at 1.0× (no penalty). The longer the usage, the higher the settled amount, the lower the remaining fee, and the refund may be 0.

Q: What is the difference between standard mode and high-speed mode?

Standard mode has the same TPS as the standard API; high-speed mode has a 1.5~2× TPS improvement over the standard API. The billing rules of the two modes are similar, but high-speed mode additionally supports pay-as-you-go/by hour, and the billing cycle options and prices are different.

Q: How to estimate the reservation fee?

Use the formula Reservation Fee = Duration (days) × (Input Unit Price × Input kTPM ÷ 10 + Output Unit Price × Output kTPM); the unit price is taken from the corresponding mode column of the price table. For more information, see the example in Billing Rules.

Q: Can I get a refund after purchase? How much?

You can scale in or unsubscribe. Refund = max(Original Spec Remaining Fee - New Spec Purchase Fee, 0); the used portion is settled by the penalty coefficient. For more information, see Scale In.

Q: What happens upon expiration?

Upon expiration, the service stops immediately and resources are released; the dedicated model Code becomes invalid and cannot be recovered. It is recommended to enable Auto-Renew on Expiration in advance to avoid service interruption. For more information, see Expiration and Lifecycle.

Q: Can the dedicated model Code still be used after zeroing?

After zeroing, no capacity fee is incurred and the dedicated model Code is retained, but the capacity is 0 and cannot be invoked. You need to scale out again to restore invocations.

​

Related Documents

• Throughput Reservation
• Throughput Reservation DashScope OpenAPI Interface Documentation
• Model Training and Deployment Billing