OpenAI compatible API · Attested · Public status

OpenAI: gpt-oss-120b vs Inkling

gpt-oss-120b vs Inkling: 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

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

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

$5.32775/1MInkling cheapest route

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

not enough dataInkling 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-120bInkling

Model idopenai/gpt-oss-120bthinkingmachines/inkling-1m

Publisher OpenAI Baseten

AI IQ IQ 97#116 —

Context131,072 tokens1,048,576 tokens

Credits provider routes221

Cheapest route$0.211/1M$5.32775/1M

Cached input$0.015825/1M to $0.1055/1M$0.17935/1M

Privacy posturehas provider E2EE routehas ZDR route

Fastest measured p50 TTFT1005 ms via cerebrasnot enough data

Highest measured throughputnot enough datanot enough data

Recent route uptime range66.67% to 100.00%100.00%

Modes chat chat

OpenAI: gpt-oss-120b routes

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

Inkling routes

Overview1 Credits routes

Related comparisons

Browse every comparison

OpenAI: gpt-oss-120b vs Z.ai: GLM 5.250 combined provider routes
OpenAI: gpt-oss-120b vs Z.ai: GLM 5.348 combined provider routes
OpenAI: gpt-oss-120b vs Z.ai: GLM 5.3 Flash47 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs OpenAI: gpt-oss-120b46 combined provider routes
MoonshotAI: Kimi K3 vs OpenAI: gpt-oss-120b46 combined provider routes
MoonshotAI: Kimi K2.6 vs OpenAI: gpt-oss-120b41 combined provider routes
DeepSeek: DeepSeek V4.1 Flash vs OpenAI: gpt-oss-120b40 combined provider routes
DeepSeek: DeepSeek V4 Pro 0423 vs OpenAI: gpt-oss-120b39 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 Inkling?

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

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

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

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

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

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