openclaw - 💡(How to fix) Fix [Feature]: Add Xiaomi MiMo Token Plan provider support / fix Token Plan connection

{
  "models": {
    "mode": "merge",
    "providers": {
      "xiaomi-coding": {
        "baseUrl": "TOKEN_PLAN_BASE_URL",
        "apiKey": "tp-REDACTED",
        "api": "openai-completions",
        "models": [
          {
            "id": "mimo-v2.5-pro",
            "name": "mimo-v2.5-pro",
            "reasoning": true,
            "input": ["text"],
            "contextWindow": 1048576,
            "maxTokens": 32000
          }
        ]
      }
    }
  }
}

### Alternatives considered


## Alternatives considered

```markdown
1. Manually editing `~/.openclaw/openclaw.json`

This can work, but it is error-prone. Users may not know where the provider block goes, whether to use `xiaomi` or a custom provider name like `xiaomi-coding`, or whether an old Xiaomi auth profile is interfering.

2. Using the normal Xiaomi provider setup

This appears to work better for pay-as-you-go keys, but it is confusing for Token Plan keys. It can lead users to keep using the wrong billing/usage pool or fail connection entirely.

3. Using another OpenAI-compatible provider manually

This is possible, but weaker because Xiaomi MiMo is already documented as OpenClaw-compatible. Users should not need to create a generic workaround when the platform could expose Token Plan as a proper provider option.

4. Relying only on documentation

Docs help, but the app should detect key type and guide the user. A built-in provider option and test button would prevent many setup mistakes.

### Impact

Affected users/systems/channels:
- OpenClaw users trying to use Xiaomi MiMo Token Plan / subscription API
- Users who have both pay-as-you-go and Token Plan access
- Users running agents that need a cheaper or subscription-based fallback model
- OpenClaw provider setup and model routing

Severity:
Blocks workflow.

Frequency:
Always or often, whenever a user tries to configure Token Plan manually or accidentally uses the normal Xiaomi provider with a `tp-` key.

Practical consequences:
- Users cannot connect Xiaomi MiMo Token Plan reliably.
- Users may accidentally keep using exhausted pay-as-you-go usage.
- Users waste time debugging Base URL/key/provider-name issues.
- OpenClaw may show confusing provider failures.
- Users cannot use `mimo-v2.5-pro` as a working model fallback for agents.
- Extra manual editing of `openclaw.json` increases risk of breaking OpenClaw config.

### Evidence/examples

_No response_

### Additional information

_No response_