OpenAI compatible API · Attested · Public status

Hy4 Preview vs Z.ai: GLM 5.2

Hy4 Preview 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

Z.ai: GLM 5.2 has the lower published input-plus-output rate, more Credits provider routes, the larger context window and the lower measured p50 time to first token.

$3.518425/1MHy4 Preview cheapest route

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

2917 msHy4 Preview fastest measured p50 TTFT via gmi

735 msZ.ai: GLM 5.2 fastest measured p50 TTFT via friendli

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.

Hy4 PreviewZ.ai: GLM 5.2

Model idtencent/hy4-previewz-ai/glm-5.2

Publisher Novita AI Z.AI

AI IQ IQ # IQ 120#28

Context1,000,000 tokens1,048,576 tokens

Credits provider routes228

Cheapest route$3.518425/1M$2.2999/1M

Cached input$0.04431/1M$0.110775/1M to $1.049725/1M

Privacy postureprovider posture varieshas provider E2EE route

Fastest measured p50 TTFT2917 ms via gmi735 ms via friendli

Highest measured throughputnot enough data67 tok/s via deepinfra

Recent route uptime range100.00%50.00% to 100.00%

Modes chat chat

Hy4 Preview routes

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

Z.ai: GLM 5.2 routes

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

Related comparisons

Browse every comparison

Z.ai: GLM 5.2 vs Z.ai: GLM 5.354 combined provider routes
Z.ai: GLM 5.2 vs Z.ai: GLM 5.3 Flash53 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Z.ai: GLM 5.252 combined provider routes
MoonshotAI: Kimi K3 vs Z.ai: GLM 5.252 combined provider routes
OpenAI: gpt-oss-120b vs Z.ai: GLM 5.250 combined provider routes
MoonshotAI: Kimi K2.6 vs Z.ai: GLM 5.247 combined provider routes
DeepSeek: DeepSeek V4 Pro 0423 vs Z.ai: GLM 5.245 combined provider routes
DeepSeek: DeepSeek V4.1 Flash vs Z.ai: GLM 5.244 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="tencent/hy4-preview",
    messages=messages,
)

Questions

Which should I use, Hy4 Preview or Z.ai: GLM 5.2?

Z.ai: GLM 5.2 has the lower published input-plus-output rate, more Credits provider routes, the larger context window and the lower measured p50 time to first token.

Is Hy4 Preview or Z.ai: GLM 5.2 cheaper?

The current cheapest TrustedRouter route is $3.518425/1M for Hy4 Preview and $2.2999/1M for Z.ai: GLM 5.2. The comparison uses current catalog prices and updates as provider pricing changes.

Is Hy4 Preview or Z.ai: GLM 5.2 faster?

Current measured p50 time to first token is 2917 ms for Hy4 Preview and 735 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 Hy4 Preview 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 tencent/hy4-preview and z-ai/glm-5.2. This makes side-by-side evals possible without maintaining two provider integrations.