ByteDance: UI-TARS 7B vs Z.ai: GLM 5.2
ByteDance: UI-TARS 7B 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. Compare price, speed, context, and privacy.
Practical read
Monthly evidenceByteDance: UI-TARS 7B 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.
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.
bytedance/ui-tars-1.5-7bz-ai/glm-5.2
ByteDance: UI-TARS 7B 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.3 Flash66 combined provider routes
- Z.ai: GLM 5.2 vs Z.ai: GLM 5.365 combined provider routes
- MoonshotAI: Kimi K3 vs Z.ai: GLM 5.261 combined provider routes
- DeepSeek: DeepSeek V4 Flash 0731 vs Z.ai: GLM 5.259 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.250 combined provider routes
- Google: Gemma 4 31B vs Z.ai: GLM 5.249 combined provider routes
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.
client = OpenAI(
base_url="https://api.trustedrouter.com/v1",
api_key="sk-tr-v1-..."
)
response = client.chat.completions.create(
model="bytedance/ui-tars-1.5-7b",
messages=messages,
)Questions
Which should I use, ByteDance: UI-TARS 7B or Z.ai: GLM 5.2?
ByteDance: UI-TARS 7B 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.
Is ByteDance: UI-TARS 7B or Z.ai: GLM 5.2 cheaper?
The current cheapest TrustedRouter route is $0.3165/1M for ByteDance: UI-TARS 7B and $2.2999/1M for Z.ai: GLM 5.2. The comparison uses current catalog prices and updates as provider pricing changes.
Is ByteDance: UI-TARS 7B or Z.ai: GLM 5.2 faster?
Current measured p50 time to first token is not enough data for ByteDance: UI-TARS 7B and 917 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 ByteDance: UI-TARS 7B 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 bytedance/ui-tars-1.5-7b and z-ai/glm-5.2. This makes side-by-side evals possible without maintaining two provider integrations.