Model comparison

Grok 4.7 vs MiMo-V2.5-Pro

Pricing, context window and real answers (September 2026)

Grok 4.7 (xAI) 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

x-ai logoGrok 4.7MiMo-V2.5-Pro
ProviderxAIXiaomi
Input (per 1M tokens)¥276.2¥77.73
Output (per 1M tokens)¥828.6¥155.47
Typical cost (1,000 in + 500 out tokens × 1,000 calls)¥691¥155
Context window500,000 tokens1,050,000 tokens
Release date9/21/20264/22/2026
Input modalitiestext, image, filetext
Throughput (p50)
Arena · overallUnranked#44 · ELO 1,467
Arena · JapaneseUnranked#52 · ELO 1,426
Arena · codingUnranked#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, 81% less than Grok 4.7.
  • For long documents, MiMo-V2.5-Pro: a 1,050,000-token context window against 500,000 for Grok 4.7.
  • 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.

Grok 4.7

The word "strawberry" consists of the letters S-T-R-A-W-B-E-R-R-Y. - The 3rd letter is R. - The 8th letter is R. - The 9th letter is R. This gives a total of 3 R's.
4.7s299 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…

Grok 4.7

The error happens because `users` is `undefined` when `UserList` renders, so calling `.map` on it fails. That usually means the parent rendered `<UserList />` (or `<UserList users={undefined} />`) before data was loaded, or the prop name doesn’t match. **Fix it in the component** so it tolerates a missing list: ```jsx function UserList({ users = [] }) { return ( <ul> {users.map(user => <li key={user.id}>{user.name}</li>)} </ul> ); } ``` Or guard the call: ```jsx function UserList({ users }) { return ( <ul> {(users ?? []).map(user => <li key={user.id}>{user.name}</li>)} </ul> ); } ``` **Also check the parent** so you pass an array once data exists: `…
12.8s393 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):…

Grok 4.7

## Review The function works for the happy path, but it hides failures, retries the wrong errors, and is harder to read and debug than it needs to be. ### Issues 1. **Imports inside the function** — move them to module level unless you have a strong reason (circular imports, optional dependency). 2. **Bare `except`** — swallows `KeyboardInterrupt`, `SystemExit`, and programming bugs. Catch specific exceptions. 3. **Retries non-retryable failures** — 4xx (except maybe 429) will not succeed on retry. Network errors and 5xx are the usual candidates. 4. **Sleeps after the last attempt** — wastes up to 2 seconds before returning `[]`. 5. **Unused loop variable** and vague names (`r`, `i`). 6.…
22.3s1525 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

Compare on more prompts →

Frequently asked questions

Which is cheaper, Grok 4.7 or MiMo-V2.5-Pro?
Per 1M output tokens, Grok 4.7 is ¥828.6 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 Grok 4.7 and MiMo-V2.5-Pro compare?
Grok 4.7 takes 500,000 tokens; MiMo-V2.5-Pro takes 1,050,000.
Can I use Grok 4.7 and MiMo-V2.5-Pro with the same API key?
Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "grok-4.7" 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 Grok 4.7 and MiMo-V2.5-Pro from the browser chat and the API. No monthly fee.

More comparisons with Grok 4.7

More comparisons with MiMo-V2.5-Pro