Skip to main content
Model Service supplies the cloud models used by Avibe product features such as Voice input. These models are separate from the models your Agents use. Voice input sends audio through avibe.bot for transcription. See the network boundary inventory for where Voice content, provider credentials, and usage records go in each mode.

​
Personal Avibes

A personal Avibe paired with avibe.bot uses Avibe’s shared model pool, with no model or API key to configure. Personal Voice input always uses Model Service; custom Voice input models are not available.

​
Enterprise organizations

In an enterprise organization, an organization owner or admin uses bring your own key (BYOK) to configure the models once. Members share that configuration, and usage is charged to the organization’s provider account.

​
Config Center

Config Center is the administration surface for Model Service on avibe.bot:
  • Organization settings > Model service lets an organization owner or admin configure Voice recognition, Chat, Embedding, and Multimodal models; verify the configuration; and inspect usage by Avibe. Configuration can be prepared before an organization moves to Enterprise and becomes active after the plan changes.
  • Platform administration > Model service lets the Avibe platform admin manage the shared pool for personal Avibes, inspect usage, and apply per-Avibe limits. This surface is not available to personal users.
Each capability uses a provider, endpoint address, model, and API key. The organization keeps responsibility for its provider account and charges.

​
Model Service and Model Hub

Changing Model Hub routes does not change the models used by Voice input. Changing Model Service does not change the models used by your Agents.