Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.openclaw.ai/llms.txt

Use this file to discover all available pages before exploring further.

Xiaomi MiMo is the API platform for MiMo models. OpenClaw uses the Xiaomi OpenAI-compatible endpoint with API-key authentication.
PropertyValue
Providerxiaomi
AuthXIAOMI_API_KEY
APIOpenAI-compatible
Base URLhttps://api.xiaomimimo.com/v1

​
Getting started

1

Get an API key

Create an API key in the Xiaomi MiMo console.
2

Run onboarding

openclaw onboard --auth-choice xiaomi-api-key
Or pass the key directly:
openclaw onboard --auth-choice xiaomi-api-key --xiaomi-api-key "$XIAOMI_API_KEY"
3

Verify the model is available

openclaw models list --provider xiaomi

​
Built-in catalog

Model refInputContextMax outputReasoningNotes
xiaomi/mimo-v2-flashtext262,1448,192NoDefault model
xiaomi/mimo-v2-protext1,048,57632,000YesLarge context
xiaomi/mimo-v2-omnitext, image262,14432,000YesMultimodal
The default model ref is xiaomi/mimo-v2-flash. The provider is injected automatically when XIAOMI_API_KEY is set or an auth profile exists.

​
Text-to-speech

The bundled xiaomi plugin also registers Xiaomi MiMo as a speech provider for messages.tts. It calls Xiaomi’s chat-completions TTS contract with the text as an assistant message and optional style guidance as a user message.
PropertyValue
TTS idxiaomi (mimo alias)
AuthXIAOMI_API_KEY
APIPOST /v1/chat/completions with audio
Defaultmimo-v2.5-tts, voice mimo_default
OutputMP3 by default; WAV when configured
{
  messages: {
    tts: {
      auto: "always",
      provider: "xiaomi",
      providers: {
        xiaomi: {
          apiKey: "xiaomi_api_key",
          model: "mimo-v2.5-tts",
          voice: "mimo_default",
          format: "mp3",
          style: "Bright, natural, conversational tone.",
        },
      },
    },
  },
}
Supported built-in voices include mimo_default, default_zh, default_en, Mia, Chloe, Milo, and Dean. mimo-v2-tts is supported for older MiMo TTS accounts; the default uses the current MiMo-V2.5 TTS model. For voice-note targets such as Feishu and Telegram, OpenClaw transcodes Xiaomi output to 48kHz Opus with ffmpeg before delivery.

​
Config example

{
  env: { XIAOMI_API_KEY: "your-key" },
  agents: { defaults: { model: { primary: "xiaomi/mimo-v2-flash" } } },
  models: {
    mode: "merge",
    providers: {
      xiaomi: {
        baseUrl: "https://api.xiaomimimo.com/v1",
        api: "openai-completions",
        apiKey: "XIAOMI_API_KEY",
        models: [
          {
            id: "mimo-v2-flash",
            name: "Xiaomi MiMo V2 Flash",
            reasoning: false,
            input: ["text"],
            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
            contextWindow: 262144,
            maxTokens: 8192,
          },
          {
            id: "mimo-v2-pro",
            name: "Xiaomi MiMo V2 Pro",
            reasoning: true,
            input: ["text"],
            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
            contextWindow: 1048576,
            maxTokens: 32000,
          },
          {
            id: "mimo-v2-omni",
            name: "Xiaomi MiMo V2 Omni",
            reasoning: true,
            input: ["text", "image"],
            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
            contextWindow: 262144,
            maxTokens: 32000,
          },
        ],
      },
    },
  },
}
The xiaomi provider is injected automatically when XIAOMI_API_KEY is set in your environment or an auth profile exists. You do not need to manually configure the provider unless you want to override model metadata or the base URL.
  • mimo-v2-flash — lightweight and fast, ideal for general-purpose text tasks. No reasoning support.
  • mimo-v2-pro — supports reasoning with a 1M token context window for long-document workloads.
  • mimo-v2-omni — reasoning-enabled multimodal model that accepts both text and image inputs.
All models use the xiaomi/ prefix (for example xiaomi/mimo-v2-pro).
  • If models do not appear, confirm XIAOMI_API_KEY is set and valid.
  • When the Gateway runs as a daemon, ensure the key is available to that process (for example in ~/.openclaw/.env or via env.shellEnv).
Keys set only in your interactive shell are not visible to daemon-managed gateway processes. Use ~/.openclaw/.env or env.shellEnv config for persistent availability.

Model selection

Choosing providers, model refs, and failover behavior.

Configuration reference

Full OpenClaw configuration reference.

Xiaomi MiMo console

Xiaomi MiMo dashboard and API key management.