SU8 Codes

Switch a key's channel

A model can be served through several channels. You decide which channel each API key uses: pick one when you create the key, and change it whenever you need to. Switching does not require a new key, and you do not change the Base URL or key in your client.

When to switch

  • The current channel has become slower or returns more errors.
  • You want a channel with a lower landed discount.
  • You want the key to use a channel covered by one of your plans.

Before switching, open the model’s detail page from Models to compare landed discounts by channel and see which plans cover which channels.

Choose channels when creating a key

On API keys in the console, click Create API key. In the Channels step:

  1. On the left, check the providers you want. You can pick more than one.
  2. On the right, choose a channel for each checked provider. Channels with a description show it under the name to help you choose.
  3. Finish the remaining steps to create the key.

Switch the channel of an existing key

  1. In the key list on API keys, open More actions (the three dots) at the end of the key’s row and choose Edit.
  2. Go to the Channels step, clear the old channel, and check the new one.
  3. Click Save.

Within 15 seconds of saving, new requests from this key use the new channel. You do not need to restart your client or change any settings.

Before you switch

  • Cost may change: the same model can have a different landed discount on each channel. The model detail page shows the current numbers.
  • Plans cover only some channels: when a key uses both plans and balance, the channel list marks the channels covered by your plans as “In package”; when a key uses plans only, the list shows only covered channels. If the new channel is not covered by your plan, the key’s requests stop using plan quota. They are charged to balance if the key allows it; otherwise the call fails. Quota left on your other plans cannot be used on channels those plans do not cover.
  • No automatic switching on errors: even if a key has several channels checked, a failed call is not retried on another channel. To switch, change it yourself using the steps above.
  • Which channel a key with several channels uses: each call picks one of the channels that can still serve it. The platform’s channel priority comes first; channels with the same priority follow the order you checked them in. So when the plan quota on one channel runs out, the next call moves to another channel that still has plan quota. When none does, the call is charged to balance if the key allows it. Cost can differ between channels, and conversations do not carry over between them.
  • Conversations do not carry over: an ongoing multi-turn conversation starts fresh upstream on the new channel, and its cache is rebuilt.

Check the result

Open Usage in the console and look at calls made after the switch. Each record shows time to first token, latency, output speed, and cost, so you can compare with before.