Several keys per provider (key rotation)
You can save extra API keys for a vendor provider, and when one key is rate limited, out of credit or refused, Omniscio carries on with the next one instead of stopping the session. It is a Lab feature that is off until you switch it on, and it never applies to Claude, Anthropic accounts or GLM.
On this page
What it is
Heavy work on one vendor tends to hit that vendor's limits on a single key, or run its balance to zero. With a key pool you save a second, third or fourth key for the same vendor. Omniscio spreads new sessions across the keys that are ready, and when a key stops working mid-session it moves that session to another key and re-runs the turn that failed, so you do not have to notice or intervene.
The key you already saved for the provider is the first member of the pool. You never re-enter it, and a provider with no extra key behaves exactly as it did before this feature existed.
What is covered, and what is not
Covered: vendors that Omniscio reaches with a key you supply. That is two kinds. The first kind runs through Omniscio's own Claude process (for example DeepSeek, Kimi and MiniMax). The second kind runs through the local proxy (for example OpenAI and the providers in the proxy catalog; xAI is eligible too but has no key card yet, so Settings does not offer it). On the proxy kind the proxy holds one active key at a time, and a key switch rewrites that one key and applies it the way any proxy change is applied.
Not covered, and the screen says so:
- Claude and every Anthropic account. Those have their own account pool.
- GLM. It already has its own several-accounts system.
- A custom provider you added yourself. It keeps its single key.
- Tools that manage their own sign-in and keys: Gemini, OpenCode, Cursor, Devin, the Codex login, Hermes, Kimi Code and Antigravity. They keep one key.
- A session served by a managed account or a reseller. The pool only acts on a session that is running on the vendor's own key.
Where to find it
- Switch it on: Settings → Lab → Several keys per provider.
- Then open Settings → Accounts, and in the card of a covered provider look for More keys for {provider}. It lists your extra keys and has an Add another key button.
With the Lab switch off, the list and the button are not shown.
How it behaves
Adding a key
Press Add another key, give the key a name (up to 64 characters) and paste the key. It is saved on this computer, encrypted, and cannot be shown again. Each key then appears as its name, the hidden part followed by its last four characters, and a state:
- Ready — can take a session.
- Resting until {time} — rate limited or out of credit for now; it comes back on its own.
- Refused by the provider — the vendor refused it, so the key was switched off. A key that is out of credit shows as resting instead.
- Off — you switched it off. A switched-off key is never used.
You can switch any key on or off, and delete it (after a confirmation). A provider can hold up to 20 extra keys.
Which key a session uses
A new session takes the ready key that was used least recently, which spreads the load. A session you resume keeps the key it started on for as long as that key is switched on and not resting. If you deleted that key, switched it off, or it is resting, the resumed session takes another ready key.
When a key fails
- Rate limited. The key rests for the wait the vendor asked for, or one minute when the vendor named none (never more than six hours). The session moves to the next ready key and the turn is re-run.
- Out of credit. The key rests for six hours and the session moves on. Some vendors report an empty balance as a sign-in error; Omniscio treats that the same way, so a funded key is never switched off by mistake.
- Refused for any other reason. The key is switched off, the session moves on, and one inbox note appears: "A saved provider key was refused", naming the provider and the key's name (never any part of the key), with a button that opens Settings, Accounts. The note clears when you switch the key back on or delete it. It appears once per key however often the key is tried.
- Every key resting. The session says all keys are resting until a given time, instead of a generic provider-unavailable message. If a usage cascade is set up, the order is: keys first, then the rest of Omniscio's recovery steps.
A key that rests comes back by itself. A refused key does not: you replace or remove it.
What an agent can and cannot do
An agent cannot add, change, switch on or read a pooled key. Adding and removing keys is done by you in the app. The phone bridge cannot reach any of it. This is deliberate: a key is a credential.
Related
- API keys — where single keys are saved and checked.
- Usage cascade — what to run when a whole provider keeps failing or runs out, after the keys here are spent.
- Custom providers — a custom provider keeps its one key.
- GLM provider — GLM's own several-accounts system.
- AI providers — the providers Omniscio can run sessions on.
Last verified 2026-10-30