Kimi apologizes for K3.1 Pro plan rate limits and wasted quota, gives every subscriber a one-time 25% monthly quota reset and trims subagent calls and output length

Background and pain point

After Kimi K3.1 Pro launched on October 23, subscribers, many using it through coding tools such as Kimi Code, ran into frequent rate limits and quota that drained faster than it should. Coding-agent subscriptions are usually metered by quota, and a long task can fire many subagent calls and long outputs, so a small metering problem can exhaust a monthly allowance early.

What changed

The official post has two parts. First, compensation: every subscriber on every plan gets a one-time usage reset that restores 25% of the monthly quota, and anyone below 25% usage is reset to zero, which Kimi says equals about one week of usage. Second, a fix to the source of the drain: plan parameters were adjusted and unnecessary subagent calls and output length are being reduced. Kimi did not say which parameters changed or publish rate-limit thresholds.

Benchmarks

This is a billing and service change, not a model change, and Kimi published no benchmarks or before-and-after consumption data. For reference, the launch-time vendor pricing for the K3.1 Pro API is $2 input and $10 output per million tokens. How much the trimmed subagent calls and outputs save on real tasks is still unmeasured.

What developers should do

Subscribers do not need to act; Kimi says usage bars update by end of day PST on October 25, roughly the afternoon of October 26 in Singapore. Check that 25% was restored, watch whether long tasks spawn fewer subagents and shorter outputs, and if rate limits persist, compare against pay-as-you-go API pricing. Source: Kimi official post.