Latency by model, measured at the gateway

30 days of real traffic, 63 models. OCR and translation answer in under a second; image generation takes a minute. Here is the actual distribution.

Quick facts (checked 2026-10-22): 111 live models through one OpenAI-compatible API · 0% platform markup, provider list price passed through · free tier gives 10 free-model calls/day · machine-readable prices: china-ai-leaderboard.json · agent index: llms.txt

Benchmarks measure models in isolation. Production teams care about the number their users see: how long the request takes end to end. That number includes upstream queueing, prefill and generation, so it is noisy — but it is the honest one.

The tiers

OCR / translation
0.3–1.0s
p50 at the gateway
Mid-tier chat
1.1–2.6s
p50
Flagship text
3–16s
p50, output-length dependent
Image generation
10–68s
p50

Measured p50 latency

Only models whose median prompt is under 2,000 tokens are listed, so the comparison is not distorted by prompt size (median input shown). Latency is end-to-end at the gateway.

Modelnmedian inputp50p90
qwen-vl-ocr3313324ms1,052ms
qwen-mt-plus2813333ms1,156ms
qwen3-omni-flash3219355ms944ms
qwen3.5-ocr3117370ms3,870ms
qwen3-coder-flash4413403ms869ms
qwen3-vl-plus4278796ms1,811ms
hy-mt2-plus3417975ms2,500ms
minimax-text-01805591,115ms28,856ms
glm-5v-turbo42151,174ms5,352ms
kimi-k2.7-code-highspeed37161,359ms1,952ms
kimi-k2.8-preview289891,624ms4,788ms
minimax-m2.5317441,860ms3,090ms
minimax-m2.7370461,911ms7,268ms
glm-5.31461462,156ms58,450ms
kimi-k2.647482,623ms11,849ms
kimi-k2.561562,963ms42,784ms
glm-5128171,585ms3,769ms
step-5-preview88752,665ms71,785ms
qwen3-max1661,7746,132ms10,000ms
qwen3.7-max11249016,228ms43,910ms
doubao-seedream-5.0-pro (image)40—68,115ms110,651ms

Three observations

1. Cheap and fast coincide at the small-model end

Qwen3.5-OCR answers in 370ms at $0.70 per 1M tokens. Hunyuan MT2-plus translates in 975ms at $0.072 per 1M. The expensive end of the catalog is not faster — it is slower, because flagship models generate longer answers and are sized for reasoning rather than turnaround. If your task is classification, extraction or translation, the cheap model is usually also the fast one.

2. Output length, not input length, drives the tail

The p90 values spread far more than p50 — from 869ms to 71s. That tail is generation: a model writing 900 tokens takes far longer than one writing 50, regardless of prompt. Streaming hides this from users but not from your request pipeline.

3. Generation tasks have a different shape entirely

Image models are 10–68 seconds at p50. That is not a latency problem to optimise; it is a job to queue. Plan for async: submit, poll, webhook — not request/response.

Comparability caveat. The table filters to models whose median prompt is under 2K tokens because prompt size and model choice are correlated in real traffic: agents send huge prompts to cheap fast models, chat users send short prompts to flagships. Comparing across the whole catalog without that filter produces misleading orderings. Latency here is end-to-end as seen at the gateway (queue + prefill + generation), not time-to-first-token.

How to use this

Every model in the table is reachable through the same endpoint, so switching tiers is a per-request model id change. Prices: live feed; cost side: what real calls cost.

FAQ

What is a typical latency for a Chinese LLM API?

From 30 days of gateway traffic: OCR and translation models respond in 324-975ms at p50, mid-tier chat models in 1.1-2.6s, flagship text models in 3-16s depending on size, and image generation takes 10-68s. The median p50 across 63 models was 1.86s.

Why are the cheapest models often the fastest?

Small models are cheaper per token and need less compute per request. Qwen3.5-OCR responds in 370ms at $0.70 per 1M tokens, while a flagship 1M-context model can take 16s. Cheap and fast coincide at the small-model end.

Does latency include generation time?

Yes. This is end-to-end time as observed at the gateway: upstream queueing plus generation. It is not time-to-first-token, so models producing long outputs appear slower even when their prefill is fast.

Do larger prompts make responses slower?

Not in a simple way in this data, because prompt size correlates with which model a workload chooses. Comparing only models whose median prompt is under 2K tokens removes that confound, and there the ordering follows model class rather than prompt size.

Measure it on your own workload

Free tier to test latency from your region, then pay only for what you use — 0% markup on 111 models.

Get an API key

Window: 30 days ending 2026-10-22. 63 models with at least 25 latency samples. Latency is end-to-end at the gateway (queue + prefill + generation), recorded per request; p50/p90 computed over all successful calls in the window. Prices: /china-ai-leaderboard.json.