HunterAlphaHub
OpenRouter model reference Facts from the public catalogue, dated and labelled

Guide

Xiaomi mimo-v2 Complete Guide: How to Use the 1M Context AI Model (2026)

Formerly known as Hunter Alpha, Xiaomi's MiMo-V2.5 offers a 1M-token context window at $0.14 in / $0.28 out per million tokens — it was free only during the March 2026 preview. Complete guide to using it.

Hunter Alpha Hub Team 23 March 2026 8 min read

Xiaomi mimo-v2 Complete Guide: How to Use the 1M Context AI Model (2026)

Quick Summary

Xiaomi mimo-v2 (formerly known as Hunter Alpha) is a free AI model with an unprecedented 1 million token context window. It’s available on OpenRouter and excels at processing long documents, multi-turn conversations, and complex reasoning tasks.

What is Xiaomi mimo-v2?

Xiaomi mimo-v2 is a large language model developed by Xiaomi, featuring:

  • 1 Trillion parameters for advanced reasoning
  • 1,048,576 token context window (approximately 700,000 words)
  • Text-only input and output
  • Free to use on OpenRouter
  • Optimized for agentic tasks including long-horizon planning and multi-step execution

Identity Update (March 2026)

The model originally appeared on OpenRouter as “Hunter Alpha” with unknown origins. On March 23, 2026, Xiaomi officially confirmed it as their mimo-v2 model. The site you’re reading this on was originally built to investigate the mystery — now it serves as a community resource for mimo-v2 users.

How to Access Xiaomi mimo-v2

Step 1: Create an OpenRouter Account

  1. Visit openrouter.ai
  2. Click “Sign Up” in the top right corner
  3. Complete registration using Google, GitHub, or email

Step 2: Find mimo-v2

  1. Use the search bar to find “mimo-v2” or “Hunter Alpha”
  2. Both names should work — they refer to the same model
  3. Click on the model to access its page

Step 3: Start Using

  1. Use the web chat interface for casual testing
  2. Or generate an API key for programmatic access
  3. A credit card is needed for API use: the preview is over and MiMo-V2.5 is billed at $0.14 in / $0.28 out per million tokens

Getting Started: First Prompts

Basic Testing

Start with simple prompts to understand the model’s behavior:

Summarize the key points of the document above in 3 bullet points.
What are the main contradictions between section 2 and section 5?

Long Document Processing

This is where mimo-v2 shines. Try:

  • Full book analysis: Upload an entire novel or technical book
  • Legal document review: Process contracts 100+ pages in one prompt
  • Codebase review: Paste multiple files for comprehensive review
  • Research paper synthesis: Compare findings across multiple papers

Example: Analyzing a 200-Page Report

I'm going to paste a 200-page market research report. After I paste it:
1. Summarize the top 5 market trends identified
2. List any data points that contradict each other
3. Extract all revenue projections for 2027-2030

[Paste your document]

Best Practices for 1M Context

Do’s

  • Specify page ranges for better precision: “Between pages 50-100, find…”
  • Break complex questions into smaller pieces for higher accuracy
  • Use follow-up questions to build on previous answers
  • Verify critical information — the model can occasionally hallucinate

Don’ts

  • Don’t expect perfect recall at maximum context — accuracy decreases beyond 500K tokens
  • Don’t use for latency-sensitive tasks — expect 20-60 second response times
  • Don’t skip verification for important decisions (legal, medical, financial)

Real-World Use Cases

Use case: Law firms processing contracts, deposition transcripts, discovery documents.

Example prompt:

Review this contract and identify:
1. All termination clauses and their conditions
2. Any clauses that conflict with standard industry practice
3. Obligations that extend beyond 24 months

2. Technical Documentation Analysis

Use case: Engineers processing API docs, system manuals, architecture specifications.

Example prompt:

Based on this technical manual, create a step-by-step guide for:
1. Initial system setup
2. Common troubleshooting procedures
3. Performance optimization settings

3. Academic Research

Use case: Researchers synthesizing multiple papers, extracting methodology, comparing findings.

Example prompt:

Compare the methodologies used in these three papers. Specifically:
1. Sample sizes and demographics
2. Statistical methods employed
3. Key differences in conclusions

4. Code Review and Refactoring

Use case: Developers reviewing large codebases, planning migrations, debugging complex issues.

Example prompt:

Review this codebase and identify:
1. Functions that are duplicated across files
2. Potential security vulnerabilities
3. Areas that would benefit from caching
4. Suggested refactoring priorities

Performance Characteristics

Speed Expectations

Context SizeResponse TimeBest For
10K tokens2-5 secondsQ&A, short analysis
100K tokens10-20 secondsMedium documents
500K tokens30-45 secondsLong reports, books
1M tokens45-90 secondsMaximum context tasks

Accuracy by Context Size

Context SizeRetrieval Accuracy
10K tokens~94%
100K tokens~91%
500K tokens~87%
1M tokens~82%

Comparison: mimo-v2 vs Alternatives

Featuremimo-v2Claude 3.5GPT-4oGemini 1.5 Pro
Context Window1M tokens200K tokens128K tokens1M tokens
Price$0.14/$0.28 per MPaid tierPaid tierPaid tier
SpeedSlowerFastFastestMedium
Code QualityGoodExcellentExcellentGood
Long Doc AccuracyExcellentGoodLimitedExcellent

Tips from the Community

From Power Users

  1. Use system prompts to set the model’s behavior for long sessions
  2. Chunk ultra-long documents (800K+ tokens) for critical tasks
  3. Save important conversations — context persists across turns
  4. Test with known documents first to calibrate your expectations

Common Pitfalls

  1. Expecting ChatGPT-speed responses — plan for latency
  2. Trusting citations without verification — always spot-check
  3. Using for simple tasks — overkill for basic Q&A
  4. Not having a fallback — keep Claude/GPT-4o for time-sensitive work

API Integration (For Developers)

Basic API Call

from openai import OpenAI

client = OpenAI(
    api_key="your-openrouter-key",
    base_url="https://openrouter.ai/api/v1"
)

response = client.chat.completions.create(
    model="xiaomi/mimo-v2",  # or "hunter-alpha"
    messages=[
        {"role": "user", "content": "Your long document here..."}
    ]
)

print(response.choices[0].message.content)

Streaming Responses

stream = client.chat.completions.create(
    model="xiaomi/mimo-v2",
    messages=[{"role": "user", "content": "Analyze this document..."}],
    stream=True
)

for chunk in stream:
    if chunk.choices[0].delta.content:
        print(chunk.choices[0].delta.content, end="")

The Bottom Line

Xiaomi mimo-v2 is a legitimate technical achievement that enables workflows impossible with smaller context windows. At free pricing, it’s an exceptional tool for:

  • Document analysis at scale
  • Batch processing where latency doesn’t matter
  • Experimentation and learning
  • Projects with zero budget

It’s not the best choice for:

  • Real-time applications
  • Short, simple tasks (overkill)
  • High-stakes code generation without review

Recommendation: Use mimo-v2 as a specialized tool in your AI toolkit — not as your only model, but as the go-to choice when you need massive context at zero cost.


Have tips or experiences to share? Submit your findings to our evidence wall or join the discussion on Reddit/Twitter.

Xiaomimimo-v2Hunter AlphaTutorial1M ContextOpenRouter

Keep reading

Send us a link

A project built with Jev, a post, a video, a correction, a tip. We open the link, check it says what you said it says, and write the entry ourselves.

Required a link, and an email to reply to. Optional everything else.

Add context — all optional

One or two sentences about what it does, in your words. We write the entry ourselves.

Cost, latency, a benchmark — anything you measured. We attribute these to you.

We store what you type and email it to ourselves. No IP address, no user agent, no referrer — the same rule as the mailing list.

What happens to what you send →