GLM 4.7 vs Grok 4.7
Pricing, context window and real answers (September 2026)
GLM 4.7 (Z.ai) and Grok 4.7 (xAI), compared as you can actually call them on FastMetal. Both are served from the same OpenAI-compatible endpoint and API key; switching is a change to the model string.
Specs and pricing
 GLM 4.7 |  Grok 4.7 | |
|---|---|---|
| Provider | Z.ai | xAI |
| Input (per 1M tokens) | ¥107.22 | ¥276.2 |
| Output (per 1M tokens) | ¥393.14 | ¥828.6 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥304 | ¥691 |
| Context window | 202,752 tokens | 500,000 tokens |
| Release date | 12/22/2025 | 9/21/2026 |
| Input modalities | text | text, image, file |
| Throughput (p50) | — | — |
| Arena · overall | #83 · ELO 1,442 | Unranked |
| Arena · Japanese | Unranked | Unranked |
| Arena · coding | #91 · ELO 1,485 | Unranked |
Prices are FastMetal's yen rates before tax. Arena ranks are as of the latest leaderboard scrape.
Which should you pick?
- On price, GLM 4.7: ¥393.14 per 1M output tokens, 53% less than Grok 4.7.
- For long documents, Grok 4.7: a 500,000-token context window against 202,752 for GLM 4.7.
- If in doubt, try both on the same key. Switching is a change to the model string, and each is billed at its own rate.
Real answers to the same prompts
Exactly what the FastMetal gateway returned, side by side. Not benchmark scores: actual output.
Count the number of 'r's in 'strawberry'
Count the number of 'r's in 'strawberry'. Explain your reasoning step by step.
GLM 4.7
There are **3** "r"s in "strawberry".
Here is the step-by-step reasoning:
1. **Break down the word into individual letters:**
s - t - r - a - w - b - e - r - r - y
2. **Identify the position of each 'r':**
* The 3rd letter is **r**.
* The 8th letter is **r**.
* The 9th letter is **r**.
3. **Count the total occurrences:**
1 + 1 + 1 = 3.
23.3s685 output tokens
Grok 4.7
The word "strawberry" consists of the letters S-T-R-A-W-B-E-R-R-Y.
- The 3rd letter is R.
- The 8th letter is R.
- The 9th letter is R.
This gives a total of 3 R's.
4.7s299 output tokens
Debug This Error
I'm getting the following error in my Node.js application: TypeError: Cannot read properties of undefined (reading 'map') at UserList (/app/components/UserList.js:12:25) at renderWithHooks (/app/node_modules/rea…
GLM 4.7
### The Cause
The error `TypeError: Cannot read properties of undefined (reading 'map')` means that the variable `users` is `undefined` when the component tries to render.
In React, this typically happens for one of two reasons:
1. The **Parent Component** is not passing the `users` prop to `UserList`.
2. The **Parent Component** passed the prop, but the data hasn't loaded yet (e.g., an API call is still pending), so the value is initially `undefined`.
Since `undefined` does not have a `.map()` method, the application crashes.
---
### How to Fix It
There are two main ways to fix this: handling it inside the `UserList` component (defensive coding) or fixing the parent component passing…
42.0s1384 output tokens
Grok 4.7
The error happens because `users` is `undefined` when `UserList` renders, so calling `.map` on it fails.
That usually means the parent rendered `<UserList />` (or `<UserList users={undefined} />`) before data was loaded, or the prop name doesn’t match.
**Fix it in the component** so it tolerates a missing list:
```jsx
function UserList({ users = [] }) {
return (
<ul>
{users.map(user => <li key={user.id}>{user.name}</li>)}
</ul>
);
}
```
Or guard the call:
```jsx
function UserList({ users }) {
return (
<ul>
{(users ?? []).map(user => <li key={user.id}>{user.name}</li>)}
</ul>
);
}
```
**Also check the parent** so you pass an array once data exists:
`…
12.8s393 output tokens
Code Review
Please review the following Python function and suggest improvements for readability, performance, and best practices: def get_data(url, retries=3): import requests import time for i in range(retries):…
GLM 4.7
Here is a review of your function with suggestions for improving readability, performance, and best practices, followed by a refactored version of the code.
### Code Review
1. **Import Placement:** You import `requests` and `time` inside the function. Imports should generally be placed at the top of the file so they are loaded once when the module starts, rather than every time the function is called.
2. **Bare `except:`:** You used `except:` without specifying an exception type. This is dangerous because it catches *everything*, including `KeyboardInterrupt` (Ctrl+C) and `SystemExit`, preventing your program from terminating when needed. You should specifically catch `requests.exception…
24.5s2951 output tokens
Grok 4.7
## Review
The function works for the happy path, but it hides failures, retries the wrong errors, and is harder to read and debug than it needs to be.
### Issues
1. **Imports inside the function** — move them to module level unless you have a strong reason (circular imports, optional dependency).
2. **Bare `except`** — swallows `KeyboardInterrupt`, `SystemExit`, and programming bugs. Catch specific exceptions.
3. **Retries non-retryable failures** — 4xx (except maybe 429) will not succeed on retry. Network errors and 5xx are the usual candidates.
4. **Sleeps after the last attempt** — wastes up to 2 seconds before returning `[]`.
5. **Unused loop variable** and vague names (`r`, `i`).
6.…
22.3s1525 output tokens
Frequently asked questions
- Which is cheaper, GLM 4.7 or Grok 4.7?
- Per 1M output tokens, GLM 4.7 is ¥393.14 and Grok 4.7 is ¥828.6 on FastMetal (yen, before tax), so GLM 4.7 is cheaper.
- How do the context windows of GLM 4.7 and Grok 4.7 compare?
- GLM 4.7 takes 202,752 tokens; Grok 4.7 takes 500,000.
- Can I use GLM 4.7 and Grok 4.7 with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "glm-4.7" or "grok-4.7" as the model. Each is billed at its own rate from the same prepaid balance.
Try both on one API key
Create an account and add credit to call GLM 4.7 and Grok 4.7 from the browser chat and the API. No monthly fee.