OpenAI compatible API · Attested · Public status

@cf/nvidia/nemotron-3-120b-a12b vs Z.ai: GLM 5.2

@cf/nvidia/nemotron-3-120b-a12b vs Z.ai: GLM 5.2: 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

@cf/nvidia/nemotron-3-120b-a12b has the lower cheapest prompt+completion route on TrustedRouter. Z.ai: GLM 5.2 has more provider fallback routes, while Z.ai: GLM 5.2 has the larger context window. Probe-backed speed data is shown when enough recent samples exist.

$2.11/1M@cf/nvidia/nemotron-3-120b-a12b cheapest route

$2.2999/1MZ.ai: GLM 5.2 cheapest route

not enough data@cf/nvidia/nemotron-3-120b-a12b fastest measured p50 TTFT

695 msZ.ai: GLM 5.2 fastest measured p50 TTFT via parasail

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.

@cf/nvidia/nemotron-3-120b-a12bZ.ai: GLM 5.2

Model idnvidia/nemotron-3-120b-a12bz-ai/glm-5.2

Publisher Cloudflare Workers AI Z.AI

AI IQ — IQ 120#20

Context256,000 tokens1,048,576 tokens

Provider routes154

Cheapest route$2.11/1M$2.2999/1M

Privacy postureprovider posture varieshas provider E2EE route

Fastest measured p50 TTFTnot enough data695 ms via parasail

Highest measured throughputnot enough datanot enough data

Recent route uptime rangenot enough data66.67% to 100.00%

Modes chat chat

@cf/nvidia/nemotron-3-120b-a12b routes

Overview1 endpoints

Z.ai: GLM 5.2 routes

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

Related comparisons

Browse every comparison

MoonshotAI: Kimi K3 vs Z.ai: GLM 5.291 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Z.ai: GLM 5.289 combined provider routes
OpenAI: gpt-oss-120b vs Z.ai: GLM 5.289 combined provider routes
MoonshotAI: Kimi K2.6 vs Z.ai: GLM 5.286 combined provider routes
DeepSeek: DeepSeek V4 Flash 0423 vs Z.ai: GLM 5.285 combined provider routes
DeepSeek: DeepSeek V4 Pro 0423 vs Z.ai: GLM 5.283 combined provider routes
Google: Gemma 4 31B vs Z.ai: GLM 5.283 combined provider routes
Z.ai: GLM 5.1 vs Z.ai: GLM 5.278 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="nvidia/nemotron-3-120b-a12b",
    messages=messages,
)

Questions

Which should I use, @cf/nvidia/nemotron-3-120b-a12b or Z.ai: GLM 5.2?

Is @cf/nvidia/nemotron-3-120b-a12b or Z.ai: GLM 5.2 cheaper?

The current cheapest TrustedRouter route is $2.11/1M for @cf/nvidia/nemotron-3-120b-a12b and $2.2999/1M for Z.ai: GLM 5.2. The comparison uses current catalog prices and updates as provider pricing changes.

Is @cf/nvidia/nemotron-3-120b-a12b or Z.ai: GLM 5.2 faster?

Current measured p50 time to first token is not enough data for @cf/nvidia/nemotron-3-120b-a12b and 695 ms for Z.ai: GLM 5.2. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test @cf/nvidia/nemotron-3-120b-a12b and Z.ai: GLM 5.2 with the same API?

Yes. Use the same OpenAI-compatible TrustedRouter base URL and API key, then change only the model id between nvidia/nemotron-3-120b-a12b and z-ai/glm-5.2. This makes side-by-side evals possible without maintaining two provider integrations.