Kimi K3.1 Pro vs Mercury 2.5
Pricing, context window and real answers (October 2026)
Kimi K3.1 Pro (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.1 Pro | Mercury 2.5 | |
|---|---|---|
| Provider | Moonshot | Inception |
| Input (per 1M tokens) | $2.11 | $0.044 |
| Output (per 1M tokens) | $10.55 | $0.165 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | $7.39 | $0.1265 |
| Context window | 1,048,576 tokens | 260,000 tokens |
| Release date | 10/23/2026 | 9/8/2026 |
| Input modalities | text, image, video | text |
| Throughput (p50) | — | — |
| Arena · overall | Unranked | Unranked |
| Arena · Japanese | Unranked | Unranked |
| Arena · coding | Unranked | Unranked |
Prices are FastMetal's rates, before tax.
Rankings: LMArena leaderboard dataset (lmarena-ai/leaderboard-dataset), CC BY 4.0, snapshot 2026-10-22; category names mapped and ratings rounded by FastMetal.
Which should you pick?
- On price, Mercury 2.5: $0.165 per 1M output tokens, 98% less than Kimi K3.1 Pro.
- For long documents, Kimi K3.1 Pro: 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.1 Pro
There are **3** ‘r’s in **“strawberry.”**
1. Write out each letter: **s – t – r – a – w – b – e – r – r – y**
2. Locate the ‘r’s: positions **3, 8, and 9**.
3. Count them: **1 + 1 + 1 = 3**.
11.3s
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.1 Pro
## What's causing the error
The error means `users` is `undefined` when the component renders, and you can't call `.map()` on `undefined`. The component itself is fine — the problem is that whatever renders `<UserList />` either isn't passing the prop, or is passing a value that isn't an array yet.
The most common cause is **async data fetching**: the parent renders `UserList` before the data has loaded.
```jsx
function App() {
const [users, setUsers] = useState(); // ❌ undefined on first render
useEffect(() => {
fetch('/api/users')
.then(res => res.json())
.then(setUsers);
}, []);
return <UserList users={users} />; // users is undefined here initially
}
```
On…
36.3s
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.1 Pro
The timeout and bounded retry loop are good starting points. The biggest issue is that failures—and even programming errors—are silently converted into retries and then `[]`.
### Suggested improvements
- **Avoid bare `except:`**. It catches `KeyboardInterrupt`, `KeyError`, JSON/schema errors, and other bugs. Retry only expected transient network failures; let malformed responses fail visibly.
- **Use a deliberate retry policy**. Retrying `401`, `403`, or `404` usually wastes time. Retry only transient statuses, use exponential backoff, and avoid sleeping after the final attempt.
- **Do not use `[]` for both failure and no results**. Prefer raising the final exception so callers can disting…
560.2s
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.1 Pro or Mercury 2.5?
- Per 1M output tokens, Kimi K3.1 Pro is $10.55 and Mercury 2.5 is $0.165 on FastMetal (US dollars, before tax), so Mercury 2.5 is cheaper.
- How do the context windows of Kimi K3.1 Pro and Mercury 2.5 compare?
- Kimi K3.1 Pro takes 1,048,576 tokens; Mercury 2.5 takes 260,000.
- Can I use Kimi K3.1 Pro and Mercury 2.5 with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "kimi-k3.1-pro" 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.1 Pro and Mercury 2.5 from the browser chat and the API. No monthly fee.