CLI

The bindly CLI is the fastest way to work with your Bindly workspace from a terminal or a script. It wraps the REST API and handles sign-in and token refresh for you. Source lives at github.com/taventech/bindly-cli.

Install

npm

npm i -g bindly-cli

Homebrew

brew install taventech/tap/bindly

curl

curl -fsSL https://github.com/taventech/bindly-cli/releases/latest/download/install.sh | sh

The npm package is bindly-cli and it provides the bindly command. The Homebrew and curl options install a self-contained binary, so Node is not required.

Sign in

bindly login

By default bindly login uses the OAuth 2.1 device flow: it prints a short code and a URL, you approve the sign-in in Bindly, and the CLI stores a short-lived token. Other modes:

bindly login --browser          # loopback browser sign-in on a machine with a browser
bindly login --api-key bsk_...  # non-interactive, using a workspace API key

Sign out with bindly logout. Credentials are stored at ~/.config/taven-cli/bindly.prod.json with 0600 permissions, and access tokens refresh automatically. For the full auth model, see Authentication.

Command reference

Run bindly <command> --help for flags and examples on any command.

Command	What it does
bindly session new --insured <name> [--state ST] [--lob a,b] [--naics code]	Start an intake session for an insured.
bindly session list	List your workspace’s sessions.
bindly session get <session-id>	Show one session’s detail and intake progress.
bindly session submit <session-id>	Submit a ready session to Hedge on your connected account.
bindly login / bindly logout	Sign in and out.

Tip

Add --json to any command for machine-readable output. This makes the CLI easy to pipe into jq or wire into a script.

bindly session list --json | jq '.sessions[] | select(.status=="ready") | .session_id'

A typical flow

1. Sign in once:

   bindly login

2. Start an intake session for the insured:

   bindly session new --insured "Acme HVAC" --state TX --lob general_liability

3. Fill the intake in the Bindly app, or from an MCP assistant, then check progress:

   bindly session get <session-id>

4. Submit the finished session to Hedge:

   bindly session submit <session-id>

   The command returns the Hedge submission id.

Note

Point the CLI at a non-production engine with the BINDLY_ENGINE_URL environment variable, and set BINDLY_APP_URL for the matching approval page.

CLI on GitHubSource, releases, and the install script for the bindly CLI.