---
title: "Xiaomi AI models — API access and skills via RunAPI"
url: "https://runapi.ai/providers/xiaomi.md"
canonical: "https://runapi.ai/providers/xiaomi.md"
locale: "en"
provider: "Xiaomi"
line_count: 1
variant_count: 2
---

# Xiaomi

MiMo base mimo-v2.5 supports text and remote HTTP(S) images through synchronous OpenAI Chat Completions; mimo-v2.5-pro is text-only.

Both models support text-only requests through Chat Completions, Responses, and Anthropic Messages on their existing synchronous and SSE paths. Base mimo-v2.5 also accepts remote HTTP(S) image_url parts in messages[].content[] through synchronous OpenAI Chat Completions. mimo-v2.5-pro is text-only; other image and media shapes remain closed or unverified.

## Models

- [MiMo](https://runapi.ai/models/mimo.md) — Text, 2 variants · from $0.0001

## Variants

| Model | Variant | Billing | Pricing | URL |
|---|---|---|---|---|
| MiMo | `v2.5` | 1K tokens | Input $0.09 / 1M tokens | Output $0.18 / 1M tokens | https://runapi.ai/models/mimo/v2.5.md |
| MiMo | `v2.5-pro` | 1K tokens | Input $0.27 / 1M tokens | Output $0.54 / 1M tokens | https://runapi.ai/models/mimo/v2.5-pro.md |

## LLM API endpoints

Base URL: `https://runapi.ai`

- `POST /v1/chat/completions` — OpenAI compatible
- `POST /v1/responses` — OpenAI Responses
- `POST /v1/messages` — Anthropic compatible

Use a compatible SDK for the endpoint you call with your RunAPI API key.


## FAQ

### Is this an official Xiaomi integration?

RunAPI exposes a managed API surface with transparent per-call pricing, fully documented capability and parameters, and clear error behavior. You get the same model output quality without managing a direct provider relationship or provider-side account.

### Do I need a Xiaomi account?

No. Your RunAPI API key is enough for managed access to all Xiaomi models. You do not need to create a separate account, manage provider-specific credentials, or handle provider-side billing.

### What's the latency overhead from proxying through RunAPI?

Typically under 20 ms. RunAPI keeps the proxy layer close to model execution regions to minimize added latency. Media generation time is dominated by the model itself, not the proxy.

### Are images / videos cached?

Generated outputs are stored and retrievable by task ID. You can fetch completed results at any time using the task status endpoint or the RunAPI dashboard. Output URLs remain accessible for the retention period shown in the API docs. Inputs are not cached or stored.

### Can I bring my own key?

Not currently. Calls use RunAPI-managed access, which simplifies authentication and lets RunAPI handle rate limiting, retries, and billing consolidation on your behalf.

### How is billing consolidated?

All API calls across all providers appear on a single monthly USD invoice. There is no per-provider billing, no subscription, and no minimum spend. Failed generations are never charged.

### What SDKs can I use with Xiaomi models?

Official SDKs are available for Python, Node.js, PHP, Java, Ruby, and Go. Each SDK handles authentication, async task polling, and typed responses. For LLM models, the OpenAI and Anthropic SDKs also work by pointing the base URL to RunAPI.

### What are model skills and how do they work?

Model skills are installable packages that load a model's docs, typed schemas, pricing notes, and setup steps directly into your coding workspace. Install a skill with one command and your agent has the right context before you write integration code. Skills work with Claude Code, Codex, Gemini CLI, Cursor, and VS Code.

### How do I switch between Xiaomi models?

Change the model parameter in your API request. All Xiaomi models share the same API key, the same request shape, and the same billing. No code changes, no re-authentication, and no separate billing setup are required when switching between models or between variants of the same model. You can also switch to models from other providers by changing the same parameter — the API surface is unified across the entire catalog.