Install
checksums.txt for verifying the download.
Auth
Auth uses the same bearer credential as the 9Squid backend — a Clerk API key sent asAuthorization: Bearer <key>. There is no separate CLI auth scheme.
Resolution order (first match wins):
--api-keyflagNINESQUID_API_KEYenv var (use this in CI)- OS keychain (stored by
9squid login, per environment) ~/.9squid/config.yamlapi_key(file fallback,0600)
Environments
prod (https://api.9squid.com) and staging (https://stg-api.9squid.com).
--base-url / NINESQUID_BASE_URL / 9squid config set base-url.staging <url> override the URL itself.
Output & scripting
- Table on a TTY, JSON when piped —
--json/--tableforce either. - Data goes to stdout, everything else to stderr, so pipes stay clean.
--non-interactivedisables all prompts (or setNINESQUID_NON_INTERACTIVE=1);--yesskips a confirmation. Destructive commands (webhooks delete,alerts delete,loans review,deals subscribe) confirm before executing.- Complex request bodies: every write command accepts
--data '<json>'or--data @file.json; individual flags override fields inside--data.
0 ok · 1 generic · 2 validation · 3 auth · 4 not found · 5 rate-limited · 6 upstream error.
Command groups
Run
9squid <group> --help for the full command list.
Releases
Each release on 9Squid/cli-releases ships prebuilt binaries for macOS (x64/arm64), Linux (x64/arm64), and Windows (x64), plus achecksums.txt for verifying the download. Update by re-running the install script or downloading the latest binary — the CLI checks for and warns about newer releases on startup.