Fugu Ultra v2 vs MiMo-V2.5-Pro
Pricing, context window and real answers (September 2026)
Fugu Ultra v2 (Sakana AI) and MiMo-V2.5-Pro (Xiaomi), 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
| Fugu Ultra v2 | MiMo-V2.5-Pro | |
|---|---|---|
| Provider | Sakana AI | Xiaomi |
| Input (per 1M tokens) | ¥893.5 | ¥77.73 |
| Output (per 1M tokens) | ¥5,361 | ¥155.47 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥3,574 | ¥155 |
| Context window | 1,000,000 tokens | 1,050,000 tokens |
| Release date | 9/11/2026 | 4/22/2026 |
| Input modalities | text, image, file | text |
| Throughput (p50) | — | — |
| Arena · overall | Unranked | #44 · ELO 1,467 |
| Arena · Japanese | Unranked | #52 · ELO 1,426 |
| Arena · coding | Unranked | #25 · ELO 1,521 |
Prices are FastMetal's yen rates before tax. Arena ranks are as of the latest leaderboard scrape.
Which should you pick?
- On price, MiMo-V2.5-Pro: ¥155.47 per 1M output tokens, 97% less than Fugu Ultra v2.
- For long documents, MiMo-V2.5-Pro: a 1,050,000-token context window against 1,000,000 for Fugu Ultra v2.
- 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.
Fugu Ultra v2
**Answer: 3**
**Step-by-step reasoning:**
1. **Write out the word letter by letter**, assigning each a position:
| Position | Letter | Is it 'r'? |
|---|---|---|
| 1 | s | no |
| 2 | t | no |
| 3 | **r** | ✅ yes |
| 4 | a | no |
| 5 | w | no |
| 6 | b | no |
| 7 | e | no |
| 8 | **r** | ✅ yes |
| 9 | **r** | ✅ yes |
| 10 | y | no |
2. **Tally the matches:** positions 3, 8, and 9 are 'r'.
3. **Sanity check by chunks:** "straw" contains one 'r' (str**a**w → the r in "str"), and "berry" contains two 'r's (be**rr**y). 1 + 2 = 3.
4. **Verify length:** the letters counted total 10, which matches the length of "strawberry" — so no letter was skipped or double-counted.
**Conclusion:** There a…
10.2s435 output tokens
MiMo-V2.5-Pro
## Counting the r's in "strawberry"
Let me go through each letter one by one:
| Position | Letter | Is it 'r'? |
|----------|--------|------------|
| 1 | s | No |
| 2 | t | No |
| 3 | **r** | ✅ Yes (#1) |
| 4 | a | No |
| 5 | w | No |
| 6 | b | No |
| 7 | e | No |
| 8 | **r** | ✅ Yes (#2) |
| 9 | **r** | ✅ Yes (#3) |
| 10 | y | No |
**There are 3 r's in "strawberry."**
The word breaks down as **straw·ber·ry**, and the r's appear at the end of "staw" and then twice in the double-r of "rry."
8.3s313 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…
Fugu Ultra v2
## What the error means
`TypeError: Cannot read properties of undefined (reading 'map')` means that when `UserList` rendered, `users` was `undefined`, and JavaScript can't read the `.map` property off `undefined`.
The important detail: **the bug isn't really in `UserList`** — that's just where it surfaces. Destructuring `function UserList({ users })` does *not* throw when the prop is missing; it silently gives you `undefined`. The crash is deferred to the first property access, which is `.map` on line 12.
So the real question is: why is `props.users` not an array?
## Why `users` is undefined
**1. Async data hasn't arrived yet — by far the most common cause.**
```jsx
const [users, setUs…
70.8s5286 output tokens
MiMo-V2.5-Pro
# Fixing `Cannot read properties of undefined (reading 'map')`
## The Problem
The error means `users` is `undefined` when the component first renders. This typically happens when:
1. **The parent component hasn't passed the `users` prop**
2. **The data is being fetched asynchronously and isn't available yet**
3. **The prop name is misspelled in the parent**
For example, the parent might be rendering it like this:
```jsx
// ❌ No users prop passed — `users` will be undefined
<UserList />
```
## Solutions
### 1. Add a Default Prop Value (Simple Fix)
```jsx
function UserList({ users = [] }) {
return (
<ul>
{users.map(user => <li key={user.id}>{user.name}</li>)}
</ul>
);
}…
14.4s680 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):…
Fugu Ultra v2
# Final Code Review: `get_data`
The function is compact and its intent is clear, but as written it will **fail silently in production**. Two defects dominate everything else:
1. The bare `except:` swallows every error — including `KeyboardInterrupt` and genuine logic bugs.
2. A total failure and a legitimately empty dataset both return `[]`, so callers cannot tell "the service is down" from "there are no active records."
Together these mean an outage looks exactly like a successful empty response. Everything else below is meaningful improvement; those two are the difference between code that fails loudly and code that fails invisibly.
---
## 1. Correctness and error handling
### 1.1 `e…
281.1s23317 output tokens
MiMo-V2.5-Pro
# Code Review: `get_data` Function
## Issues Identified
```
┌──────────────────────────────────────────────────────────────┐
│ ISSUE SEVERITY MAP │
├──────────────────┬────────────┬──────────────────────────────┤
│ Issue │ Severity │ Category │
├──────────────────┼────────────┼──────────────────────────────┤
│ Bare except │ 🔴 High │ Error Handling / Best Prac. │
│ Silent failures │ 🔴 High │ Debuggability │
│ == True check │ 🟡 Medium │ Readability / PEP 8 │
│ Inline imports │ 🟡 Medium │ Best Practice │
│ No type hints │ 🟡 Medium │ Best Practice…
10.4s1572 output tokens
Frequently asked questions
- Which is cheaper, Fugu Ultra v2 or MiMo-V2.5-Pro?
- Per 1M output tokens, Fugu Ultra v2 is ¥5,361 and MiMo-V2.5-Pro is ¥155.47 on FastMetal (yen, before tax), so MiMo-V2.5-Pro is cheaper.
- How do the context windows of Fugu Ultra v2 and MiMo-V2.5-Pro compare?
- Fugu Ultra v2 takes 1,000,000 tokens; MiMo-V2.5-Pro takes 1,050,000.
- Can I use Fugu Ultra v2 and MiMo-V2.5-Pro with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "fugu-ultra-v2" or "mimo-v2.5-pro" 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 Fugu Ultra v2 and MiMo-V2.5-Pro from the browser chat and the API. No monthly fee.