Skip to content

Getting Started

This guide walks you through authentication, your first commands, and useful configuration options.

Info

For installation instructions, see the Verda CLI overview.

Configure authentication

Run the interactive login wizard to save your credentials:

verda auth login

The wizard prompts you for your Client ID and Client Secret, then saves them to ~/.verda/credentials.

To verify your credentials are configured correctly:

verda auth show

Credential resolution

The CLI resolves credentials in this order:

  1. CLI flags — --auth.client-id and --auth.client-secret
  2. Config file — ~/.verda/config.yaml
  3. Environment variables — VERDA_CLIENT_ID and VERDA_CLIENT_SECRET
  4. Credentials file — ~/.verda/credentials

For CI/CD pipelines, environment variables are recommended:

export VERDA_CLIENT_ID="your-client-id"
export VERDA_CLIENT_SECRET="your-client-secret"

Multiple profiles

You can store credentials for multiple accounts using profiles. Switch between them with:

verda auth use <profile-name>

Run your first command

Check what instance types are available:

verda instance-types

Or see available locations:

verda locations

To get an overview of your account including running instances, volumes, and costs:

verda status

Diagnose issues

If something isn't working, run the built-in diagnostic tool:

verda doctor

This checks your credentials, API reachability, authentication, CLI version, and directory permissions.

Shell completion

Generate shell completions for your shell:

verda completion bash > /etc/bash_completion.d/verda

verda completion zsh > "${fpath[1]}/_verda"

verda completion fish > ~/.config/fish/completions/verda.fish

Global flags

These flags are available on all commands:

Flag Description
-o, --output Output format: table, json, or yaml (default: table)
--agent Agent mode: JSON output, no prompts, structured errors
--debug Enable debug output with API request/response details
--timeout HTTP request timeout (default: 30s)
--config Path to config file (default: ~/.verda/config.yaml)

Next steps

You're now ready to start managing Verda resources from the command line.

Next, explore:

  • Instances — provision and manage GPU and CPU instances
  • Storage — create and manage block volumes
  • Resources — manage SSH keys, startup scripts, and templates
  • Cost & Status — estimate costs and monitor your account