.TXT Build pipelines?→Serve models?↓Release models?→
Updated October 31, 2026 · How we measure

Structured-output index

The same model breaks your pipeline's structured outputs 15× more often on some inference providers than on others. Find the best one for your pipelines.

Give this to your agent ↓
← All providers
9 models · 2.5M structured outputs a day
#ModelBroken
structured outputs
RankBest for
this model
Structured outputs
a day
1DeepSeek V4 Flash 0423fp81.12%3 of 13Alibaba Cloud Int. (fp8) 0.66%1.3M
2Qwen3.5 397B A17B1.64%6 of 7AtlasCloud (fp8) 0.65%11k
3DeepSeek V4 Pro 0423fp82.32%4 of 8DeepInfra (fp8) 0.36%106k
4GLM 5.2fp82.38%14 of 22Venice (fp8) 0.23%59k
5Kimi K2.6fp82.76%6 of 13Parasail (int4) 1.53%3.6k
6GLM 5.1fp83.16%2 of 3Nebius Token Factory (fp8) 0.45%1.7k
7DeepSeek V4.1 Flash 1017fp83.36%29 of 33Reka AI 0.40%19k
8GLM 5.3 Flashfp83.78%27 of 29Parasail (fp4) 0.28%932k
9GLM 5fp85.52%2 of 3Baidu Qianfan (fp8) 3.34%1.7k
New models

Get updates when a new model drops

And which provider to use.

For inference providers

Structured outputs don't have to break

The same provider can handle structured outputs well on one model and struggle on the next. Implementations diverge on strings, optionals, composition and conditionals (the April announcement): the schema one provider enforces, another ignores.

Worst model5.52%

of GLM 5's structured outputs fail on StreamLake (fp8).

Best model1.12%

on DeepSeek V4 Flash 0423, its best model.

Ignored on4 of 9

models, where the settings tell OpenRouter to skip StreamLake.

dotjson plugs into your inference stack, so every model you serve gets perfect structured outputs from day 0.

Fix StreamLake's structured outputs↵