Bankr Dev Api Workflow
- 337 installs
- 80 repo stars
- Updated March 24, 2026
- bankrbot/claude-plugins
Bankr Dev - API Workflow is a Bankr agent skill that implements the asynchronous submit-poll-complete job pattern for POST /agent/prompt and GET /agent/job endpoints for developers building multi-chain DeFi integrations
About
Bankr Dev - API Workflow is a bankrbot/claude-plugins skill (version 1.0.0) documenting the Bankr Agent API asynchronous job lifecycle. The core pattern submits a natural-language prompt via POST /agent/prompt to receive jobId and threadId, polls GET /agent/job/{id} every 2 seconds, and processes terminal states completed, failed, or cancelled with response text, richData, and executed transactions. Polling best practices cap waits at 150 polls (5 minutes), track only new statusUpdates, and retry fetch failures with backoff. Conversation threads reuse threadId so follow-up prompts retain agent context. Error tables cover HTTP 400 prompt limits (10,000 characters), 403 when agentApiEnabled is false, and 429 rate limits with resetAt timestamps. TypeScript examples show waitForCompletion with progress callbacks and swap transaction handling. Pair with bankr-client-patterns for reusable client code and bankr-api-basics for endpoint reference.
- Bankr-specific API development workflow
- Agent and plugin integration patterns
- Structured backend implementation steps
- Consistent endpoint and service conventions
- Fits bankrbot/claude-plugins dev flow
Bankr Dev Api Workflow by the numbers
- 337 all-time installs (skills.sh)
- Ranked #1,193 of 4,347 Backend & APIs 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---api-workflowAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 337 |
|---|---|
| repo stars | ★ 80 |
| Last updated | March 24, 2026 |
| Repository | bankrbot/claude-plugins ↗ |
How do you implement Bankr Agent API job polling?
Use when building or extending Bankr API endpoints, wiring agent-to-service calls, or following the repo’s prescribed dev workflow for backend changes in bankrbot/claude-plugins.
Who is it for?
Backend developers building Bankr-powered trading bots or DeFi services who need the async job workflow with conversation threads and transaction results.
Skip if: Developers who only need synchronous Bankr sign-submit endpoints or API key security guidance without async job polling logic.
When should I use this skill?
A developer asks to implement Bankr job polling, handle POST /agent/prompt responses, process richData from completed jobs, or manage threadId conversations.
What you get
TypeScript polling client, job status handler, threadId conversation flow, and richData or transaction result processing.
- polling client functions
- job status handlers
- conversation thread integration
By the numbers
- Five documented job status states
- 2-second poll interval with 150-poll (5-minute) maximum
- 10,000-character maximum prompt length
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
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Use Bankr Dev - API Workflow for async natural-language agent jobs; use bankr-sign-submit-api when synchronous signed transaction submission is sufficient.
FAQ
What polling interval does Bankr Dev - API Workflow recommend?
Bankr Dev - API Workflow recommends polling GET /agent/job/{id} every 2 seconds, tracking only new statusUpdates, and stopping after 150 polls (about 5 minutes) or when status reaches completed, failed, or cancelled.
What fields appear on a completed Bankr job?
Completed Bankr jobs return response natural-language text, an optional richData array for charts or social cards, a transactions array of executed on-chain actions, plus completedAt and processingTime timestamps.