OpenAI compatible API · Attested · Public status

mistral-medium-3.5-128b vs Z.ai: GLM 5.3

mistral-medium-3.5-128b vs Z.ai: GLM 5.3: 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.3 has the lower published input-plus-output rate and more Credits provider routes. There is not enough recent probe data to compare speed.

$11.425335/1Mmistral-medium-3.5-128b cheapest route

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

not enough datamistral-medium-3.5-128b fastest measured p50 TTFT

1083 msZ.ai: GLM 5.3 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.

mistral-medium-3.5-128bZ.ai: GLM 5.3

Model idmistralai/mistral-medium-3.5-128bz-ai/glm-5.3

Publisher Mistral Z.AI

AI IQ — IQ 123#17

Context0 tokens1,048,576 tokens

Credits provider routes126

Cheapest route$11.425335/1M$4.2833/1M

Cached inputNot published$0.1477/1M to $1.02546/1M

Privacy postureprovider posture varieshas provider E2EE route

Fastest measured p50 TTFTnot enough data1083 ms via friendli

Highest measured throughputnot enough datanot enough data

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

Modes chat chat

mistral-medium-3.5-128b routes

Overview1 Credits routes

Z.ai: GLM 5.3 routes

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

Related comparisons

Browse every comparison

Z.ai: GLM 5.2 vs Z.ai: GLM 5.354 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Z.ai: GLM 5.351 combined provider routes
Z.ai: GLM 5.3 vs Z.ai: GLM 5.3 Flash51 combined provider routes
MoonshotAI: Kimi K3 vs Z.ai: GLM 5.350 combined provider routes
OpenAI: gpt-oss-120b vs Z.ai: GLM 5.348 combined provider routes
MoonshotAI: Kimi K2.6 vs Z.ai: GLM 5.345 combined provider routes
DeepSeek: DeepSeek V4 Pro 0423 vs Z.ai: GLM 5.343 combined provider routes
DeepSeek: DeepSeek V4 Flash 0423 vs Z.ai: GLM 5.342 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="mistralai/mistral-medium-3.5-128b",
    messages=messages,
)

Questions

Which should I use, mistral-medium-3.5-128b or Z.ai: GLM 5.3?

Z.ai: GLM 5.3 has the lower published input-plus-output rate and more Credits provider routes. There is not enough recent probe data to compare speed.

Is mistral-medium-3.5-128b or Z.ai: GLM 5.3 cheaper?

The current cheapest TrustedRouter route is $11.425335/1M for mistral-medium-3.5-128b and $4.2833/1M for Z.ai: GLM 5.3. The comparison uses current catalog prices and updates as provider pricing changes.

Is mistral-medium-3.5-128b or Z.ai: GLM 5.3 faster?

Current measured p50 time to first token is not enough data for mistral-medium-3.5-128b and 1083 ms for Z.ai: GLM 5.3. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test mistral-medium-3.5-128b and Z.ai: GLM 5.3 with the same API?

Yes. Use the same OpenAI-compatible TrustedRouter base URL and API key, then change only the model id between mistralai/mistral-medium-3.5-128b and z-ai/glm-5.3. This makes side-by-side evals possible without maintaining two provider integrations.