.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
8 models · 1.9M structured outputs a day
#ModelBroken
structured outputs
RankBest for
this model
Structured outputs
a day
1DeepSeek V4 Flash 0731fp40.50%3 of 18AtlasCloud (fp4) 0.16%449k
2GLM 5.3 Flashfp40.51%7 of 29Parasail (fp4) 0.28%456k
3DeepSeek V4.1 Flash 1017fp40.93%10 of 33Reka AI 0.40%351k
4DeepSeek V4.1 Flashfp41.52%13 of 28DeepInfra (fp8/flex) 0.35%447k
5DeepSeek V4 Pro 0813fp41.81%9 of 13Cloudflare 0.39%62k
6Kimi K3fp44.00%19 of 20Parasail (fp4) 0.20%29k
7GLM 5.3fp84.19%17 of 28Together 0.25%18k
8gpt-oss-120bfp46.95%17 of 18MARA 0.76%41k
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 model6.95%

of gpt-oss-120b's structured outputs fail on Sail Research (fp4).

Best model0.50%

on DeepSeek V4 Flash 0731, its best model.

Ignored on3 of 8

models, where the settings tell OpenRouter to skip Sail Research.

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

Fix Sail Research's structured outputs↵