Usage of premier models incurs additional costs (MAUs). Administrators must communicate this to users before enabling. Premier models are not available in trial tenants. When premier models are disabled, all agents (live and draft) that use them stop working immediately.
Enabling premier models for a local or default tenant
Run the following command to enable premier models on your local or default tenant.Note:
If your local Developer Edition targets a remote watson Orchestrate instance because you set
WO_INSTANCE and WO_API_KEY in your environment file, the command above enables premier models on your local tenant only. To make premier models available in the local UI, you must also enable them on the remote instance.
The CLI warns you if this applies to your setup. To enable premier models on the remote instance, activate that environment and re-run the command. For more information, see Enabling premier models for a remote tenant (SaaS).Enabling premier models for a remote tenant (SaaS)
Before you run the enable command against a remote SaaS tenant, you must activate that remote environment. Otherwise, the command applies to your local context instead.-
Activate the target remote environment.
-
Enable premier models on that tenant.
Confirming that premier models are enabled
Run the following command to check whether premier models are currently enabled on the active tenant.Disabling premier models
To disable premier models on the active tenant, run the following command.If you disable premier models, all agents (live and draft) that use them stop working immediately.