Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix [Feature]: Add possibility to use Xiaomi MiMo token plan [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#14285•Fetched 2026-04-23 07:45:46
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
acidkillacidkill
Participants
acidkillacidkillalt-glitchalt-glitch
Timeline (top)
labeled ×4commented ×2
RAW_BUFFERClick to expand / collapse

Problem or Use Case

Currently there is only option to use api with pay as you go for Xiaomi. Xiaomi released token plan - which generates an custom api key and assign to one of two endpoints: https://token-plan-ams.xiaomimimo.com/v1 https://token-plan-cn.xiaomimimo.com/v1

Proposed Solution

when choosing provider Xiaomi user should have possible official API's to choose

change reuire (or it did in my case) editing auth.json and adding:

"custom:xiaomi-token-plan": [
  {
    "id": "0cxxxx",
    "label": "xiaomi-token-plan",
    "auth_type": "api_key",
    "priority": 0,
    "source": "config:xiaomi-token-plan",
    "access_token": "tp-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "last_status": null,
    "last_status_at": null,
    "last_error_code": null,
    "last_error_reason": null,
    "last_error_message": null,
    "last_error_reset_at": null,
    "base_url": "https://token-plan-ams.xiaomimimo.com/v1",
    "request_count": 0
  }
]

and the upper part of config.yaml to:

model: default: mimo-v2.5-pro api_mode: chat_completions provider: custom:xiaomi-token-plan base_url: https://token-plan-ams.xiaomimimo.com/v1 xiaomi-token-plan:

  • mimo-v2.5-pro
  • mimo-v2.5

and on the bottom of config.yaml:

custom_providers:

Alternatives Considered

No response

Feature Type

New tool

Scope

None

Contribution

  • I'd like to implement this myself and submit a PR

Debug Report (optional)

extent analysis

TL;DR

To use Xiaomi's token plan, update the auth.json and config.yaml files with the custom API key and endpoint.

Guidance

  • Add a new entry to the auth.json file with the custom API key and endpoint, as shown in the proposed solution.
  • Update the config.yaml file to include the custom provider and API key, and set the provider to custom:xiaomi-token-plan.
  • Ensure the base_url in both files matches the desired endpoint (either https://token-plan-ams.xiaomimimo.com/v1 or https://token-plan-cn.xiaomimimo.com/v1).
  • Verify that the custom_providers section in config.yaml includes the new provider with the correct API key and model.

Example

custom_providers:
- name: xiaomi-token-plan
  base_url: https://token-plan-ams.xiaomimimo.com/v1
  api_key: tp-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  model: mimo-v2.5-pro

Notes

This solution assumes that the user has already obtained a custom API key from Xiaomi's token plan. The base_url should be updated to match the desired endpoint.

Recommendation

Apply workaround: Update the auth.json and config.yaml files as described, to use the custom API key and endpoint provided by Xiaomi's token plan.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#GPU setup#container setup#orchestration issue#cache issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING