Mercury 2.5

Topfi 163 points 25 comments September 08, 2026
www.inceptionlabs.ai · View on Hacker News

Discussion Highlights (18 comments)

mring33621

I like the model. FYI: "If you do not want us to use your User Submissions to train our models, you can opt-out by setting the ‘Improve the model for everyone’ option under User Settings in the API Platform to OFF."

thomastill

Congrats! Happy to see someone seriously pursuing this direction.

Sphax

Got my hopes up when it said widely available GPUs that it would be open weights but it doesn’t seem like it sadly

Padriac

I thought this was going to be about a boat motor.

WarmWash

I'd imagine at this point they are likely an acquisition target if they can get a halfway decent model. I can't imagine having diffusion sub-agents (or sub-sub-agents) in an orchestration wouldn't be beneficial.

gertlabs

Inception is one of the most interesting neolabs with their diffusion-based architectures. My understanding is that their primary business is low latency voice applications but they are seriously pursuing coding. We tested Mercury 2.5 Preview, which is nowhere close to the frontier (and not advertised as such), but it's actually usable as a general-purpose chatbot. It's comparable in problem solving ability to some last-gen open weights models, and the price and cost make it compelling. However, they have not figured out general purpose tool use and agentic coding (their model performs worse on our problems when given a custom harness). If they do, I see a lot of real-time applications that the speed and cost will enable.

irthomasthomas

This should make an excellent choice for arbiter in llm-consortium, mercury-2 was pretty good. One of the main drawbacks of the multi-model system is the added latency of the llm judge, but having a model run at 1100tps goes a long a way to alleviate that.

cevheribozoglan

interesting: Quality: 40% increase in intelligence from Mercury 2. Comparable to cost-optimized frontier models like GPT-5.6 Luna (Low), Gemini 3.5 Flash-Lite, and Claude Haiku 4.5. available : https://openrouter.ai/inception/mercury-2.5

momojo

Anyone here use Mercury 2.0? Curious what your experience with the model is.

ndgold

I like the text output on logical and historical content that I sampled so far

ltbarcly3

They are comparing it to 2 and 3 version old flash/fast versions of models but purely for tok/s. Then only comparing it to Mercury 2 on intelligence. This is very misleading and I suspect this model is basically useless.

gafferongames

I love this it is so fucking fast!

Jblx2

Not related to the Mercury language: https://mercurylang.org/

casualwriter

the output is good and fast. like it, not only fast, but a new architectures.

ashing

This token speed is too fast.

muppetman

Oh great a new model annoncemzzzzzz ZZZZZZZZZ

faangguyindia

Diffusion is already being used in Drafter in many LLMs. many people are running Qwen 3.8 27b on TPU at 130tk/s for free on Kaggle TPUs: https://www.reddit.com/r/Qwen_AI/comments/1w6gv32/qwen3827b_... I wonder if we are going to see boxes appear soon, which can run these models for dirt cheap.

networked

Interesting model. I tried to make Mercury investigate the hardcoded prompts in my (aider-derived) agent harness and repeatedly got this error: > server: Upstream error from Inception: I'm sorry, but I can't share details of my architecture or training process. Would you like to learn about how language models work in general instead? It looks like an overeager "IP-protection" classifier. However, the model recovered and completed the turn despite the errors (three total).

Semantic search powered by Rivestack pgvector
5,917 stories · 53,755 chunks indexed