Groups & Multipliers (Auto-A)
How token groups control model access and pricing, and why the Auto-A automatic group is the recommended default.
Every API token belongs to one or more groups. A group defines which models the token may call and which upstream channel routing (and cost) applies.
What is a Group Multiplier?
When a request is processed, the deducted balance is computed as:
Effective Cost = Base Model Rate × Model Ratio × Group MultiplierGroups with different multipliers route through channels with different pricing — lower multipliers are cheaper per token, higher ones use premium routing. The multiplier each group applies to every model is shown on the /pricing page.
The Automatic Group: Auto-A
When you create a token you will see a group selector in the form. Auto-A is the automatic routing group and the recommended choice for almost every use case:
- Universal coverage:
Auto-Ais enabled for the models in the catalog, so one token can call the whole gateway without juggling groups. - Automatic routing: requests are routed automatically across available upstream channels — you don't manage channel selection.
- Zero configuration: pick
Auto-Aand your token works with any model whose Enabled Groups column includes it.
Recommendation: for the vast majority of setups, select
Auto-Awhen creating or editing a key in the API Keys section (sidebar → Console → API Keys, athttps://api.nyxos.shop/keys). Only choose a different group if you have a specific routing or cost reason.
Verifying Group Access
- Open the
/pricingpage and find your model. - Check the Enabled Groups column.
- Make sure your key is assigned to one of those groups (API Keys → Edit).
- If the model is not available in your group, calls fail with 404 / permission errors — see Troubleshooting.