nemo-secrets

To securely store API keys for inference providers in NeMo, use the nemo-secrets skill via the CLI to create named secrets, allowing safe reference in platform commands without exposing raw values.

Yes, you can manage credentials for multiple LLM providers within the NeMo platform by creating, listing, updating, and deleting named secrets to facilitate secure injection into provider configurations.

Yes, you need the nemo CLI tool to interact with local platform services and workspace configuration to securely store and retrieve authentication tokens for inference providers.

The best way to avoid exposing raw API keys when configuring inference providers is to store them as named secrets via the CLI, then reference those names safely in subsequent NeMo platform commands.

Using named secrets instead of direct values when setting up a new LLM provider in NeMo ensures secure storage of authentication tokens, preventing the exposure of sensitive credentials in your workspace configuration.

Credential management for the NeMo platform environment requires the local nemo CLI tool to interact with workspace configuration, limiting direct usage to environments where the CLI is installed and configured.