.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
4 models · 217k structured outputs a day
#ModelBroken
structured outputs
RankBest for
this model
Structured outputs
a day
1Qwen3.8 27Bfp80.57%2 of 16NEAR AI (fp8) 0.25%88k
2Gemma 4 31Bfp41.04%8 of 13ModelRun [by Modular] (fp4) 0.21%123k
3Kimi K3mxfp42.05%12 of 20Parasail (fp4) 0.20%1.1k
4Kimi K2.6int45.07%12 of 13Parasail (int4) 1.53%4.3k
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.07%

of Kimi K2.6's structured outputs fail on Chutes (int4).

Best model0.57%

on Qwen3.8 27B, its best model.

Ignored on1 of 4

models, where the settings tell OpenRouter to skip Chutes.

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

Fix Chutes's structured outputs↵