PRICING & BILLING
Understand prices, multipliers, and actual charges
Start with the model's official USD numeric price, then apply the current group multiplier. The final bill is the amount recorded against actual usage.
Last updated:
Pricing formula
懂api price = official USD numeric price × CNY 1 × current group multiplier. The official CNY reference = the same official USD number × approximately CNY 7.
Platform input = official input USD / 1M tokens × CNY 1 × group multiplier
Platform output = official output USD / 1M tokens × CNY 1 × group multiplier
Official CNY reference = official USD number × approximately CNY 7If the official input number is USD 5 and the group multiplier is 1x, 懂api displays CNY 5 per 1M tokens; the official CNY reference is approximately CNY 35.
Each billing dimension is calculated separately
| Dimension | Meaning | Usage log |
|---|---|---|
| Input | Billable tokens sent to the model | Prompt tokens |
| Output | Billable tokens generated by the model | Completion tokens |
| Cache read | Tokens served from an existing context cache | Cache read |
| Cache write | Tokens written to a context cache | Cache write |
| Per request | Image, video, or task-based billing | Request or task charge |
Grok image and video billing
Grok images are billed per image: each image costs the
configured base price times the group multiplier. Grok
videos follow the live catalog price_unit:
second charges
the base rate for the selected mode and resolution × submitted
duration × the current group multiplier. Single-image and 2–4-image generation use their
image-generation rate; reference images carry no separate count
fee. Version 1.5 without images uses the text-only rate. 1080p
requires version 1.5 with reference images. Base rates and group
multipliers remain separate; discounts never rewrite the base
rate. Grok second rates follow the platform pricing rule: the USD
numeric rate forms the CNY base at 1 USD = 1 CNY, then the group
multiplier applies once. The official CNY reference uses
approximately 1 USD = 7 CNY for comparison only. For example, a
base rate of CNY P per second for 8 seconds at multiplier 0.6
costs P × 8 × 0.6 = 4.8P CNY; the current rate of each mode and
resolution is on the Grok model page.
Mode, resolution, duration, and rate freeze at
submission and appear in Usage logs. Models still marked
request and historical tasks retain their original
per-request contract. The live model catalog is authoritative for
currency and current prices.
Seedance 2.5 video billing
Seedance 2.5 models named with 480p, 720p or 1080p are billed per second by Volcengine Ark's official rules at the official CNY prices:
- Without reference video (text, reference images, reference audio): the no-video price × output seconds × your group ratio.
- With reference video: the with-video price × (output seconds + total reference video length) × your group ratio; reference videos count at their actual length, and a total under 4 seconds counts as 4 seconds.
Example: a 5-second 720p output with a 6-second reference video
at group ratio 1 costs 0.9072 × (5 + 6) = CNY 9.98. Mode,
resolution, seconds, reference video length and price freeze at
submission and appear in Usage logs; a reference video that
cannot be read rejects the request before any charge, and failed
generations are refunded. Models named with a duration (such as
-30s) are billed per request. Parameters and media
requirements are in the
API reference; the live
model catalog is authoritative for current prices.
Why group prices differ
A group quote exists only when an enabled channel supports the model, the group is available to the user, and the group has a valid public multiplier. Unsupported model/group pairs are omitted.
The live JSON catalog provides a version, checked time, capabilities, endpoints, and quotes for every currently valid model/group pair.
MiniMax-H3 currently supports 768P and 4–15 seconds, default 5 seconds. See AIGC parameters for reference limits and Task API for polling and Bearer-authenticated downloads.
Verify the actual charge
- Open Usage logs and filter by request ID, model, or time.
- Check final status, input/output tokens, cache dimensions, and charged amount.
- For smart routing, the selected concrete token group is recorded in request details.
Use Models for pre-call comparison and Usage logs for post-call settlement.
Overview and log statistics
The overview defaults to today with hourly aggregation. Wallet/lifetime usage, filtered usage, and platform totals have separate scopes. Log charge summaries follow the selected log type and filters. Error logs describe failed attempts; a summary amount does not prove a failed request was charged. Check the final result and charge for the same request ID. See Overview statistics.
Common questions
Is a multiplier applied more than once?
No. The current selected group multiplier is applied once to the official model base price.
Why is a group quote missing?
The model currently has no enabled channel in that group, the group is unavailable to the user, or no valid public multiplier is configured.
Which value is final?
The charged amount in Usage logs, calculated from actual usage and task parameters, is final.