Moonshot AI has set a deadline for its latest release, but the absence of supporting documentation on its primary distribution channel suggests builders should look past the calendar. The company’s announcement page states: “Full model weights will be released by Nov 4, 2026.” While secondary coverage dates the announcement to October 23, 2026, at approximately 17:15 UTC, other outlets report October 24 due to timezone discrepancies. Moonshot’s own page carries no visible date stamp, making the exact timing of the announcement ambiguous.
The repository that will carry those weights does not exist yet, as verified at the first-party surface. A check of the Moonshot Hugging Face organization reveals 19 existing repositories, with the most recent being Kimi-K3, last updated on September 2. There is no repository, model card, or license file for Kimi K3.1 Pro. For enterprise deployers and agent builders, the date is a signal, but the license is the operational reality.
Moonshot describes K3.1 Pro as its most capable 3T-class open-weight model to date, featuring a 1-million-token context window and significant post-training compute. It is currently available on Kimi.ai, Kimi Work, Kimi Code, and the Kimi API, with a Highspeed version that is 2-3x faster. The blog describes it as a post-trained version of Kimi K3. However, the only readable precedent for how this model will be governed is the existing Kimi K3 License. That document established a specific gate for commercial use: if a licensee operates a Model-as-a-Service business and their aggregate revenue exceeds $20 million USD over any consecutive 12 months, they must secure a separate agreement with Moonshot AI.
This $20 million threshold is a central pillar of the Club of Four convention – a group including StepFun, Meta, Moonshot AI, and Mistral – that has converged on this specific revenue gate for agent builders. Moonshot was the first of these labs to implement this structure, and the $20 million figure is calculated as a rolling 12-month aggregate of group revenue from all sources. This approach contrasts with the StepFun Oct 15 failure, where the date passed with no repository and no license, and the ongoing Mistral Large 4 countdown, which tests whether the $20 million threshold will harden into a standard. Unlike the late-October tracker pegs, Moonshot has provided a specific date on its own surface, yet the document remains missing.
There is also a technical delta to consider. Moonshot has stated that for the open-weight release, it “identified and removed cyber-related data from both training stages.” According to the lab, a checkpoint without these risk-reduction measures solved 90.5% of problems on its in-house xdev-bench-hard benchmark, while the final K3.1 Pro reaches 81.0%. In vendor-reported benchmarks, the model scores 65.7% on Terminal-Bench 4.0, compared to 66.4% for Claude Opus 5.5. The lab maintains that K3.1 Pro’s cyber capability remains behind that of frontier proprietary models available for at least three months, adhering to a principle of not releasing weights that extend the absolute frontier of cyber capability.
Builders should gate Nov 4 planning on the license fetch, not the date. The date is a target, but the license is the constraint. Until the repository appears with a valid license file, the terms of use for K3.1 Pro remain speculative. Wait for the document to surface before committing to the model; the license will dictate whether the $20 million gate remains the standard or Moonshot has introduced new requirements for its latest iteration.