Skip to main content
An AI Provider records how Agent software reaches a model service. Keep these two surfaces separate: Changing one surface does not automatically change the other. See Core concepts and Cloud Agents.

​
Configure a Cloud Agent Provider

Sign in to the Clawdi dashboard. Keep provider credentials in the secure connection form and out of messages, screenshots, and Project instructions.
  1. Open Library > AI Providers and choose Add provider.
  2. Select a provider and, when offered, the matching region or plan.
  3. Use the provider’s credential link to obtain the correct API key, or complete the supported account sign-in flow. ChatGPT account access is offered only for compatible Agent software and connections.
  4. Save the connection and resolve any readiness or connection-test warning.
  5. Open the Cloud Agent’s AI Providers, select the saved connection, and save the change.
  6. Wait for the update to finish, then open Hermes or OpenClaw to choose a model and start a conversation.
Cloud Agent AI Providers with Clawdi AI, Configure inside agent, and Add a provider. Select AI access for this Cloud Agent after saving the account connection. Available providers and models depend on the runtime and account. View full-size image For supported native provider connections, Clawdi needs the credential; it applies it without requiring a model catalog or default model. The Agent software owns model selection, and connecting credentials preserves its existing model choices. Custom endpoints can still require an endpoint and model configuration. Clawdi AI uses its managed model catalog. Follow the fields shown for the chosen connection rather than applying native-provider instructions to every provider type.
The saved connection is available to the intended Agent, and the Agent can start a conversation with a model supported by that connection.
These controls update the remote runtime. They do not edit the local Provider Catalog on your computer. Conversely, clawdi ai-provider add does not assign a provider to a Cloud Agent.
Removing a dashboard Provider that is assigned to a Cloud Agent can leave that Agent without model access. Reassign affected Agents first and review the impact shown by the removal confirmation.
For local catalog, OAuth, import, export, and provider-specific options, use clawdi ai-provider --help and the relevant subcommand help. For remote lifecycle behavior, see Cloud Agent settings and lifecycle.

​
Add a local Provider record

Use an environment or exact Vault reference instead of putting an API key in the catalog:
The local catalog stores metadata and the env:OPENAI_API_KEY reference, not the environment variable’s value. The default test checks configuration and credential availability. Add --live only when you intentionally want a direct provider probe.To use a Vault value, first copy the exact reference from clawdi vault list and pass it as the auth reference:
The local catalog lives on this computer. It does not upload its records to the dashboard AI Providers page, and Clawdi does not proxy the Agent’s model requests; supported local Agent software calls the provider directly.

​
Manage local records

The released CLI manages Provider Catalog records; it does not activate or write provider configuration into a local Codex, Hermes, or OpenClaw installation. Inspect the shipped command list before automating a workflow:
Use the supported subcommands for the specific catalog task:
The local catalog provides list, add, edit, remove, validate, test, connect, complete-oauth, import-auth, export, and import. Run the relevant subcommand with --help before using its credential or file options. Configure local Agent software through that software’s supported settings; a catalog record by itself is inventory, not proof that an Agent is using it.
Last modified on September 10, 2026