Skip to main content
Documentation menu / Integrations

Integrations

Store provider credentials and control the model providers that Versalist can use.

Manage provider credentials in Inference providers. Manage Versalist platform keys in Developer API.

Credential types

  • A provider credential authorizes supported calls to OpenAI, Anthropic, Google Gemini, xAI, Mistral, Cohere, DeepSeek, Amazon Bedrock, Azure OpenAI, Google Vertex AI, Cloudflare Workers AI, Groq, Cerebras, Together AI, Fireworks AI, Baseten, DeepInfra, Replicate, OpenRouter, Perplexity, or any OpenAI-compatible endpoint you host.
  • A Versalist API key authorizes the CLI, MCP server, or supported Versalist API request.

These credentials are not interchangeable.

Add a provider credential

  1. Open Inference providers.
  2. Select the provider that the workflow uses.
  3. Enter the credential fields the provider needs: a single API key for most providers, access key, secret, and region for Amazon Bedrock, endpoint URL and key for Azure OpenAI, a service account key file for Google Vertex AI, account ID and token for Cloudflare, or a base URL and optional key for a self-hosted endpoint.
  4. Pick a model, or enter a custom model id where the provider allows it.
  5. Save the credential. You can choose to verify the connection when you save it.
  6. If you verify the connection, check the result.
  7. If the provider is paused, enable it.

Verification methods differ by provider. A successful credential check does not always confirm access to the selected model.

Do not add credentials for providers that the workspace does not use.

How credentials are stored

  • Versalist stores provider credentials in Google Secret Manager, in a separate secret for each user and provider. Self-hosted deployments can use encrypted database storage instead. The settings page shows the backend in use and labels credentials stored in a different one.
  • Versalist shows a masked hint for a saved credential. It does not show the secret again.
  • Versalist reads the credential in memory to make supported provider requests.
  • For Secret Manager credentials, deletion removes the credential record and queues secret cleanup.

Provider groups

Frontier model labs

OpenAI, Anthropic, Google Gemini, xAI, Mistral AI, Cohere, and DeepSeek authenticate with a single API key.

Hyperscaler clouds

Amazon Bedrock, Azure OpenAI, and Google Vertex AI use your cloud account credentials. Use these when organization infrastructure or policy requires the provider.

Open-source model hosts

Groq, Cerebras, Together AI, Fireworks AI, Baseten, DeepInfra, Replicate, and Cloudflare Workers AI host open models. Cloudflare needs an account ID and an API token. Replicate support is in beta because its models expose different input schemas.

Routers and self-hosted

OpenRouter and Perplexity use an API key. The Ollama / custom option accepts any OpenAI-compatible base URL that is reachable from Versalist servers over HTTPS.

Capability status

Provider keys: available

Versalist stores provider credentials per user and uses them for supported model calls. Company-managed provider credentials are not available.

Custom model endpoint: available

Connect vLLM, TGI, LM Studio, Ollama, or a dedicated deployment through the OpenAI-compatible option. Local addresses require a deployment configured to allow private endpoints.

User-managed compute: planned

The current product does not expose a general container, cluster, or graphics processor adapter.

A provider entry in the product directory does not confirm an executable integration.

Rotate a credential

  1. Create a new credential with the provider.
  2. Replace the stored credential in Versalist.
  3. Check the verification result, or choose Verify connection from the Manage menu.
  4. Revoke the old provider credential.

For Secret Manager credentials, Versalist queues cleanup of the previous secret version.

Disable a provider

Pause a credential to stop using that credential without removing its saved configuration. Requests may use platform credentials when available. Delete the credential when you no longer need 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.

Was this page helpful?