Mercury
Give the Sazabi agent the Mercury CLI (mercury) in its sandbox to access read-only banking API data.
About
This CLI connection makes the Mercury CLI (mercury) available in the Sazabi agent's sandbox. The agent can use it for read-only banking API access. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.
Prerequisites
- A Sazabi project.
- A Mercury API key (
MERCURY_API_KEY), available from your Mercury account settings.
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Mercury in the catalog
In Settings > Sandbox CLIs, find Mercury under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: MERCURY_API_KEY — your Mercury 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 Mercury CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type mercury --env MERCURY_API_KEY=<your-mercury-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 mercury 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 Mercury CLI connection is enabled for the project under Settings > Sandbox CLIs.
Authentication or connection fails — Recheck the credential/connection values under Settings > Sandbox CLIs.