⠀⠀⠀⠀⠀⠀⠀⣀⡤⠶⠒⠛⠛⠉⠛⠛⢶⡶⠤⣄⡀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⣠⠔⠋⠁⠀⣀⡤⢤⡴⠶⠦⡄⠀⠹⡄⠀⠉⠳⣄⠀⠀⠀⠀
⠀⠀⢠⠞⠁⠀⣠⠖⢻⡁⠀⢾⠀⠀⠀⣹⠀⠀⡿⠓⢤⡀⠀⠱⣄⠀⠀
⠀⣰⠋⠀⢠⠞⠁⠀⠈⢧⡀⠈⠓⠲⠶⠧⢄⣰⠃⠀⠀⠙⢆⠀⠈⢧⠀
⢠⣇⡴⠒⠛⠛⠓⠲⡴⠋⠙⢦⣤⣤⣄⡀⠀⠈⢳⠴⠒⠛⠙⢧⠀⠈⣇
⣾⠋⠀⣠⠴⠶⢤⡼⠁⠀⡴⠋⠀⠀⠀⠉⢳⣴⠃⠀⣠⠴⠶⢼⡆⠀⢹
⣿⠀⠀⡇⠀⠀⢀⡇⠀⢸⡇⠀⠀⠀⠀⠀⠀⡇⠀⢰⡇⠀⠀⢈⡇⠀⢸
⢿⠀⠀⣟⠒⠒⠋⠀⢀⡼⠳⣄⠀⠀⠀⢀⡼⠁⠀⡼⠙⠒⠒⠋⠀⢀⣾
⠘⡆⠀⠸⣦⣤⡤⠴⠻⣄⠀⠈⠉⠛⠛⠻⢤⣀⠞⠳⢤⣤⣤⡤⠖⢋⡏
⠀⠹⣄⠀⠘⢦⡀⠀⢀⡞⠙⢒⡶⠶⢤⡀⠀⠹⡄⠀⠀⣠⠎⠀⢀⡞⠀
⠀⠀⠘⢦⡀⠀⠙⠦⣼⡁⠀⢼⠀⠀⠀⣹⠀⠀⣷⡤⠞⠁⠀⡰⠋⠀⠀
⠀⠀⠀⠀⠙⠢⣄⡀⠈⢧⠀⠈⠓⠶⠶⠛⠚⠋⠁⠀⣀⠴⠋⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠉⠓⠶⠷⣦⣤⣀⣠⣤⠤⠴⠒⠋⠁⠀⠀⠀⠀⠀⠀
Mercury CLI – Run your banking* from the terminal
The official command-line interface for Mercury.
Manage your Mercury account from the terminal — cards, transactions, accounts, and more.
Install
curl
curl -sSf https://cli.mercury.com/install.sh | shNix
Run without installing:
nix run github:MercuryTechnologies/mercury-cli -- accounts list
Install into your profile:
nix profile install github:MercuryTechnologies/mercury-cli
Requires Nix (or Lix) with flakes enabled.
Install with Go
To test or install the CLI locally, you need Go version 1.22 or later installed.
go install 'github.com/MercuryTechnologies/mercury-cli/cmd/mercury@latest'Once you have run go install, the binary is placed in your Go bin directory:
- Default location:
$HOME/go/bin(or$GOPATH/binif GOPATH is set) - Check your path: Run
go env GOPATHto see the base directory
If commands aren't found after installation, add the Go bin directory to your PATH:
# Add to your shell profile (.zshrc, .bashrc, etc.) export PATH="$PATH:$(go env GOPATH)/bin"
Quick start
mercury login
mercury accounts list
mercury payments create \
--account-id acc_xxx \
--recipient-id rcp_xxx \
--amount 5000 \
--payment-method ach \
--idempotency-key $(uuidgen)What you can do
- View accounts and balances (
mercury accounts) - Send payments and transfer funds between accounts (
mercury payments) - List, search, and update transactions (
mercury transactions) - Manage cards (
mercury cards) - Manage recipients, customers, and invoices (
mercury recipients,mercury customers,mercury invoices) - Download statements and SAFE documents (
mercury statements,mercury safes) - Manage treasury accounts (
mercury treasury) - Create and verify webhook endpoints (
mercury webhooks)
Upgrading
mercury upgrade # latest mercury upgrade --version 0.3.1 # pin a version mercury upgrade --force # reinstall current
Set MERCURY_INSTALL_DIR to override the install location.
When a newer release is available, mercury prints a one-line notice on stderr
after the command runs (at most once per day). To disable it:
export MERCURY_NO_UPDATE_CHECK=1Running Locally
After cloning the git repository for this project, you can use the
scripts/run script to run the tool locally:
Usage
The CLI follows a resource-based command structure:
mercury [resource] <command> [flags...]
mercury accounts get \
--api-key 'My API Key' \
--account-id REPLACE_MEFor details about specific commands, use the --help flag.
Environment variables
| Environment variable | Description |
|---|---|
MERCURY_API_KEY |
Bearer token authentication for Mercury API. |
Create and manage API tokens here: https://app.mercury.com/settings/tokens
Your Mercury API token should include the secret-token: prefix. Use it in the
Authorization header:
Authorization: Bearer secret-token:mercury_<TOKEN>
If --api-key or MERCURY_API_KEY is set, the API token takes precedence over
any OAuth session from mercury login. Run mercury status to see
which credential is active.
Global flags
--api-key- Bearer token for Mercury API--help- Show command line usage--debug- Enable debug logging (includes HTTP request/response details)--version,-v- Show the CLI version--base-url- Use a custom API backend URL--format- Change the output format (auto,explore,json,jsonl,pretty,raw,yaml)--format-error- Change the output format for errors (auto,explore,json,jsonl,pretty,raw,yaml)--transform- Transform the data output using GJSON syntax--transform-error- Transform the error output using GJSON syntax
Passing files as arguments
To pass files to your API, you can use the @myfile.ext syntax:
mercury <command> --arg @abe.jpg
Files can also be passed inside JSON or YAML blobs:
mercury <command> --arg '{image: "@abe.jpg"}' # Equivalent: mercury <command> <<YAML arg: image: "@abe.jpg" YAML
If you need to pass a string literal that begins with an @ sign, you can
escape the @ sign to avoid accidentally passing a file.
mercury <command> --username '\@abe'
Explicit encoding
For JSON endpoints, the CLI tool does filetype sniffing to determine whether the
file contents should be sent as a string literal (for plain text files) or as a
base64-encoded string literal (for binary files). If you need to explicitly send
the file as either plain text or base64-encoded data, you can use
@file://myfile.txt (for string encoding) or @data://myfile.dat (for
base64-encoding). Note that absolute paths will begin with @file:// or
@data://, followed by a third / (for example, @file:///tmp/file.txt).
mercury <command> --arg @data://file.txt
*Mercury is a fintech company, not an FDIC-insured bank. Banking services provided through Choice Financial Group and Column N.A., Members FDIC.