Bankr

At a glance

Bankr turns chat instructions into cryptocurrency actions and also exposes wallet and agent APIs. Its potential value is reducing the interface work around an on-chain task, but that convenience delegates consequential authority. It is worth investigating for users who already understand the transactions they want; it is a poor substitute for learning what a trade or permission does.

Good fit

An experienced user comparing chat-driven swaps, recurring orders or wallet integration with handling those steps manually. The distinction between interfaces matters: the Agent API interprets natural language, while the Wallet API takes explicit transaction parameters. The latter is the more direct starting point when your application already knows the exact operation.

Consider something else when

You want an agent to choose investments, guaranteed execution or an embedded wallet whose keys you can export. Bankr’s support documentation says embedded-wallet transactions are signed server-side and keys are non-exportable; external-wallet mode leaves signing with you and has different feature limits. Token-launch fees only fund an agent if there is trading activity, so the self-funding claim is conditional.

Start here

Begin with the wallet-mode and API-permission documentation before signing in or funding anything. If you later create an API key, explicitly select read-only and restrict its access to the surfaces needed for a balance or address lookup. New keys are documented as read-write by default. Verify which wallet and chain a response refers to before considering any write action; no transaction was attempted for this guide.

Cost and requirements

The Club FAQ lists five free terminal messages daily, then a $20 monthly or $198 yearly subscription, or per-token Max Mode credits. Club requires an embedded wallet and renews from wallet assets automatically unless cancelled. Model access does not remove pool fees, price impact or network costs. Embedded gas sponsorship has daily and chain-specific limits; connected wallets pay their own gas.

Limits to know

Wallet-level spending controls and per-key controls are documented separately and both matter. Security screening is a vendor claim, not proof that an instruction is safe. The privacy policy collects prompts, wallet addresses and trading history. The terms’ personal, non-commercial licence needs clarification before a business integration, despite developer-facing marketing. Public pages and source documents were inspected; signing, fills, automations and custody recovery were not tested.

Related work

• ADL Dashboard: a separate read-only view of HIP3 deleveraging scenarios, not a Bankr execution feature (complement)

Still unclear

• What written permission covers commercial integrations given the published personal, non-commercial licence?