OpenAI compatible API · Attested · Public status

Z.ai: GLM 5 Turbo vs Z.ai: GLM 5.1

Z.ai: GLM 5.1 has the lower published input-plus-output rate and more Credits provider routes. Their context windows are the same size. There is not enough recent probe data to compare speed. Compare price, speed, context, and privacy.

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.1 has the lower published input-plus-output rate and more Credits provider routes. Their context windows are the same size. There is not enough recent probe data to compare speed.

$5.486/1MZ.ai: GLM 5 Turbo cheapest route

$4.2833/1MZ.ai: GLM 5.1 cheapest route

not enough dataZ.ai: GLM 5 Turbo fastest measured p50 TTFT

1175 msZ.ai: GLM 5.1 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.

Z.ai: GLM 5 TurboZ.ai: GLM 5.1

Model idz-ai/glm-5-turboz-ai/glm-5.1

Publisher Z.AI Z.AI

AI IQ — IQ 113#59

Context202,752 tokens202,752 tokens

Credits provider routes113

Cheapest route$5.486/1M$4.2833/1M

Cached input$0.2532/1M$0.10339/1M to $0.690456/1M

Privacy postureprovider posture varieshas Confidential route (E2EE + ZDR)

Fastest measured p50 TTFTnot enough data1175 ms via friendli

Highest measured throughputnot enough datanot enough data

Recent route uptime rangenot enough data0.00% to 100.00%

Modes chat chat

Z.ai: GLM 5 Turbo routes

Overview1 Credits routes

Z.ai: GLM 5.1 routes

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

Related comparisons

Browse every comparison

Z.ai: GLM 5.1 vs Z.ai: GLM 5.346 combined provider routes
Z.ai: GLM 5.1 vs Z.ai: GLM 5.3 Flash46 combined provider routes
Z.ai: GLM 5.1 vs Z.ai: GLM 5.245 combined provider routes
MoonshotAI: Kimi K3 vs Z.ai: GLM 5.142 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Z.ai: GLM 5.140 combined provider routes
DeepSeek: DeepSeek V4.1 Flash vs Z.ai: GLM 5.137 combined provider routes
OpenAI: gpt-oss-120b vs Z.ai: GLM 5.136 combined provider routes
Qwen: Qwen3.8 27B vs Z.ai: GLM 5.131 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="z-ai/glm-5-turbo",
    messages=messages,
)

Questions

Which should I use, Z.ai: GLM 5 Turbo or Z.ai: GLM 5.1?

Z.ai: GLM 5.1 has the lower published input-plus-output rate and more Credits provider routes. Their context windows are the same size. There is not enough recent probe data to compare speed.

Is Z.ai: GLM 5 Turbo or Z.ai: GLM 5.1 cheaper?

The current cheapest TrustedRouter route is $5.486/1M for Z.ai: GLM 5 Turbo and $4.2833/1M for Z.ai: GLM 5.1. The comparison uses current catalog prices and updates as provider pricing changes.

Is Z.ai: GLM 5 Turbo or Z.ai: GLM 5.1 faster?

Current measured p50 time to first token is not enough data for Z.ai: GLM 5 Turbo and 1175 ms for Z.ai: GLM 5.1. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test Z.ai: GLM 5 Turbo and Z.ai: GLM 5.1 with the same API?

Yes. Use the same OpenAI-compatible TrustedRouter base URL and API key, then change only the model id between z-ai/glm-5-turbo and z-ai/glm-5.1. This makes side-by-side evals possible without maintaining two provider integrations.