ZenMux

Data handling can vary by model and deployment. The privacy badge above shows the more conservative of the provider-wide fallback and the policies for routes on this page; each model page shows the policy for that specific route.

Models served by ZenMux

Model name

Model	Context	Input /M	Output /M	Cache read /M	Cache write /M	TTFT	Throughput
Doubao Seed Character bytedance/doubao-seed-character:zenmux	128k	$0.12/M	$0.31/M	$0.02/M	$0.0026/M	N/A	N/A
>32k tokens		$0.19/M	$0.93/M	N/A	N/A

Doubao Seed Character

bytedance/doubao-seed-character:zenmux

Context

128k

Input /M

$0.12/M

Output /M

$0.31/M

Cache read /M

$0.02/M

Cache write /M

$0.0026/M

TTFT

N/A

Throughput

N/A

Above 32k tokens: in $0.19/M · out $0.93/M

Prices are per million tokens. TTFT is the observed time to first token. Selectable routes include the applicable provider-selection markup; fixed routes show the standard model price. Availability and pricing refresh continuously; each model page shows the live provider comparison.

Using ZenMux via the API

Call a model served by ZenMux using its displayed model ID, including the provider suffix when selection is supported.

curl https://nano-gpt.com/api/v1/chat/completions \
  -H "Authorization: Bearer $NANOGPT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "bytedance/doubao-seed-character:zenmux",
    "messages": [{"role": "user", "content": "Hello"}]
  }'

For models with provider selection, append :zenmux to the model ID, set "provider": "zenmux" in the request body, or send an X-Provider: zenmux header. Explicit provider selection adds a route-specific markup over that provider's base price; the prices in the table above already include it. Models without provider selection use the displayed model ID without a provider suffix or selection surcharge.

See the API documentation for provider preferences, price-aware routing, and error behavior.