GLM 4.7 vs LLM-jp-3.1 8x13B instruct4
Pricing, context window and real answers (August 2026)
GLM 4.7 (Z.ai) and LLM-jp-3.1 8x13B instruct4 (Llm Jp), 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 | LLM-jp-3.1 8x13B instruct4 | |
|---|---|---|
| Provider | Z.ai | Llm Jp |
| Input (per 1M tokens) | ¥107.22 | ¥16 |
| Output (per 1M tokens) | ¥393.14 | ¥79 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥304 | ¥56 |
| Context window | 202,752 tokens | 4,096 tokens |
| Release date | 12/22/2025 | 3/21/2026 |
| Input modalities | text | text |
| Arena · overall | #79 · ELO 1,442 | Unranked |
| Arena · Japanese | Unranked | Unranked |
| Arena · coding | #87 · 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, LLM-jp-3.1 8x13B instruct4: ¥79 per 1M output tokens, 80% less than GLM 4.7.
- For long documents, GLM 4.7: a 202,752-token context window against 4,096 for LLM-jp-3.1 8x13B instruct4.
- 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
LLM-jp-3.1 8x13B instruct4
To count the number of 'r's in the word 'strawberry', follow these steps:
1. Identify the word: The word we are examining is 'strawberry'.
2. Understand the task: We need to find and count all occurrences of the letter 'r' in this word.
3. Begin with the first letter: The first letter is 's', which is not 'r', so we move on to the next letter.
4. Proceed to the second letter: The second letter is 't', which is also not 'r', so we continue to the third letter.
5. Reach the third letter: The third letter is 'r'. We have found one 'r'.
6. Continue to the fourth letter: The fourth letter is 'a', which is not 'r', so we move on to the fifth letter.
7. Examine the fifth letter: The fifth letter i…
4.0s400 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
LLM-jp-3.1 8x13B instruct4
The error TypeError: Cannot read properties of undefined (reading 'map') suggests that the 'users' argument passed to the UserList component is undefined or does not have a 'map' method.
The cause of the problem may be that the users variable is not being passed correctly or is not defined in the parent component. Check the props being passed to the UserList component to ensure that they are defined and contain the expected data.
To fix the issue, you can add some error handling and debugging to your component. Try logging the users variable to the console to verify that it is not undefined:
```jsx
function UserList({ users }) {
console.log("Users:", users);
if (!users) {
return <…
3.0s279 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
LLM-jp-3.1 8x13B instruct4
The provided Python function aims to get data from a URL using the requests library, filter out specific items based on their "active" field, and return the result. Here are some suggestions to improve readability, performance, and adherence to best practices:
1. Configure the linter (e.g., flake8 or pylint) to ensure code quality and enforce a consistent coding style.
2. Use type hints to improve readability and maintainability.
3. Use context managers (with statement) for handling requests:
4. Rewrite the function using a more functional programming style:
Here's the improved version of the function:
```python
import requests
import time
from typing import List, Dict, Any
def get_da…
3.9s406 output tokens
Frequently asked questions
- Which is cheaper, GLM 4.7 or LLM-jp-3.1 8x13B instruct4?
- Per 1M output tokens, GLM 4.7 is ¥393.14 and LLM-jp-3.1 8x13B instruct4 is ¥79 on FastMetal (yen, before tax), so LLM-jp-3.1 8x13B instruct4 is cheaper.
- How do the context windows of GLM 4.7 and LLM-jp-3.1 8x13B instruct4 compare?
- GLM 4.7 takes 202,752 tokens; LLM-jp-3.1 8x13B instruct4 takes 4,096.
- Can I use GLM 4.7 and LLM-jp-3.1 8x13B instruct4 with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "glm-4.7" or "llm-jp-3.1-8x13b-instruct4" 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 LLM-jp-3.1 8x13B instruct4 from the browser chat and the API. No monthly fee.