Opening IO Gateway

How-to guides

Provider accounts

Use when
Upstream account management
Storage
auths/
Updated
September 4, 2026

Provider accounts are the upstream identities IO Gateway uses when routing model requests. Add at least one healthy account before exposing an API key to clients.

Provider account cards with enabled, disabled, priority, quota, reset limit, and attention states.
Provider cards make routing eligibility visible before traffic reaches the account pool.

Before you start

  • Credential storage Confirm auth_dir points to the directory where provider credentials should live.
  • Provider support Use provider-specific account flows for Claude, Gemini, Codex, Qwen, GLM, Grok, Copilot, or other enabled providers.

Add or maintain an account

  1. 1
    Open the dashboard provider section.

    Select the provider that should receive traffic.

  2. 2
    Add the credential.

    Use the provider-specific OAuth or API-key flow.

  3. 3
    Test the account.

    Run a short Test API prompt to prove the account can serve traffic.

  4. 4
    Watch state changes.

    Disabled, failed, cooling-down, and quota-exhausted accounts are skipped by routing.

Account operations

OperationUse when
DisableRemove an account from routing without deleting its credential.
RefreshReload health, quota, or provider-side state.
Re-authenticateRepair expired OAuth or invalid provider credentials.
DeleteRemove the account and prune routing state such as priority membership.

Verify routing

Use usage history to confirm that traffic reaches the expected account. For deliberate account draining, enable priority routing.