.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
8 models · 1.6M structured outputs a day
#ModelBroken
structured outputs
RankBest for
this model
Structured outputs
a day
1Qwen3.6 35B A3Bfp80.18%2 of 8Parasail (fp8) 0.09%476k
2Gemma 4 26B A4Bfp40.30%2 of 11Prime Intellect (bf16) 0.23%473k
3Llama 3.3 70B Instructfp80.67%3 of 5SambaNova Turbo 0.16%185k
4Qwen3.8 27Bfp80.82%3 of 16NEAR AI (fp8) 0.25%72k
5gpt-oss-120bbf160.90%2 of 18MARA 0.76%293k
6GLM 5.3fp81.87%10 of 28Together 0.25%5.5k
7Kimi K3fp41.98%10 of 20Parasail (fp4) 0.20%1.1k
8gpt-oss-20bfp45.24%4 of 8CoreWeave (fp4) 1.17%76k
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.24%

of gpt-oss-20b's structured outputs fail on AkashML (fp4).

Best model0.18%

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

Ignored on1 of 8

models, where the settings tell OpenRouter to skip AkashML.

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

Fix AkashML's structured outputs↵