Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Moonshot AI suspends new subscriptions due to Kimi K3 demand

twitter.com

Post reply on HN
Print view View original

61–70 of 118 posts

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#61

Post by KronisLV »

Currently using their 100 USD subscription, considering going up to their 200 USD subscription, because the model is approximately as capable as Opus (maybe sometimes better, sometimes worse) but less annoying to use in practice, a bit less of slop phrasing: https://blog.kronis.dev/blog/ai-slop-is-a-self-inflicted-tra...

The token limits do feel a bit less than I get with Anthropic Max 5x, but maybe that's because I've mostly been running it on Max reasoning (oh and Anthropic is also temporarily boosting the limits, who knows, it's hard to keep track of all of this stuff exactly) and there's plenty of tasks where High is still close enough in performance. The token limits still feel a bit more generous proportionally to the price compared to what I got when trying out the 65 USD tier of GLM Coding Subscription with GLM 5.2, and that was with the ZCode usage discount as well, though I did enjoy that harness.

Plus, if I decide to go with Kimi's annual pricing, then it'd come out to only around 159 USD per month or 139 EUR per month, which is really good and pretty close to what I pay Anthropic anyways: https://www.kimi.com/help/membership/membership-pricing

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#62

Post by KronisLV »

sbochins wrote: post #53
ffsm8 wrote: post #30

Earlier quoted context omitted.

Moonshot AI has two subscriptions archetypes and the one they link to from their main page is the subscription for the web interface/research/agents/OpenClaw (that they host for you) There is a small link below the tiles for these plans saying something "looking to use it for code? Use Kimi code" and upon clicking you'll get a basically identically looking subscription page with different sub prices and more quota No…

That doesn’t appear to be the case anymore. They just have one set of plans: Allegreto, modereto, etc which apply to both the chat app and the coding apps.

Can confirm, I see these monthly prices on both pages:

Moderato: 19 USD or 15 USD annually

Allegretto: 39 USD or 31 USD annually

Allegro: 99 USD or 79 USD annually

Vivace: 199 USD or 159 USD annually

However, they're saying that the plans might get split up again:

> New Membership Plans Coming Soon

> Kimi and Kimi Code benefits will be separated. Existing subscribers are unaffected.

> You can still buy the current plan before launch.

Same as with the Tweet:

> Going forward, we'll also split membership into two more focused plans: Kimi Membership for Kimi Web, App, and Work; and Kimi Code Membership for coding workflows. This will help us match compute more precisely and keep the experience stable.

Problem is I don't know whether to pull the trigger on the annual Vivace now or wait for after the split - whether it's gonna be a cash grab afterwards on the account of the demand, or whether I might save some money if I buy it after the split.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#63

Post by KronisLV »

kburman wrote: post #24

They could've simply cut the usage limits, removed K3 from the plan, added a weekly cap, and called it "fair usage." Anthropic has been running that playbook for a while now, and they're a trillion-dollar company.

To be honest, they have both 5 hour caps, weekly caps and also monthly caps:

  Total usage
  12.85%
  Resets in 2026-08-17
  
  5-hour usage
  71.97%
  Resets in 07-20 03:14
  
  7-day usage
  31.29%
  Resets in 07-24 10:14
Still, I can respect the commitment to not over provisioning.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#64

Post by jdthedisciple »

kamranjon wrote: post #52
thevinter wrote: post #15

Personal anecdote: I exhausted my Claude usage yesterday so I decided to spend 20$ to try Kimi while I was at it. Logged in, paid, downloaded Kimi Code, set it to use K3 and prompted something along the lines of: "Check this repository and find all the settings that can be passed as input related to hardware, I/O, thread control or networking. Produce a report". It thought for about 12 minutes and then told me I had…

So I am likely coming from a completely different world because I use entirely self hosted models - but is it really common in your workflows to just wait for 12 minutes without any feedback? I am constantly watching my model and following the path it’s taking and cutting it off or steering it if it’s headed down a dead path. I was just curious if this is really common to just have no feedback for 12 minutes?

I recently had GPT 5.6 work on something for 54 minutes while I went to sleep

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#66

Post by kzrdude »

vblanco wrote: post #3

Ive been pleasantly surprised with the quality of this model. Its really good at code review and PR review. But right now due to them being so overloaded + this being a big model, its SO slow. It takes forever to do a relatively simple code review.

Kimi K3 is on the opencode-go plan's price list now. I haven't confirmed it, but I guess that means it's available. (Not in Zen.)

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#67

Post by ezekiel68 »

I tried it through siliconflow (I have no relationship to them other than as a normal customer) with the command line Pi agent and it's pretty good at adding features to a rust lang code repo. Compared to Deepseek V4 Pro there, M3 is about 3X the cost for non-cached input tokens and 5X the cost for output tokens. (both offering a 1M token context window). It certainly wasn't worh 5X the output of the Deepseek model for my uses, though.

I couldn't find any info on how they (siliconflow) quantized the model. I think some of the other ineference service aggregators might offer it as well, already.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#69

Post by wingworks »

satvikpendem wrote: post #31
thevinter wrote: post #15

Personal anecdote: I exhausted my Claude usage yesterday so I decided to spend 20$ to try Kimi while I was at it. Logged in, paid, downloaded Kimi Code, set it to use K3 and prompted something along the lines of: "Check this repository and find all the settings that can be passed as input related to hardware, I/O, thread control or networking. Produce a report". It thought for about 12 minutes and then told me I had…

Codex works for this, it'll continue thinking and will answer the prompt even if your limit is reached.

I feel like this is the right way to do it. Especially if you're using your own credits. Unless it's obnoxiously long task.

So often it'll cut off just as it's about to finish.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#70

Post by roncesvalles »

kamranjon wrote: post #52
thevinter wrote: post #15

Personal anecdote: I exhausted my Claude usage yesterday so I decided to spend 20$ to try Kimi while I was at it. Logged in, paid, downloaded Kimi Code, set it to use K3 and prompted something along the lines of: "Check this repository and find all the settings that can be passed as input related to hardware, I/O, thread control or networking. Produce a report". It thought for about 12 minutes and then told me I had…

So I am likely coming from a completely different world because I use entirely self hosted models - but is it really common in your workflows to just wait for 12 minutes without any feedback? I am constantly watching my model and following the path it’s taking and cutting it off or steering it if it’s headed down a dead path. I was just curious if this is really common to just have no feedback for 12 minutes?

Usually, the longer the AI works on something the crappier its output because that means the context is getting filled up.

If my AI prompt takes more than 5 minutes to execute, I'm almost certain to stop it and break up the task or be more specific about what files it should look at or what subtask it should tackle first. The people who let it run for hours are absolutely not getting anything worth keeping in the end.

Post reply on HN