of Nemotron 3.5 Lightning's structured outputs fail on Darkbloom (int4).
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 ↓
| # | Provider | Structured outputs a day | $ in / out per M | Tokens/s | Uptime | |
|---|---|---|---|---|---|---|
| 1 | CoreWeavebf16# | 1.75% | 117k | $0.07 / $0.20 | 107 | 100.0% |
| 2 | DeepInfrabf16# | 1.77% | 18k | $0.06 / $0.16 | 232 | 99.6% |
| 3 | Fireworks# | 2.83% | 2.3k | $0.05 / $0.20 | 384 | 90.9% |
| 4 | io.net# | 4.18% | 4.1k | $0.05 / $0.13 | 160 | 99.7% |
| 5 | Darkbloomint4# | 6.93% | 12k | $0.03 / $0.12 | 62 | 99.7% |
Recommended OpenRouter settings for Nemotron 3.5 Lightning
{
"provider": {
"order": [
"coreweave/bf16",
"deepinfra/bf16",
"fireworks"
],
"ignore": [
"io-net",
"darkbloom/int4"
]
}
}Give llms.txt to your agent
Get updates when its successor drops
And which provider to use.
For model makers
Broken structured outputs carry your model's name
Your users don't see the provider. They see your model failing.
as often on Darkbloom (int4) as on CoreWeave (bf16), its best provider.
broken structured outputs a day across its 5 providers.
Releasing a model? Make your own API the one every provider is measured against.
Set the bar for your model↵