Gemini 3.1 Pro Preview vs Qwen3.7 Max
Pricing, context window and real answers (September 2026)
Gemini 3.1 Pro Preview (Google) and Qwen3.7 Max (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
 Gemini 3.1 Pro Preview |  Qwen3.7 Max | |
|---|---|---|
| Provider | Qwen | |
| Input (per 1M tokens) | ¥357.4 | ¥263.58 |
| Output (per 1M tokens) | ¥2,144.4 | ¥790.75 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥1,430 | ¥659 |
| Context window | 1,048,576 tokens | 1,000,000 tokens |
| Release date | 2/19/2026 | 5/21/2026 |
| Input modalities | audio, file, image, text, video | text |
| Throughput (p50) | — | — |
| Arena · overall | #15 · ELO 1,487 | #34 · ELO 1,473 |
| Arena · Japanese | #9 · ELO 1,494 | Unranked |
| Arena · coding | #28 · ELO 1,520 | #21 · ELO 1,525 |
Prices are FastMetal's yen rates before tax. Arena ranks are as of the latest leaderboard scrape.
Which should you pick?
- On price, Qwen3.7 Max: ¥790.75 per 1M output tokens, 63% less than Gemini 3.1 Pro Preview.
- On the Overall arena board, Gemini 3.1 Pro Preview ranks higher (#15; Qwen3.7 Max is #34).
- On the Coding arena board, Qwen3.7 Max ranks higher (#21; Gemini 3.1 Pro Preview is #28).
- For long documents, Gemini 3.1 Pro Preview: a 1,048,576-token context window against 1,000,000 for Qwen3.7 Max.
- 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.
Gemini 3.1 Pro Preview
There are **3** 'r's in the word 'strawberry'.
Here is the step-by-step breakdown of the spelling:
1. **s** - not an 'r'
2. **t** - not an 'r'
3. **r** - **1st 'r'**
4. **a** - not an 'r'
5. **w** - not an 'r'
6. **b** - not an 'r'
7. **e** - not an 'r'
8. **r** - **2nd 'r'**
9. **r** - **3rd 'r'**
10. **y** - not an 'r'
Therefore, the total count is 3.
5.3s503 output tokens
Qwen3.7 Max
To count the number of 'r's in the word "strawberry", let's break the word down letter by letter from left to right:
1. **s** - not an 'r'
2. **t** - not an 'r'
3. **r** - This is the **1st** 'r'
4. **a** - not an 'r'
5. **w** - not an 'r'
6. **b** - not an 'r'
7. **e** - not an 'r'
8. **r** - This is the **2nd** 'r'
9. **r** - This is the **3rd** 'r'
10. **y** - not an 'r'
By examining each character individually, we can see that the letter 'r' appears in the 3rd, 8th, and 9th positions.
Therefore, there are **3** 'r's in "strawberry".
15.1s842 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…
Gemini 3.1 Pro Preview
### The Cause
This error occurs because the `users` prop being passed to your `UserList` component is currently `undefined`.
In JavaScript, you can only use the `.map()` method on arrays. Because `users` is `undefined` (often due to data not finishing an API fetch yet, or the parent component forgetting to pass the prop), Node/React throws an error when it tries to read `.map`.
### How to Fix It
You can fix this in a few different ways, depending on how you want your application to behave.
#### Fix 1: Assign a Default Value (Recommended)
The cleanest way to handle this is to assign a default empty array to `users` in your component's parameters. If `users` is undefined, it defaults to…
13.2s1511 output tokens
Qwen3.7 Max
This error occurs because the `users` prop being passed to your `UserList` component is **`undefined`** at the time React tries to render it. JavaScript cannot call the `.map()` method on `undefined`, which throws the error.
This usually happens for one of three reasons:
1. **Asynchronous Data Fetching:** The parent component is fetching `users` from an API. On the *initial render*, the data hasn't arrived yet, so the variable is `undefined`.
2. **Missing Prop:** The parent component forgot to pass the `users` prop (e.g., `<UserList />` instead of `<UserList users={myUsers} />`).
3. **Incorrect State Initialization:** The parent component initialized its state as `undefined` or `null` inste…
34.9s1851 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):…
Gemini 3.1 Pro Preview
Here is a review of your function. While the original code works, there are several areas where it can be improved regarding **best practices**, **readability**, and **performance**.
### 1. Refactored Code
Here is the improved version of your function. I will explain the specific changes below.
```python
import time
import requests
import logging
from typing import Any
# Optional: Set up a logger
logger = logging.getLogger(__name__)
def get_data(url: str, retries: int = 3, delay: int = 2, timeout: int = 10) -> list[dict[str, Any]]:
"""
Fetches JSON data from a URL and extracts active items.
Args:
url: The API endpoint to fetch data from.
retries: Number o…
23.6s3094 output tokens
Qwen3.7 Max
Here is a comprehensive review of your function, broken down by readability, performance, and best practices, followed by a refactored version.
### 1. Readability & Style (PEP 8)
* **Imports inside the function:** Imports should generally be placed at the top of the file, not inside the function. This makes dependencies clear and avoids slight overhead on every function call.
* **`item["active"] == True`:** In Python, explicitly comparing to `True` is discouraged (PEP 8). You should just use `if item.get("active"):`. Using `.get()` also prevents `KeyError` if the key is missing.
* **Manual List Building:** The `for` loop with `.append()` can be replaced with a much cleaner and faster **list…
58.3s3301 output tokens
Frequently asked questions
- Which is cheaper, Gemini 3.1 Pro Preview or Qwen3.7 Max?
- Per 1M output tokens, Gemini 3.1 Pro Preview is ¥2,144.4 and Qwen3.7 Max is ¥790.75 on FastMetal (yen, before tax), so Qwen3.7 Max is cheaper.
- How do the context windows of Gemini 3.1 Pro Preview and Qwen3.7 Max compare?
- Gemini 3.1 Pro Preview takes 1,048,576 tokens; Qwen3.7 Max takes 1,000,000.
- Which ranks higher, Gemini 3.1 Pro Preview or Qwen3.7 Max?
- Gemini 3.1 Pro Preview ranks higher on the public arena (Gemini 3.1 Pro Preview #9, Qwen3.7 Max #34). Ranks move as the leaderboard updates.
- Can I use Gemini 3.1 Pro Preview and Qwen3.7 Max with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "gemini-3.1-pro-preview" or "qwen3.7-max" 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 Gemini 3.1 Pro Preview and Qwen3.7 Max from the browser chat and the API. No monthly fee.