OpenRouter's :nitro variant now pulls in priority service tiers
- Source
- x.com
- Date
TIP 💡 Our :nitro and :floor model variants tap into service tiers, not just sorting Example: "~openai/gpt-latest:nitro" has many features packed into 1 model slug: 1. ~latest alias resolves to the latest gpt model 2. :nitro sorts endpoints by measured throughput 3. (NEW) :nitro admits priority service tier endpoints into the pool, competing on speed alongside the defaults
Learn more in the updated docs: https://t.co/TtZ5RuTaOF https://t.co/ySMIHluoWX https://t.co/pu0l9JBRr5
Context
Appending :nitro to a model name on OpenRouter changes which serving endpoints can compete for the request as well as how they are ranked. It admits priority-tier endpoints alongside default endpoints, then orders the combined pool by measured throughput. Simply setting a throughput sort does not add those priority endpoints. The routing documentation confirms that difference.
The announcement's comparison table also distinguishes :nitro from explicitly requesting priority service: :nitro gives neither tier an automatic preference. A default endpoint can still win when its measured generation speed is higher.
Checking sign-in…
Loading comments…