I have trouble thinking of tasks that "require" this kind of speed. The usual trade-off is between price and quality/reliability.

It's not really all that fast, for most things it's full seconds or at least a significant portion of a second. As computing goes that's quite slow and there are many things that require much faster speeds than this. However compared to the typical LLM it's quite speedy and opens some new doors for real-time-ish scenarios.

Speed matters most when people are waiting for a response, when information loses value by the second, or when agents make dozens of calls to complete a task.

Customers are already using Mercury 3 for browser use agents, interactive education, real-time search agents, customer support, and more.

in my case, I'm hoping that the time-to-first-token isn't so bad that I can have my admin users parse some information in the web ui pretty quickly (a very specific use case, i know)

The time isn’t too relevant for let’s say coding tasks. But if you’re doing user facing, or processing live-data (logs for example) the speed becomes important