Bankr Skills

---
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/](references/).** A copy of `SKILL.md` alone leaves every reference link below dead.

This file is the entry point. Topic detail lives in [references/](references/) (read the one for your task before acting), in the docs at [docs.bankr.bot](https://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](references/safety.md#host-managed-credentials-no-key-on-disk).

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](https://bankr.bot/terms)**. 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` |