Model pricing
Current model prices and how PAYG charges and subscription Credits are calculated.
Prices are loaded from the current database configuration. This page shows public standard rates; account-specific rates and access are shown in your console.
Video model prices
Video rates are per requested output second and are configured separately for each model and resolution. Missing prices are not free prices; a configured zero is valid.
minimax-h3 · t2v, i2v, r2v
| Resolution | PAYG / second | Credits / second | Included seconds |
|---|---|---|---|
768P | USD 0.10 | 1000 | 0 |
minimax-h3-pai · t2v, i2v, r2v
| Resolution | PAYG / second | Credits / second | Included seconds |
|---|---|---|---|
768P | USD 0.10 | 1000 | 0 |
minimax-h3-vdn-8step · t2v, i2v
| Resolution | PAYG / second | Credits / second | Included seconds |
|---|---|---|---|
768P | USD 0.05 | 500 | 0 |
Video billing deducts the included seconds from the requested duration and applies the selected resolution rate. Generation runtime and the returned file duration do not replace the requested duration for billing.
For example, requesting 6 seconds with 1 included second bills 5 seconds. A 2K request uses the 2K rate, never the 768P rate.
The playground only shows configured resolutions with both PAYG and Credits prices. Supplier cost does not control option visibility; request creation also validates backend pricing readiness.
Video models →Billing rules
PAYG uses your prepaid balance. Subscription usage consumes Credits and is subject to the active plan quota, 5-hour window, weekly window, and model access rules.
When subscription quota or window allowances are exhausted, requests can use PAYG if the account and plan allow it and sufficient balance is available. Otherwise the request is rejected; an exhausted subscription does not make usage free.
A reservation or hold before execution is provisional, not an additional charge. Settlement applies the final charge and releases the unused reservation. Video tasks keep a pricing snapshot so later price changes do not reprice an existing task.
Video model prices ↑Failures and retries
Failed, cancelled, or expired video tasks release their reserved balance or Credits without a generation charge. Release can be asynchronous; the settled billing state in the request details is the source of truth.
Use the same idempotency key and identical request body when retrying video task creation. A different key creates a new logical task and can incur a separate charge.