AI agents

Bankr wallets

Run Gifted Stock from a Bankr wallet.

A Bankr wallet (bankr.bot ↗) can run Gifted Stock through the same skill. Bankr holds the wallet's key and sends each step for you, so you never see the key. The plans are the same as for any wallet; what differs is how a step is sent and the Bankr settings that can refuse it.

Install the skill

In a Bankr agent:

install the giftedstock skill from https://github.com/alitiknazoglu/giftedstock-skill

Bankr's agent keeps the repo's files in /skills/giftedstock/, verify.mjs among them. The wallet is the Bankr wallet's EVM address (bankr whoami or the evm entry of GET https://api.bankr.bot/wallet/me), the same address on Base and Robinhood Chain.

Send each step

Send the steps as they are, in order, each once the one before succeeded:

FromHow
Bankr's Wallet APIPOST https://api.bankr.bot/wallet/submit with { "transaction": { "to", "data", "value", "chainId" }, "description", "waitForConfirmation": true } and your key in X-API-Key. value stays in wei. The key needs Wallet API access and must not be read-only.
Bankr's agentIt reads a raw transaction's value in whole ETH. First check the step's valueEth is exactly its value divided by 10^18 (viem's formatEther(value)). Stop if it is not. Then submit to, data and chainId with valueEth as the value.

From the repo, the example script sends through Bankr and adds the skill version to every body:

BANKR_API_KEY=… node examples/giftedstock.mjs buy '{"chain":"base","box":"normal","quantity":1,"payWith":"USDC"}' --bankr

It runs the same checks and dry run as with your own key. It sends BANKR_API_KEY to api.bankr.bot only.

Bankr's settings come first

Before the first plan and again before a gift or a send of boxes, the agent asks its user to check these at bankr.bot, Security. Neither the agent nor an API key can read or change them. Each refuses a step before it is sent:

SettingWhat it doesBankr's refusal
MFA (MFA & Sessions)Contract calls need MFA on: a passkey or an authenticator app.MFA required
Enable arbitrary contract calls (Transactions)Every step is a contract call. Turned on with a timer, it switches itself off when the timer ends.Arbitrary contract calls disabled
Daily and per-transaction limitsBankr prices the ETH a step sends in dollars. Tokens a step moves count as $0.DAILY_LIMIT_EXCEEDED, PER_TX_LIMIT_EXCEEDED
Allow NFT transfersA send of boxes and a gift's boxes may count, one a box.a 400 with no errorCode
Permitted recipientsWhile on, a step that sends ETH to a contract not on the list is refused.RECIPIENT_NOT_PERMITTED
Pause all transactionsNo step goes out while it is on.Wallet paused

The agent says which of these a plan meets (how much ETH it sends, how many boxes leave the wallet) and never suggests a value for any setting.

When something goes wrong

  • A Bankr refusal is final: Arbitrary contract calls disabled, Read-only API key, Restricted API key, Wallet paused, any errorCode or Transaction blocked by security scan. Stop and tell the user what Bankr said. Never change, split or resend a step another way to get it through.
  • A failure that carries a transactionHash was sent. Look the hash up before anything else; /wallet/submit takes no idempotency key, so never resend blind. A reverted step spent its gas: build the plan again.
  • Bankr does not pay gas for raw transactions: the wallet needs ETH on the chain.

Two things that look odd

  • Prizes under $1 are hidden. Bankr's portfolio leaves out tokens worth under $1 unless asked (showLowValueTokens=true on /wallet/portfolio or bankr wallet portfolio --low-value). A normal box's prize often is. GET /box/{chain}/{box}/{id} shows what a box paid.
  • A gift link's key is made and used where the agent runs, never by the Bankr wallet: viem's generatePrivateKey() makes it and its signTypedData signs a claim. In Bankr's agent, use its code sandbox with viem.
These steps are from skill 1.3.0. The full Bankr section is in SKILL.md; the endpoints are under Agent API.