OpenAI compatible API · Attested · Public status

NVIDIA: Nemotron 3 Super vs Xiaomi: MiMo-V2.5

NVIDIA: Nemotron 3 Super vs MiMo-V2.5: compare current API pricing, context, provider routes, privacy, p50 latency, and OpenAI-compatible access.

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

Xiaomi: MiMo-V2.5 has the lower cheapest prompt+completion route on TrustedRouter. Xiaomi: MiMo-V2.5 has more provider fallback routes, while Xiaomi: MiMo-V2.5 has the larger context window. Current TrustedRouter probes show NVIDIA: Nemotron 3 Super with the lower p50 TTFT.

$0.511675/1MNVIDIA: Nemotron 3 Super cheapest route

$0.4431/1MXiaomi: MiMo-V2.5 cheapest route

839 msNVIDIA: Nemotron 3 Super fastest measured p50 TTFT via nvidia-nim

3397 msXiaomi: MiMo-V2.5 fastest measured p50 TTFT via xiaomi

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.

NVIDIA: Nemotron 3 SuperXiaomi: MiMo-V2.5

Model idnvidia/nemotron-3-super-120b-a12bxiaomi/mimo-v2.5

Publisher DeepInfra Xiaomi MiMo

AI IQ — IQ 109#59

Context262,144 tokens1,048,576 tokens

Credits provider routes45

Cheapest route$0.511675/1M$0.4431/1M

Cached input$0.15825/1M$0.01/1M to $0.102019/1M

Privacy posturehas ZDR routeprovider posture varies

Fastest measured p50 TTFT839 ms via nvidia-nim3397 ms via xiaomi

Highest measured throughputnot enough datanot enough data

Recent route uptime range100.00%100.00%

Modes chat chat

NVIDIA: Nemotron 3 Super routes

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

Xiaomi: MiMo-V2.5 routes

Overview5 Credits routes
PricingInput, cached input, and output rates
BenchmarksTrustedRouter and external sources
ProvidersAll serving providers

Related comparisons

Browse every comparison

Xiaomi: MiMo-V2.5 vs Z.ai: GLM 5.236 combined provider routes
NVIDIA: Nemotron 3 Super vs Z.ai: GLM 5.235 combined provider routes
MoonshotAI: Kimi K3 vs Xiaomi: MiMo-V2.528 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Xiaomi: MiMo-V2.527 combined provider routes
MoonshotAI: Kimi K3 vs NVIDIA: Nemotron 3 Super27 combined provider routes
Xiaomi: MiMo-V2.5 vs Z.ai: GLM 5.327 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs NVIDIA: Nemotron 3 Super26 combined provider routes
NVIDIA: Nemotron 3 Super vs Z.ai: GLM 5.326 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="nvidia/nemotron-3-super-120b-a12b",
    messages=messages,
)

Questions

Which should I use, NVIDIA: Nemotron 3 Super or Xiaomi: MiMo-V2.5?

Is NVIDIA: Nemotron 3 Super or Xiaomi: MiMo-V2.5 cheaper?

The current cheapest TrustedRouter route is $0.511675/1M for NVIDIA: Nemotron 3 Super and $0.4431/1M for Xiaomi: MiMo-V2.5. The comparison uses current catalog prices and updates as provider pricing changes.

Is NVIDIA: Nemotron 3 Super or Xiaomi: MiMo-V2.5 faster?

Current measured p50 time to first token is 839 ms for NVIDIA: Nemotron 3 Super and 3397 ms for Xiaomi: MiMo-V2.5. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test NVIDIA: Nemotron 3 Super and Xiaomi: MiMo-V2.5 with the same API?

Yes. Use the same OpenAI-compatible TrustedRouter base URL and API key, then change only the model id between nvidia/nemotron-3-super-120b-a12b and xiaomi/mimo-v2.5. This makes side-by-side evals possible without maintaining two provider integrations.