OpenAI compatible API · Attested · Public status

DeepSeek V4 Pro 0813 vs MoonshotAI: Kimi K2.5

DeepSeek V4 Pro 0813 vs MoonshotAI: Kimi K2.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

DeepSeek V4 Pro 0813 has the lower cheapest prompt+completion route on TrustedRouter. MoonshotAI: Kimi K2.5 has more provider fallback routes, while DeepSeek V4 Pro 0813 has the larger context window. Current TrustedRouter probes show DeepSeek V4 Pro 0813 with the lower p50 TTFT.

$2.7852/1MDeepSeek V4 Pro 0813 cheapest route

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

1714 msDeepSeek V4 Pro 0813 fastest measured p50 TTFT via baseten

1790 msMoonshotAI: Kimi K2.5 fastest measured p50 TTFT via siliconflow

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.

DeepSeek V4 Pro 0813MoonshotAI: Kimi K2.5

Model iddeepseek/deepseek-v4-pro-0813moonshotai/kimi-k2.5

Publisher DeepSeek Kimi

AI IQ — IQ 111#55

Context1,024,000 tokens262,144 tokens

Credits provider routes39

Cheapest route$2.7852/1M$2.79575/1M

Cached input$0.02321/1M to $0.13926/1M$0.07385/1M to $0.422/1M

Privacy posturehas ZDR routeprovider posture varies

Fastest measured p50 TTFT1714 ms via baseten1790 ms via siliconflow

Highest measured throughputnot enough datanot enough data

Recent route uptime range100.00%100.00%

Modes chat chat

DeepSeek V4 Pro 0813 routes

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

MoonshotAI: Kimi K2.5 routes

Overview9 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.240 combined provider routes
DeepSeek V4 Pro 0813 vs Z.ai: GLM 5.234 combined provider routes
MoonshotAI: Kimi K2.5 vs MoonshotAI: Kimi K332 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs MoonshotAI: Kimi K2.531 combined provider routes
MoonshotAI: Kimi K2.5 vs Z.ai: GLM 5.331 combined provider routes
MoonshotAI: Kimi K2.5 vs Z.ai: GLM 5.3 Flash29 combined provider routes
MoonshotAI: Kimi K2.5 vs MoonshotAI: Kimi K2.628 combined provider routes
MoonshotAI: Kimi K2.5 vs OpenAI: gpt-oss-120b28 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="deepseek/deepseek-v4-pro-0813",
    messages=messages,
)

Questions

Which should I use, DeepSeek V4 Pro 0813 or MoonshotAI: Kimi K2.5?

Is DeepSeek V4 Pro 0813 or MoonshotAI: Kimi K2.5 cheaper?

The current cheapest TrustedRouter route is $2.7852/1M for DeepSeek V4 Pro 0813 and $2.79575/1M for MoonshotAI: Kimi K2.5. The comparison uses current catalog prices and updates as provider pricing changes.

Is DeepSeek V4 Pro 0813 or MoonshotAI: Kimi K2.5 faster?

Current measured p50 time to first token is 1714 ms for DeepSeek V4 Pro 0813 and 1790 ms for MoonshotAI: Kimi K2.5. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test DeepSeek V4 Pro 0813 and MoonshotAI: Kimi K2.5 with the same API?

Yes. Use the same OpenAI-compatible TrustedRouter base URL and API key, then change only the model id between deepseek/deepseek-v4-pro-0813 and moonshotai/kimi-k2.5. This makes side-by-side evals possible without maintaining two provider integrations.