Bring your own key

MoonshotAI: Kimi K2.6 vs Tencent: Hy3 preview

One key routes both. Starter credit covers your first Kimi K2.6 requests, while Hy3 preview runs on your own provider key. 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.6 has more Credits provider routes. A published Credits price comparison is not available for both models. Their context windows are the same size. There is not enough recent probe data to compare speed.

$2.31045/1MMoonshotAI: Kimi K2.6 cheapest route

$0.8229/1MTencent: Hy3 preview cheapest route

1056 msMoonshotAI: Kimi K2.6 fastest measured p50 TTFT via telnyx

not enough dataTencent: Hy3 preview 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.6Tencent: Hy3 preview

Model idmoonshotai/kimi-k2.6tencent/hy3-preview

Publisher Kimi Tencent Cloud TokenHub

AI IQ IQ 114#62 IQ 99#133

Context262,144 tokens262,144 tokens

Credits provider routes170

Cheapest route$2.31045/1M$0.8229/1M

Cached input$0.041145/1M to $0.420154/1MNot published

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

Fastest measured p50 TTFT1056 ms via telnyxnot enough data

Highest measured throughputnot enough datanot enough data

Recent route uptime range100.00%not enough data

Modes chat chat

MoonshotAI: Kimi K2.6 routes

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

Tencent: Hy3 preview routes

Overview0 Credits routes
BenchmarksTrustedRouter and external sources

Related comparisons

Browse every comparison

MoonshotAI: Kimi K2.6 vs Z.ai: GLM 5.250 combined provider routes
MoonshotAI: Kimi K2.6 vs Z.ai: GLM 5.350 combined provider routes
MoonshotAI: Kimi K2.6 vs Z.ai: GLM 5.3 Flash49 combined provider routes
MoonshotAI: Kimi K2.6 vs MoonshotAI: Kimi K345 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs MoonshotAI: Kimi K2.643 combined provider routes
DeepSeek: DeepSeek V4.1 Flash vs MoonshotAI: Kimi K2.641 combined provider routes
MoonshotAI: Kimi K2.6 vs OpenAI: gpt-oss-120b40 combined provider routes
MoonshotAI: Kimi K2.6 vs Qwen: Qwen3.8 27B39 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="moonshotai/kimi-k2.6",
    messages=messages,
)

Questions

Which should I use, MoonshotAI: Kimi K2.6 or Tencent: Hy3 preview?

Is MoonshotAI: Kimi K2.6 or Tencent: Hy3 preview cheaper?

The current cheapest TrustedRouter route is $2.31045/1M for MoonshotAI: Kimi K2.6 and $0.8229/1M for Tencent: Hy3 preview. The comparison uses current catalog prices and updates as provider pricing changes.

Is MoonshotAI: Kimi K2.6 or Tencent: Hy3 preview faster?

Current measured p50 time to first token is 1056 ms for MoonshotAI: Kimi K2.6 and not enough data for Tencent: Hy3 preview. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test MoonshotAI: Kimi K2.6 and Tencent: Hy3 preview 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.6 and tencent/hy3-preview. This makes side-by-side evals possible without maintaining two provider integrations.