Model comparison

GPT-6.1 Sol vs gpt-oss-20b

Pricing, context window and real answers (September 2026)

GPT-6.1 Sol (OpenAI) and gpt-oss-20b (OpenAI), 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 Solopenai logogpt-oss-20b
ProviderOpenAIOpenAI
Input (per 1M tokens)¥357.4¥5.04
Output (per 1M tokens)¥1,787¥23.52
Typical cost (1,000 in + 500 out tokens × 1,000 calls)¥1,251¥17
Context window1,050,000 tokens131,072 tokens
Release date9/29/20268/5/2025
Input modalitiesfile, image, texttext
Throughput (p50)——
Arena · overallUnranked#259 · ELO 1,318
Arena · JapaneseUnranked#184 · ELO 1,256
Arena · codingUnranked#240 · ELO 1,369

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, gpt-oss-20b: ¥23.52 per 1M output tokens, 99% less than GPT-6.1 Sol.
  • For long documents, GPT-6.1 Sol: a 1,050,000-token context window against 131,072 for gpt-oss-20b.
  • 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

gpt-oss-20b

**Count of ‘r’ in “strawberry”: 3** --- ### Step‑by‑step reasoning 1. **Write out the word in individual letters** ``` s t r a w b e r r y ``` 2. **Identify each ‘r’** - The first ‘r’: appears after the “t” → **r** - The second ‘r’: appears in the part “berry” → **r** - The third ‘r’: the next letter after that → **r** 3. **Verify there are no more letters left** The remaining letters are “b”, “e”, “y”, none of which are “r”. 4. **Count the identified ‘r’s** 1 (first) + 1 (second) + 1 (third) = **3** --- ### Quick recap - Word: **strawberry** - Letters containing “r”: positions 3, 8, and 9. - Total count: **3**.
11.6s371 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

gpt-oss-20b

### Why does the error happen? `users.map(...)` can only run when **`users` is an array**. The stack trace shows that the crash happens on line 12 of `UserList.js`, which is the exact spot where the code tries to call `.map`. The value that is being passed to `UserList` (or the initial value that the parent creates) is **`undefined`** (or it could be `null`/`{}`). When JavaScript tries to read `users.map`, it throws: ``` TypeError: Cannot read properties of undefined (reading 'map') ``` Typical reasons for this are: 1. The parent component **didn’t pass the `users` prop** at all. 2. The parent passed it but the value was **`undefined` / `null`** because data hasn’t been loaded ye…
11.4s1303 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

gpt-oss-20b

Below is a quick “code‑review” style list that touches the three axes you asked for – **readability**, **performance**, and **best practices**. After the bullet‑list I’ll paste a refactored version that incorporates the most common fixes. --- ## 1. Readability | Issue | Why it hurts | Quick fix | |-------|--------------|-----------| | **Imports inside the function** | Every call recompiles the import tables and makes the module’s top‑level slower. | Move `import requests` and `import time` to the module’s global header. | | **Bare `except:`** | Catches *everything* (KeyboardInterrupt, SystemExit, MemoryError, etc.) and swallows useful tracebacks. | Catch only the expected network-relate…
24.6s2267 output tokens

Compare on more prompts →

Frequently asked questions

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

More comparisons with GPT-6.1 Sol

More comparisons with gpt-oss-20b