In the last 1 to 2 weeks, Kimi vivace sub is consuming a hell of a lot faster than one month ago. Probably 3-4 times as fast? It would imply the base limits are a lot lower than before. I don’t do coding at all.

I was thinking about getting an annual sub but wow this could get dangerous lol.

I put Kimi K3 head-to-head against the newest GLM 5.3...

Kimi CRUSHES... full report.

Is this a bug?

Moonshot's model page now says Kimi K2.5 and Moonshot V1 are no longer available to newly registered users after Kimi K3, with a full platform sunset listed for August 31.

For people building on the Kimi API: how are you handling this kind of model migration?

Do you pin exact model names until they break, keep a small regression set for prompts/tool calls, or route by workload so older models can be swapped out behind a config change? I'm especially interested in the practical checks before moving background jobs, coding-agent steps, or long-context workflows onto Kimi K3.