Kimi K3 vs Mercury 2.5
Pricing, context window and real answers (September 2026)
Kimi K3 (Moonshot) and Mercury 2.5 (Inception), 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 K3 | Mercury 2.5 | |
|---|---|---|
| Provider | Moonshot | Inception |
| Input (per 1M tokens) | ¥536.1 | ¥6.77 |
| Output (per 1M tokens) | ¥2,680.5 | ¥25.38 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥1,876 | ¥19 |
| Context window | 1,048,576 tokens | 260,000 tokens |
| Release date | 7/16/2026 | 9/8/2026 |
| Input modalities | text, image | text |
| Arena · overall | #12 · ELO 1,489 | Unranked |
| Arena · Japanese | #3 · ELO 1,516 | Unranked |
| Arena · coding | #6 · ELO 1,542 | Unranked |
Prices are FastMetal's yen rates before tax. Arena ranks are as of the latest leaderboard scrape.
Which should you pick?
- On price, Mercury 2.5: ¥25.38 per 1M output tokens, 99% less than Kimi K3.
- For long documents, Kimi K3: a 1,048,576-token context window against 260,000 for Mercury 2.5.
- 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 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
Mercury 2.5
To determine the number of 'r's in the word "strawberry", we can examine each letter in sequence:
1. **s** - Not 'r'
2. **t** - Not 'r'
3. **r** - First 'r' found
4. **a** - Not 'r'
5. **w** - Not 'r'
6. **b** - Not 'r'
7. **e** - Not 'r'
8. **r** - Second 'r' found
9. **r** - Third 'r' found
10. **y** - Not 'r'
Counting these occurrences, there are **3** 'r's in "strawberry".
1.8s968 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 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
Mercury 2.5
This error occurs because the `users` prop is `undefined` when the component renders. Since the code calls `.map()` on `users`, JavaScript throws a TypeError when `users` is not an array.
Here is how to fix it:
1. **Set a Default Value**
Update the function signature to default `users` to an empty array if it is not provided:
```javascript
function UserList({ users = [] }) {
// ...
}
```
2. **Add a Conditional Check**
If `users` might be null or undefined during data loading, guard the map operation:
```javascript
{users && users.map(user => <li key={user.id}>{user.name}</li>)}
```
3. **Verify Parent Props**
Ensure the parent component pas…
2.4s1028 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 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
Mercury 2.5
Here is a review of the function with suggestions for improvement.
### Key Observations
1. **Imports:** Libraries should be imported at the module level, not inside functions.
2. **Exception Handling:** Bare `except:` clauses catch system exits and interrupts. Use specific exceptions like `requests.exceptions.RequestException`.
3. **Logic & Pythonicity:**
* Avoid `== True`; rely on truthiness or `item.get("active")`.
* List comprehensions are more concise and efficient than manual appending.
4. **Retry Strategy:** Implement exponential backoff instead of fixed sleeps, and avoid sleeping after the final failed attempt.
5. **Documentation:** Add type hints and a docstring fo…
4.6s1999 output tokens
Frequently asked questions
- Which is cheaper, Kimi K3 or Mercury 2.5?
- Per 1M output tokens, Kimi K3 is ¥2,680.5 and Mercury 2.5 is ¥25.38 on FastMetal (yen, before tax), so Mercury 2.5 is cheaper.
- How do the context windows of Kimi K3 and Mercury 2.5 compare?
- Kimi K3 takes 1,048,576 tokens; Mercury 2.5 takes 260,000.
- Can I use Kimi K3 and Mercury 2.5 with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "kimi-k3" or "mercury-2.5" 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 K3 and Mercury 2.5 from the browser chat and the API. No monthly fee.