nazca CLI
- Command
-
nazca - Docs
- https://github.com/Mysios-Labs-inc/nazca#readme
$ nazca setup Acquired by the CLI — running nazca setup opens the auth flow and stores the credential.
$ nazca login Run nazca login and select fal.ai, then paste your key; for non-interactive use, export FAL_KEY or store it with nazca config set fal_key <key>. The nazca docs point users to the fal.ai key dashboard. See mysioslabs integrations metadata, the nazca README, and CLI source.
$ nazca login Run nazca login and select ByteDance ModelArk, then paste your key; for non-interactive use, export ARK_API_KEY or store it with nazca config set ark_api_key <key>. The owner metadata notes you must activate the specific Seedream/Seedance model first in the ModelArk console. See mysioslabs integrations metadata, the nazca README, and CLI source.
$ nazca login Run nazca login and select OpenAI, then paste your key; for non-interactive use, export OPENAI_API_KEY or store it with nazca config set openai_api_key <key>. See mysioslabs integrations metadata, the nazca README, and CLI source.
$ nazca config set atlas_api_key Store your Atlas Cloud key with nazca config set atlas_api_key <key>; for non-interactive use, export ATLAS_API_KEY. The owner metadata lists Atlas as an opt-in backend. See mysioslabs integrations metadata, the nazca README, and config source.
$ nazca login Run nazca login and select Worder, then paste your key; for non-interactive use, export WORDER_API_KEY or store it with nazca config set worder_api_key <key>. See mysioslabs integrations metadata, the nazca README, and CLI source.