Top picks for Real-Time Chat (2026)
Models tuned for sub-second response. Ranked from 461 live models on the OpenRouter catalog, weighted for low latency, low cost.
Updated 2026-10-22 · prices checked at this morning's rebuild
Which should you use? MiniMax: MiniMax M3.1 Flash (free) tops this ranking on blended score. If cost drives the decision, DeepSeek: DeepSeek V4.1 Flash (batch) is the cheapest of the leaders at $0.05/M input. To prototype without spending, MiniMax: MiniMax M3.1 Flash (free) is the best free option ranked here.
| # | Model | Score | In / 1M | Out / 1M | Context | |
|---|---|---|---|---|---|---|
| 1 | MiniMax: MiniMax M3.1 Flash (free)minimax/minimax-m3.1-flash:free | 118 | Free | Free | 1,000,000 | Details → |
| 2 | NVIDIA: Nemotron 3.5 Super VL (free)nvidia/nemotron-3.5-super-vl:free | 118 | Free | Free | 1,000,000 | Details → |
| 3 | Anthropic: Claude Haiku 5.5 (batch)anthropic/claude-haiku-5.5:batch | 118 | $0.05 | $0.25 | 1,000,000 | Details → |
| 4 | OpenAI: GPT-6 Luna Pro (batch)openai/gpt-6-luna-pro:batch | 118 | $0.05 | $0.25 | 1,050,000 | Details → |
| 5 | OpenAI: GPT-6 Luna (batch)openai/gpt-6-luna:batch | 118 | $0.05 | $0.25 | 1,050,000 | Details → |
| 6 | Xiaomi: MiMo-V2.6-Flashxiaomi/mimo-v2.6-flash | 118 | $0.14 | $0.28 | 1,050,000 | Details → |
| 7 | inclusionAI: Ling 3.0 Flash VLinclusionai/ling-3.0-flash-vl | 118 | $0.06 | $0.18 | 131,072 | Details → |
| 8 | DeepSeek: DeepSeek V4.1 Flash (batch)deepseek/deepseek-v4.1-flash:batch | 118 | $0.05 | $0.15 | 1,048,576 | Details → |
| 9 | Nex AGI: Nex-N2.5-Pronex-agi/nex-n2.5-pro | 118 | $0.07 | $0.25 | 262,144 | Details → |
| 10 | Meta: Muse Spark 1.3 Contributormeta/muse-spark-1.3-contributor | 118 | $0.10 | $0.20 | 1,048,576 | Details → |
| 11 | Z.ai: GLM Flash Latest~z-ai/glm-flash-latest | 118 | $0.02 | $0.14 | 1,048,576 | Details → |
| 12 | Z.ai: GLM 5.3 Flashz-ai/glm-5.3-flash | 118 | $0.02 | $0.14 | 1,048,576 | Details → |
| 13 | Z.ai: GLM 5.3 Flash (batch)z-ai/glm-5.3-flash:batch | 118 | $0.05 | $0.18 | 1,048,576 | Details → |
| 14 | Meta: Muse Spark 1.2 Contributormeta/muse-spark-1.2-contributor | 118 | $0.10 | $0.20 | 1,048,576 | Details → |
| 15 | Qwen: Qwen3.7 Flashqwen/qwen3.7-flash | 118 | $0.03 | $0.13 | 1,000,000 | Details → |
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.