SkillAgentSearch skills...

bankr

Bankr is an AI crypto agent with its own wallets, a direct Wallet API and a pay-as-you-go LLM gateway, driven by the `bankr` CLI or the REST API.

Install / Use

npx skills add BankrBot/skills --skill bankr

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Category

Automation

Supported Platforms

Zed

Our assessment of bankr

bankr scores 90/100 on our quality scale, 1245th of 2,790 Automation skills we index (top 45%).

Its SKILL.md is 21 KB long, well organised into 16 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 1,201 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
17/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so bankr is actively maintained.
  • Our last check on 2026-10-30 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

bankr compared with similar skills

All 4 of these similar skills score higher than bankr; compare them before choosing.

SkillScoreStarsUpdatedFormat
bankr (this skill)by BankrBot901.2k54d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install bankr?
Run npx skills add BankrBot/skills --skill bankr. The install tabs above show the steps for each supported agent.
Which AI agents does bankr work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is bankr safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is bankr still maintained?
The repository was last updated about 2 months ago, so bankr is actively maintained.

name: bankr description: Bankr is an AI crypto agent with its own wallets, a direct Wallet API and a pay-as-you-go LLM gateway, driven by the bankr CLI or the REST API. Use it when the user wants to trade or swap crypto or tokenized stocks, check balances or PnL, send tokens, trade perps (Hyperliquid, Avantis) or prediction markets (Polymarket), buy, sell or mint NFTs, look up prices, market data or token research, claim Merkl rewards, browse the web through the agent, launch a token or claim its fees, automate orders, sign or submit transactions, call or deploy x402 paid endpoints, store files on their wallet, or use and pay for LLMs through Bankr. Chains: Base, Ethereum, Polygon, Solana, Unichain, World Chain, Arbitrum, BNB Chain, Robinhood Chain and Arc. metadata: { "clawdbot": { "emoji": "📺", "homepage": "https://bankr.bot", "requires": { "bins": ["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].

| New-key default | Flag to change it | | --- | --- | | Wallet API on | --no-wallet-api | | Agent API on | --no-agent-api | | Token Launch API on | --no-token-launch | | Read-write | --read-only (for research or monitoring keys that must never transact) | | LLM gateway off | --llm |

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+).

Other ways in

  • Existing key: bankr login --api-key bk_.... Add --llm-key <key> if the user has a separate gateway key. To mint a key in the browser, bankr login --url prints the bankr.bot/api-keys link.
  • Sign-In with Ethereum: bankr login siwe --private-key 0x.... These keys start read-only; pass --read-write to allow transactions.
  • Confirm the login with bankr whoami.

Bankr CLI

Install with bun install -g @bankr/cli (or npm install -g @bankr/cli), and update with bankr update.

bankr --help and bankr <command> --help are the command reference, docs.bankr.bot/cli has the full guide, and the changelog lists what changed in each published version. Command groups: wallet (portfolio, transfer, swap, sign, submit), agent (prompt, status, cancel, skills), tokens, launch, fees, project (0.3.43+), files, club, llm, x402, webhooks, config, plus login, logout and whoami.

Behavior that --help doesn't spell out:

  • Anything that isn't a command is a prompt. bankr what is the price of ETH? is the same as bankr agent "what is the price of ETH?". Named commands take precedence, so a prompt that starts with a command word (claude, launch, …) has to go through bankr agent "...".
  • The shell expands $. In "Buy $50 of ETH", $5 expands to nothing and the agent sees Buy 0 of ETH. Use single quotes, pipe the prompt (echo 'Buy $50 of ETH on Base' | bankr agent prompt), or run bankr agent prompt with no argument for an interactive input.
  • Threads. Every prompt runs in a thread. -c/--continue reuses the last thread and --thread <id> picks one.
  • Progress. While a prompt runs, the CLI prints the agent's status lines to stderr (0.3.43+), so piped stdout carries only the response. bankr agent status <jobId> --wait (0.3.43+) follows an existing job.
  • Max Mode. -m/--model <id> runs the prompt on a model from the Max Mode lineup, billed from LLM credits. An ID outside the lineup is rejected with the accepted list (see LLM gateway).
  • Non-interactive mode (--ni, or BANKR_NOT_INTERACTIVE=1) implies --yes and fails fast instead of prompting. Commands that normally prompt then need their inputs as flags:
    • login: --api-key, email … --code, or siwe --private-key;
    • launch: --name;
    • fees claim-wallet: --all, plus --private-key or BANKR_PRIVATE_KEY;
    • agent: the prompt as an argument or on stdin.
  • Config lives in ~/.bankr/config.json; override the path with --config <path> or BANKR_CONFIG. Environment variables win over the file: BANKR_API_KEY, BANKR_API_URL, BANKR_LLM_KEY (falls back to the API key) and BANKR_LLM_URL. Read and write values with bankr config get|set apiKey|apiUrl|llmKey|llmUrl.
  • Deprecated aliases still work but print a warning: prompt, status, cancel, balances, sign, submit, and profile / agent profile (now bankr project, 0.3.43+). On older versions bankr project … isn't a command, so the prompt fallthrough sends it to the agent as text; use bankr agent profile there.

REST API

Base URL: https://api.bankr.bot. Send X-API-Key: bk_... on every request.

Agent API: prompts (async)

  1. POST /agent/prompt answers 202 with { jobId, threadId }. Any other status means no job was created; read the body instead of polling.
  2. Poll GET /agent/job/{jobId} every ~2 s until status is completed, failed or cancelled.
  3. POST /agent/job/{jobId}/cancel stops a running job.

To continue a conversation, send the returned threadId with the next prompt.

Prompts need Bankr Club, or Max Mode with LLM credits (a maxMode model on the request, or one saved on the wallet). Without either, the request gets 403 subscription_required with a remediation list. Club allows 1,000 prompts per rolling 24 hours; Max Mode without Club allows 100.

RESP=$(curl -s -X POST https://api.bankr.bot/agent/prompt \
  -H "X-API-Key: $BANKR_API_KEY" -H "Content-Type: application/json" \
  -d '{"prompt": "What is my ETH balance?"}')
JOB_ID=$(echo "$RESP" | jq -r '.jobId // empty')
if [ -z "$JOB_ID" ]; then echo "$RESP"; exit 1; fi   # no job: the body says why (403 subscription_required, 429, ...)
for _ in $(seq 150); do                               # 150 x 2 s = 5 min, the CLI's own cap
  R=$(curl -s "https://api.bankr.bot/agent/job/$JOB_ID" -H "X-API-Key: $BANKR_API_KEY")
  case $(echo "$R" | jq -r .status) in completed|failed|cancelled) break ;; esac
  sleep 2
done
echo "$R" | jq -r '.response // .error // .status'

Never poll without a jobId: GET /agent/job/null answers 404 Job not found on every call, so an unguarded loop never ends. A job still running after five minutes keeps running; keep its jobId and poll again later, or cancel it.

references/agent-api.md covers job fields, status updates, rich data and failure handling.

Wallet API: direct, synchronous

| Endpoint | What it does | | --- | --- | | GET /wallet/me | Wallet addresses and account info. This is also the quickest way to check that a key works | | GET /wallet/portfolio | Balances, with ?include=pnl,nfts and ?chains=base,solana | | POST /wallet/swap-quote | Quotes a swap: same-chain EVM, cross-chain or Solana | | POST /wallet/swap | Executes a swap. The output always goes to your own wallet | | POST /wallet/transfer | Sends a token (by contract address) to a 0x address. Resolve an ENS name or social handle first with GET /addresses/resolve | | POST /wallet/sign | Signs a message, EIP-712 typed data or a transaction | | POST /wallet/submit | Broadcasts a raw transaction |

  • Reads (me, portfolio, swap-quote) work with read-only keys. swap-quote still needs walletApiEnabled.
  • Writes (swap, transfer, sign, submit) need walletApiEnabled on a read-write key.
  • Once a key has a recipient allowlist on either chain, transfer only sends to addresses on its EVM list, so a Solana-only allowlist refuses every transfer. swap has no recipient to check, because its output returns to you.
  • submit is also checked against the wallet's security settings: spend limits, permitted recipients and the arbitrary-contract-calls switch. Its 403 comes either with a machine-readable errorCode or with a plain message and no code, so handle both shapes.
  • These endpoints need no key: GET /addresses/resolve, GET /users/search, GET /token-launches and GET /token-launches/quote-tokens?chain=<chain>.

For details, see docs.bankr.bot/wallet-api/overview and references/sign-submit-api.md. Swaps are covered in references/token-trading.md.

Capabilities: where to look

Most of these work by asking the agent (bankr agent "..." or POST /agent/prompt). Before anything non-trivial, read the reference for that area.

| Area | Reference | Docs | | --- | --- | --- | | Swaps and bridging, including the direct swap API | token-trading.md | Swaps, Wallet API swap | | Limit, stop, DCA and TWAP orders; scheduled

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryAutomation
Updated1mo ago
Forks629

Languages

JavaScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium