.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
7 models · 412k structured outputs a day
#ModelBroken
structured outputs
RankBest for
this model
Structured outputs
a day
1DeepSeek V4 Pro 08130.39%1 of 13—7.0k
2DeepSeek V4 Flash 07311.57%7 of 18AtlasCloud (fp4) 0.16%53k
3DeepSeek V4.1 Flash 10171.58%22 of 33Reka AI 0.40%60k
4Kimi K2.61.70%2 of 13Parasail (int4) 1.53%1.5k
5GLM 5.22.12%12 of 22Venice (fp8) 0.23%6.1k
6DeepSeek V4 Flash 04233.39%9 of 13Alibaba Cloud Int. (fp8) 0.66%256k
7DeepSeek V4 Pro 042313.22%8 of 8DeepInfra (fp8) 0.36%27k
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 model13.22%

of DeepSeek V4 Pro 0423's structured outputs fail on Cloudflare.

Best model0.39%

on DeepSeek V4 Pro 0813, its best model.

Ignored on2 of 7

models, where the settings tell OpenRouter to skip Cloudflare.

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

Fix Cloudflare's structured outputs↵