FeaturesPlans
ITENBuy now

The “Auto” provider option

What it is

"Auto" is the default value of AISA's Default provider setting. Instead of forcing one specific provider, Auto lets AISA pick the first usable provider for you. It first tries the native WordPress AI connector (WordPress 7.0+ AI Services, if configured), then falls back to your manually configured BYOK providers in a fixed order, choosing the first one that has a key and is enabled. This means generation keeps working even if you have only set up one provider, without you having to nominate it.

Where to find it

AISA → Settings → API Keys tab, in the Default provider dropdown at the top. "Auto" is the first option; the others let you pin a specific provider (DeepSeek, Claude, OpenAI, Gemini, Mistral, Grok, Perplexity) or the WordPress AI connector.

Requirements & tier

  • Applies to Free and Premium (BYOK) tiers. On Cloud, provider choice is irrelevant — the server always handles it.
  • At least one enabled provider with a valid key, or a configured WordPress 7.0+ AI Services provider, for Auto to resolve to something.

How to use

  1. Leave Default provider set to "Auto" (the default) in Settings → API Keys.
  2. Add and enable at least one provider key, and run Test connection on it.
  3. Generate as normal — AISA resolves Auto each time: WordPress AI connector first (if usable), then your enabled BYOK providers in order (DeepSeek, Claude, OpenAI, Gemini, Grok, Mistral, Perplexity), using the first available.
  4. If you want a specific provider for every job (for example always DeepSeek for cheap bulk), change the dropdown from "Auto" to that provider and save.
  5. For images, remember the dedicated image provider is set separately and is not governed by this text-provider choice.

Questions people ask

  • What does Auto actually pick? The WordPress 7.0+ AI connector if it is configured and usable; otherwise the first enabled BYOK provider that has a key, in AISA's fixed fallback order.
  • Will Auto switch providers mid-batch if one fails? Auto resolves a provider per run; it is not a live failover that retries on a different provider within one call. For resilience against rate limits, use the multi-key pool and AISA Turbo's auto-tuning.
  • Does Auto pick the cheapest provider? Not by cost — it follows the configured order and availability. If you specifically want cheapest, pin DeepSeek.
  • What if I have no provider configured? Auto resolves to nothing and generation is blocked until you add a key (or you are on Cloud).
  • Does Auto include Perplexity for SEO? Perplexity is in the fallback list but is search-priced and meant for GEO Radar; for SEO batches pin a cheaper text provider instead of relying on Auto reaching it.
  • Is "auto" also used for language? Separately, yes — the language selector can be "auto", but that resolves the page's real language, which is unrelated to provider choice.

Troubleshooting

If Auto seems to use a provider you did not expect, check the fixed fallback order and which providers are enabled with valid keys — Auto takes the first usable one (WordPress AI connector before BYOK). If generation says no provider is available, no enabled provider has a working key; add or re-test one. If you need predictable behaviour across a team or multiple sites, pin an explicit provider rather than leaving it on Auto.

Related

  • Connect an AI provider and add your API key
  • Supported AI providers and which one to choose
  • Multi-key pool: spread load across several keys
  • AISA Turbo: parallel speed and auto-tuning on rate limits

← Back to support