Kimi K2.6 vs Kimi K3
Pricing, context window and real answers (August 2026)
Kimi K2.6 (Moonshot) 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
 Kimi K2.6 | Kimi K3 | |
|---|---|---|
| Provider | Moonshot | Moonshot |
| Input (per 1M tokens) | ¥169.77 | ¥536.1 |
| Output (per 1M tokens) | ¥714.8 | ¥2,680.5 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥527 | ¥1,876 |
| Context window | 262,144 tokens | 1,048,576 tokens |
| Release date | 4/20/2026 | 7/16/2026 |
| Input modalities | text, image | text, image |
| Arena · overall | #41 · ELO 1,461 | #11 · ELO 1,486 |
| Arena · Japanese | #25 · ELO 1,449 | Unranked |
| Arena · coding | #30 · ELO 1,515 | #8 · ELO 1,530 |
Prices are FastMetal's yen rates before tax. Arena ranks are as of the latest leaderboard scrape.
Which should you pick?
- On price, Kimi K2.6: ¥714.8 per 1M output tokens, 73% less than Kimi K3.
- On the Overall arena board, Kimi K3 ranks higher (#11; Kimi K2.6 is #41).
- On the Coding arena board, Kimi K3 ranks higher (#8; Kimi K2.6 is #30).
- For long documents, Kimi K3: a 1,048,576-token context window against 262,144 for Kimi K2.6.
- 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.
Kimi K2.6
Here is the step-by-step count:
**Step 1:** Write out the word and number each letter.
1. s
2. t
3. **r** ← 1st 'r'
4. a
5. w
6. b
7. e
8. **r** ← 2nd 'r'
9. **r** ← 3rd 'r'
10. y
**Step 2:** Identify the positions containing the letter 'r'.
- The 3rd letter is **r**
- The 8th letter is **r**
- The 9th letter is **r**
**Step 3:** Tally the total.
There are **3** letter 'r's in "strawberry".
4.5s352 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…
Kimi K2.6
The error occurs because `users` is `undefined` when your component renders. The `.map()` method only works on arrays, so calling it on `undefined` throws this error.
This usually happens when:
- The parent component hasn't finished fetching data yet
- The `users` prop isn't being passed at all
- The prop is misspelled in the parent component
## Quick Fix
Set a **default value** for the `users` prop:
```jsx
function UserList({ users = [] }) {
return (
<ul>
{users.map(user => <li key={user.id}>{user.name}</li>)}
</ul>
);
}
```
## Alternative Fixes
**Optional chaining** (renders nothing if undefined):
```jsx
{users?.map(user => <li key={user.id}>{user.name}</li>)}
```…
71.8s864 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):…
Kimi K2.6
Here is a refactored version followed by a breakdown of the improvements.
### Refactored Function
```python
import logging
import time
from typing import Any
import requests
logger = logging.getLogger(__name__)
def fetch_active_items(
url: str,
*,
retries: int = 3,
timeout: float = 10.0,
backoff: float = 2.0,
) -> list[dict[str, Any]]:
"""Fetch active items from an API endpoint with retry logic.
Args:
url: The API endpoint URL.
retries: Number of retry attempts for transient failures.
timeout: HTTP request timeout in seconds.
backoff: Base delay in seconds between retries (linear backoff).
Returns:
A list of activ…
17.9s4061 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, Kimi K2.6 or Kimi K3?
- Per 1M output tokens, Kimi K2.6 is ¥714.8 and Kimi K3 is ¥2,680.5 on FastMetal (yen, before tax), so Kimi K2.6 is cheaper.
- How do the context windows of Kimi K2.6 and Kimi K3 compare?
- Kimi K2.6 takes 262,144 tokens; Kimi K3 takes 1,048,576.
- Which ranks higher, Kimi K2.6 or Kimi K3?
- Kimi K3 ranks higher on the public arena (Kimi K2.6 #25, Kimi K3 #11). Ranks move as the leaderboard updates.
- Can I use Kimi K2.6 and Kimi K3 with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "kimi-k2.6" 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 Kimi K2.6 and Kimi K3 from the browser chat and the API. No monthly fee.