> ## Documentation Index
> Fetch the complete documentation index at: https://docs.avibe.bot/llms.txt
> Use this file to discover all available pages before exploring further.

# Model Service

> Understand the cloud models that power Avibe Voice input and Memory, and who chooses them.

Model Service supplies the cloud models used by Avibe product features such as Voice input and Memory. These models are separate from the models your Agents use.

Voice input sends audio through avibe.bot for transcription.

See the [network boundary inventory](/concepts/local-first#what-leaves-your-machine) for where Voice and Memory 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. Memory works out of the box with a limited free allowance, with no model or API key to configure.

When you turn Memory on, message content is sent to Avibe's cloud models to build memories, and Memory searches send their queries to the same cloud service. Eligible attachment copies are also sent when attachment processing is available. Your Memory store and search index remain on your machine. See [Set up Memory](/get-started/memory) before enabling it.

If you prefer your own provider, switch Memory to **Custom endpoints** at any time. 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.

Members see **Models are managed by your organization** in Memory settings. The organization controls the model source; each member still controls the local Memory toggle, **Restart engine**, and **Clear Memory Data** on their own Avibe.

## 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. Changing an Embedding model or endpoint address rebuilds the local Memory index for every member, so Config Center asks for confirmation before saving that change.

## Model Service and Model Hub

|                  | Model Service                            | [Model Hub](/concepts/model-hub)   |
| ---------------- | ---------------------------------------- | ---------------------------------- |
| Powers           | Avibe Voice input and Memory             | Your Agents                        |
| Models come from | Avibe's shared pool or your organization | Subscriptions and API keys you add |
| Runs through     | avibe.bot                                | Your machine                       |
| Configured by    | Avibe or an organization admin           | You                                |

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