.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.6M structured outputs a day
#ModelBroken
structured outputs
RankBest for
this model
Structured outputs
a day
1MiniMax M3.1 Flash0.59%2 of 8Nebius Token Factory (fp4) 0.14%15k
2GLM 5.3 Flash0.74%10 of 29Parasail (fp4) 0.28%248k
3DeepSeek V4.1 Flash 10171.26%19 of 33Reka AI 0.40%284k
4DeepSeek V4.1 Flash1.62%14 of 28DeepInfra (fp8/flex) 0.35%887k
5DeepSeek V4 Flash 07312.70%13 of 18AtlasCloud (fp4) 0.16%750k
6Qwen3.5 397B A17B4.19%7 of 7AtlasCloud (fp8) 0.65%7.9k
7GLM 5.34.41%19 of 28Together 0.25%4.8k
8DeepSeek V4 Flash 04235.93%12 of 13Alibaba Cloud Int. (fp8) 0.66%350k
9GLM 5.263.34%22 of 22Venice (fp8) 0.23%3.2k
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 model63.34%

of GLM 5.2's structured outputs fail on DigitalOcean.

Best model0.59%

on MiniMax M3.1 Flash, its best model.

Ignored on4 of 9

models, where the settings tell OpenRouter to skip DigitalOcean.

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

Fix DigitalOcean's structured outputs↵