Axiom
Give the Sazabi agent the Axiom CLI (axiom) in its sandbox to run query, stream, and ingest workflows.
About
This CLI connection makes the Axiom CLI (axiom) available in the Sazabi agent's sandbox. The agent can run query, stream, and ingest workflows against your Axiom organization. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.
Prerequisites
- A Sazabi project.
- An Axiom API token (
AXIOM_TOKEN) and organization ID (AXIOM_ORG_ID).
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Axiom in the catalog
In Settings > Sandbox CLIs, find Axiom under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required values: AXIOM_TOKEN — your Axiom API token; AXIOM_ORG_ID — your Axiom organization ID. Optionally set AXIOM_URL to target a self-hosted or non-default Axiom endpoint. 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 Axiom CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type axiom --env AXIOM_TOKEN=<your-axiom-token> --env AXIOM_ORG_ID=<your-org-id>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 axiom CLI (for example axiom dataset 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 Axiom 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 axiom.