.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
1Gemma 4 26B A4B3.06%10 of 11Prime Intellect (bf16) 0.23%2.2M
2MiMo-V2.6-Flashfp43.16%6 of 8GMICloud (bf16) 0.21%2.1k
3Qwen3.8 27Bfp43.88%15 of 16NEAR AI (fp8) 0.25%23k
4Qwen3.6 35B A3Bfp44.18%8 of 8Parasail (fp8) 0.09%42k
5Nemotron 3.5 Super VLnvfp44.39%6 of 6Venice (fp4) 1.45%11k
6GLM 5.3 Flashfp45.04%28 of 29Parasail (fp4) 0.28%5.1k
7Nemotron 3.5 Lightningint46.93%5 of 5CoreWeave (bf16) 1.75%12k
8Qwen3.5-9Bfp413.39%5 of 6Prime Intellect (bf16) 0.30%28k
9gpt-oss-20bfp823.51%8 of 8CoreWeave (fp4) 1.17%235k
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 model23.51%

of gpt-oss-20b's structured outputs fail on Darkbloom (fp8).

Best model3.06%

on Gemma 4 26B A4B, its best model.

Ignored on9 of 9

models, where the settings tell OpenRouter to skip Darkbloom.

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

Fix Darkbloom's structured outputs↵