Latency · best for

Top picks for Real-Time Chat (2026)

Models tuned for sub-second response. Ranked from 425 live models on the OpenRouter catalog, weighted for low latency, low cost.

Updated 2026-09-07 · prices checked at this morning's rebuild

What this is Ranked by capability match + real benchmark scores (Aider Polyglot, Artificial Analysis Intelligence Index) + live pricing. Models need the right specs for Real-Time Chat, then benchmark performance refines the order. Full methodology →

Which should you use? Meta: Muse Spark 1.3 Contributor tops this ranking on blended score. If cost drives the decision, inclusionAI: Ling 3.0 Flash is the cheapest of the leaders at $0.02/M input. To prototype without spending, MiniMax: MiniMax M3 (free) is the best free option ranked here.

#ModelScoreIn / 1MOut / 1MContext
1 Meta: Muse Spark 1.3 Contributormeta/muse-spark-1.3-contributor 118 $0.10 $0.20 1,048,576 Details →
2 Z.ai: GLM Flash Latest~z-ai/glm-flash-latest 118 $0.07 $0.25 1,310,720 Details →
3 Z.ai: GLM 5.3 Flashz-ai/glm-5.3-flash 118 $0.07 $0.25 1,310,720 Details →
4 Meta: Muse Spark 1.2 Contributormeta/muse-spark-1.2-contributor 118 $0.10 $0.20 1,048,576 Details →
5 Qwen: Qwen3.7 Flashqwen/qwen3.7-flash 118 $0.03 $0.13 1,000,000 Details →
6 inclusionAI: Ling 3.0 Flashinclusionai/ling-3.0-flash 118 $0.02 $0.06 262,144 Details →
7 Nex AGI: Nex-N2-Mininex-agi/nex-n2-mini 118 $0.03 $0.10 262,144 Details →
8 MiniMax: MiniMax M3 (free)minimax/minimax-m3:free 118 Free Free 1,048,576 Details →
9 NVIDIA: Nemotron 3 Nano Omni (free)nvidia/nemotron-3-nano-omni-30b-a3b-reasoning:free 118 Free Free 256,000 Details →
10 Xiaomi: MiMo-V2.5xiaomi/mimo-v2.5 118 $0.14 $0.28 1,050,000 Details →
11 Google: Gemma 4 26B A4B google/gemma-4-26b-a4b-it 118 $0.07 $0.34 262,144 Details →
12 Google: Gemma 4 26B A4B (free)google/gemma-4-26b-a4b-it:free 118 Free Free 262,144 Details →
13 Google: Gemma 4 31Bgoogle/gemma-4-31b-it 118 $0.09 $0.34 262,144 Details →
14 Google: Gemma 4 31B (free)google/gemma-4-31b-it:free 118 Free Free 262,144 Details →
15 Qwen: Qwen3.5-9Bqwen/qwen3.5-9b 118 $0.10 $0.15 262,144 Details →
AI Apps OnSpace AI Build and deploy AI-powered apps without code.
Try free →

Affiliate link. PicksByModel may earn a commission at no extra cost to you.

How we ranked these

For Real-Time Chat, we weight models on low latency, low cost. Scores combine each model's public specs with independent benchmark results (Aider Polyglot coding scores, Artificial Analysis intelligence/coding/agentic indices) and live pricing. See full methodology →

About Real-Time Chat

Real-Time Chat is the task of generating conversational responses in under one second, typically 200-800ms per turn. You need this when users expect immediate feedback during dialogue, such as customer support bots, in-app assistants, or voice interfaces where latency breaks the illusion of conversation. A good model for this task combines low parameter count with efficient inference: smaller fine-tuned models like Llama 2 7B or Mistral 7B outperform larger ones here. Bad models are either too large (requiring batching that adds delay) or poorly quantized (losing coherence to gain speed). The practical tradeoff: sub-second response often means accepting slightly lower reasoning depth or restricting context window to 2K-4K tokens. Inference cost scales directly with model size and context length, so a 70B parameter model will rarely hit sub-second latency on commodity hardware.

When to use: Use this when you're building a chatbot, voice assistant, or live support tool where users notice delays longer than a second and will perceive the system as slow or unresponsive.

Common questions

Which AI models can actually respond in under one second for chat?

Llama 2 7B, Mistral 7B, and Phi-2 are production-proven choices, especially when quantized to 4-bit and deployed on GPU hardware with batch size 1. GPT-3.5-turbo via OpenAI's API typically hits 300-600ms end-to-end, though that includes network latency.

How much does real-time chat latency cost compared to batch processing?

Real-time chat demands low-batch, high-concurrency infrastructure: you're paying for GPU reservation per user session rather than amortizing inference across batches. Expect 2-5x higher cost per token than batch APIs, though smaller models (7B-13B) keep total costs reasonable for high-volume applications.