.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
Reflection · 2 providers · 22k structured outputs a day
#ProviderStructured outputs
a day
$ in / out
per M
Tokens/sUptime
1Nebius Token Factoryfp4#1.41%14k$0.25 / $1.0017099.4%
2CoreWeavefp4#2.10%7.7k$0.30 / $1.0012199.8%

Also ignored, under 1,000 structured outputs a day: DigitalOcean 5.53%, Baseten (fp4) 9.84%.

Recommended OpenRouter settings for Beam 1.0 501B A23B
{
  "provider": {
    "order": [
      "nebius/fp4",
      "coreweave/fp4"
    ],
    "ignore": [
      "digitalocean",
      "baseten/fp4"
    ]
  }
}

Give llms.txt to your agent

Using Beam 1.0 501B A23B?

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 provider2.10%

of Beam 1.0 501B A23B's structured outputs fail on CoreWeave (fp4).

Best to worst1×

as often on CoreWeave (fp4) as on Nebius Token Factory (fp4), its best provider.

Every day363

broken structured outputs a day across its 2 providers.

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

Set the bar for your model↵