Skip to main content
A generation provider is the account Voyager uses to make an image, video, voice, music track, or sound effect. For example, you can use ChatGPT for the conversation and your FAL key for the video. The agent subscription and the generation provider are separate connections, with separate bills.

​
Set the provider order

Open Settings → Accounts → Generation providers. Voyager starts with the first connected, enabled provider in your list that offers the requested model. On a fresh setup, the order is: An existing installation may have a different order. Use the list shown in your app as the guide to which account Voyager will try first. A provider cannot run every model just because it appears in the list.
The Generation providers list, numbered 1 to 5: Higgsfield (Inactive, Sign in), FAL (Key ending in 4d3e, Remove), Google and ElevenLabs (Inactive, Add key) and Voyager credits (Billed to Demo Studio). Each row has an on/off switch and up and down arrows. Below the list, the Automatic fallback switch is on.The Generation providers list, numbered 1 to 5: Higgsfield (Inactive, Sign in), FAL (Key ending in 4d3e, Remove), Google and ElevenLabs (Inactive, Add key) and Voyager credits (Billed to Demo Studio). Each row has an on/off switch and up and down arrows. Below the list, the Automatic fallback switch is on.

The arrows change which provider Voyager tries first. Automatic fallback controls whether it can move on after a failure.

  1. Connect the providers you want to use.
  2. Move your preferred provider up with its arrow.
  3. Turn off the switch beside any provider you do not want used for new generations.
  4. Review Automatic fallback below the list.
Changes apply to new jobs. They do not move a job that is already running to another account.

​
Add your own media keys

Your own keys work without a paid Voyager plan. The provider bills your account directly.
  1. Find FAL, Google, or ElevenLabs in Generation providers.
  2. Choose Add key. Use the key-page link in that row if you need to create one.
  3. Paste the key into Paste your key and choose Save.
  4. Check the row’s connection status before starting a generation.
The FAL row expanded to show a FAL API key field with a pasted key, Paste, Save and Cancel buttons, and a Get a key at fal.ai/dashboard/keys hint.The FAL row expanded to show a FAL API key field with a pasted key, Paste, Save and Cancel buttons, and a Get a key at fal.ai/dashboard/keys hint.

Save the key in the provider's row, then check its connection status.

Keys entered here are saved in your system’s secure storage, not in project files. Paste keys into the account controls, not into a chat. If Voyager detects a key you already configured on your computer, check that it is the account you intend to pay with. A saved key takes precedence over a key from your environment.

​
Understand automatic fallback

Automatic fallback is on by default. If a generation provider is out of credits, rejects its sign-in, or is down, Voyager tries the next usable provider in your list. It shows a notification that names the provider and where the generation continued, for example Higgsfield is out of credits with Continued on Voyager credits below it. Settings such as duration or resolution may change slightly to match what that provider offers; the notification lists the main changes.
A warning notification titled Higgsfield is out of credits, with the line Continued on Voyager credits and an Open Settings button.A warning notification titled Higgsfield is out of credits, with the line Continued on Voyager credits and an Open Settings button.

A fallback notification: the title names the provider that failed, the line below names where the generation continued.

Fallback can bill a different account. For example, a job that starts with your Higgsfield plan can continue using a personal API balance or Voyager credits.
Turn Automatic fallback off if you want Voyager to stop when the first usable provider fails. For one request, ask the agent to pin a provider: “Generate this with my FAL account only. Pin FAL and stop if it cannot run.” A pinned provider prevents fallback for that request. Fallback does not fix rejected inputs or a content-filter refusal. A model that needs a higher Voyager plan also needs you to choose an included model or change the plan; Voyager does not automatically charge another account to get around that refusal.

​
Higgsfield plan versus API balance

These are two separate balances:
  • Higgsfield in Generation providers signs in to your Higgsfield plan. Choose Sign in and finish in your browser. If Voyager detects an existing sign-in, it may offer Use this account.
  • Higgsfield API balance, inside Voyager → Use your own API keys, uses a separate prepaid API balance. Enter the key in the key ID:secret format shown in the field and choose Save key.
When both are connected, Voyager tries the plan before the API balance. With automatic fallback enabled, a depleted plan can continue on the API balance. The notification says Higgsfield plan credits ran out and tells you where the generation continued. Turning fallback off prevents that move for a failed plan attempt. If no plan sign-in is connected, the saved API key can still be the Higgsfield connection used first. Remove the API key if you do not want Voyager to use that balance at all.

​
Check who paid

Read any fallback notification and inspect the generation in the chat’s Jobs panel. An out-of-credits message for FAL or Higgsfield refers to that provider account, not necessarily your Voyager balance. Managed Voyager voices always use your Voyager account; rearranging this list does not move them to a personal key. For credit renewals and auto-reload, see Plans and credits. For expired sign-ins, refused keys, or stopped jobs, see Generation problems.