.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 models
NVIDIA · 6 providers · 186k structured outputs a day
#ProviderStructured outputs
a day
$ in / out
per M
Tokens/sUptime
1Venicefp4#1.45%15k$0.20 / $0.5027899.1%
2CoreWeavenvfp4#1.66%16k$0.15 / $0.5028899.1%
3Crusoebf16#1.68%46k$0.10 / $0.407899.4%
4Together#2.64%68k$0.15 / $0.5032299.9%
5DeepInfrafp4#2.74%30k$0.15 / $0.5031296.0%
6Darkbloomnvfp4#4.39%11k$0.06 / $0.353997.2%
Recommended OpenRouter settings for Nemotron 3.5 Super VL
{
  "provider": {
    "order": [
      "venice/fp4",
      "coreweave/nvfp4",
      "crusoe/bf16"
    ],
    "ignore": [
      "darkbloom/nvfp4"
    ]
  }
}

Give llms.txt to your agent

Using Nemotron 3.5 Super VL?

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.

Worst provider4.39%

of Nemotron 3.5 Super VL's structured outputs fail on Darkbloom (nvfp4).

Best to worst3×

as often on Darkbloom (nvfp4) as on Venice (fp4), its best provider.

Every day4k

broken structured outputs a day across its 6 providers.

Releasing a model? Make your own API the one every provider is measured against.

Set the bar for your model↵