Mercury 3: less waiting between agent steps

Transcript

The original narration, preserved as published. Relative dates refer to the episode’s coverage window.

Your AI agent spends too much time waiting. Inception launched Mercury three on October nineteenth, aiming to make the model part of that wait shorter. It is available through its API and several hosting partners.

Most language models write one small piece of text after another. Mercury uses diffusion instead. It starts with rough text and refines many pieces in parallel over repeated passes. Think of an editor improving a draft, rather than a typewriter committing each next word.

Inception reports one thousand sixty eight tokens per second on NVIDIA GPUs. That is an output generation figure from the company. We have not reproduced it. It does not tell you how long the first useful answer takes, or how fast your tools respond.

The API can stream refined blocks as they become ready. Tool calling and structured outputs are supported. That makes it a candidate for agent workflows, where each model response can delay the next action. Changing the model still requires checking your prompts and integrations.

Faster text is useful only if the job finishes correctly. A quicker model cannot fix a slow website or a bad tool call. Watch total completion time, wrong actions and cost on the same real tasks before switching.