Grok 4.7 vs Qwen3.8 27B
Pricing, context window and real answers (September 2026)
Grok 4.7 (xAI) and Qwen3.8 27B (Qwen), 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
 Grok 4.7 |  Qwen3.8 27B | |
|---|---|---|
| Provider | xAI | Qwen |
| Input (per 1M tokens) | ¥276.2 | ¥80.41 |
| Output (per 1M tokens) | ¥828.6 | ¥571.84 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥691 | ¥366 |
| Context window | 500,000 tokens | 1,000,000 tokens |
| Release date | 9/21/2026 | 8/14/2026 |
| Input modalities | text, image, file | text, image, video |
| Throughput (p50) | — | — |
| Arena · overall | Unranked | #90 · ELO 1,437 |
| Arena · Japanese | Unranked | #91 · ELO 1,383 |
| Arena · coding | Unranked | #67 · ELO 1,499 |
Prices are FastMetal's yen rates before tax. Arena ranks are as of the latest leaderboard scrape.
Which should you pick?
- On price, Qwen3.8 27B: ¥571.84 per 1M output tokens, 31% less than Grok 4.7.
- For long documents, Qwen3.8 27B: a 1,000,000-token context window against 500,000 for Grok 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.
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
Qwen3.8 27B
The word is: **strawberry**
Break it into letters:
1. s
2. t
3. r
4. a
5. w
6. b
7. e
8. r
9. r
10. y
Now count the **r**’s:
- 3rd letter: **r**
- 8th letter: **r**
- 9th letter: **r**
So, there are **3** r’s in **strawberry**.
3.6s239 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…
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
Qwen3.8 27B
The error means that `users` is `undefined` when `UserList` renders:
```jsx
{users.map(...)}
```
JavaScript cannot call `.map()` on `undefined`.
For example, this would cause the error:
```jsx
<UserList />
```
because `users` is not being passed in.
## Simple fix: give `users` a default value
```jsx
function UserList({ users = [] }) {
return (
<ul>
{users.map(user => <li key={user.id}>{user.name}</li>)}
</ul>
);
}
```
Now if `users` is not passed in, it defaults to an empty array.
## Better fix: make sure the parent passes an array
Wherever you use `UserList`, pass `users`:
```jsx
<UserList users={users} />
```
If `users` comes from an API or state, make sure it…
9.5s601 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):…
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
Qwen3.8 27B
The function works at a basic level, but it has several readability, reliability, and best-practice issues.
## Main issues
1. **Imports inside the function**
```python
import requests
import time
```
Imports should normally be at the top of the module unless there is a specific reason to lazy-load them.
2. **Bare `except` is too broad**
```python
except:
time.sleep(2)
```
This catches almost everything, including `KeyboardInterrupt`, `SystemExit`, `KeyError`, `TypeError`, and other programming errors. It makes debugging harder and can retry failures that should not be retried.
3. **It retries on every non-`200` status**
Retrying `401 Unauthorized`, `4…
205.9s13103 output tokens
Frequently asked questions
- Which is cheaper, Grok 4.7 or Qwen3.8 27B?
- Per 1M output tokens, Grok 4.7 is ¥828.6 and Qwen3.8 27B is ¥571.84 on FastMetal (yen, before tax), so Qwen3.8 27B is cheaper.
- How do the context windows of Grok 4.7 and Qwen3.8 27B compare?
- Grok 4.7 takes 500,000 tokens; Qwen3.8 27B takes 1,000,000.
- Can I use Grok 4.7 and Qwen3.8 27B with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "grok-4.7" or "qwen3.8-27b" 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 Grok 4.7 and Qwen3.8 27B from the browser chat and the API. No monthly fee.