.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 · 918k structured outputs a day
#ModelBroken
structured outputs
RankBest for
this model
Structured outputs
a day
1Qwen3.6 35B A3B0.81%4 of 8Parasail (fp8) 0.09%51k
2Gemma 4 31B1.14%9 of 13ModelRun [by Modular] (fp4) 0.21%10k
3gpt-oss-120bbf161.17%6 of 18MARA 0.76%245k
4Qwen3 30B A3B Instruct 25071.23%3 of 3Nebius Token Factory (fp8) 0.65%14k
5DeepSeek V4 Pro 08131.43%6 of 13Cloudflare 0.39%2.1k
6Qwen3.8 27B1.56%8 of 16NEAR AI (fp8) 0.25%45k
7Mistral Nemofp82.24%3 of 3Parasail (fp8) 0.15%514k
8gpt-oss-20bbf1612.29%7 of 8CoreWeave (fp4) 1.17%29k
9GLM 5.324.50%28 of 28Together 0.25%7.5k
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 model24.50%

of GLM 5.3's structured outputs fail on DekaLLM.

Best model0.81%

on Qwen3.6 35B A3B, its best model.

Ignored on2 of 9

models, where the settings tell OpenRouter to skip DekaLLM.

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

Fix DekaLLM's structured outputs↵