OpenAI compatible API · Attested · Public status

OpenAI GPT OSS vs MoonshotAI: Kimi K2.7 Code

OpenAI GPT OSS vs MoonshotAI: Kimi K2.7 Code: 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

OpenAI GPT OSS 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. Current TrustedRouter probes show OpenAI GPT OSS with the lower p50 TTFT.

$1.1605/1MOpenAI GPT OSS cheapest route

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

1311 msOpenAI GPT OSS fastest measured p50 TTFT via cerebras

1632 msMoonshotAI: Kimi K2.7 Code fastest measured p50 TTFT via inceptron

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.

OpenAI GPT OSSMoonshotAI: Kimi K2.7 Code

Model idcerebras/gpt-oss-120bmoonshotai/kimi-k2.7-code

Publisher Cerebras Kimi

AI IQ IQ 98#99 IQ 108#66

Context131,072 tokens262,144 tokens

Credits provider routes113

Cheapest route$1.1605/1M$4.29385/1M

Cached inputNot published$0.15825/1M to $0.56548/1M

Privacy posturehas ZDR routehas ZDR route

Fastest measured p50 TTFT1311 ms via cerebras1632 ms via inceptron

Highest measured throughputnot enough datanot enough data

Recent route uptime range100.00%100.00%

Modes chat chat

OpenAI GPT OSS routes

Overview1 Credits routes

MoonshotAI: Kimi K2.7 Code routes

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

Related comparisons

Browse every comparison

MoonshotAI: Kimi K2.7 Code vs Z.ai: GLM 5.241 combined provider routes
MoonshotAI: Kimi K2.7 Code vs Z.ai: GLM 5.340 combined provider routes
MoonshotAI: Kimi K2.7 Code vs Z.ai: GLM 5.3 Flash38 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs MoonshotAI: Kimi K2.7 Code37 combined provider routes
MoonshotAI: Kimi K2.7 Code vs MoonshotAI: Kimi K337 combined provider routes
MoonshotAI: Kimi K2.7 Code vs OpenAI: gpt-oss-120b35 combined provider routes
MoonshotAI: Kimi K2.6 vs MoonshotAI: Kimi K2.7 Code33 combined provider routes
DeepSeek: DeepSeek V4 Flash 0423 vs MoonshotAI: Kimi K2.7 Code29 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="cerebras/gpt-oss-120b",
    messages=messages,
)

Questions

Which should I use, OpenAI GPT OSS or MoonshotAI: Kimi K2.7 Code?

Is OpenAI GPT OSS or MoonshotAI: Kimi K2.7 Code cheaper?

The current cheapest TrustedRouter route is $1.1605/1M for OpenAI GPT OSS and $4.29385/1M for MoonshotAI: Kimi K2.7 Code. The comparison uses current catalog prices and updates as provider pricing changes.

Is OpenAI GPT OSS or MoonshotAI: Kimi K2.7 Code faster?

Current measured p50 time to first token is 1311 ms for OpenAI GPT OSS and 1632 ms for MoonshotAI: Kimi K2.7 Code. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test OpenAI GPT OSS and MoonshotAI: Kimi K2.7 Code with the same API?

Yes. Use the same OpenAI-compatible TrustedRouter base URL and API key, then change only the model id between cerebras/gpt-oss-120b and moonshotai/kimi-k2.7-code. This makes side-by-side evals possible without maintaining two provider integrations.