Doubao API Prices: China RMB Token Bands, Cache Hits and Routing Modes

The Ark pricing matrix is conditional

Volcengine’s official Ark rate table distinguishes doubao-seed model lines by version, context-length band, low-latency or lower-priority execution, input type and cache hits. For example, its displayed low-latency doubao-seed-2.0-mini tier for inputs no longer than 32,000 tokens lists CNY 0.4 per million non-audio input tokens, CNY 0.08 cache-hit input tokens and CNY 4 per million output tokens. These figures describe that route and band only. Another Doubao model or longer request should have its own snapshot row even when the model marketing family is unchanged.

A simple call budget, with one threshold

Suppose the full request remains inside the first 32k input band and the billing response reports one million new text input tokens across a day, 500,000 cache-hit tokens and 300,000 output tokens. The illustrative subtotal is CNY 1.64: 1×0.4 + 0.5×0.08 + 0.3×4. It is a made-up usage scenario calculated from vendor list rates, not an observed workload. Crossing the documented input-length threshold can change both input and output tariffs; do not split a single long request into a cheap first segment and a second segment unless the vendor explicitly bills that way.

The cache has both read and storage economics

Volcengine’s detailed pricing documentation identifies input cache hits and optional cache-storage token-hours as distinct categories. If long instructions or retrieval context persist, usage accounting should track cache storage duration as well as requests. A price table that exposes a dash for a particular audio input meter should be treated as “not listed/not applicable to this row,” not as proof that any audio task is free. Keep audio and text input separate, and preserve the vendor’s original CNY currency rather than silently applying a spot exchange rate.

Low-priority and batch are not a universal discount

Lower-priority inference may advertise materially lower tariffs in the official docs, at the cost of changed queueing or delivery properties. Those are separate product schedules, not an adjustment to the online price of every request. Production systems should record whether the job was interactive, queued or batch, plus observed waiting time and any resubmitted calls. Compare alternatives on accepted output, not just an appealing token price: failed JSON formatting and retry loops can erase theoretical rate savings.

Regional evidence and audit trail

These are mainland-China-facing Volcengine list figures and do not establish overseas account availability, local taxes or payment methods. The web documentation requires JavaScript in some environments, so the recorded evidence is the searchable first-party pricing extract rather than an independently tested checkout. The live table has no verified rate effective date for every line: it stays null. For publication refresh, obtain the relevant product-console invoice or dated pricing notice before claiming a contracted tariff.

Decision checklist and limitations

Before purchase or deployment, retain the literal model or plan identifier, payer/merchant, country or cloud region, billing currency, exact usage meter, source URL, checked date, effective date if explicitly supported, and any plan commitment or promotional eligibility. Recalculate from the companion price and quota snapshots rather than assuming that a remembered list tariff will remain unchanged. A credit allowance, maximum input length, published token rate and confirmed billed currency answer different questions; never add them as if they were the same quantity.

When comparing another provider or route, use the same input/output distribution and acceptable result definition. Include unsuccessful attempts, optional tools, storage, tax, payment and human review only when those components are actually measured or supported by an explicit source. Vendor marketing and documentation are not independent product tests. This article makes no claim to have personally tested paid endpoints, purchased plans, or checked account-specific taxes or availability.