Bring your own key

OpenAI: gpt-oss-120b vs sonar

One key routes both. Starter credit covers your first gpt-oss-120b requests, while sonar 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

gpt-oss-120b has more Credits provider routes. A published Credits price comparison is not available for both models. There is not enough recent probe data to compare speed.

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

$2.90125/1Msonar cheapest route

not enough dataOpenAI: gpt-oss-120b fastest measured p50 TTFT

not enough datasonar 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-120bsonar

Model idopenai/gpt-oss-120bperplexity/sonar

Publisher OpenAI Perplexity

AI IQ IQ 98#132 —

Context131,072 tokens0 tokens

Credits provider routes230

Cheapest route$0.211/1M$2.90125/1M

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

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

Fastest measured p50 TTFTnot enough datanot enough data

Highest measured throughputnot enough datanot enough data

Recent route uptime rangenot enough datanot enough data

Modes chat chat

OpenAI: gpt-oss-120b routes

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

sonar routes

Overview0 Credits routes

Related comparisons

Browse every comparison

OpenAI: gpt-oss-120b vs Z.ai: GLM 5.356 combined provider routes
OpenAI: gpt-oss-120b vs Z.ai: GLM 5.255 combined provider routes
OpenAI: gpt-oss-120b vs Z.ai: GLM 5.3 Flash55 combined provider routes
MoonshotAI: Kimi K3 vs OpenAI: gpt-oss-120b51 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs OpenAI: gpt-oss-120b49 combined provider routes
DeepSeek: DeepSeek V4.1 Flash vs OpenAI: gpt-oss-120b47 combined provider routes
OpenAI: gpt-oss-120b vs Qwen: Qwen3.8 27B42 combined provider routes
MoonshotAI: Kimi K2.6 vs OpenAI: gpt-oss-120b40 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-azure.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 sonar?

gpt-oss-120b has more Credits provider routes. A published Credits price comparison is not available for both models. There is not enough recent probe data to compare speed.

Is OpenAI: gpt-oss-120b or sonar cheaper?

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

Is OpenAI: gpt-oss-120b or sonar faster?

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

Can I test OpenAI: gpt-oss-120b and sonar 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 perplexity/sonar. This makes side-by-side evals possible without maintaining two provider integrations.