OpenAI compatible API · Attested · Public status

MoonshotAI: Kimi K2.7 Code vs Tencent: Hunyuan A13B Instruct

MoonshotAI: Kimi K2.7 Code vs Tencent: Hunyuan A13B Instruct: 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

Tencent: Hunyuan A13B Instruct has the lower cheapest prompt+completion route on TrustedRouter. MoonshotAI: Kimi K2.7 Code has more provider fallback routes, while MoonshotAI: Kimi K2.7 Code has the larger context window. Probe-backed speed data is shown when enough recent samples exist.

$4.2735/1MMoonshotAI: Kimi K2.7 Code cheapest route

$0.7455/1MTencent: Hunyuan A13B Instruct cheapest route

1200 msMoonshotAI: Kimi K2.7 Code fastest measured p50 TTFT via parasail

not enough dataTencent: Hunyuan A13B Instruct fastest measured p50 TTFT

MoonshotAI: Kimi K2.7 CodeTencent: Hunyuan A13B Instruct

Model idmoonshotai/kimi-k2.7-codetencent/hunyuan-a13b-instruct

Publisher Kimi SiliconFlow

AI IQ IQ 118#22 —

Context262,144 tokens131,072 tokens

Provider routes192

Cheapest route$4.2735/1M$0.7455/1M

Privacy posturehas ZDR routeprovider posture varies

Fastest measured p50 TTFT1200 ms via parasailnot enough data

Highest measured throughputnot enough datanot enough data

Recent route uptime range100.00%not enough data

Modes chat chat

MoonshotAI: Kimi K2.7 Code routes

Overview19 endpoints
PricingPrompt and completion rates
BenchmarksTrustedRouter and external sources
ProvidersAll serving providers

Tencent: Hunyuan A13B Instruct routes

Overview2 endpoints
PricingPrompt and completion rates
ProvidersAll serving providers

Related comparisons

Browse every comparison

MoonshotAI: Kimi K2.7 Code vs Z.ai: GLM 5.266 combined provider routes
MoonshotAI: Kimi K2.7 Code vs MoonshotAI: Kimi K352 combined provider routes
MoonshotAI: Kimi K2.6 vs MoonshotAI: Kimi K2.7 Code49 combined provider routes
DeepSeek: DeepSeek V4 Flash 0423 vs MoonshotAI: Kimi K2.7 Code48 combined provider routes
DeepSeek: DeepSeek V4 Pro vs MoonshotAI: Kimi K2.7 Code46 combined provider routes
MoonshotAI: Kimi K2.7 Code vs OpenAI: gpt-oss-120b45 combined provider routes
Google: Gemma 4 31B vs MoonshotAI: Kimi K2.7 Code43 combined provider routes
MoonshotAI: Kimi K2.7 Code vs Z.ai: GLM 5.143 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.7-code",
    messages=messages,
)

Questions

Which should I use, MoonshotAI: Kimi K2.7 Code or Tencent: Hunyuan A13B Instruct?

Is MoonshotAI: Kimi K2.7 Code or Tencent: Hunyuan A13B Instruct cheaper?

The current cheapest TrustedRouter route is $4.2735/1M for MoonshotAI: Kimi K2.7 Code and $0.7455/1M for Tencent: Hunyuan A13B Instruct. The comparison uses current catalog prices and updates as provider pricing changes.

Is MoonshotAI: Kimi K2.7 Code or Tencent: Hunyuan A13B Instruct faster?

Current measured p50 time to first token is 1200 ms for MoonshotAI: Kimi K2.7 Code and not enough data for Tencent: Hunyuan A13B Instruct. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test MoonshotAI: Kimi K2.7 Code and Tencent: Hunyuan A13B Instruct 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.7-code and tencent/hunyuan-a13b-instruct. This makes side-by-side evals possible without maintaining two provider integrations.