Bankr Dev Client Patterns
- 362 installs
- 80 repo stars
- Updated March 24, 2026
- bankrbot/claude-plugins
bankr dev - client patterns is a Claude skill that provides reusable bankr-client.ts TypeScript helpers and project templates for developers who need consistent Bankr Agent API polling, cancellation, and typed response h
About
bankr dev - client patterns is a version-1.0.0 Bankr developer skill that packages reusable TypeScript integration code for the Bankr Agent API. It includes a ready-made `bankr-client.ts` with typed helpers—`submitPrompt`, `getJobStatus`, `cancelJob`, `waitForCompletion`, and `execute`—plus curated scaffolding files such as `package.json`, `tsconfig.json`, `.env.example`, and `.gitignore`. Response types cover swaps, approvals, transfers, NFT flows, cross-chain swaps, and staking shapes so downstream handlers stay consistent. Environment variables `BANKR_API_KEY` and `BANKR_API_URL` drive configuration, and the polling strategy implements the documented submit-poll-complete workflow with progress callbacks. Developers reach for this skill when bootstrapping a trading bot, web service, dashboard, or CLI that wraps Bankr instead of rewriting HTTP and job polling boilerplate from scratch. Pair it with bankr dev api basics when you need endpoint documentation alongside copy-paste client code for production services.
- Bankr client SDK usage patterns
- Auth and session handling on client
- Consistent request and state flows
- UI-ready integration examples
- Safer consumer-side API calls
Bankr Dev Client Patterns by the numbers
- 362 all-time installs (skills.sh)
- Ranked #687 of 2,245 Frontend Development 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---client-patternsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 362 |
|---|---|
| repo stars | ★ 80 |
| Last updated | March 24, 2026 |
| Repository | bankrbot/claude-plugins ↗ |
How do you implement a typed Bankr API client in TypeScript?
Apply Bankr client integration patterns in apps and SDK consumers so UI layers call Bankr safely with consistent state, auth, and request handling.
Who is it for?
TypeScript developers bootstrapping Bankr Agent API clients who want standardized polling, cancellation, and response typing out of the box.
Skip if: Developers using only the x402 @bankr/sdk micropayment model without Agent API keys or async job workflows.
When should I use this skill?
User asks to implement bankr-client.ts, Bankr TypeScript patterns, or common Bankr project files.
What you get
bankr-client.ts module, project scaffold files, and typed async job polling integration code.
- bankr-client.ts
- Project scaffold files
- Typed response interfaces
By the numbers
- Version 1.0.0 skill with 5 core client helpers for Agent API jobs
- Scaffolds 4+ project files: package.json, tsconfig.json, .env.example, .gitignore
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
Vercel React Best PracticesAutomatically apply Vercel’s official React and Next.js performance rules during code generation and review.587k29.6kVercel Composition PatternsGenerate and refactor React components that stay maintainable as complexity grows without boolean prop explosion.267k29.6k
ShadcnAdd, compose, search, fix, and style production-grade React components directly from source without leaving their editor.257k120k
Develop UserscriptsCorrectly write, debug, and package userscripts for Tampermonkey and ScriptCat with proper metadata, GM APIs, and runtime decisions.224k72
Minimalist UiGenerate clean, editorial-style web interfaces with warm monochrome palettes, typographic hierarchy, bento grids and flat components that feel premium and utilita212k69.4kImage To CodeConvert high-fidelity design images into production-ready, visually accurate frontend code that avoids generic AI design pitfalls.177k69.4kHow it compares
Use client patterns for reusable TypeScript scaffolding; use api basics first when you only need endpoint documentation without code templates.
FAQ
What files does Bankr client patterns provide?
Bankr client patterns provides `bankr-client.ts` plus common project files including `package.json`, `tsconfig.json`, `.env.example`, and `.gitignore`, along with typed Bankr response models for DeFi operations.
Which helpers are in bankr-client.ts?
Bankr client patterns documents helpers `submitPrompt`, `getJobStatus`, `cancelJob`, `waitForCompletion`, and `execute`, implementing the Agent API submit-poll-complete flow with optional progress callbacks.