Mercury 2 ditches sequential decoding for parallel refinement. As the first reasoning diffusion LLM, it generates tokens simultaneously to hit 1,000+ tokens/sec. This delivers reasoning-grade quality inside tight latency budgets for your agentic loops.
Diffusion models, or dLLMs, are currently one of the most promising paths outside the standard autoregressive route. Everyone is exploring this space right now, from @Seed Diffusion to @Dream 7B and even @Gemini Diffusion. But the standout player is definitely Inception with their Mercury series, and they just pushed their second generation live.
The architectural shift changes everything about latency. Mercury 2 abandons standard left-to-right sequential decoding. Parallel refinement drives the generation instead. Think of the model less like a typewriter printing one token at a time and more like an editor revising a full draft simultaneously.
This parallel approach makes the inference insanely fast. Hitting over 1,000 tokens per second gives you a 5x speedup over leading speed-optimized models. This fundamentally alters the equation for multi-step agentic loops or real-time voice apps where latency compounds across every single step.
The API is strictly OpenAI compatible, so you do not need to rewrite any code. You can apply for early access to the API or just chat with it right now to feel the raw speed of a next-gen diffusion model.
@zaczuo Incredible stuff. Just applied for early access!
Report
Parallel refinement instead of sequential decoding is a bold technical shift. 1,000+ tokens per second with reasoning grade quality is not a small claim, especially for agentic loops where latency compounds fast.
From a positioning angle, though, the speed story is clear, but the practical transformation could be sharper. Is the real win lower infra cost, smoother agent chains, or enabling use cases that were previously too slow to ship?
You could test framing Mercury 2 around one concrete before and after scenario, like what becomes possible at 1,000 tokens per second that was painful before.
Curious, what is the first production use case where teams feel this speed difference most viscerally?
Congratulations! What do you mean by 'reasoning' for a diffusion llm? Do you have a paper/blog post you could point me to?
Report
The diffusion-style reasoning approach here is really interesting. If it can reduce latency in multi-step agent workflows while still maintaining strong reasoning quality, that could be very valuable for production systems.
The ability to handle planning, retrieval, and verification pipelines efficiently also makes it feel well suited for real agent-based applications.
Curious what kinds of real-world workloads you saw the biggest performance improvements on while testing Mercury 2.
Congrats on the launch.
Replies
Flowtica Scribe
Hi everyone!
Diffusion models, or dLLMs, are currently one of the most promising paths outside the standard autoregressive route. Everyone is exploring this space right now, from @Seed Diffusion to @Dream 7B and even @Gemini Diffusion. But the standout player is definitely Inception with their Mercury series, and they just pushed their second generation live.
The architectural shift changes everything about latency. Mercury 2 abandons standard left-to-right sequential decoding. Parallel refinement drives the generation instead. Think of the model less like a typewriter printing one token at a time and more like an editor revising a full draft simultaneously.
This parallel approach makes the inference insanely fast. Hitting over 1,000 tokens per second gives you a 5x speedup over leading speed-optimized models. This fundamentally alters the equation for multi-step agentic loops or real-time voice apps where latency compounds across every single step.
The API is strictly OpenAI compatible, so you do not need to rewrite any code. You can apply for early access to the API or just chat with it right now to feel the raw speed of a next-gen diffusion model.
Fluent
@zaczuo Incredible stuff. Just applied for early access!
Parallel refinement instead of sequential decoding is a bold technical shift. 1,000+ tokens per second with reasoning grade quality is not a small claim, especially for agentic loops where latency compounds fast.
From a positioning angle, though, the speed story is clear, but the practical transformation could be sharper. Is the real win lower infra cost, smoother agent chains, or enabling use cases that were previously too slow to ship?
You could test framing Mercury 2 around one concrete before and after scenario, like what becomes possible at 1,000 tokens per second that was painful before.
Curious, what is the first production use case where teams feel this speed difference most viscerally?
Adjust Page Brightness - Smart Control
this is just awesome!