The command line

Same data as the app, no browser. Useful if you already live in a terminal, and useful for scripting things the app does not do.

Install

npm install -g @leadbind/cli

Or run it straight from the repo without installing:

node leadbind.mjs

It has no dependencies. That is deliberate: a tool you use to check on your business should not break because something four levels down published a bad version.

Sign in

leadbind login

Paste a key from Account → AI Access in the web app. See Connect an assistant for how to make one.

The key is stored at ~/.leadbind/config.json with permissions 0600, meaning only your user account can read it. Sign out with leadbind logout, which deletes it.

Warning: logout removes the key from your machine. It does not revoke it. If you think a key leaked, revoke it in the web app, which kills it everywhere at once.

Commands

Command	What it does
leadbind leads	Your leads, newest first
leadbind calls	Recent calls with outcomes
leadbind bookings	Upcoming appointments
leadbind availability	Your genuinely open slots
leadbind metrics	Calls, connect rate, and bookings over a window
leadbind add-lead	Add someone to the pipeline
leadbind book	Book an appointment
leadbind login / logout	Manage your key on this machine

Most read commands take --limit. metrics takes --days.

Examples

Check the morning:

leadbind bookings
leadbind calls --limit=10

Add someone who just phoned:

leadbind add-lead --name="Maria Lopez" --phone=8325550134

Book a slot. Take --start from leadbind availability, never from your head:

leadbind availability
leadbind book --start=2026-07-24T14:00:00-05:00 \
  --name="Maria Lopez" \
  --phone=8325550134 \
  --email=maria@example.com \
  --consent

Important: --consent means the customer actually agreed to the appointment and to being contacted about it. It is not a flag you add to make the command work. See Consent and opt-outs.

Scripting it

Every command prints plain text, so it pipes:

# Anything with no answer, into a file for the morning
leadbind calls --limit=100 | grep no_answer > callbacks.txt

The same permissions apply as everywhere else. A read-only key runs the read commands and refuses book and add-lead. See Keys and permissions.

CLI or assistant?

Both hit the same API, so it is purely about how you want to work.

• The CLI is exact. You said leadbind bookings, you got bookings. Good for scripts and for anything running unattended.
• An assistant is better when the question is fuzzy, or when the answer needs something outside LeadBind. "Which leads went cold and are worth another call" is a question the CLI cannot answer and Claude can.

Anything the CLI can do, a connected assistant can do too. The reverse is not true.