Stripe
Give the Sazabi agent the Stripe CLI (stripe) in its sandbox to inspect and work with your Stripe account.
About
This CLI connection makes the Stripe CLI (stripe) available in the Sazabi agent's sandbox. 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 Stripe secret key (
STRIPE_SECRET_KEY). Find this in your Stripe dashboard under Developers > API keys. Use a restricted key scoped to the minimum permissions the agent needs.
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Stripe in the catalog
In Settings > Sandbox CLIs, find Stripe under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: STRIPE_SECRET_KEY (your Stripe secret key, beginning with sk_live_ or sk_test_). 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 Stripe CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type stripe --env STRIPE_SECRET_KEY=<your-stripe-secret-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 stripe 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 Stripe CLI connection is enabled for the project under Settings > Sandbox CLIs.
Authentication or connection fails — Recheck the credential/connection values under Settings > Sandbox CLIs.