Arize
Give the Sazabi agent the Arize AX CLI (ax) in its sandbox to inspect Arize spaces, models, traces, evals, and monitors.
About
This CLI connection makes the Arize AX CLI (ax) available in the Sazabi agent's sandbox. The agent can inspect Arize spaces, models, traces, evals, and monitors on your behalf. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.
Prerequisites
- A Sazabi project.
- An Arize API key (
ARIZE_API_KEY) and an Arize space identifier (ARIZE_SPACE).
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Arize in the catalog
In Settings > Sandbox CLIs, find Arize under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required values: ARIZE_API_KEY — your Arize API key; ARIZE_SPACE — your Arize space identifier. Optionally set ARIZE_REGION to target a non-default Arize region. Save to store them securely; Sazabi injects them into the sandbox when the agent runs.
Set up with the CLI
You can also configure the Arize CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type arize --env ARIZE_API_KEY=<your-arize-key> --env ARIZE_SPACE=<your-arize-space>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 ax CLI (for example ax spaces list) and confirm it returns real output from your account. If the command is not found, the CLI connection may not be enabled; if it runs unauthenticated, recheck the credentials.
Troubleshooting
Command not found — Confirm the Arize CLI connection is enabled for the project under Settings > Sandbox CLIs.
Authentication fails — Recheck the credential values; a rotated or revoked token must be re-entered under Settings > Sandbox CLIs or with sazabi sandbox-clis set --type arize.