Model comparison

GPT-6.1 Sol vs Qwen3.8 27B

Pricing, context window and real answers (September 2026)

GPT-6.1 Sol (OpenAI) 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

openai logoGPT-6.1 Solqwen logoQwen3.8 27B
ProviderOpenAIQwen
Input (per 1M tokens)¥357.4¥33.6
Output (per 1M tokens)¥1,787¥420
Typical cost (1,000 in + 500 out tokens × 1,000 calls)¥1,251¥244
Context window1,050,000 tokens1,000,000 tokens
Release date9/29/20268/14/2026
Input modalitiesfile, image, texttext, image, video
Throughput (p50)—92 tokens/s (n=17)
Arena · overallUnranked#95 · ELO 1,438
Arena · JapaneseUnranked#79 · ELO 1,402
Arena · codingUnranked#65 · ELO 1,504

Prices are FastMetal's yen rates before tax.

Rankings: LMArena leaderboard dataset (lmarena-ai/leaderboard-dataset), CC BY 4.0, snapshot 2026-09-25; category names mapped and ratings rounded by FastMetal.

Which should you pick?

  • On price, Qwen3.8 27B: ¥420 per 1M output tokens, 76% less than GPT-6.1 Sol.
  • For long documents, GPT-6.1 Sol: a 1,050,000-token context window against 1,000,000 for Qwen3.8 27B.
  • 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.

GPT-6.1 Sol

“strawberry” is spelled **s-t-r-a-w-b-e-r-r-y**. The letter **r** appears at positions **3, 8, and 9**. So, there are **3 r’s** in “strawberry.”
2.8s88 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…

GPT-6.1 Sol

The error means **`users` is `undefined` when `UserList` renders**. Calling `.map()` on `undefined` throws this error. This commonly happens when the parent doesn’t pass the `users` prop, or when data hasn’t finished loading yet. ### Fix: provide a default empty array ```jsx function UserList({ users = [] }) { return ( <ul> {users.map(user => ( <li key={user.id}>{user.name}</li> ))} </ul> ); } ``` This renders an empty list if `users` is omitted or `undefined`. It does **not** handle `null`. ### Check the parent component too Make sure it passes an array: ```jsx <UserList users={users} /> ``` If you’re fetching users asynchronously, initialize the stat…
5.8s306 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):…

GPT-6.1 Sol

The function is short, but its main weakness is that it hides failures: a network error, invalid JSON, and a genuinely empty result all return `[]`. ### Suggested improvements - **Move imports to module scope.** This is conventional and makes dependencies visible. Repeated imports are cached, so the performance benefit is minor. - **Avoid bare `except:`.** It catches everything, including `KeyboardInterrupt` and `SystemExit`, and can hide programming errors. - **Handle HTTP errors explicitly.** `raise_for_status()` provides useful exceptions. Retry transient failures such as timeouts, connection errors, HTTP 429, and HTTP 5xx—not permanent errors such as HTTP 404. - **Don’t sleep after the…
19.0s1094 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

Compare on more prompts →

Frequently asked questions

Which is cheaper, GPT-6.1 Sol or Qwen3.8 27B?
Per 1M output tokens, GPT-6.1 Sol is ¥1,787 and Qwen3.8 27B is ¥420 on FastMetal (yen, before tax), so Qwen3.8 27B is cheaper.
How do the context windows of GPT-6.1 Sol and Qwen3.8 27B compare?
GPT-6.1 Sol takes 1,050,000 tokens; Qwen3.8 27B takes 1,000,000.
Can I use GPT-6.1 Sol and Qwen3.8 27B with the same API key?
Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "gpt-6.1-sol" 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 GPT-6.1 Sol and Qwen3.8 27B from the browser chat and the API. No monthly fee.

More comparisons with GPT-6.1 Sol

More comparisons with Qwen3.8 27B