Kimi K2.5 API Keys Hit 401s

This reads more like an auth-policy or platform migration problem than a model bug, especially since brand-new keys fail immediately and the error happens before any model response.

• –The post uses `api.moonshot.cn/v1` from the UK, while current docs say overseas users should use `platform.moonshot.ai`; that endpoint split is a likely failure mode.
• –Hitting `401` on both `/v1/chat/completions` and `/v1/models` suggests the request is rejected at authentication, not by model selection or prompt formatting.
• –Three fresh keys failing in a row points to account-, project-, or platform-level enforcement, not a single bad secret.
• –The mismatch between the post's model string and the documented `kimi-k2.5` alias could trip wrappers, but the uniform 401 strongly suggests the key or base URL is the real issue.
• –For developers, the practical risk is downtime in agent/tooling setups that hardcode Moonshot endpoints and assume keys are portable across the China and overseas platforms.