Bankr

Bankr

Bankr is an AI crypto agent that holds its own wallets. Two ways in, both using the same bk_... API key:

• Bankr CLI (@bankr/cli, recommended). It handles login, job polling and confirmations for you.
• REST API at https://api.bankr.bot. Use /agent/* for natural-language prompts (async jobs) and /wallet/* for direct, synchronous wallet operations.

Installing this skill means downloading the whole bankr/ folder: this SKILL.md plus every file in references/. A copy of SKILL.md alone leaves every reference link below dead.

This file is the entry point. Topic detail lives in references/ (read the one for your task before acting), in the docs at docs.bankr.bot, and in the OpenAPI spec at https://docs.bankr.bot/openapi/api.yaml. Fetch the spec instead of guessing a route or payload. It is the authoritative request/response schema and can be newer than this skill.

Get an API key

Check whether you're already authenticated. The host may supply the key, either as BANKR_API_KEY or through an egress proxy that attaches it to requests. Try bankr whoami, or make a request, before logging in, and never ask the user to paste a key just because the variable is empty. See host-managed credentials.

Signing up provisions an EVM wallet (one address on every EVM chain) and a Solana wallet, so there is nothing to set up by hand.

Headless email login (recommended for agents)

Run bankr update first. The flow below works on @bankr/cli 0.3.38 and later. Pass --accept-terms and --key-name explicitly: from 0.3.43 a headless login accepts the Terms by itself and picks a unique key name, but on 0.3.38 a headless login without --accept-terms fails after the one-time code has been used, and an omitted key name defaults to CLI-<date>, which collides with a key created earlier that day.

1. bankr login email <email> sends a one-time code.
2. Ask the user for everything in one message:
   • the code from their email;
   • their go-ahead on the Terms of Service. Share the link and say plainly that step 3 accepts the Terms on their behalf. If they decline, stop.
   • any changes to the key defaults below, and a key name (an active key can't reuse a name).
3. Run bankr login email <email> --code <otp> --accept-terms --key-name "<name>" [flags].

Optional hardening flags: --allowed-ips <ips> (IP/CIDR allowlist) and --allowed-recipients <addresses> (EVM/Solana send allowlist). After login, the Features: line shows what the key actually got.

• The code is single-use. From 0.3.43 the CLI retries dropped connections during login by itself. If step 3 fails, restart from step 1 for a fresh code; never re-run it with the same code.
• Accounts with MFA on: step 3 prints a https://bankr.bot/mfa/confirm/... link and waits up to five minutes for the user to approve in a browser with their passkey or authenticator app. Show the user the link, keep the command running and don't retry. If the link expires, fall back to an existing key (below). A headless login never asks for the authenticator code in the terminal; only an interactive bankr login email does (0.3.45+).