of GLM 5.2's structured outputs fail on Alibaba Cloud Int. (fp8/fast).
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.
| # | Model | Broken structured outputs | Rank | Best for this model | Structured outputs a day |
|---|---|---|---|---|---|
| 1 | DeepSeek V4 Flash 0423fp8 | 0.66% | 1 of 13 | — | 104k |
| 2 | Kimi K3 | 0.70% | 4 of 20 | Parasail (fp4) 0.20% | 1.7k |
| 3 | GLM 5.2fp8 | 2.30% | 13 of 22 | Venice (fp8) 0.23% | 9.0k |
| 4 | DeepSeek V4 Flash 0731 | 3.36% | 16 of 18 | AtlasCloud (fp4) 0.16% | 26k |
| 5 | DeepSeek V4 Pro 0813 | 3.60% | 11 of 13 | Cloudflare 0.39% | 9.3k |
| 6 | DeepSeek V4 Pro 0423fp8 | 4.88% | 7 of 8 | DeepInfra (fp8) 0.36% | 26k |
| 7 | GLM 5.2fp8/fast | 20.46% | 21 of 22 | Venice (fp8) 0.23% | 1.3k |
And which provider to use.
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.
of GLM 5.2's structured outputs fail on Alibaba Cloud Int. (fp8/fast).
on DeepSeek V4 Flash 0423, its best model.
models, where the settings tell OpenRouter to skip Alibaba Cloud Int..
dotjson plugs into your inference stack, so every model you serve gets perfect structured outputs from day 0.
Fix Alibaba Cloud Int.'s structured outputs↵