DeepSeek V4 Pro vs Kimi K3
Pricing, context window and real answers (August 2026)
DeepSeek V4 Pro (DeepSeek) 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
 DeepSeek V4 Pro |  Kimi K3 | |
|---|---|---|
| Provider | DeepSeek | Moonshot |
| Input (per 1M tokens) | ¥341.32 | ¥536.1 |
| Output (per 1M tokens) | ¥684.42 | ¥2,680.5 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥684 | ¥1,876 |
| Context window | 1,048,576 tokens | 1,048,576 tokens |
| Release date | 4/24/2026 | 7/16/2026 |
| Input modalities | text | text, image |
| Arena · overall | #49 · ELO 1,457 | #11 · ELO 1,486 |
| Arena · Japanese | #18 · ELO 1,462 | Unranked |
| Arena · coding | #54 · ELO 1,502 | #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, DeepSeek V4 Pro: ¥684.42 per 1M output tokens, 74% less than Kimi K3.
- On the Overall arena board, Kimi K3 ranks higher (#11; DeepSeek V4 Pro is #49).
- On the Coding arena board, Kimi K3 ranks higher (#8; DeepSeek V4 Pro is #54).
- 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.
DeepSeek V4 Pro
The word is "strawberry". Let's count the occurrences of the letter 'r' step by step:
1. Write the word: s t r a w b e r r y
2. Examine each character:
- s: not an 'r'
- t: not an 'r'
- r: is an 'r' → count 1
- a: not an 'r'
- w: not an 'r'
- b: not an 'r'
- e: not an 'r'
- r: is an 'r' → count 2
- r: is an 'r' → count 3
- y: not an 'r'
3. Total number of 'r's = 3.
Therefore, there are **3** 'r's in "strawberry".
7.3s1136 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…
DeepSeek V4 Pro
The error is occurring because `users` is `undefined` when the component renders, and you're trying to call `.map()` on it. This typically happens when the data hasn't been loaded yet or wasn't passed correctly to the component.
## Here are several ways to fix this:
### 1. **Add a default value with empty array (Simplest fix)**
```javascript
function UserList({ users = [] }) {
return (
<ul>
{users.map(user => <li key={user.id}>{user.name}</li>)}
</ul>
);
}
```
### 2. **Add a conditional check**
```javascript
function UserList({ users }) {
if (!users) {
return <div>No users found</div>;
}
return (
<ul>
{users.map(user => <li key={user.id}>{user.name}<…
6.9s442 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):…
DeepSeek V4 Pro
Here’s a review of your `get_data` function, highlighting issues and suggesting improvements.
## Overall Observations
- The function works but has several readability, robustness, and maintainability issues.
- Imports are inside the function, bare `except` hides errors, and the filtering logic is not Pythonic.
- No type hints or docstring, making it harder to use and understand.
## Specific Improvements
### 1. Move Imports to the Top of the Module
**Why:** Imports inside a function are executed every time the function is called, which is slightly slower and violates PEP 8 style guidelines.
**Before:**
```python
def get_data(url, retries=3):
import requests
import time
# ...
`…
40.5s2277 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, DeepSeek V4 Pro or Kimi K3?
- Per 1M output tokens, DeepSeek V4 Pro is ¥684.42 and Kimi K3 is ¥2,680.5 on FastMetal (yen, before tax), so DeepSeek V4 Pro is cheaper.
- How do the context windows of DeepSeek V4 Pro and Kimi K3 compare?
- DeepSeek V4 Pro takes 1,048,576 tokens; Kimi K3 takes 1,048,576.
- Which ranks higher, DeepSeek V4 Pro or Kimi K3?
- Kimi K3 ranks higher on the public arena (DeepSeek V4 Pro #18, Kimi K3 #11). Ranks move as the leaderboard updates.
- Can I use DeepSeek V4 Pro and Kimi K3 with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "deepseek-v4-pro" 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 DeepSeek V4 Pro and Kimi K3 from the browser chat and the API. No monthly fee.