AI agents are spreading rapidly through the business world, yet many organizations still struggle to prove whether they deliver a meaningful return on investment.
Sam Altman says the AI singularity is here. Learn what the term means, what evidence supports the claim and why leading researchers remain divided.
Chinese AI startup Moonshot AI, creators of the increasingly famous “Kimi K” family of powerful, open AI models, today released the full weights for its largest and most performant version yet — Kimi K3. But enterprises evaluating the model should read the attached custom Kimi K3 usage license as carefully as the benchmark charts.
VentureBeat previously covered Kimi K3 when it debuted through Moonshot’s hosted API earlier this month, including its 2.8 trillion-parameter architecture, one million-token context window and frontier benchmark performance. Today’s announcement completes that rollout with the release of the full model weights, a 47-page technical report documenting its training innovations and obstacles, and much of the infrastructure required to run the model independently.
That includes the complete 2.8 trillion-parameter Mixture-of-Experts model, inference infrastructure, optimized attention kernels, MoE communication libraries and deployment components aimed at researchers and enterprise developers who want to self-host the system rather than consume it exclusively through an API.
Moonshot is also releasing implementation support for ecosystems including vLLM and SGLang, alongside a technical report detailing the architectural innovations behind the model, including Kimi Delta Attention, Attention Residuals and Stable LatentMoE. Together, those techniques underpin what the company describes as the world’s first open 3T-class model, activating 104 billion parameters from a pool of 896 experts while supporting native multimodal reasoning and a one million-token context window.
While Kimi K3’s license grants broad rights to developers and even enterprises to download, modify and deploy the model for commercial purposes — a win for those seeking low-cost, frontier-level AI they can control and run offline — it also imposes some added obligations on larger companies and AI service providers not found in traditional open-source licenses like Apache 2.0 or MIT.
Here’s the text of the new Kimi K3 License in full:
Permission is hereby granted, free of charge, to any person (the “Licensee”) obtaining a copy of this software — including the model weights, parameters, configuration files, inference and training code, and associated documentation (collectively, the “Software”) — to deal in the Software without restriction. This includes, without limitation, the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software; to run, deploy, fine-tune, or otherwise modify the Software and create derivative works from it; and to permit persons to whom the Software is furnished to do so, in each case subject to the following conditions:
1. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. Licensee’s use of the Software must comply with applicable laws and regulations.
2. “Model as a Service” means giving a third party access to language model inference or fine-tuning (e.g., via API) in a manner that allows such third party to exercise meaningful control over the inputs, parameters, or training data. This does not include (a) end-user products with model capabilities solely embedded within specific features or harnesses, or (b) mere relaying of requests to models hosted by others.
If the Licensee or any of its affiliates operates a Model as a Service business, and the aggregate revenue of the Licensee and its affiliates exceeds 20 million US dollars (or the equivalent in other currencies) in total over any consecutive 12 months, the Licensee must enter into a separate agreement with Moonshot AI before using the Software or its derivative works for any commercial purpose.
3. If the Software (or any derivative works thereof) is used for any of the Licensee’s commercial products or services that have more than 100 million monthly active users, or more than 20 million US dollars (or equivalent in other currencies) in monthly revenue, “Kimi K3” must be prominently displayed on the user interface of such product or service.
4. The requirements set forth in Sections 2 and 3 do not apply to: (a) internal use of the Software, defined as any use that does not make the Software, its outputs, or its underlying capabilities available to third parties; or (b) any use of the Software accessed through Moonshot AI’s official products or certified inference partners.
The most significant clause is 2., as it governs companies operating what Moonshot defines as a “Model as a Service.”
That wording is notable because it does not limit the revenue calculation to products built on Kimi K3. Instead, it references the aggregate revenue of the licensee and its affiliates, potentially bringing even smaller companies that are part of larger parents into the requirement that they must commercially license the model from Moonshot, pending the parent firm generates revenue of $20 million or more per year.
Importantly, the revenue threshold alone does not appear to trigger the requirement. The clause applies specifically to organizations operating as a “Model as a Service” business, making that definition central to determining whether a commercial agreement is required.
Therefore, simply using the model as a customer service chatbot or other public-facing backend shouldn’t trigger a commercial license. However, in clause 3, the license separately requires attribution once a commercial deployment reaches significant scale:
“If the Software… is used for any of the Licensee’s commercial products or services that have more than 100 million monthly active users, or more than 20 million US dollars in monthly revenue, ‘Kimi K3’ must be prominently displayed on the user interface.”
For enterprise software vendors, AI copilots and consumer applications, that branding requirement may prove just as significant as the revenue threshold. Companies that typically abstract away the underlying model may instead need to disclose it directly within their products.
But, if your enterprise is sticking to using Kimi K3 internally as an employee tool for information retrieval, creating spreadsheets and documents, or answering employee questions, Moonshot offers a significant carve out, stating that clauses 2 and 3 “do not apply to: (a) internal use of the Software, defined as any use that does not make the Software, its outputs, or its underlying capabilities available to third parties.”
The licensing provisions quickly became one of the dominant topics of discussion following the release of the model weights.
AI researcher Nathan Lambert, previously the co-leader of the Olmo family of open models at AI startup Ai2, summarized the issue in a post on X:
“Kimi K3 license. It’s inspired by MIT but distinctly non-commercial, where any company making over $20M/yr must get a specific commercial deal (and display Kimi K3 if over 100M users or $20M/mo revenue).”
Lambert’s assessment reflected what many developers noticed as they dug into the newly published license: while Kimi K3 offers unrestricted access to the model weights for researchers, startups and many enterprises, commercial obligations become significantly more complex for larger organizations.
The broader community reaction was largely positive toward the release itself. Developers praised Moonshot for publishing not only the weights but also supporting infrastructure, including attention kernels, MoE communication libraries and agent tooling, viewing the release as a significant contribution to the open-weight AI ecosystem.
Others highlighted the rapid pace of ecosystem support, with inference projects such as vLLM and SGLang, along with cloud providers and infrastructure partners, moving quickly to support Kimi K3 deployments.
At the same time, discussion centered on two practical caveats. One was licensing: many developers argued the model is more accurately described as open weight than fully open source, given the commercial conditions attached to larger deployments. The other was operational.
At roughly 1.5 TB of model weights, Kimi K3 remains a system aimed primarily at well-resourced organizations capable of operating large-scale inference infrastructure, even as reports emerged of successful deployments on clusters of consumer RTX 5090 GPUs.
Moonshot is far from the first frontier AI developer to embrace an “open, but not completely open” licensing strategy.
Meta’s Llama family, for example, has long been distributed under its own community license requiring a commercial agreement for those building with the model and exceeding 700 million monthly users, rather than a traditional open-source software license. Other frontier model developers have likewise adopted bespoke licensing terms governing redistribution, commercial use or attribution.
Kimi K3 follows that broader trend, albeit with a different mechanism. Rather than broadly restricting redistribution, Moonshot ties certain commercial rights to company scale.
Organizations operating a Model-as-a-Service business above specified revenue thresholds must negotiate a separate commercial agreement, while the largest commercial deployments must visibly attribute Kimi K3 within their products.
For enterprises, the practical implication is that “open weights” and “open source” are becoming increasingly distinct concepts. Downloading and modifying frontier models may be straightforward; understanding the legal conditions attached to commercial deployment increasingly is not.
For CIOs, chief AI officers and engineering leaders, the first step is to determine how the organization intends to use Kimi K3 before evaluating its technical performance.
If the model will remain entirely inside the organization—for example, supporting developers, researchers, legal teams or internal productivity workflows—the published license appears substantially more permissive. Those deployments may qualify as internal use under Moonshot’s terms, avoiding the commercial licensing provisions that apply to customer-facing AI services.
Organizations planning to build products on top of Kimi K3 should take a different approach.
Legal, engineering and product leaders should determine whether the planned deployment constitutes “Model as a Service” under the license, whether the company or its affiliates exceed the $20 million revenue threshold, and whether future growth could trigger the requirement to negotiate a commercial agreement with Moonshot.
Companies expecting products to reach more than 100 million monthly active users—or more than $20 million in monthly revenue—should also evaluate the license’s attribution requirement and how it fits with existing branding, contractual commitments and white-label offerings.
More broadly, Kimi K3 illustrates a transition taking shape across frontier AI. As the industry’s most capable models increasingly become available as downloadable weights instead of exclusively through hosted APIs, enterprises will need to evaluate licensing terms with the same rigor they apply to benchmarks, security reviews and infrastructure planning.
The next competitive battleground may not simply be whether AI models are open or closed, but the increasingly nuanced legal frameworks that determine who can commercialize them, under what conditions and at what scale.
Sam Altman calls the OpenAI -Hugging Face hack a singularity. It wasn’t! The model did what it was told. OpenAI forgot the fence. What business leaders should understand.
If your business depends on people clicking through to web pages, the last two years have been brutal. Pew Research Center tracked the browsing behavior of 900 U.S. adults and found that when Google shows an AI summary, users click a traditional result just 8% of the time, roughly half the 15% rate when no summary appears. Links cited inside the AI answers themselves fare worse: users click on them only about 1% of the time.
This has had a huge impact on publishers. Chartbeat data reported by Axios shows page views from Google Search fell 34% across its publisher network between December 2024 and December 2025, and small publishers have lost roughly 60% of their search referral traffic over two years. Business Insider’s organic search traffic dropped 55% over three years, and some smaller publishers have already shut down. Chatbot referrals, meanwhile, still account for less than 1% of publisher page views despite growing more than 200% in a year.
The story in publisher circles has been simple: AI is killing the web. But recent developments show the reality is more nuanced.
Similarweb’s 2026 Generative AI Landscape report reveals that while AI platforms send fewer humans to web pages relative to the answers they generate, the AI systems themselves are consuming the web at an accelerating rate in the form of searching the web on the user’s behalf to answer their questions. The share of ChatGPT answers containing live web citations grew more than fivefold in under a year, reaching 6.8% of all answers by May 2026. In some categories like travel, it is as high as 22.6%.
Every major AI search product fetches live pages from search indexes and synthesizes answers from them, which means the quality of AI answers depends directly on the health of the content layer underneath. As Lily Ray, VP of SEO and AI search at Amsive, puts it in the Similarweb report, if your organic visibility dips, your AI search visibility follows, because the models are less likely to find your content.
This has created a troublesome feedback loop. AI answers are built on an information supply chain whose funding model, ad-supported clicks, is collapsing primarily because of AI answers. A critical question for the continued viability of the open web is whether some alternative business model will work, and what the model will be.
There is some early data showing where things may be going. Following ChatGPT’s May 7 search update, which surfaced prominent clickable brand links inside answers, referral traffic from ChatGPT surged by 157% in a week. But the shape of that traffic changed: the share of referrals landing on homepages more than doubled, from roughly 25% to nearly 60%.
Traditional search sent users to specific articles and deep pages tied to specific queries. AI referrals increasingly deliver a pre-informed visitor to a brand’s front door. The chatbot does the researching and comparing; the human arrives ready to act. Similarweb’s data shows AI-recommended brands receive two to four times as many subsequent visits as competitors that were not recommended.
Money follows the behavior. Sponsored results appeared in 26% of U.S. desktop ChatGPT conversations in June 2026, up from 14% just a month earlier, per Similarweb’s ad intelligence data. Two-thirds of those ads appear after the second prompt, targeted on conversation context rather than a keyword. Click-through sits around 0.50%.
The traditional search engine keyword auction is being replaced by something new: paid placement inside a conversation, targeted on accumulated context. That is a direct challenge to the auction Google has run, and dominated, for two decades.
Google is not a bystander here; it is simultaneously the incumbent being disrupted and one of the largest players in the disruption. AI Overviews now appear in a growing share of Google searches, more than 40% by May 2026 per Similarweb, and visits to Google’s conversational AI Mode have climbed steadily since launch. Google is cannibalizing its own click economy rather than ceding the territory.
But the ground was already shifting under Google’s core business. eMarketer projects Google’s share of U.S. search advertising will fall below 50% in 2026, the first time since roughly 2004. The biggest chunk of that lost share is going to Amazon, whose sponsored product searches count as search advertising and which are growing three times as fast as Google’s. Conversational ads are barely a rounding error in that accounting right now, but they open up a second front in a war Google has got used to not needing to fight.
Meanwhile, more structural shifts are coming for Google. A federal court entered final judgment in the DOJ search antitrust case in December 2025, imposing remedies that bar exclusive default agreements and require Google to share search data with qualified competitors. Google appealed in January 2026; the DOJ cross-appealed seeking stronger remedies. However the appeals resolve, the de facto arrangement that made Google the web’s tollbooth, defaults everywhere and a closed index, is ending just as conversational advertising is changing the landscape.
The competitive landscape that results is genuinely new. OpenAI, Google, Perplexity, and Microsoft are now competing not just for users but for the advertising demand that funded the open web, and none of them, including Google, controls the new surface the way Google controlled the old one.
It’s not clear whether this new model helps or hurts the web. The web as a destination for human attention is shrinking, and the ad-supported publishers built for that web are in real trouble. The web as a machine-readable substrate is growing in importance, and a new referral and advertising economy is forming that routes value to brands rather than to content pages.
The problem for publishers may be that they are powerless to influence the outcome. Ahrefs, analyzing over a billion data points across its studies, found that 67% of ChatGPT’s most-cited sources are things marketers cannot influence: Wikipedia alone accounts for nearly 30%. And 28.3% of ChatGPT’s most-cited pages have zero Google organic visibility, suggesting the retrieval layer is only partially tethered to traditional search, a complication for anyone assuming SEO success translates cleanly.
According to three independent datasets, in the new world, the pages AI systems cite and the pages AI systems send humans to are different pages doing different jobs. That’s a big change, and most teams are still optimizing for the old world.
Similarweb’s data shows 65% of ChatGPT-cited URLs sit two or three folders deep in a site, while 58.8% of referral traffic lands on homepages. Ahrefs found the same split in its own analytics: more than 80% of its AI referral traffic goes to its homepage, product pages, and free tools, not its extensive editorial content. And a Previsible analysis of 6.77 million AI-referred sessions found a third destination: 28.8% of ChatGPT referrals land on internal site search pages, a navigation surface most publishers have long neglected precisely because Google searches were doing it for them.
The right action to take is to audit your search traffic patterns. Pull your AI referral logs and whatever citation data you can access, and map which pages are being quoted as evidence versus where visitors actually enter. If it looks like you’re in the new world, there are three clear things to do:
Deep pages, documentation, comparisons, and benchmarks should be structured to be citable: specific claims, clear headings, and descriptive URLs (Ahrefs found pages with natural-language URL slugs get cited at 89.78% versus 81.11% without).
The homepage should be rebuilt for a visitor who arrives with context from a conversation rather than from a blue link. They already know you have what they need, get them to it as quickly as possible.
And internal search, a neglected feature on most sites, is now an acquisition surface that deserves real UX investment.
There’s a lot that’s still unknown or in flux here. But the underlying shift is confirmed by every independent source that has looked: the click economy is not coming back, and the entities that learn to be quoted by machines and to convert the humans those machines send will own whatever the web becomes next.
In the second half of 2026, tech leaders are challenged with readying their organizations for an AI-intensive, interconnected and security-conscious business environment.
One of the best interfaces in the home security market gets a major usability upgrade and the Gen 3 Outdoor Camera Pro brings behavior-based detection to outdoor security
Over the weekend, Reddit user -void1 posted an alarming discovery on the r/ClaudeAI subreddit: some conversations that users of Anthropic’s Claude AI chatbot had made “shareable” via a link were being indexed by Google Search, and could be clicked on and accessed by seemingly anyone.
The conversation took off on the social networks X and Reddit, the latter with thousands of upvotes and comments, many expressing concern about user privacy and information security, and the additional finding by users that shared Claude Artifacts — including interactive applications, dashboards, documents and other AI-generated work products — were also appearing in Google Search results.
VentureBeat independently verified that some Claude Artifacts not shared directly with us were indeed searchable and accessible via Google. We could not access any shared conversations.
By Sunday morning, many of the original Google search results for shared Claude conversations appeared to have disappeared or become significantly harder to find, suggesting either Google, Anthropic or both had begun taking action.
The exposure could carry broader implications for enterprise users. Anthropic has increasingly positioned the feature as a collaborative workspace for building and sharing software, dashboards, documents and other business assets rather than simply chatbot responses.
I have reached out to Anthropic for comment and will update this article when the company responds.
Reddit user -void1 posted to r/ClaudeAI on July 25, 2026, demonstrating that the Google query site:claude.ai/share surfaced numerous publicly accessible Claude conversations.
Screenshots shared across Reddit and X showed Google returning pages from Claude’s /share URLs, while other users reported finding conversations containing cryptocurrency wallet creation, legal questions, résumés and internal business discussions.
While many users expressed concern that conversations they believed were effectively “unlisted” could become discoverable through public search engines, others argued the behavior reflected the expected consequences of creating publicly accessible share links rather than a software vulnerability.
Indeed, Anthropic requires the user themselves to go into Claude’s options and select to make a conversation or Artifact shareable to others with the link, warning them it will be accessible to anyone with it, over multiple dialog boxes. It is similar to sharing a Google Doc link, where the user must also select the option — it is not enabled by default.
On July 26, X user Om Patel, founder of research firm BigIdeasDB, posted allegingthat searches such as site:claude.ai/public/artifacts surfaced publicly shared applications, dashboards, reports and documents.
Screenshots circulating online appeared to show search results referencing internal-looking proposal documents and other business materials. Another widely circulated post warned that users often interpret “Anyone with the link” as equivalent to an unlisted YouTube video—accessible only if someone possesses the URL—not necessarily as content eligible for indexing by public search engines.
VentureBeat independently verified that multiple third-party Claude Artifacts appeared in Google Search results for the query site:claude.ai/public/artifactslaunch and were accessible without authentication, despite the URLs not being previously known to the reporter.
However, VentureBeat has not independently verified the full volume or representativeness of the examples circulating on social media.
The reports are particularly significant because Artifacts has become one of Anthropic’s flagship product initiatives.
First introduced alongside Claude 3.5 Sonnet in June 2024, Artifacts transformed Claude from a conventional chatbot into a collaborative workspace capable of generating interactive web applications, dashboards, visualizations, documents, games and other live software alongside a conversation.
VentureBeat previously described the launch as potentially marking the beginning of an “interface war” among AI companies, shifting competition from raw model performance toward collaborative AI workspaces.
Anthropic subsequently rolled Artifacts out to all Claude users, saying tens of millions had already been created, before expanding the concept again this year into Claude Code.
That update allows engineering teams to publish live HTML dashboards and interactive project workspaces directly from coding sessions, making Artifacts an increasingly important part of Anthropic’s enterprise strategy.
That broader functionality raises the potential stakes if publicly shared Artifacts were also being indexed. Unlike ordinary chat transcripts, Artifacts can contain interactive software prototypes, engineering dashboards, planning documents, product mockups, data visualizations and other work products organizations increasingly rely on to collaborate across technical and business teams. If those pages become searchable through public search engines, the exposure could extend well beyond conversational text.
Importantly, nothing so far suggests attackers gained access to private Claude accounts or conversations.
Rather, the controversy centers on conversations and Artifacts that users explicitly chose to share publicly via Claude’s sharing tools.
The dispute instead is whether users reasonably understood those shared pages could become discoverable through public search engines rather than only by recipients possessing the link.
Technically, pages that are publicly accessible without authentication can generally be indexed by search engines unless publishers explicitly prevent crawling through mechanisms such as noindex directives or other indexing controls.
Several Reddit commenters noted that Claude’s long, randomly generated share URLs are effectively impossible to guess. Instead, search engines typically discover them only after links appear somewhere they are permitted to crawl, such as public websites, forums or social media posts. Others questioned exactly how Google initially discovered so many Claude share URLs.
The issue also illustrates a growing challenge for AI companies as chatbots evolve into collaborative workspaces for creating software, documents, dashboards and business applications.
Features originally designed to make sharing AI-generated work easier now increasingly expose assets that may carry significantly more business value than a simple conversation.
As enterprises adopt AI as a platform for building internal tools and workflows, the distinction between “shared by link” and “publicly discoverable through search” becomes far more consequential.
Anthropic is far from the first AI company to confront the distinction between “shared” and “searchable.”
Reddit users quickly pointed out that OpenAI previously faced criticism after publicly shared ChatGPT conversations became discoverable through Google, prompting similar debates over whether “share by link” should imply a publicly indexed webpage or something closer to an unlisted document.
Anthropic’s situation also echoes an incident involving Google’s pre-Gemini AI assistant, Bard, in September 2023. SEO consultant Gagan Ghotra discovered that Google Search had begun indexing shared Bard conversation links, warning that users could mistakenly assume they were sharing conversations only with intended recipients rather than making them discoverable through search.
Google later responded publicly that it did not intend for shared Bard chats to be indexed and said it was working to block them from Google Search while emphasizing that only conversations users explicitly chose to share were affected.
Together, the Bard, ChatGPT and now Claude episodes suggest AI companies continue to wrestle with the boundary between content that is technically public on the web and users’ expectations that “share with a link” behaves more like an unlisted Google Doc or YouTube video than a webpage eligible for indexing by search engines.
For organizations deploying generative AI broadly across employees, the distinction between “shared with a link” and “publicly discoverable through search” is not merely semantic. It can determine whether an internal engineering dashboard, financial model, product roadmap, customer-facing prototype or AI-generated application remains effectively private—or becomes visible to anyone using a search engine.
Whether this ultimately proves to be a technical indexing oversight, a mismatch between product design and user expectations, or some combination of both, the episode serves as another reminder that AI products are increasingly functioning less like chatbots and more like collaborative operating systems for knowledge work.
As those platforms begin hosting internal dashboards, software prototypes, financial analyses, business planning documents and increasingly sophisticated enterprise applications, seemingly small decisions about how shared links behave can have outsized consequences for enterprise security, product design and user trust.
Enterprise leaders should consider taking several practical steps:
Audit existing shared AI content: Review shared conversations, Artifacts and other publicly accessible AI-generated assets to determine whether they should remain available or be unpublished.
Clarify what “Share” actually means to your ENTIRE organization: Don’t assume employees understand the difference between “accessible by link” and “discoverable through search.” Update internal guidance to explain how each AI platform handles shared content.
Treat AI platforms like collaboration software: Apply the same governance you use for Google Docs, Microsoft 365, Slack, GitHub, Notion or SharePoint—including policies around sharing sensitive intellectual property, customer information and regulated data.
Prefer authenticated enterprise workspaces for sensitive information: When possible, keep confidential projects, code, financial models and customer data inside enterprise accounts with identity-based access controls instead of publicly accessible links.
Review vendor defaults and sharing controls: As AI platforms evolve rapidly, administrators should periodically revisit default sharing settings, retention policies and indexing behavior rather than assuming they remain unchanged after new feature releases.
For now, it appears Anthropic has begun limiting the visibility of at least some shared pages in Google Search, though reports suggest cached copies, archived pages and indexing by other search engines may persist for some content. Enterprises that have relied on Claude’s sharing features may wish to review existing shared conversations and Artifacts while Anthropic’s investigation continues.
AI’s ability to accelerate research cycles, in and of itself, will be crucial for freeing researchers for higher-level tasks.
Technology creates consistency. People create connection. The strongest customer experiences require both.