OpenAI compatible API · Attested · Public status

Qwen: Qwen3.5 397B A17B vs Xiaomi MiMo V2.5 Pro

Qwen: Qwen3.5 397B A17B has more Credits provider routes. Xiaomi MiMo V2.5 Pro has the lower published input-plus-output rate and the larger context window. There is not enough recent probe data to compare speed. Compare price, speed, context, and privacy.

Verify gateway

Onebase URL to migrate

100sof models and routes

0prompt or output logs. Always.

Compare routesProviders, price, context, and policy posture in one view.

Use auto when uptime mattersKeep a primary model and let fallback handle provider failures.

Same API shapeUse the OpenAI client and set the model you want.

Practical read

Monthly evidence

$3.63975/1MQwen: Qwen3.5 397B A17B cheapest route

$1.65213/1MXiaomi MiMo V2.5 Pro cheapest route

2007 msQwen: Qwen3.5 397B A17B fastest measured p50 TTFT via digitalocean

not enough dataXiaomi MiMo V2.5 Pro fastest measured p50 TTFT

The price comparison adds each route's rate for one million input tokens and one million output tokens; your cost depends on your input/output mix. Prices and live route measurements can change. Use the monthly reports when you need a stable evidence window, then run a small task-specific eval before choosing a production default.

Qwen: Qwen3.5 397B A17BXiaomi MiMo V2.5 Pro

Model idqwen/qwen3.5-397b-a17bxiaomimimo/mimo-v2.5-pro

Publisher Alibaba Cloud Model Studio Xiaomi MiMo

AI IQ — IQ 115#53

Context262,144 tokens1,048,576 tokens

Credits provider routes111

Cheapest route$3.63975/1M$1.65213/1M

Cached input$0.047475/1M to $0.58025/1M$0.01/1M

Privacy posturehas Confidential route (E2EE + ZDR)provider posture varies

Fastest measured p50 TTFT2007 ms via digitaloceannot enough data

Highest measured throughputnot enough datanot enough data

Recent route uptime range75.00% to 100.00%not enough data

Modes chat chat

Qwen: Qwen3.5 397B A17B routes

Overview11 Credits routes
PricingInput, cached input, and output rates
ProvidersAll serving providers

Xiaomi MiMo V2.5 Pro routes

Overview1 Credits routes

Related comparisons

Browse every comparison

Qwen: Qwen3.5 397B A17B vs Z.ai: GLM 5.344 combined provider routes
Qwen: Qwen3.5 397B A17B vs Z.ai: GLM 5.3 Flash44 combined provider routes
Qwen: Qwen3.5 397B A17B vs Z.ai: GLM 5.243 combined provider routes
MoonshotAI: Kimi K3 vs Qwen: Qwen3.5 397B A17B40 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Qwen: Qwen3.5 397B A17B38 combined provider routes
DeepSeek: DeepSeek V4.1 Flash vs Qwen: Qwen3.5 397B A17B35 combined provider routes
OpenAI: gpt-oss-120b vs Qwen: Qwen3.5 397B A17B34 combined provider routes
Xiaomi MiMo V2.5 Pro vs Z.ai: GLM 5.3 Flash34 combined provider routes

Production choice

Pick a default model. Keep fallback enabled.

TrustedRouter is useful when you know the model you want, but still need provider rollover, budget limits, usage records, and a prompt path you can verify.

OpenAI clientPython

client = OpenAI(
    base_url="https://api.trustedrouter.com/v1",
    api_key="sk-tr-v1-..."
)

response = client.chat.completions.create(
    model="qwen/qwen3.5-397b-a17b",
    messages=messages,
)

Questions

Which should I use, Qwen: Qwen3.5 397B A17B or Xiaomi MiMo V2.5 Pro?

Is Qwen: Qwen3.5 397B A17B or Xiaomi MiMo V2.5 Pro cheaper?

The current cheapest TrustedRouter route is $3.63975/1M for Qwen: Qwen3.5 397B A17B and $1.65213/1M for Xiaomi MiMo V2.5 Pro. The comparison uses current catalog prices and updates as provider pricing changes.

Is Qwen: Qwen3.5 397B A17B or Xiaomi MiMo V2.5 Pro faster?

Current measured p50 time to first token is 2007 ms for Qwen: Qwen3.5 397B A17B and not enough data for Xiaomi MiMo V2.5 Pro. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test Qwen: Qwen3.5 397B A17B and Xiaomi MiMo V2.5 Pro with the same API?

Yes. Use the same OpenAI-compatible TrustedRouter base URL and API key, then change only the model id between qwen/qwen3.5-397b-a17b and xiaomimimo/mimo-v2.5-pro. This makes side-by-side evals possible without maintaining two provider integrations.