RunPod
Give the Sazabi agent the RunPod CLI (runpodctl) in its sandbox to manage GPU pods and serverless endpoints.
About
This CLI connection makes the RunPod CLI (runpodctl) available in the Sazabi agent's sandbox. The agent can use it for GPU pods and serverless endpoints. The tool is baked into the sandbox image; connecting it authenticates (or configures the connection for) the already-installed CLI.
Prerequisites
- A Sazabi project.
- A RunPod API key (
RUNPOD_API_KEY). Generate one in your RunPod account settings.
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find RunPod in the catalog
In Settings > Sandbox CLIs, find RunPod under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: RUNPOD_API_KEY (your RunPod API key). Save to store it securely; Sazabi injects it into the sandbox when the agent runs.
Set up with the CLI
You can also configure the RunPod CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type runpod --env RUNPOD_API_KEY=<your-runpod-key>To validate the credentials without saving, run the same command with test in place of set (the test command also requires the --env flags).
Verify
Ask the agent, in a thread, to run the runpodctl CLI (a read-only or status command) and confirm it returns real output. If the command is not found, the CLI connection may not be enabled; if it runs unauthenticated or cannot connect, recheck the credentials.
Troubleshooting
Command not found — Confirm the RunPod CLI connection is enabled for the project under Settings > Sandbox CLIs.
Authentication or connection fails — Recheck the credential/connection values under Settings > Sandbox CLIs.