
Bankr Dev Nft Operations
- 378 installs
- 80 repo stars
- Updated March 24, 2026
- bankrbot/claude-plugins
bankr dev - nft operations is an agent skill that integrates Bankr NFT mint, transfer, listing, and metadata endpoints into application code for developers who ship marketplaces, games, or creator tools on Bankr.
About
bankr dev - nft operations is a Claude Code skill from bankrbot/claude-plugins that guides developers through wiring Bankr NFT API endpoints into production applications. The skill covers minting assets, transferring ownership, creating marketplace listings, and reading or updating token metadata so backend services and agent workflows can automate on-chain NFT actions safely. Developers reach for bankr dev - nft operations when building Bankr-powered marketplaces, in-game item systems, or creator dashboards that must call real NFT endpoints instead of stubbing blockchain behavior. The workflow assumes familiarity with Bankr API keys, wallet configuration, and standard REST or SDK patterns for authenticated requests. Use it during feature implementation when NFT lifecycle operations must be encoded, tested against Bankr sandboxes, and kept consistent with marketplace or game inventory rules.
- Programmatic NFT minting
- Transfer and listing APIs
- Metadata retrieval patterns
- Backend service integration
- Complements agent NFT skill
Bankr Dev Nft Operations by the numbers
- 378 all-time installs (skills.sh)
- Ranked #34 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---nft-operationsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 378 |
|---|---|
| repo stars | ★ 80 |
| Last updated | March 24, 2026 |
| Repository | bankrbot/claude-plugins ↗ |
How do you integrate Bankr NFT API endpoints?
Integrate NFT mint, transfer, listing, and metadata endpoints into application code for marketplaces, games, or creator tools powered by Bankr.
Who is it for?
Backend or full-stack developers adding Bankr NFT lifecycle features to marketplaces, games, or creator platforms.
Skip if: Teams that only need Bankr API key security guidance without any NFT endpoint integration work.
When should I use this skill?
The user asks to mint, transfer, list, or manage NFT metadata through the Bankr API in application code.
What you get
Application modules with Bankr NFT mint, transfer, listing, and metadata API integration plus tested request handlers
- NFT API integration modules
- Mint and transfer handlers
- Listing and metadata update code
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
FAQ
What NFT operations does bankr dev - nft operations cover?
bankr dev - nft operations covers Bankr API integration for minting NFTs, transferring ownership, creating marketplace listings, and reading or updating token metadata inside application code for marketplaces, games, and creator tools.
When should developers use bankr dev - nft operations?
Developers should use bankr dev - nft operations while building features that call Bankr NFT endpoints during implementation, before shipping marketplace, game, or creator workflows that depend on on-chain asset lifecycle actions.