AI Models

What AI Models is for

AI Models configures the model routes used by AI Companion and supported Notebook assistance. It separates provider credentials from named model routes so one protected key can serve more than one permitted model configuration.

The model supplies assistance. You remain responsible for reviewing generated code, reasoning, parameter suggestions, and explanations before using them.

Store a hosted-provider key

In AI Provider Keys:

1. select the provider;
2. paste the key supplied by its developer or account portal;
3. store it through the protected control; and
4. confirm that the provider row shows a configured reference.

Arizmic stores the reusable secret through the operating system secret store and displays a reference instead of the key. Removing the key disables routes that depend on it but does not delete their model definitions.

Review the provider's pricing, data-use, retention, and regional terms before sending context. Do not place keys inside prompts, Notebook source, Signal code, Strategy code, or support bundles.

Add a model route

In AI Models, provide:

• Provider — the service or local route that receives the request;
• Model ID — the exact identifier accepted by that provider;
• Display Name — the human-readable label shown in Arizmic; and
• Base URL — the compatible endpoint when the provider or local server requires one.

Use the model ID from the provider's current documentation or your local model server. The display name is only a label; it does not change the requested model. Leave the base URL at the provider default unless you intentionally use a compatible gateway or local endpoint.

For a local model, configure the supported local provider and the endpoint exposed by the model server. A local URL is private only if that server does not forward requests elsewhere.

Use the configuration across Arizmic

Configured model routes become available to AI Companion and to supported Notebook AI controls. The global Companion can help brainstorm Signals and Strategies, explain visible Results, draft Python authoring work, and suggest possible improvements. Treat every suggestion as a proposal to review, not an automatic product action or a performance guarantee.

When a route fails, check the provider key, exact model ID, base URL, local server state, network access, and provider entitlement. A model can be listed but unavailable because its key was removed or the external service rejected the request.

Replace or remove a route

Update a model definition when its endpoint or identifier changes. Remove an obsolete model route to take it out of selection. This does not delete the provider key; remove that separately only when no remaining route needs it.

Before removing either item, change any saved default or workflow that still selects it. See Connect models for the complete local-versus-hosted setup and privacy boundary.