FeaturesPlans
ITENBuy now

Multi-key pool: spread load across several keys

What it is

The multi-key pool lets you give one provider more than one API key. AISA then rotates between the keys for each request and, when a key hits a rate-limit (HTTP 429/503/529), puts that key into a short cooldown and prefers the others. Combined with AISA Turbo, independent keys give you more real parallel capacity: more requests can go out at once before any single key trips its limit. This is the practical way to push very large 1-Click/Bulk runs without constant 429 blocks.

Where to find it

AISA → Settings → API Keys. Under each provider's primary key field there is an extra keys textarea labelled to accept one key per line (commas also work). The primary key plus the extra keys together form that provider's pool.

Requirements & tier

  • Works on BYOK tiers (Free/Premium). Most valuable on big batches with AISA Turbo on.
  • Two or more valid keys for the same provider. Ideally from independent accounts — several keys from the same account often share one rate limit, depending on the provider's tier, so the headroom gain is smaller.

How to use

  1. Open the provider's card in Settings → API Keys and confirm the primary key works (Test connection).
  2. Paste your additional keys into the extra keys textarea, one per line (or comma-separated).
  3. Save. AISA now treats all of them as a pool, de-duplicating and ignoring blanks automatically.
  4. Turn on AISA Turbo (e.g. ×8 or higher) so the parallel requests are spread across the pool.
  5. Run 1-Click SEO or Bulk SEO. When a key is rate-limited it goes into a brief cooldown and AISA picks from the remaining available keys.
  6. For maximum effect, use keys from separate provider accounts so they do not share a single limit.

Questions people ask

  • How are keys chosen? With more than one key, AISA picks at random among the keys not currently in cooldown; if all are cooling down it still uses the least-bad one rather than stopping.
  • How long is a cooled-down key benched? A short cooldown is applied to the specific key that hit the limit, after which it rejoins the rotation.
  • Do same-account keys help? Less than independent ones — many providers share the limit across an account's keys at a given tier. Independent accounts give the real boost.
  • Does the pool change cost? No. It only spreads requests; you still pay each provider for the tokens used.
  • Can I pool keys for several providers? Yes, each provider has its own extra-keys field; pools are per provider.
  • Is this the same as Turbo? No, but they pair up: Turbo sets how parallel you go; the pool gives those parallel requests more keys to ride on, so you hit fewer 429s.

Troubleshooting

If you still hit limits with a pool, the keys probably share one account/tier limit — add keys from independent accounts, switch the batch to DeepSeek (generous limits), or lower the Turbo multiplier. If a key is invalid it simply contributes nothing useful; re-test each key individually with Test connection. If you delete the primary key field and save, the provider is disabled even if extra keys remain, so keep a valid primary key in place. Remember OpenAI's blocker on big sites is a per-tier daily request cap, which more same-account keys will not bypass.

Related

  • AISA Turbo: parallel speed and auto-tuning on rate limits
  • Connect an AI provider and add your API key
  • Supported AI providers and which one to choose
  • The "Auto" provider option

← Back to support