Volcengine Ark Doubao-Seed-2.1-Pro Model ID and Pricing Configuration

One-sentence takeaway

Use doubao-seed-2.1-pro as the online model ID, and put the 256K input limit, online/Batch pricing, and cache-hit pricing into the routing configuration so Agent evaluations can be reproduced under a fixed budget.

Use cases

• Suitable tasks: API routing, cost budgeting, Pro/Turbo A/B evaluations, and batch planning on Volcengine Ark.

• Unsuitable tasks: Treating the normalized configuration block below as a complete SDK request; authentication, region, endpoint, tool parameters, and response fields still need to be configured according to the current API documentation.

• Applicable model versions: Online model doubao-seed-2.1-pro; the page also lists doubao-seed-2.1-turbo, so do not mix up the model IDs.

• Applicable clients, Agents, or APIs: Volcengine Ark online calls and Batch; the specific endpoint/authentication details are not fully disclosed on this page.

• Recommended reasoning tier and parameters: Not disclosed; during evaluation, fix and record the thinking toggle, maximum output, temperature, and other fields in the actual request.

Ready-to-use content

The following is a minimal template that organizes the official pricing table into a routing configuration. The field names are normalized knowledge-base fields, not the official API schema:

provider: volcengine-ark
model: doubao-seed-2.1-pro
mode: online
max_input_context: 256k
pricing:
  input_yuan_per_million_tokens: 6.00
  cached_input_yuan_per_million_tokens: 1.20
  output_yuan_per_million_tokens: 30.00
batch_pricing:
  input_yuan_per_million_tokens: 3.00
  cached_input_yuan_per_million_tokens: 1.20
  output_yuan_per_million_tokens: 15.00
evaluation_record:
  model_snapshot: record-the-current-endpoint-snapshot
  reasoning_mode: record-from-request
  tools: record-tool-list
  prompt_tokens: record
  completion_tokens: record

Testing/workflow steps

1. Confirm the actually purchasable model ID, region, and endpoint in the Ark console; the official page states that final specifications and fees are subject to the order result.

2. For online evaluations, record input tokens, cache hits, output tokens, and request mode; for long-context tasks, separately record whether the 256K input limit is exceeded.

3. Use the Batch pricing table to calculate costs separately for large-volume, latency-tolerant tasks; do not treat Batch pricing as the price for an online low-latency service.

4. Whenever the model or pricing is updated, save the page collection date and the model snapshot from the actual response, then rerun the same test set.

Raw evidence and data

• The official page lists the online input limit for doubao-seed-2.1-pro as [0,256]K, with online input priced at CNY 6.00 per million tokens, cache hits at CNY 1.20 per million tokens, and output at CNY 30.00 per million tokens.

• The same page lists Pro Batch input at CNY 3.00 per million tokens, cache hits at CNY 1.20 per million tokens, and output at CNY 15.00 per million tokens.

• The same page lists Turbo as a separate model: online 3.00/0.60/15.00 CNY and Batch 1.50/0.60/7.50 CNY (input/cache hit/output); these figures should not be applied to Pro.

• The page marks its last update as 2026-08-17 13:54:22; pricing and purchasable specifications may change.

Applicability boundaries

• This page is a pricing and model-list page, not a complete API parameter reference; tool calls, response formats, reasoning tiers, audio input, and regional availability cannot be inferred from it.

• “256K” is the input-length range shown on the page, and does not mean that every Agent harness can use it losslessly; actual use is also affected by the system prompt, tool results, and output budget.

• Pricing excludes business-side retry, routing, preprocessing, cache-strategy, and human-review costs; total cost should be calculated across the complete task lifecycle.

Source excerpts or observations (for compliant short quotations only)

• The page emphasizes that actual purchasable specifications and fees are subject to the order result.

• The page lists online and Batch separately; this configuration must also retain these two execution modes.