Free to start

OpenAI: gpt-oss-120b vs Ternary Bonsai 27B

Try both on us. Starter credit covers your first requests, then one key routes gpt-oss-120b and Ternary Bonsai 27B. 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

gpt-oss-120b has more Credits provider routes. Ternary Bonsai 27B has the lower published input-plus-output rate and the larger context window. There is not enough recent probe data to compare speed.

$0.211/1MOpenAI: gpt-oss-120b cheapest route

$0.02/1MTernary Bonsai 27B cheapest route

1033 msOpenAI: gpt-oss-120b fastest measured p50 TTFT via cerebras

not enough dataTernary Bonsai 27B 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.

OpenAI: gpt-oss-120bTernary Bonsai 27B

Model idopenai/gpt-oss-120bprism-ml/ternary-bonsai-27b

Publisher OpenAI prism-ml

AI IQ IQ 98#132 —

Context131,072 tokens262,144 tokens

Credits provider routes241

Cheapest route$0.211/1M$0.02/1M

Cached input$0.015825/1M to $0.1055/1MNot published

Privacy posturehas Confidential route (E2EE + ZDR)has ZDR route

Fastest measured p50 TTFT1033 ms via cerebrasnot enough data

Highest measured throughput132 tok/s via amazon-bedrocknot enough data

Recent route uptime range88.31% to 100.00%100.00%

Modes chat chat

OpenAI: gpt-oss-120b routes

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

Ternary Bonsai 27B routes

Overview1 Credits routes

Related comparisons

Browse every comparison

OpenAI: gpt-oss-120b vs Z.ai: GLM 5.357 combined provider routes
OpenAI: gpt-oss-120b vs Z.ai: GLM 5.256 combined provider routes
OpenAI: gpt-oss-120b vs Z.ai: GLM 5.3 Flash56 combined provider routes
MoonshotAI: Kimi K3 vs OpenAI: gpt-oss-120b52 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs OpenAI: gpt-oss-120b50 combined provider routes
DeepSeek: DeepSeek V4.1 Flash vs OpenAI: gpt-oss-120b48 combined provider routes
OpenAI: gpt-oss-120b vs Qwen: Qwen3.8 27B43 combined provider routes
MoonshotAI: Kimi K2.6 vs OpenAI: gpt-oss-120b41 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="openai/gpt-oss-120b",
    messages=messages,
)

Questions

Which should I use, OpenAI: gpt-oss-120b or Ternary Bonsai 27B?

gpt-oss-120b has more Credits provider routes. Ternary Bonsai 27B has the lower published input-plus-output rate and the larger context window. There is not enough recent probe data to compare speed.

Is OpenAI: gpt-oss-120b or Ternary Bonsai 27B cheaper?

The current cheapest TrustedRouter route is $0.211/1M for OpenAI: gpt-oss-120b and $0.02/1M for Ternary Bonsai 27B. The comparison uses current catalog prices and updates as provider pricing changes.

Is OpenAI: gpt-oss-120b or Ternary Bonsai 27B faster?

Current measured p50 time to first token is 1033 ms for OpenAI: gpt-oss-120b and not enough data for Ternary Bonsai 27B. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test OpenAI: gpt-oss-120b and Ternary Bonsai 27B with the same API?

Yes. Use the same OpenAI-compatible TrustedRouter base URL and API key, then change only the model id between openai/gpt-oss-120b and prism-ml/ternary-bonsai-27b. This makes side-by-side evals possible without maintaining two provider integrations.