Mira Murati's lab just shipped the biggest open-weight model the US has produced

Mira Murati's lab just shipped the biggest open-weight model the US has produced

Good morning ๐Ÿ‘‹ Mira Murati just did the one thing OpenAI won't: she gave away the weights.

In today's issue:

Get tomorrow's issue in your inbox.

One concise AI brief, sent after the signal clears the noise.


๐Ÿ”ญ THE ONE THING

๐Ÿ”“ Mira Murati's lab just shipped the biggest open-weight model the US has produced

Thinking Machines, the lab Murati built after leaving OpenAI as CTO, released Inkling on July 15: 975 billion parameters total, 41 billion active via mixture-of-experts, trained on 45 trillion tokens of text, image, audio, and video, with a context window up to 1M tokens. Full weights are live on Hugging Face under Apache 2.0, no waitlist, alongside a smaller preview called Inkling-Small (276B total, 12B active) that the lab says performs competitively despite the much lighter active load. Treat that claim as a vendor benchmark until someone outside the lab reproduces it. Still, at 975B parameters this is the largest open-weight model any US lab has shipped, and giving away the weights instead of gating an API is a direct rebuke of the approach Murati's old employer takes. For builders it's a frontier-class model you can fine-tune and own, though running the full-size checkpoint means you need the kind of GPU cluster only a handful of companies have lying around.


๐Ÿง  MODELS & RELEASES


๐Ÿ”ฌ RESEARCH HIGHLIGHTS


๐Ÿš€ AI STARTUPS


๐Ÿ›๏ธ POLICY & REGULATION


๐Ÿ› ๏ธ TRY THIS

Stress-test the new 975B-param open-weight model before you touch production

1. Pull the weights, or the hosted endpoint if self-hosting 975B params isn't your week, and read the license terms yourself instead of trusting the headline.

2. Run it against your own eval set, not a public benchmark. Your prompts, your edge cases.

3. Price out tokens and latency against whatever you're running now. A model this size changes your inference math even when quality holds steady.

4. If it wins, swap your lowest-risk endpoint first and watch error rates for a week before going wider.

Prompt: Compare these two model outputs on [task] for accuracy and tone, score 1-10 each. Flag any response that contradicts our documented API behavior. Output as a table.

Worth a look


๐Ÿ”— QUICK LINKS


That's the one worth acting on today. See you tomorrow.

Pradeep Perugu

Get inovAIte in your inbox.