Free to start

@cf/meta/llama-3.1-8b-instruct-fp8 vs Z.ai: GLM 5.2

Try both on us. Starter credit covers your first requests, then one key routes @cf/meta/llama-3.1-8b-instruct-fp8 and GLM 5.2. 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

@cf/meta/llama-3.1-8b-instruct-fp8 has the lower published input-plus-output rate. Z.ai: GLM 5.2 has more Credits provider routes and the larger context window. There is not enough recent probe data to compare speed.

$0.463145/1M@cf/meta/llama-3.1-8b-instruct-fp8 cheapest route

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

not enough data@cf/meta/llama-3.1-8b-instruct-fp8 fastest measured p50 TTFT

not enough dataZ.ai: GLM 5.2 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.

@cf/meta/llama-3.1-8b-instruct-fp8Z.ai: GLM 5.2

Model idmeta-llama/llama-3.1-8b-instruct-fp8z-ai/glm-5.2

Publisher Meta Z.AI

AI IQ — IQ 118#48

Context32,000 tokens1,048,576 tokens

Credits provider routes132

Cheapest route$0.463145/1M$2.2999/1M

Cached inputNot published$0.131875/1M to $0.84611/1M

Privacy postureprovider posture varieshas Confidential route (E2EE + ZDR)

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

@cf/meta/llama-3.1-8b-instruct-fp8 routes

Overview1 Credits routes

Z.ai: GLM 5.2 routes

Overview32 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.365 combined provider routes
Z.ai: GLM 5.2 vs Z.ai: GLM 5.3 Flash64 combined provider routes
MoonshotAI: Kimi K3 vs Z.ai: GLM 5.260 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Z.ai: GLM 5.258 combined provider routes
DeepSeek: DeepSeek V4.1 Flash vs Z.ai: GLM 5.256 combined provider routes
OpenAI: gpt-oss-120b vs Z.ai: GLM 5.255 combined provider routes
Qwen: Qwen3.8 27B vs Z.ai: GLM 5.251 combined provider routes
MoonshotAI: Kimi K2.6 vs Z.ai: GLM 5.249 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="meta-llama/llama-3.1-8b-instruct-fp8",
    messages=messages,
)

Questions

Which should I use, @cf/meta/llama-3.1-8b-instruct-fp8 or Z.ai: GLM 5.2?

Is @cf/meta/llama-3.1-8b-instruct-fp8 or Z.ai: GLM 5.2 cheaper?

The current cheapest TrustedRouter route is $0.463145/1M for @cf/meta/llama-3.1-8b-instruct-fp8 and $2.2999/1M for Z.ai: GLM 5.2. The comparison uses current catalog prices and updates as provider pricing changes.

Is @cf/meta/llama-3.1-8b-instruct-fp8 or Z.ai: GLM 5.2 faster?

Current measured p50 time to first token is not enough data for @cf/meta/llama-3.1-8b-instruct-fp8 and not enough data 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/meta/llama-3.1-8b-instruct-fp8 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 meta-llama/llama-3.1-8b-instruct-fp8 and z-ai/glm-5.2. This makes side-by-side evals possible without maintaining two provider integrations.