Model Configurations

​

Provider connections and model configurations

Use Providers in the sidebar to connect provider accounts, and Models to create named model configurations. Providers lists each added connection in its own row. You can connect multiple accounts for the same provider and reuse them across configurations. Connections and configurations belong to your organization. Voice AiLunaPro provisions an initial AiLunaPro connection and default setup during signup. You can add more AiLunaPro connections with different Service Keys, or connect external providers.

​

Add a provider connection

You need the credentials and any connection settings required by your provider. To create an AiLunaPro Service Key, see API Keys and Service Keys.

1. Open Providers in the sidebar and click Add Provider to open the connection editor page.
2. Choose the provider and name the connection so you can distinguish its account or environment.
3. Enter its credentials and any required connection settings, then save. Where key pools are supported, use Add API Key to enter each key in its own row.

Click Edit on a provider row to open its editor page. Use All provider connections to return to the list. You choose which services use the connection when editing a named model configuration in Models. You can repeat these steps for multiple accounts at the same provider. Editing a connection lets you keep or replace configured credentials; saved secrets are not returned to the browser. Model settings reference the connection instead of copying its key. Saving a new connection, replacing credentials, or changing connection settings runs the provider’s available credential checks before saving. Every API key in a pool is checked. A rejected key leaves the existing connection unchanged. Renaming a connection does not repeat provider checks. The checks vary by provider; some validate field structure or token format rather than making a live request. A provider’s realtime and standard services may require separate connection types, even when they accept the same key. The available roles come from the provider definitions.

​

Create a named configuration

1. Open Models in the sidebar, click Add Configuration, and give it a name.
2. Choose Realtime, AiLunaPro, or BYOK mode. In BYOK and Realtime, each service has its own tab where you select a provider connection. To connect a new account without leaving the page, choose Add a provider at the end of a provider list.
3. Adjust the available settings, then save.
4. Click Make org default on its row in Named Model Configurations if agents should inherit it. The current default has an Org default badge.

In BYOK and Realtime modes, you can also select an external embedding connection on the Embedding tab. Its model must match the indexes of the knowledge-base documents you use. Changing the configuration does not rebuild existing indexes. AiLunaPro mode manages embeddings automatically and has no separate embedding controls. AiLunaPro connections are selected only through AiLunaPro mode in the editor. Use Duplicate to create a variation, or Copy UUID to reference a saved configuration or connection from your API integration. Names are labels; UUIDs identify references. Creating, editing, and duplicating model configurations opens a dedicated page. Use All model configurations to return to the list. In AiLunaPro mode, choose the managed tier under LLM model, and click Voice to browse, filter, and play voice samples before selecting Use this voice. For AiLunaPro’s Flux-supported languages and Deepgram Flux multilingual, select Language hints with the language checkboxes. Model and language dropdowns offer Enter Custom Value where the provider supports it. In BYOK mode, ElevenLabs, Cartesia, and Deepgram voices load using the selected provider connection’s saved API key. Rime uses its public voice catalog, and Sarvam offers model-specific speaker lists. Voice choices refresh when you change the connection, model, or language. If a catalog cannot load, you can retry or enter a voice ID manually. Saving a named model configuration checks its structure and supported settings without repeating provider credential checks. A run’s final configuration is validated before billing and quota authorization. For one run, all selected AiLunaPro services must share a service key. You can keep multiple AiLunaPro connections in the catalog and use them in different configurations.

​

Configure an individual agent

1. Open the agent’s Settings and its model configuration section.
2. Inherit the organization default or select a named configuration.
3. Save and publish the agent.

Create and edit configurations in Models. For a variation, duplicate a named configuration there and select it in your workflow. Override individual fields such as temperature or voice through the API trigger for a single run. If an existing workflow has custom model settings, they remain in use until you explicitly select and save a named configuration or the organization default. Workflow settings show that existing override without offering individual field editing. A named selection follows edits to that configuration for future runs. A run that has already started keeps its saved settings and credential selection.

​

Override a single run

The effective order is organization default, published workflow override (or draft for test calls), API trigger override, then pre-call data fetch override. The pre-call data fetch runs once the call is connected, so it can only change the services the agent owns: llm, llm_fallback, and tts. The mode, stt, realtime, and embeddings are fixed by the first three layers. An override can select a named configuration by UUID, select a provider connection for a service, or change a field such as temperature or voice. Selecting a different named configuration replaces earlier model-setting patches; that override’s own explicit fields then apply. Changing to a connection for the same provider preserves model settings. Changing provider starts that service from the new provider’s defaults plus your explicit settings. See API Trigger for request examples and Pre-call Data Fetch for response examples. Overrides do not edit your saved configurations.

​

Archive unused setups

Archive a named configuration or connection when you no longer need it. AiLunaPro rejects archiving references still needed by a default, active configuration, workflow, or pending campaign. Change those references first. Started runs keep their resolved model settings and load the connection’s current credentials. Credential updates replace the stored values; previous credentials are not retained. Expand Archived at the bottom of Models or Providers to see archived items and select Restore to use them again. Restoring preserves the item’s UUID and settings without changing your org default. If a model configuration uses archived provider connections, restore those providers first. Archived items do not appear in configuration selectors.