BankSync
Command-line interface

Your bank data, one command away.

Install the BankSync CLI with one command, log in with an API key, and pull transactions, list banks, or sync feeds without leaving your terminal. Designed tables for you, stable JSON for your scripts and agents.

Get StartedInstallation Guide →

Script your finance stack from the terminal.

two minutes, tops

Install and log in

One package, one login. Then you are pulling live bank data.

# One-line install: self-contained binary, no Node required
curl -fsSL https://banksync.io/install.sh | sh


# Authenticate (API key from Workspace > Developers)
banksync login --api-key bsk_...


# You're in
banksync banks list
built with taste

A CLI you will actually enjoy

Polished and restrained. Aligned tables, tasteful color, zero noise.

Ergonomic by design

Noun-verb grammar like gh and stripe: banksync banks list.

Output that fits the job

Tables for humans, stable JSON when piped. -o json|csv|ndjson.

Built for agents

Stable envelope, machine-readable errors, discoverable commands.

Tracks the API contract

Generated from the same OpenAPI spec, gated in CI.

Easy to install

One self-contained binary. macOS, Linux, Windows. No runtime.

Auth that suits you

API keys for CI and agents, OAuth for humans, encrypted locally.

noun, then verb

Grammar you can guess

Every command reads like a sentence. Pick a resource, pick a verb, pipe the rest.

# List every connected bank, with live status
banksync banks list


# Accounts under one bank
banksync accounts list bnk_123


# A one-screen overview of your workspace
banksync status
a better agent tool

Agents love a clean CLI

A stable JSON envelope, machine-readable errors, and banksync commands --json let an AI agent discover and drive the whole surface. Recent benchmarks put a well-designed CLI ahead of MCP on both token cost and reliability.

Read the agent guide →
more than a query

What you can do

From a quick lookup to a full automation pipeline.

Pull transactions in a pipeline

NDJSON into a script or warehouse, cursor paging, 429-aware.

Watch a sync finish

banksync feeds sync fd_123 --watch, live until it is done.

Give an agent a shell tool

Clean stdout, structured errors, a discoverable catalog.

Automate feeds and enrichments

Create, preview and trigger — all non-interactive.

Connect a bank from the terminal

Hands off to the web app, then polls until it appears.

Query any endpoint raw

banksync api GET /v1/... for anything not yet wrapped.

up and running fast

Get started in 3 steps

1

Install the CLI

Run curl -fsSL https://banksync.io/install.sh | sh (or irm https://banksync.io/install.ps1 | iex on Windows). A self-contained binary, no Node required. Update any time by re-running it.

2

Log in with an API key

Create an API key in Workspace > Developers, then run banksync login --api-key bsk_...

3

Pull your data

banksync banks list, banksync transactions list --bank amex --json, banksync feeds sync fd_123 --watch. You are live.

also available

Prefer an API or an AI agent?

The CLI, the REST API, and the MCP server share one API key and one dataset. Query from your own code, or talk to your bank data in Claude and Cursor.

Explore REST API →Explore MCP Server →
good questions

Frequently asked questions

What is the BankSync CLI?

The BankSync CLI is a first-party command-line tool for the BankSync public API. It lets you list banks, pull transactions, manage feeds, and trigger syncs from your terminal, with designed tables for humans and stable JSON for scripts and AI agents.

How do I install the BankSync CLI?

Install with one command: curl -fsSL https://banksync.io/install.sh | sh on macOS or Linux, or irm https://banksync.io/install.ps1 | iex on Windows. It is a self-contained binary, no Node required. Then authenticate with banksync login --api-key bsk_... using an API key from Workspace > Developers.

Is the BankSync CLI good for AI agents?

Yes. The CLI is built as a first-class agent tool. It emits a stable JSON envelope, machine-readable errors on stderr, consistent exit codes, and a banksync commands --json catalog so an agent can discover every command, flag, and field without reading docs. Recent benchmarks show a well-designed CLI beats MCP on both token cost and reliability.

What output formats does the CLI support?

Use -o to choose table, json, csv, ndjson, or toon. Tables are the default on a terminal and JSON is the default when piped, so banksync transactions list --json | jq just works. --fields selects columns with dot-paths.

How does the CLI authenticate?

API-key auth works today for both humans and CI or agent use, via banksync login --api-key or the BANKSYNC_API_KEY environment variable. OAuth login for interactive humans is phased in. Credentials are stored in an encrypted local file, never in plaintext, and are redacted from verbose logs.

Does the CLI stay in sync with the BankSync API?

Yes. The CLI generates its typed core and command reference from the same OpenAPI contract that drives the REST API, and a CI gate fails the build if they drift. A route change that is not reflected in the CLI cannot ship.

Can I use the CLI, REST API, and MCP server together?

Yes. All three use the same API key and read the same data. Use the CLI for scripting and agents, the REST API for custom integrations, and the MCP server for conversational AI access.

How do I connect a bank from the CLI?

Run banksync banks connect. The CLI opens the authenticated BankSync web app to complete the secure open-banking flow, then polls until your new bank appears. Your banking credentials never touch the CLI.

come on in

Bank data at your prompt

Connect once to 11,000+ banks, then script it all from your terminal. Free 14-day trial.

Get Started Free →Installation Guide →