API Keys

Obtaining a key#

Dash uses NVIDIA NIM API keys. Create an account at build.nvidia.com and generate an API key. NVIDIA keys start with nvapi_.

Setting the key#

Run dash, then use the provider command:

/providers

Paste the key into the encrypted-input field (the prompt hints the nvapi_... format) and save. The key is stored immediately; no re-launch is required.

Key storage and encryption#

Keys live in ~/.dash/config.json. Dash encrypts the key before writing it to disk and decrypts it on load:

{
  "providers": {
    "nvidia": {
      "apiKey": "BASE64-AES-256-GCM-DATA",
      "model": ""
    }
  }
}

• Cipher: AES-256-GCM, 12-byte random IV, appended auth tag, stored as base64 (IV ‖ tag ‖ ciphertext).
• The SHA-256 of your home directory path-derived key is used to encrypt/decrypt, so the file is unreadable outside your user account.
• Dash never prints your key to the terminal or logs.

Key hygiene#

• Never paste real keys into chat, issue trackers, or documentation — use placeholders like YOUR_API_KEY.
• Rotate the key from the NVIDIA portal and update it with /providers if you suspect exposure.
• Back up ~/.dash/config.json when migrating to a new machine, or simply re-enter the key there.