Developers

Talise CLI

Your Talise wallet in the terminal: read your balance, send to a name, request money and script payments, with the signing key on your machine.

The talise command uses the same account as the Talise apps. You sign in once through your browser; after that you can check your balance, send to a Talise name, create a payment link or ask Copilot in plain English. Every command takes --json, so scripts and agents can read the result.

Install

The CLI needs Node.js 22 or later. Build it from the public repository at github.com/talise-public/talise-cli and link it onto your PATH:

Install from source
git clone https://github.com/talise-public/talise-cli.git
cd talise-cli
npm install
npm run build
npm link

Check it worked with talise --version. Without npm link, run it as node dist/index.js from the repository folder.

Sign in

  1. Run talise login

    The CLI creates a fresh signing key on your machine and opens your browser.

  2. Sign in with Google

    Sign in to your Talise account. Your sign-in is tied to the key the CLI just made, and only this CLI can finish it.

  3. You’re signed in

    The CLI saves your session and prints your name and address. If the sign-in times out, run talise login again.

talise login

You’ll need to sign in again from time to time. When that’s due, commands that move money tell you to run talise login.

Configuration

Session file

Your session lives in one file, session.json, readable only by you. It holds your sign-in, your Sui address and name, and the local signing key. Treat it like a password.

LocationWhen
$TALISE_CONFIG_DIR/session.jsonTALISE_CONFIG_DIR is set
$XDG_CONFIG_HOME/talise/session.jsonXDG_CONFIG_HOME is set
~/.talise/session.jsonOtherwise

Environment variables

TALISE_SESSIONstring
A whole session from talise session export. Takes the place of the session file, for servers and agent hosts with no disk.
TALISE_CONFIG_DIRpath
Where to keep session.json.
NO_COLORany
Turns colour off, like --no-color.

Output and scripting

  • Human mode (the default) prints friendly text, coloured only in an interactive terminal.
  • --json writes one JSON object per command to stdout and sends every message to stderr, so stdout is always clean data.
  • Exit codes: 0 on success, 1 on any failure. In --json mode a failure prints an error object to stdout.
A failure with --json
{"ok":false,"error":"not signed in - run `talise login` first"}

Global flags

--jsonflag
Machine output on stdout, messages on stderr.
--yes, -yflag
Skip the confirmation. Required to move money when there’s no terminal.
--quiet, -qflag
Hide human messages.
--no-colorflag
Turn colour off.
--help, -hflag
Help for any command, for example talise send --help.
--version, -vflag
Print the version.

Commands

CommandWhat it does
login, logout, whoamiSign in, sign out, show who you are
balance, activity, resolveRead your account
send, requestPay someone, or create a link to get paid
swap, save, cashoutSwap to USDsui, earn, cash out
ask, chatTalk to Copilot
agent, sessionAgent-to-agent payments, and moving your session to another machine
mcpRun Talise as a local MCP server

login

Opens your browser to sign in and saves a session. See Sign in.

Usage
talise login

logout

Deletes the local session file. You’ll need to sign in again to read or send.

Usage
talise logout

whoami

Prints the signed-in account: Sui address, Talise name, .sui name and email.

Usage
talise whoami [--json]
talise whoami --json

balance

Shows your USDsui, your SUI and the total in US dollars. Alias: bal.

Usage
talise balance [--json]
talise balance --json

activity

Lists your recent transactions, newest first.

Usage
talise activity [--limit N] [--json]
--limitnumber
How many to show. Defaults to 20.
talise activity --limit 2 --json

resolve

Turns a Talise name, @handle or .sui name into its Sui address, without sending anything. Use it to check a recipient first.

Usage
talise resolve <name|@handle|0x…>
talise resolve @amara --json

send

Sends money to a Talise name, a .sui name or a Sui address. The CLI finds the recipient, asks you to confirm, signs on your machine and sends. It settles on Sui in under a second. Alias: pay.

Usage
talise send <amount> <recipient> [--asset USDsui|SUI] [--yes] [--json]
amountnumberRequired
How much to send, in US dollars for USDsui.
recipientstringRequired
@amara, amara, amara.talise.sui, any .sui name, or a 0x address.
--assetUSDsui | SUI
What to send. Defaults to USDsui.
talise send 5 @amara --yes --json

request

Creates a money request link anyone can pay. No money moves and nothing is signed.

Usage
talise request <amount> [--note "…"] [--json]
amountnumberRequired
The amount to request, in US dollars.
--notestring
A note the payer sees, like what it’s for.
talise request 20 --note "lunch" --json

swap

Swaps SUI, USDC or DEEP in your wallet into USDsui. The CLI shows what you’re swapping and asks you to confirm.

Usage
talise swap <amount> <SUI|USDC|DEEP> [--yes] [--json]
amountnumberRequired
How much of the source token to swap.
tokenSUI | USDC | DEEPRequired
What to swap from. You always receive USDsui.
talise swap 10 USDC --yes --json

save

Puts USDsui to work in Earn, at the best rate available when you save. To take money out of Earn, use Earn in the Talise app.

Usage
talise save <amount> [--yes] [--json]
amountnumberRequired
USDsui to save.
talise save 50 --yes --json

cashout

For accounts in Nigeria: cashes out in naira to your saved primary Nigerian bank account. You give the amount in US dollars; the output shows how much naira arrives and the last 4 digits of the account. To cash out in other currencies, use the app: see Cash out.

Usage
talise cashout <amount> [--yes] [--json]
amountnumberRequired
US dollars to cash out.
talise cashout 20 --yes --json

If you have no saved bank account, the command stops and asks you to add one in the app first.

ask

Asks Copilot one question in plain English. It streams the answer. For a money request it proposes a plan, shows each step and runs it only after you confirm.

Usage
talise ask "<what you want>" [--yes] [--json]
talise ask "send 5 dollars to amara"

With --json, the result is { reply, intent, results }: Copilot’s answer, the proposed plan (or null), and what each step returned.

chat

Opens an interactive session with Copilot. It keeps the conversation’s context, and confirms before any step that moves money. Type /exit or press Ctrl+C to leave.

Usage
talise chat

agent whoami

Prints a machine-readable identity another agent can pay. The payTo field is your @handle, or your address if you don’t have one.

Usage
talise agent whoami --json
Output
{ "cli": "talise", "protocol": "talise-a2a/1", "address": "0x1234…abcd", "handle": "svc", "payTo": "@svc" }

agent pay

Pays another agent or person without prompts. It signs with your own session’s key, exactly like send. Pass --yes when there’s no terminal.

Usage
talise agent pay --to <recipient> --amount <n> [--memo "…"] [--asset USDsui|SUI] --yes --json
--tostringRequired
A Talise name, .sui name or 0x address.
--amountnumberRequired
How much to pay.
--memostring
A reference for your own records, echoed back in the output.
--assetUSDsui | SUI
What to pay with. Defaults to USDsui.
talise agent pay --to @serviceb --amount 0.25 --memo "job:123" --yes --json

agent recv

Lists payments you’ve received recently. Use it to watch for new ones.

Usage
talise agent recv [--since <ms>] --json
--sincenumber
Only show payments after this time, in Unix milliseconds.
Output
{
  "inbound": [
    {
      "digest": "3Jd8…p2Lm",
      "amount": 0.25,
      "from": "clientbot",
      "at": 1762905600000,
      "suiscan": "https://suiscan.xyz/mainnet/tx/3Jd8…p2Lm"
    }
  ]
}

session

Moves your signed-in session to another machine you control, such as a server that runs your agent. export prints the session as text; import saves it from a file, an argument or stdin.

Usage
talise session export
talise session import [file]
Examples
# Use it as an environment variable on the agent host
export TALISE_SESSION="$(talise session export)"

# Or copy it over SSH
talise session export | ssh agent-host 'talise session import'

mcp

Runs a local MCP server, signed in as your CLI session. Most people should use the hosted MCP connector instead; the local server is for desktop clients that start a command.

Usage
talise mcp
claude_desktop_config.json
{
  "mcpServers": {
    "talise": { "command": "talise", "args": ["mcp"] }
  }
}
ToolWhat it does
talise_whoamiThe signed-in identity: Sui address, handle, email.
talise_balanceUSDsui, SUI and the total in US dollars.
talise_activityRecent transactions. Input: limit (default 10).
talise_resolveA name to its address. Input: query.
talise_askAsk Copilot. Returns the answer and any proposed plan; never moves money. Input: prompt.
talise_sendSend USDsui. Inputs: amount, recipient, confirm. Without confirm: true it returns the plan and sends nothing.

help and version

talise help lists every command. talise help send or talise send --help shows one command. talise --version prints the version.

Troubleshooting

MessageWhat to do
not signed in - run `talise login`No session, or it ended. Sign in again.
your session can no longer sign - run `talise login` againYour sign-in on this machine has ended. Sign in again.
this account isn't approved to move money yetReading works, but payments aren’t on for this account yet. Email support@talise.io.
blocked by a compliance screenA safety check stopped the payment. Nothing moved. Email support@talise.io if you think it’s wrong.
could not resolve recipientCheck the name, or use a 0x address.
refusing to move money non-interactively without --yesThere’s no terminal to confirm in. Add --yes if you mean it.
rate limited - slow down and retry shortlyWait a moment and try again.
request timed outCheck your connection. Before you retry a send, check talise activity so you don’t pay twice.

The CLI works on the same account as the Talise apps, so everything you do here shows in the apps too.

Next steps