How Do I Execute Direct Transactions via the Wallet API?

The Wallet API is for direct operations. The Agent API reads natural language and figures out what you want; the Wallet API skips the AI reasoning and executes exactly the transaction you specify — transfers, swaps, signing, and broadcasting — with low latency. Use it when you know precisely what you want on-chain.

What You Need

An API key with the Wallet & Agent API feature enabled, generated at bankr.bot/api-keys. A standard key returns 403 Forbidden on write operations.
Endpoints live at https://api.bankr.bot and cover transfers, swap quotes, swap execution, signing, and broadcasting. Same-chain EVM, Solana, and cross-chain swaps all route through the one swap endpoint. If you prefer the command line, the Bankr CLI wraps the same operations (e.g. bankr wallet submit tx).

Gotchas

Swaps are quote-then-execute. Price the swap first, then execute with the minBuyAmount the quote returned.
Slippage: slippageBps accepts 10–2000 (default 500 = 5%), but on the same-chain EVM aggregator path execution re-quotes with a tighter 2% clamp — a 2000 bps quote does not execute at 2000 bps there.
Tokenized stocks on Robinhood Chain require a passed location check — without one, swap execution returns 403. Quotes are not gated, so a successful quote is not clearance to execute.
Units: transfer values are in wei; swap amounts are human-readable (e.g. "0.5"). Use decimal chain IDs (8453 for Base, 1 for Ethereum).
Native gas tokens: pass the native sentinel 0xeeee…eeee (or the zero address) as the token.
403 on a swap can also mean the buy token was flagged by the security scan — not just a key permission issue.
Who broadcasts: hosted wallets sign and broadcast for you; self-custody integrations get transaction data back and sign/broadcast themselves (e.g. with viem or ethers.js).

For endpoints, parameters, and full request/response shapes, see the Wallet API reference on docs.bankr.bot.