The AgenticBooks CLI
Your books from the terminal: open an account with the same one-approval handshake agents use, connect banks with read-only credentials, and see what's connected. Thin by design — every command drives the same public surface any agent uses.
Install
Node 20+. The CLI has zero runtime dependencies and stores exactly one thing on your machine: its credential file (below). Run:
npm install -g agenticbooks
Confirm it's installed:
agenticbooks --version
agenticbooks login
Open (or connect to) an account. This is the agent-signup handshake driven from a terminal — the CLI starts the request, you approve it from your inbox by typing the code the CLI displays (that code proves the request came from your terminal; a phishing email has no code), and the CLI collects a scoped key. Run:
agenticbooks login
Your email (the approval is sent here): you@company.com
Check you@company.com for an email from AgenticBooks.
Open the link and enter this code:
GHK-42P
Waiting for approval (the link expires in ~15 minutes)…
Approved. Key saved to ~/.agenticbooks/credentials (chmod 600).
Try: agenticbooks statusIt prompts for your email, then waits. The key it collects can read the books and resolve the review queue — it cannot move money — and you can revoke it any time from the integrations page. Skip the prompt with agenticbooks login --email you@company.com.
agenticbooks status
See what's connected and the one next step. Run:
agenticbooks status
✓ mercury connected (last sync 2026-07-15T09:12:00Z) ✓ stripe connected (last sync 2026-07-07T18:40:11Z) · meow not connected · quickbooks not connected Next: Ask your human for a read-only Meow API key (Meow dashboard → API keys — read keys need no IP allowlist). Then call the connect_meow tool with it.
Renders get_onboarding_status: what's connected (with sync recency), what's broken and needs reconnecting, what's pending, and the one next step. If a step ever carries a warning, it prints verbatim (no step warns today).
agenticbooks connect
Connect a bank with a read-only credential. Supported: mercury and meow. Run (using Mercury as the example):
agenticbooks connect mercury
Mercury dashboard → Settings → API Tokens → create a read-only token. Mercury read-only API token (input hidden): •••••••••••• Connected. Verify with: agenticbooks status
The token is typed at a hidden prompt — never passed as an argument, which would leak it into shell history. Validation is server-side: an invalid credential stores nothing. For automation, pipe the credential on stdin instead:
cat token.txt | agenticbooks connect mercury --json
Stripe, QuickBooks, RevenueCat and Revolut connect on app.agenticbooks.ai → Integrations (their OAuth and webhook flows need a browser).
agenticbooks logout
Remove the local credential file. Run:
agenticbooks logout
Local credentials removed. The key itself stays valid until you revoke it: app.agenticbooks.ai → Integrations → MCP server access.
Logging out and revoking are different: this removes the local file, but the key stays valid until you revoke it on the integrations page.
Reference
| Flag / path | Meaning |
|---|---|
--json | Machine-readable output on every command — for scripts and agents that shell out. |
--email you@company.com | Skip the interactive email prompt on login. |
~/.agenticbooks/credentials | The key, chmod 600. The only state the CLI keeps. |
AGENTICBOOKS_API_URL / AGENTICBOOKS_MCP_URL | Endpoint overrides for staging or local development. |
Everything the CLI does, an AI agent can do over the same surface — hand yours the runbook and ask for your books.