I’ve been a paying Kimi subscriber since early 2026 and hold an annual Allegro plan ($948, charged July 21, 2026). When the plan split was announced, your site stated “Existing subscribed users are unaffected,” and the sales page advertised Allegro with “5x agent credits” and “Kimi Code 15x credits.” I kept and upgraded my plan based on that.
Three months later, I have something nobody else has posted here: three complete billing cycles measured against Moonshot’s own backend (MembershipService/GetSubscriptionStats + ListBalanceActions), with server timestamps.
THE CORE FINDING — the monthly quota is mathematically unreachable:
My measured 7-day Kimi Code cap equals ~21–24% of my monthly credit pool (measured three times: Aug 16, Aug 23, Sep 28). Consequences, all documented:
- Cycle 1 (Jul 21–Aug 21): blocked by the weekly cap with ~19% of the monthly pool unused. That balance expired on Aug 21.
- Cycle 2 (Aug 21–Sep 21): blocked on day 3 with 89.5% of the pool untouched (ratelimitCode7d ratio = 1 while amountUsedRatio = 0.1054).
- Cycle 3 (Sep 21–present): weekly cap at 90.8% with the monthly pool at 18.96%.
Even at exactly 100% of the weekly cap every single week, the theoretical ceiling is ~90% of the monthly pool. In any realistic work pattern, the monthly figure on the pricing page is decorative. Allegro is a weekly pass with an annual price.
AND THE TRAP: the 7-day limiter is a rolling window that ignores billing-cycle boundaries. Consumption from the expired cycle (the “use it or lose it” rush your design forces) counts against the first week of the new cycle. I was blocked on day 3 of cycle 2 partly because of usage your expiry design compelled me to do.
FURTHER DOCUMENTED ISSUES:
-
Multipliers removed after purchase. Around July 31, the “15x coding credits” language disappeared from the plan pages. My own subscription page now says merely “Kimi Code available.” The criterion I paid with no longer exists in writing.
-
Unauditable billing. Your own ListBalanceActions API exposes only the current balance’s ledger, capped at 1,000 records. The ledger for my July–August cycle became inaccessible to me the moment it expired. A customer cannot audit 54% of what was billed in cycle 1. And the ledger only shows ratios (amountRatio) — never absolute credits or tokens — so the unit of account of the product I pay for is invisible by design.
-
Background consumption I never initiated counts against my weekly cap: daily “Claw — Cloud Instance” runs at 05:00 (~0.20%/day ≈ 4%/month), scheduled automations, Dream Memory.
-
Server-side evidence of capacity issues in my own client logs: repeated “429 The engine is currently overloaded” errors with 54–135s TTFT on Aug 25 — matching what your team publicly acknowledged here. (To be fair, and documented: those failed turns were NOT billed in my ledger.)
-
Meanwhile, your own Help Center (updated Sep 24, 2026) states that upgrades are prorated and unused portions refunded — while billing replies to downgrade/refund requests cite “all payments are final and non-refundable.” Which policy is real?
MY QUESTIONS TO MOONSHOT:
Q1. Publish absolute quota numbers per plan: monthly pool, 7-day cap, 5-hour cap, in credits or tokens. Today it is impossible to know what any plan actually sells.
Q2. Will the 7-day cap be restructured so a monthly subscription can actually deliver a month? Your team acknowledged here that the legacy quota design was flawed and being reworked — that was two months ago.
Q3. What is the remediation path for legacy annual subscribers whose purchased plan was degraded in place? We cannot switch back to what we bought, and the multipliers we paid for no longer exist.
I have formally disputed the charge via [email protected] (Aug 8) with no substantive reply to date, and I am documenting everything for my card issuer and Brazilian consumer-protection channels (CDC, arts. 6 III, 30, 35, 51; LGPD art. 18 request for the complete ledger is in that thread).
I post this publicly because cases with data got official answers here, and because every subscriber deserves to know the number before paying for it. Happy to share extraction methodology with anyone who wants to measure their own account.
— F., Allegro annual subscriber