
Bankr X402 Sdk Job Management
- 352 installs
- 80 repo stars
- Updated March 24, 2026
- bankrbot/claude-plugins
bankr x402 sdk - job management is an agent skill that manages x402-paid agent jobs with the Bankr SDK for developers who create, track, settle, and coordinate HTTP 402 micropayment work units.
About
bankr x402 sdk - job management is a Bankr plugin skill for orchestrating paid agent jobs through the x402 HTTP micropayment protocol. Developers use it to create work units, track job state, and settle payments via the Bankr SDK and related agent API endpoints documented alongside Bankr safety guidance. The companion Bankr Agent skill (version 1.0.0) covers API key capability flags such as agentApiEnabled and llmGatewayEnabled for securing agent access. Teams reach for this skill when building autonomous agents that must quote, execute, and settle x402-priced tasks rather than handling flat subscription billing.
- x402 micropayment job lifecycle
- Bankr SDK job APIs
- Agent task tracking and settlement
- HTTP 402 payment coordination
- Paid autonomous work orchestration
Bankr X402 Sdk Job Management by the numbers
- 352 all-time installs (skills.sh)
- Ranked #2,132 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-x402-sdk---job-managementAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 352 |
|---|---|
| repo stars | ★ 80 |
| Last updated | March 24, 2026 |
| Repository | bankrbot/claude-plugins ↗ |
How do you manage x402 paid agent jobs in code?
Manage x402-paid agent jobs with the Bankr SDK, including creating, tracking, settling, and coordinating HTTP 402 micropayment work units.
Who is it for?
Developers building Bankr-powered agents that must create, monitor, and settle x402 micropayment jobs through the official SDK.
Skip if: Applications without HTTP 402 micropayments or teams only needing read-only Bankr key rotation docs without job orchestration.
When should I use this skill?
User asks to create, track, settle, or coordinate x402-paid agent jobs, Bankr SDK work units, or HTTP 402 micropayments
What you get
Created job records, payment settlement status, and coordinated HTTP 402 work-unit lifecycle state
- Job creation records
- Settlement status
- Coordinated work-unit state
By the numbers
- Related Bankr Agent safety skill is version 1.0.0
- Bankr API keys use bk_ prefix with agentApiEnabled and llmGatewayEnabled capability flags
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
How it compares
Pick bankr x402 sdk - job management for paid agent job lifecycles; use generic payment skills when you do not need HTTP 402 micropayment semantics.
FAQ
What does bankr x402 sdk - job management handle?
bankr x402 sdk - job management covers creating, tracking, settling, and coordinating HTTP 402 micropayment agent jobs through the Bankr SDK rather than only documenting API key safety settings.
Which Bankr APIs relate to job management?
bankr x402 sdk - job management targets Bankr agent API endpoints and SDK calls for paid work units, while related Bankr docs define bk_ API keys with agentApiEnabled and llmGatewayEnabled capability flags.