Manage provider credentials in Integrations. Manage Versalist platform keys in API keys.
Credential types
- A provider credential authorizes supported calls to OpenAI, Anthropic, Google, Azure, Amazon Bedrock, or another provider.
- A Versalist API key authorizes the CLI, MCP server, or supported Versalist API request.
These credentials are not interchangeable.
Add a provider credential
- Open Integrations.
- Select the provider that the workflow uses.
- Enter the provider credential.
- Save the credential.
- Enable the provider.
- Run a small test request.
Do not add credentials for providers that the workspace does not use.
Provider groups
OpenAI and Anthropic
Use these integrations for supported model calls through your provider account.
Google, Azure, and Amazon Bedrock
Use these integrations when organization infrastructure or policy requires the provider.
Other providers
The integration page lists other supported providers. Test a provider before production use.
Capability status
Provider keys: available
Versalist can store supported provider credentials and use them for supported model calls.
Custom model endpoint: planned
The current product does not expose a general OpenAI-compatible endpoint adapter.
User-managed compute: planned
The current product does not expose a general container, cluster, or graphics processor adapter.
A provider entry in the tool catalog does not confirm an executable integration.
Rotate a credential
- Create a new credential with the provider.
- Replace the stored credential in Versalist.
- Run a test request.
- Revoke the old provider credential.
Disable a provider
Disable a provider when you must stop traffic without removing its saved configuration. Remove the credential when the workspace no longer needs it.
Troubleshooting
The CLI rejects authentication
Check the Versalist platform key. Provider credentials do not authenticate CLI requests.
A model request does not reach the provider
Confirm that the correct provider is enabled.
The provider rejects the request
Check credential validity, provider permissions, billing status, and model access.
The failure continues
Record the provider, model, request time, and error message. Then contact support.