CLI

The bindly CLI runs the full Bindly intake lifecycle from a terminal or a script: start sessions, answer questions, extract from PDFs, fill ACORD forms, download them, and submit to Hedge. 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 (Node.js 18 or newer; npx bindly-cli also works without installing). 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

Check the signed-in workspace, plan, and auth method with bindly whoami. 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>	Session detail, intake progress, and the next questions.
bindly session answer <session-id> --message <text>	Answer intake questions conversationally; returns the next asks.
bindly session extract <session-id> <pdf>	Extract intake answers from a PDF (ACORD, dec page, supplement; 20MB max).
bindly session fill <session-id>	Fill the session’s ACORD forms from the collected answers.
bindly session download <session-id> [form-key] [-o <dir>]	Download one filled form PDF, or all of them.
bindly session risk <session-id>	Underwriting risk flags Bindly spotted in the intake.
bindly session upload <session-id> <pdf>	Attach a supporting document (loss runs, prior policy).
bindly session archive <session-id>	Archive a session.
bindly session submit <session-id>	Submit a completed session to Hedge on your connected Hedge account.
bindly whoami	Show the signed-in workspace, plan, and auth method.
bindly login / bindly logout	Sign in and out.

session submit forwards the session’s filled ACORD forms and supplements to Hedge and returns the resulting Hedge submission id.

Tip

Add --json to any command for the raw API response, so the CLI composes in scripts and pipes into jq.

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

A typical flow

1. Sign in once, and confirm the workspace:

   bindly login
   bindly whoami

2. Start an intake session for the insured:

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

3. Answer the intake conversationally, or extract answers straight from a PDF you already have:

   bindly session answer <session-id> --message "12 employees, $2.4M revenue, no claims in the last 5 years"
   bindly session extract <session-id> ./prior-acord-125.pdf

4. Check what is still open, then fill the ACORD forms:

   bindly session get <session-id>
   bindly session fill <session-id>

5. Download the filled PDFs and review the risk flags:

   bindly session download <session-id> -o ./filled
   bindly session risk <session-id>

6. 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.