Free to start

MoonshotAI: Kimi K2.5 vs NVIDIA: Nemotron 3 Super

Try both on us. Starter credit covers your first requests, then one key routes Kimi K2.5 and Nemotron 3 Super. Switch by changing the model name.

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

MoonshotAI: Kimi K2.5 has more Credits provider routes. NVIDIA: Nemotron 3 Super has the lower published input-plus-output rate. Their context windows are the same size. There is not enough recent probe data to compare speed.

$2.79575/1MMoonshotAI: Kimi K2.5 cheapest route

$0.511675/1MNVIDIA: Nemotron 3 Super cheapest route

not enough dataMoonshotAI: Kimi K2.5 fastest measured p50 TTFT

not enough dataNVIDIA: Nemotron 3 Super 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.

MoonshotAI: Kimi K2.5NVIDIA: Nemotron 3 Super

Model idmoonshotai/kimi-k2.5nvidia/nemotron-3-super-120b-a12b

Publisher Kimi NVIDIA

AI IQ IQ 110#77 —

Context262,144 tokens262,144 tokens

Credits provider routes94

Cheapest route$2.79575/1M$0.511675/1M

Cached input$0.07385/1M to $0.422/1M$0.15825/1M

Privacy posturehas ZDR routehas ZDR route

Fastest measured p50 TTFTnot enough datanot enough data

Highest measured throughputnot enough datanot enough data

Recent route uptime rangenot enough datanot enough data

Modes chat chat

MoonshotAI: Kimi K2.5 routes

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

NVIDIA: Nemotron 3 Super routes

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

Related comparisons

Browse every comparison

MoonshotAI: Kimi K2.5 vs Z.ai: GLM 5.342 combined provider routes
MoonshotAI: Kimi K2.5 vs Z.ai: GLM 5.241 combined provider routes
MoonshotAI: Kimi K2.5 vs Z.ai: GLM 5.3 Flash41 combined provider routes
MoonshotAI: Kimi K2.5 vs MoonshotAI: Kimi K337 combined provider routes
NVIDIA: Nemotron 3 Super vs Z.ai: GLM 5.337 combined provider routes
NVIDIA: Nemotron 3 Super vs Z.ai: GLM 5.236 combined provider routes
NVIDIA: Nemotron 3 Super vs Z.ai: GLM 5.3 Flash36 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs MoonshotAI: Kimi K2.535 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-azure.trustedrouter.com/v1",
    api_key="sk-tr-v1-..."
)

response = client.chat.completions.create(
    model="moonshotai/kimi-k2.5",
    messages=messages,
)

Questions

Which should I use, MoonshotAI: Kimi K2.5 or NVIDIA: Nemotron 3 Super?

Is MoonshotAI: Kimi K2.5 or NVIDIA: Nemotron 3 Super cheaper?

The current cheapest TrustedRouter route is $2.79575/1M for MoonshotAI: Kimi K2.5 and $0.511675/1M for NVIDIA: Nemotron 3 Super. The comparison uses current catalog prices and updates as provider pricing changes.

Is MoonshotAI: Kimi K2.5 or NVIDIA: Nemotron 3 Super faster?

Current measured p50 time to first token is not enough data for MoonshotAI: Kimi K2.5 and not enough data for NVIDIA: Nemotron 3 Super. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test MoonshotAI: Kimi K2.5 and NVIDIA: Nemotron 3 Super with the same API?

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