Hi HN, this is Volodymyr, Inception Co-Founder & Chief Scientist.

Today we're launching Mercury 3, our most capable production diffusion LLM.

Quality: Outperforms GPT-6 Luna and Claude Haiku 5.5 across a range of benchmarks at matched reasoning effort. Speed: 1,000+ tokens per second on widely available NVIDIA Blackwell GPUs, 4–8x faster than those models. Context: 1M tokens, up from 260K. Price: $0.10 per million input and $0.35 per million output tokens at launch.

The main takeaway is that diffusion scales. Since Mercury 1 we’ve scaled the model more than 40x in total parameters, and intelligence has gone up at every step without giving up speed. Diffusion generates tokens in parallel through iterative denoising rather than one at a time, so as reasoning models think longer per answer, the speed advantage over autoregressive models of the same size grows.

Early-access partners are running Mercury 3 in browser agents, tutoring apps, real-time search, and customer support. It’s OpenAI API compatible, and it’s also available on OpenRouter, Baseten, and Vercel.

Try it on our API with 100M free tokens.

Happy to dig into the architecture, scaling results, evals, or anything else in the comments.

I'm curious if you could comment on why your DeepSWE performance is below Haiku. This is not a dig - getting 46% vs. Haiku's 52% is still amazing. I'm just wondering if perhaps your post-training was less aggressively RL'ed on coding tasks than perhaps Haiku was. Having a cheap 1,000 tok/s option for coding work is a dream because - if it's reliable enough - you could blast through work such as high-level security reviews or finicky and repetitive refactorings that don't necessarily require SOTA performance.

Whats the model total param size and will you release the weights? What does harness integration look like? Do you have an harness? Is it good at coding? What about tool calls? Do we have to wait a fixed amount of time for every step it takes?

Google's research showed some of the speed benefits tended to drop off at larger batch sizes on an H100. Are there published batch-size vs tokens/s figures for Mercury 3?

Will you make the weights available?

Why medium in benchmarks? I've not seen that many people use other than xhigh/max on the cheap models. No low->max performance curve either. Time to task completion would also be nice!

If I may, are there plans for visual input support?

Incredible. Any luck in having a model that's multimodal in the future?

Is the model size secret?

I don't see it on Baseten. Is it special in some way?