Bankr Agent Arbitrary Transactions
- 363 installs
- 80 repo stars
- Updated March 24, 2026
- bankrbot/claude-plugins
bankr agent - arbitrary transactions is a Claude Code skill that submits raw EVM transactions with explicit calldata through the Bankr agent API for developers who need programmatic on-chain execution beyond preset swap
About
bankr agent - arbitrary transactions is a BankrBot Claude plugin skill (version 1.0.0) for submitting raw EVM transactions through the Bankr agent API. Developers pass a JSON object with `to`, `data`, `value`, and `chainId` fields; the skill validates address format, hex calldata, wei value strings, and supported chain IDs before execution. Supported chains include Ethereum (1), Polygon (137), Base (8453), and Unichain (130). The skill triggers on prompts like "submit a transaction", "execute calldata", or "send raw transaction" when building agent wallets, DeFi automations, or contract interactions. It complements Bankr safety guidance around `bk_...` API keys with capability flags such as `agentApiEnabled`. Reach for this skill when natural-language Bankr flows are insufficient and you already have encoded contract calldata ready to broadcast.
- Natural-language to transaction plans
- Plugin hooks for Bankr execution
- Safety checks before broadcast
- Supports varied transfer intents
Bankr Agent Arbitrary Transactions by the numbers
- 363 all-time installs (skills.sh)
- Ranked #2,094 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---arbitrary-transactionsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 363 |
|---|---|
| repo stars | ★ 80 |
| Last updated | March 24, 2026 |
| Repository | bankrbot/claude-plugins ↗ |
How do you submit raw EVM calldata via Bankr?
Let a Bankr Claude agent construct and submit arbitrary on-chain or custodial transactions from natural-language intents with guardrails.
Who is it for?
Backend or agent developers integrating Bankr who already have ABI-encoded calldata and need guarded raw transaction submission on four supported EVM chains.
Skip if: Developers who only need conversational token swaps or quotes should use Bankr token-trading skills instead of arbitrary calldata submission.
When should I use this skill?
User provides or requests submission of a JSON transaction with `to`, `data`, `value`, and `chainId` fields through Bankr.
What you get
Validated transaction JSON, chain ID confirmation, and a submitted on-chain transaction hash from the Bankr agent wallet.
- Validated transaction JSON
- Submitted transaction hash
By the numbers
- Supports 4 EVM chains: Ethereum (1), Polygon (137), Base (8453), Unichain (130)
- Requires 4 JSON fields: to, data, value, chainId
- Skill version 1.0.0 in BankrBot claude-plugins
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.246k10How it compares
Use when you have pre-encoded contract calldata; prefer Bankr token-trading skills for natural-language swaps and bridges.
FAQ
What JSON fields does Bankr arbitrary transaction submission require?
bankr agent - arbitrary transactions requires four fields: `to` (0x plus 40 hex chars), `data` (0x-prefixed calldata), `value` (wei as a string), and `chainId` (a supported numeric chain ID). Missing or malformed fields fail validation before the Bankr agent broadcasts the transa
Which chains support Bankr raw transaction submission?
bankr agent - arbitrary transactions supports four EVM chains: Ethereum (chainId 1), Polygon (137), Base (8453), and Unichain (130). Submitting an unsupported chainId returns an error; switch to one of these networks or use a different Bankr capability for other chains.