Compare GLM 5.2 from Z.AI and Grok 4.7 from Grok on key metrics including benchmarks, price, context length, and other model features. Access both models and hundreds of others through the AIHubMix API.
GLM 5.2
Grok 4.7GLM-5.2 is Z.ai’s flagship model for the era of long-horizon tasks. With a truly usable 1M-token context window, it can handle project-level engineering context, execute long-running tasks more reliably, follow engineering standards more consistently, and complete the full development workflow from requirements to multi-platform deployment in a single task.
Grok 4.7 is xAI’s flagship model for coding, agentic tasks, and professional knowledge work. Compared with Grok 4.6, it uses a larger base model and longer reinforcement-learning training, improving long-horizon task execution, self-verification, context management, and document and presentation creation.
Prices are per million tokens. Time to First Token and throughput are rolling averages measured on AIHubMix.
Promotional prices show the discounted rate; see each model page for promotion windows.
Daily traffic served through AIHubMix — how demand for each model is trending.
Measured on real AIHubMix traffic, hourly buckets. Gaps mean no traffic in that hour.
Estimate your monthly bill for the same workload on each model.
Monthly = daily × 30. Discounted rates applied where a promotion is active.
GLM 5.2: $2.524/M output tokens; Grok 4.7: $6.6/M. Use the cost calculator above to estimate your own workload.
GLM 5.2: 0.6s time to first token measured on AIHubMix; see the live performance charts above for how each model behaves across the day.
GLM 5.2 accepts 1,000,000 and Grok 4.7 accepts 500,000 input tokens.
GLM 5.2 at 35.9 tok/s and Grok 4.7 at 15.1 tok/s, measured as output throughput on AIHubMix — a separate metric from time to first token.
GLM 5.2 accepts text input and supports thinking, tool calling, function calling and structured outputs; Grok 4.7 accepts text and image input.
Yes. AIHubMix serves every model on this page behind one OpenAI-compatible endpoint, so switching between them is a one-line change to the model field — no second account, key or SDK.
Related model match-ups readers also look at.