Bankr Dev Arbitrary Transactions
- 366 installs
- 80 repo stars
- Updated March 24, 2026
- bankrbot/claude-plugins
bankr dev - arbitrary transactions is a Claude skill that validates and submits raw EVM transaction JSON with to, data, value, and chainId fields through Bankr for developers who need custom contract calls beyond standar
About
bankr dev - arbitrary transactions is a version-1.0.0 Bankr developer skill for submitting raw EVM transactions with explicit calldata via the Bankr Agent API. It accepts JSON payloads specifying target contract address (`to` as 0x plus 40 hex chars), calldata (`data`), wei value (`value`), and numeric `chainId`, then validates formats before on-chain execution. Supported chain IDs documented in the skill include 1 (Ethereum), 137 (Polygon), 8453 (Base), and 130 (Unichain). Developers reach for this skill when automating arbitrary function calls, debugging calldata encoding, or executing pre-built transaction payloads that Bankr swap templates do not cover. Triggers include submit transaction, execute calldata, send raw transaction, or pasted JSON with to/data/value/chainId fields. The skill returns validation errors or revert diagnostics when submission fails. It complements bankr-agent-dev scaffolding skills when your integration needs direct contract calls rather than natural-language swap routing through 0x.
- Custom transaction construction
- Multi-step DeFi flows
- Contract call patterns
- Bankr execution routing
- Beyond template endpoints
Bankr Dev Arbitrary Transactions by the numbers
- 366 all-time installs (skills.sh)
- Ranked #37 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---arbitrary-transactionsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 366 |
|---|---|
| repo stars | ★ 80 |
| Last updated | March 24, 2026 |
| Repository | bankrbot/claude-plugins ↗ |
How do you submit raw EVM calldata through Bankr?
Construct and submit custom on-chain transactions through Bankr when standard templates do not cover complex swaps, contract calls, or multi-step DeFi flows.
Who is it for?
Backend developers executing custom EVM contract calls or debugging calldata through Bankr instead of hand-rolling RPC submit logic.
Skip if: Developers who only need natural-language token swaps without raw calldata or explicit chainId JSON payloads.
When should I use this skill?
User provides transaction JSON with to/data/value/chainId or asks to submit raw EVM calldata via Bankr.
What you get
Validated transaction JSON, submitted on-chain execution attempt, and revert or validation diagnostics.
- Submitted raw transaction
- Validation report
- Revert diagnostics
By the numbers
- Version 1.0.0 skill requiring 4 JSON fields: to, data, value, chainId
- Documents 4 supported EVM chain IDs: 1, 137, 8453, 130
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
Use arbitrary transactions for raw calldata JSON; use bankr agent token trading for natural-language swaps and bridges.
FAQ
What fields does Bankr arbitrary transactions require?
Bankr arbitrary transactions requires JSON with `to` (0x address), `data` (hex calldata), `value` (wei string), and numeric `chainId`. All four fields are validated before Bankr submits the raw EVM transaction.
Which chain IDs does Bankr arbitrary transactions support?
Bankr arbitrary transactions documents supported chain IDs 1 (Ethereum), 137 (Polygon), 8453 (Base), and 130 (Unichain). Unsupported chainId values fail validation before submission.