EDITORIAL ARTICLE
Bankr: Wallet APIs, Trading Agents and x402 Services
The takeaway: Bankr serves on-chain trading and agent development with direct wallet operations, a natural-language agent interface and paid API services. Wallet API, Agent API, Bankr Club and x402 Cloud have different functions and billing units; assess them separately.
Sources reviewed October 28, 2026. We did not register, call the APIs or transact.
Product and users
The Wallet API documentation describes direct balance queries, swaps, transfers, signing and broadcasting. The Agent API accepts requests an agent can interpret. The former suits developers who know the precise action; the latter supports natural-language orchestration. Their shared use of “agent” does not make them the same interface.
| Component | User | Main task |
|---|---|---|
| Wallet API | Developers requiring explicit wallet operations | Query, transfer, sign, broadcast and swap |
| Agent API | Developers who want an agent to interpret and execute requests | Submit a task for the agent to handle |
| Bankr Club | Subscribers using Bankr terminal and related features | Subscription quotas and capabilities |
| x402 Cloud | Providers selling paid endpoints | Host and charge for services per use |
One task, two routes
A research agent needs a paid data API. If the developer already knows the address and price, it could call a wallet payment interface. If the application needs a complex task interpreted first, it might orchestrate an Agent API request. Authorization, execution and failure handling differ.
This conceptual diagram does not establish that every Agent API request passes through the same Wallet API. Bankr documents different read and transaction permissions, and describes /wallet/x402-pay as requesting a paid URL with a maximum payment amount within its documented scope. Check current parameters and version in the API documentation.
Capabilities and boundaries
| Capability | Value | Questions to verify |
|---|---|---|
| Balance queries | View assets and positions | Data latency and supported networks |
| Signing and submission | Automate on-chain actions | Can the API key move all assets? |
| Swaps and transfers | Exchange and move assets | Quotes, slippage, failures and network fees |
| x402 payment | Pay supported endpoints | Per-request versus cumulative caps and retry handling |
| Agent requests | Execute natural-language tasks | Tool permissions and approvals |
The developer security documentation emphasizes credential protection. Permission toggles are not a complete budget system: a key that can sign or transfer may have far more authority than a single paid API request requires. Verify recipient restrictions, daily limits, revocation and approval separately.
Subscription and service fees are separate
At review, Bankr Club documentation listed $20 monthly or $198 annually, with different terminal and Agent API limits. This is not a uniform price for Wallet API or all transactions.
The x402 Cloud pricing page describes seller services: a free tier of up to 1,000 settlement requests monthly, Pro with a listed 5% platform fee and Enterprise with a listed 3% rate and contact requirement. Rules for exceeding the free allowance and special assets need current documentation and contract review. A platform fee is not a general payer wallet fee.
| Billing unit | Example | Does not mean |
|---|---|---|
| Club subscription | Terminal and agent service package | All API, transaction and network usage is free |
| x402 Cloud platform fee | Seller offers a paid endpoint | Every wallet transfer pays the same rate |
| On-chain or trading fees | Network and conversion costs | They are covered by a fixed subscription |
Coinbase and MetaMask compared
Coinbase emphasizes a developer entry point for controlled wallets and x402; MetaMask emphasizes user-configured on-chain rules and approvals; Bankr combines a direct wallet API, agent and seller monetization products. Compare the same $1 API purchase across permissions, signature, limits, failure recovery and total charges, and ask about custody and recovery.
Still to verify: key control, policy enforcement, regional eligibility, supported assets and chains, duplicate-payment protection and actual response to a leaked API credential. We conducted no API or payment tests.
API keys and real permissions
Bankr’s API key documentation describes account-level credentials with individually configurable permissions. It warns that new keys are read-write by default and recommends enabling only required endpoints, restricting IPs and using a separate account and wallet for production agents. A balance-only key has a different risk profile from one that can sign, broadcast and transfer.
An auditable rollout would prepare a test or separate wallet, create a minimally scoped key, configure available endpoints, read/write access, IP and recipient restrictions, validate with limited funds, and record requests and outcomes. Verify whether each product supports the limits needed. An address allowlist is not a substitute for understanding every contract call and signature message.
| Credential exposure | Possible actions exposed | Preparation |
|---|---|---|
| Read-only key | Account and asset information | Revoke the key and inspect access logs |
| Writable wallet key | Authorized wallet actions described in the docs | Disable the key, freeze relevant entry points and inspect pending transactions |
| Agent API key | Authorized agent tasks | Limit agent tools and keep secrets out of model context |
| Shared primary account | Difficult isolation | Use a separate wallet and limited funds in advance |
This is threat modeling, not a verified claim that each control covers every action. Ask specifically whether signing and broadcasting independently remain subject to recipient and amount rules.
Two illustrative price calculations
Bankr Club. At the listed $20 monthly or $198 annually, a full year at monthly rates is $240, or $42 more than the annual list price. This excludes transaction and network costs and other service usage. Agent API request and terminal-message limits are counted separately under the documentation.
x402 Cloud. If a service successfully settles 2,000 requests at $0.01 each, gross revenue is $20. If a contract explicitly applies a 5% platform fee to that entire billable amount, the fee could be $1. Whether it applies to all or only some requests must be confirmed from the invoice and plan. Different tokens and custom pricing have separate terms; this is not a fee promise. See x402 Cloud pricing.
The payers differ: Club subscribers pay for their use; x402 Cloud fees concern sellers providing paid endpoints. Do not call the seller’s 5% a buyer wallet fee.
A service provider’s full flow
A weather-data developer might configure and price an endpoint, publish it with x402 Cloud, have a buyer’s agent request and pay for the resource, then return data and review requests and income. The buyer’s wallet, balance, limits and retries may be controlled by another system. A seller’s revenue record does not necessarily prove the buyer consumed the response; both sides need a correlatable request or transaction identifier.
If payment succeeds but the backend times out, an immediate retry can pay twice and the seller may not know the first response failed. Before launch ask how receipts map to requests, whether safe retries are possible, who initiates refunds and whether limits cover concurrent calls. These are integration questions, not universal answers established by the documentation.
For periodic balance checks, a read-only wallet API can be easier to audit than a natural-language agent executing complex trades. Where tasks require market judgment, an Agent API provides richer interaction but needs separate evaluation of prompt injection, tool permissions, output review and emergency stops.