Bankr Dev Transfers
- 377 installs
- 80 repo stars
- Updated March 24, 2026
- bankrbot/claude-plugins
bankr dev - transfers is an agent skill that implements crypto transfer flows in Bankr Claude plugins for developers building agent-triggered wallet sends with recipient checks, amount formatting, and on-chain settlement
About
bankr dev - transfers is an agent skill from bankrbot/claude-plugins version 1.0.0 that guides crypto transfer operations through the Bankr Agent API and CLI. It handles token sends to wallet addresses, ENS names, and social handles including Twitter, Farcaster, and Telegram usernames, resolving handles to linked wallet addresses before execution. Supported chains include EVM networks Base, Polygon, Ethereum, and Unichain for ETH, MATIC, and ERC-20 transfers plus Solana for SOL and SPL tokens. Amounts can be specified in USD, percentage of balance, or exact token units with balance checks and chain selection guidance based on recipient activity and gas costs. Developers reach for bankr dev - transfers when building payment flows or wallet features in Bankr-powered agent plugins and want to avoid writing custom recipient resolution logic. The skill surfaces resolution results and common failure modes so transfers can be confirmed before on-chain settlement.
- Agent-native crypto transfer patterns
- Bankr dev plugin conventions
- On-chain settlement guidance
- Recipient and amount validation
Bankr Dev Transfers by the numbers
- 377 all-time installs (skills.sh)
- Ranked #35 of 479 Web3 & Blockchain skills by installs in the Skillselion catalog
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/bankrbot/claude-plugins --skill bankr-dev---transfersAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 377 |
|---|---|
| repo stars | ★ 80 |
| Last updated | March 24, 2026 |
| Repository | bankrbot/claude-plugins ↗ |
How do you send crypto transfers via Bankr agents?
Implement crypto transfer flows in Bankr Claude plugins—wallet sends, recipient checks, amounts, and on-chain settlement for agent-triggered payouts.
Who is it for?
Developers building Bankr Claude plugins or agent payment flows who need multi-chain transfers with ENS and social handle recipient resolution.
Skip if: Traditional fiat payment integrations or teams not using Bankr API keys and agent wallet infrastructure for on-chain transfers.
When should I use this skill?
User asks to send tokens, transfer ETH, send to ENS, send to @username, or implement Bankr wallet payout flows.
What you get
Resolved recipient wallet address, validated transfer amount and chain, and executed or prepared on-chain token send via Bankr API.
- Transfer request with resolved recipient
- Chain and amount validation output
- On-chain settlement via Bankr agent
By the numbers
- Skill version 1.0.0 covering 4 EVM chains plus Solana
- Supports 3 recipient formats: wallet address, ENS name, and social handles
Files
Safety & Access Control
Comprehensive safety guidance for using the Bankr API and CLI.
API Key Types
Bankr uses a single key format (bk_...) with capability flags:
| Flag | Controls | Default |
|---|---|---|
agentApiEnabled | /agent/* endpoints | false |
llmGatewayEnabled | LLM Gateway at llm.bankr.bot | false |
readOnly | Restricts agent to read-only tools | false |
Manage flags at bankr.bot/api.
Read-Only API Keys
When readOnly: true, all write tools are filtered from the agent session:
Allowed: Balances, prices, analytics, portfolio, research Blocked: Swaps, transfers, NFT purchases, staking, orders, token launches, leverage, Polymarket bets, claims
The /agent/sign and /agent/submit endpoints return 403 for read-only keys.
IP Whitelisting
Set allowedIps on your API key to restrict usage to specific IPs. Requests from non-whitelisted IPs are rejected with 403.
- Empty array = all IPs allowed (default)
- Non-empty array = only listed IPs can use the key
Dedicated Agent Wallet
When building autonomous agents, create a separate Bankr account rather than using your personal wallet:
- Limited exposure — compromised key only exposes agent wallet funds
- Clear accounting — agent transactions isolated from personal activity
- Independent controls — apply stricter access controls without affecting personal use
- Easy revocation — disable agent account without disrupting primary wallet
Recommended Funding
| Chain | Gas Buffer | Trading Capital |
|---|---|---|
| Base | 0.01-0.05 ETH | As needed |
| Polygon | 5-10 MATIC | As needed |
| Ethereum | 0.05-0.1 ETH | As needed |
| Solana | 0.1-0.5 SOL | As needed |
Rate Limits
| Tier | Daily Limit |
|---|---|
| Standard | 100 messages/day |
| Bankr Club | 1,000 messages/day |
| Custom | Set per API key |
Reset window is 24 hours from first message (rolling), not midnight.
Key Management
- Store keys in environment variables (
BANKR_API_KEY,BANKR_LLM_KEY), never in source code - Add
~/.bankr/and.envto.gitignore - Rotate keys periodically at bankr.bot/api
- Revoke immediately if compromised
- Use separate keys for Agent API vs LLM Gateway if needed
Transaction Safety
- Test first — small amounts on Base/Polygon before scaling
- Verify recipients — double-check addresses before transfers
- Gas buffer — keep enough native tokens for gas
- Immediate execution —
/agent/submitexecutes with no confirmation prompt - Understand calldata — verify trusted source for arbitrary transactions
Pre-Deployment Checklist
- Use a dedicated agent wallet, not your personal account
- Fund with limited amounts appropriate to purpose
- Set read-only if agent only queries data
- Configure IP whitelisting for server-side agents
- Store keys in environment variables
- Test with small amounts first
- Implement error handling for rate limits (429) and access control (403)
Related skills
Solidity SecurityCatch and fix critical Solidity vulnerabilities like reentrancy before deploying smart contracts.13k38.4k
Extension Http OutcallsEnable their Internet Computer backend canister to make secure HTTP GET and POST requests to external APIs.10.3k
Okx Dapp DiscoveryCorrectly route Chinese-language DeFi and on-chain queries to the right protocol plugins inside an agent workflow.9.5k315Okx Growth CompetitionGuide users through OKX OnchainOS competition reward status checks, atomic claims, and post-win contact collection via the onchainos CLI.9.1k315Okx Agent Payments ProtocolLet their AI agent create and fulfill on-chain payment links without leaving the coding session.8.7k315
Query Token InfoGive your coding agent a Node CLI to search Binance tokens and pull metadata while you build crypto or DeFi features.6.1k946How it compares
Pick bankr dev - transfers over generic Web3 SDK skills when building inside Bankr Claude plugins and need built-in social handle and ENS recipient resolution.
FAQ
Which chains does bankr dev - transfers support?
bankr dev - transfers supports EVM chains Base, Polygon, Ethereum, and Unichain for native and ERC-20 tokens, plus Solana for SOL and SPL token transfers through the Bankr Agent API.
How does bankr dev - transfers resolve recipients?
bankr dev - transfers accepts wallet addresses, ENS names, and social handles for Twitter, Farcaster, and Telegram, resolving social usernames to linked on-chain wallet addresses before preparing the transfer.