Gemini 3.8 Flash vs Kimi K3
Pricing, context window and real answers (September 2026)
Gemini 3.8 Flash (Google) and Kimi K3 (Moonshot), 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.8 Flash |  Kimi K3 | |
|---|---|---|
| Provider | Moonshot | |
| Input (per 1M tokens) | ¥128.83 | ¥536.1 |
| Output (per 1M tokens) | ¥644.15 | ¥2,680.5 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥451 | ¥1,876 |
| Context window | 1,048,576 tokens | 1,048,576 tokens |
| Release date | 9/2/2026 | 7/16/2026 |
| Input modalities | text, image, video, file, audio | text, image |
| Arena · overall | #8 · ELO 1,494 | #12 · ELO 1,489 |
| Arena · Japanese | Unranked | #3 · ELO 1,516 |
| Arena · coding | #7 · ELO 1,537 | #6 · ELO 1,542 |
Prices are FastMetal's yen rates before tax. Arena ranks are as of the latest leaderboard scrape.
Which should you pick?
- On price, Gemini 3.8 Flash: ¥644.15 per 1M output tokens, 76% less than Kimi K3.
- On the Overall arena board, Gemini 3.8 Flash ranks higher (#8; Kimi K3 is #12).
- On the Coding arena board, Kimi K3 ranks higher (#6; Gemini 3.8 Flash is #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.
Gemini 3.8 Flash
There are **3** 'r's in the word "strawberry".
Here is the step-by-step breakdown:
1. **Break the word into its individual letters:**
* **s** (1st letter)
* **t** (2nd letter)
* **r** (3rd letter) — **1st 'r'**
* **a** (4th letter)
* **w** (5th letter)
* **b** (6th letter)
* **e** (7th letter)
* **r** (8th letter) — **2nd 'r'**
* **r** (9th letter) — **3rd 'r'**
* **y** (10th letter)
2. **Count the occurrences:**
* One 'r' is in the first syllable: "st**r**aw"
* Two 'r's are in the second syllable: "be**rr**y"
Total: **3**
3.9s562 output tokens
Kimi K3
# Counting the 'r's in "strawberry"
**Step 1: Write out each letter with its position**
| Position | Letter |
|----------|--------|
| 1 | s |
| 2 | t |
| 3 | **r** ✓ |
| 4 | a |
| 5 | w |
| 6 | b |
| 7 | e |
| 8 | **r** ✓ |
| 9 | **r** ✓ |
| 10 | y |
**Step 2: Identify each 'r'**
- Position 3: the 'r' in "st**r**"
- Position 8: the first 'r' in "be**r**ry"
- Position 9: the second 'r' in "ber**r**y"
**Step 3: Verify by splitting the word**
"Strawberry" = "straw" + "berry"
- "straw" contains **1** r
- "berry" contains **2** r's
**Answer: There are 3 r's in "strawberry."** 🍓
12.2s594 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.8 Flash
### The Cause
This error occurs because the `users` prop is `undefined` when the component renders, and JavaScript cannot call `.map()` on `undefined`.
This typically happens in two common scenarios:
1. **Asynchronous data fetching:** The parent component fetches `users` from an API. On the initial render, the data hasn't arrived yet, so `users` defaults to `undefined`.
2. **Missing prop:** The parent component forgot to pass `users` (e.g., `<UserList />` instead of `<UserList users={data} />`).
---
### How to Fix It
Here are the most common ways to resolve this:
#### Option 1: Provide a default parameter (Recommended)
Set a default value of an empty array (`[]`) for `users`. If `users…
7.1s1003 output tokens
Kimi K3
## What's causing it
The error means `users` is `undefined` when the component renders — `.map()` only exists on arrays, so calling it on `undefined` throws. Your component code is fine; the problem is **upstream**: whatever renders `<UserList />` isn't passing a valid array.
The most common culprit is **async data fetching with uninitialized state** in the parent:
```jsx
function App() {
const [users, setUsers] = useState(); // ← undefined!
useEffect(() => {
fetch('/api/users')
.then(res => res.json())
.then(setUsers);
}, []);
return <UserList users={users} />; // undefined on first render
}
```
The component renders *before* the fetch resolves, so `users` is `…
47.5s1756 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.8 Flash
Here is a code review of your function, broken down by issue category, followed by refactored versions.
---
### Key Issues & Areas for Improvement
#### 1. Correctness & Error Handling
* **Bare `except:` clause:** Catching all exceptions with a bare `except:` is dangerous. It suppresses system exits (`KeyboardInterrupt`, `SystemExit`) and masks programming bugs (like `KeyError` or `NameError`). You should catch specific exceptions, primarily `requests.RequestException`.
* **Silent failure returning `[]`:** If all retries fail, returning an empty list makes it impossible for the caller to distinguish between *"the API returned 0 active items"* and *"the network is completely down"*. It is u…
15.1s2139 output tokens
Kimi K3
This works, but there are several issues worth addressing. Here's a breakdown, followed by an improved version.
## Issues
### Correctness & best practices
1. **Bare `except:`** — catches *everything*, including `KeyboardInterrupt` and programming bugs like `KeyError` on a malformed item (which then get pointlessly retried). Catch `requests.RequestException` specifically.
2. **Silent failures** — errors are swallowed with no logging, and returning `[]` makes "API is down" indistinguishable from "no active items." At minimum, log; ideally, raise after the final attempt.
3. **Retrying non-retryable errors** — a 400/401/404 will never succeed on retry, but the code sleeps and retries anyway. O…
57.6s8060 output tokens
Frequently asked questions
- Which is cheaper, Gemini 3.8 Flash or Kimi K3?
- Per 1M output tokens, Gemini 3.8 Flash is ¥644.15 and Kimi K3 is ¥2,680.5 on FastMetal (yen, before tax), so Gemini 3.8 Flash is cheaper.
- How do the context windows of Gemini 3.8 Flash and Kimi K3 compare?
- Gemini 3.8 Flash takes 1,048,576 tokens; Kimi K3 takes 1,048,576.
- Which ranks higher, Gemini 3.8 Flash or Kimi K3?
- Kimi K3 ranks higher on the public arena (Gemini 3.8 Flash #8, Kimi K3 #3). Ranks move as the leaderboard updates.
- Can I use Gemini 3.8 Flash and Kimi K3 with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "gemini-3.8-flash" or "kimi-k3" 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.8 Flash and Kimi K3 from the browser chat and the API. No monthly fee.