Bankr Agent Error Handling
- 355 installs
- 80 repo stars
- Updated March 24, 2026
- bankrbot/claude-plugins
Bankr Agent error handling is an agent skill, version 1.0.0, that troubleshoots Bankr API authentication, rate limits, and job failures for developers integrating Bankr agents who need retries and user-safe error recover
About
Bankr Agent error handling is a version 1.0.0 agent skill from bankrbot/claude-plugins that diagnoses Bankr API authentication errors, missing BANKR_API_KEY configuration, HTTP 401 and 429 responses, x402 payment-required 402 errors, and on-chain job failures such as insufficient balance, token not found, slippage exceeded, and transaction reverted. The skill inspects error messages and status codes from Bankr /agent endpoints, then provides targeted remediation: API key setup with bk_ capability flags, environment restarts, balance checks, token metadata verification, and retry guidance with user-safe messaging instead of silent breakage. Developers reach for Bankr Agent error handling when Bankr agent calls fail with invalid API key errors, rate limits, tool timeouts, or job status failed responses during agent integration work. Bankr Agent error handling complements transaction-building skills by focusing on failure classification and recovery rather than constructing new on-chain payloads.
- retry with backoff
- tool failure fallbacks
- user-safe errors
- logging hooks
- graceful degradation
Bankr Agent Error Handling by the numbers
- 355 all-time installs (skills.sh)
- Ranked #2,111 of 16,546 AI & Agent Building 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-agent---error-handlingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 355 |
|---|---|
| repo stars | ★ 80 |
| Last updated | March 24, 2026 |
| Repository | bankrbot/claude-plugins ↗ |
How do you fix Bankr agent API errors?
Handle Bankr agent failures—API errors, tool timeouts, and invalid user input—with retries, fallbacks, and user-safe messages instead of silent breakage.
Who is it for?
Developers integrating Bankr /agent APIs who hit authentication, rate limit, x402 payment, or on-chain job failure errors.
Skip if: Developers building new Bankr transactions from scratch who should use Bankr x402 SDK transaction builder instead of error troubleshooting.
When should I use this skill?
User reports Bankr 401, invalid API key, BANKR_API_KEY not set, job failed, rate limit 429, or Bankr agent tool timeouts.
What you get
Classified error diagnoses, BANKR_API_KEY setup steps, retry guidance, and user-safe fallback messages for failed Bankr agent jobs.
- Error classification checklist
- API key setup instructions
- Retry and user messaging guidance
By the numbers
- Skill version 1.0.0
- Documents HTTP status codes 400, 401, 402, 429, and 500 with remediation actions
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
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10FAQ
Which Bankr errors does Bankr Agent error handling cover?
Bankr Agent error handling covers HTTP 401 unauthorized, 402 payment required, 429 rate limits, and job failures including insufficient balance, token not found, slippage exceeded, and transaction reverted states.
What API key does Bankr Agent error handling require?
Bankr Agent error handling expects BANKR_API_KEY set to a bk_ key with agentApiEnabled for /agent endpoints. The skill guides capability flag configuration and environment restart when keys are missing or invalid.